Please enable JavaScript.
Coggle requires JavaScript to display documents.
HTTP/HTTPS (Hypertext Transfer Protocol Secure (History (Were primarily…
HTTP/HTTPS
Hypertext Transfer Protocol
Secure
Protects against man-in-the-middle attacks
Bidirectional encryption of communications
Principal motivation for HTTPS is authentication of the accessed website and protection of the privacy and integrity of the exchanged data while in transit
Reasonable assurance of communication without interference
For secure communication over a computer network
History
Were primarily used for payment transactions on the WWW, e-mail and for sensitive transactions in corporate information systems
Since 2018is used more often by webusers than the original non-secure HTTP
To protect page authenticity on all types of websites
Extension of HTTP
HTTPS signals the browser to use an added encryption layer of SSL/TLS to protect the traffic
Creates a secure channel over an insecure network
Hypertext Transfer Protocol
The server returns a response message to the client
Provides resources such as HTML files
Performs other functions on behalf of the client,
The response contains completion status information about the request and may also contain requested content in its message body
Designed to permit intermediate network elements to improve or enable communications between clients and servers
Request–response protocol in the client–server computing model
High-traffic websites often benefit from web cache servers
Deliver content on behalf of upstream servers
To improve response time
Web browsers cache previously accessed web resources and reuse them
To reduce network traffic
Foundation of data communication for the WWW
History
CERN are credited with inventing the original HTTP
Berners-Lee first proposed the "WorldWideWeb" project in 1989
First documented version of HTTP was HTTP V0.9
1991 - v0.9
The first version of the protocol had only one method
GET
Which would request a page from a server
The response from the server was always an HTML page
1996 - v1.0
1997 - v1.1
2015 - v2.0
Application protocol for distributed, collaborative, and hypermedia information systems
Request methods
DELETE
Deletes the specified resource
TRACE
Echoes the received request so that a client can see what changes or additions have been made by intermediate servers
PUT
Requests that the enclosed entity be stored under the supplied URI
OPTIONS
Returns the HTTP methods that the server supports for the specified URL
POST
Requests that the server accepts the entity enclosed in the request as a new subordinate of the web resource identified by the URI
CONNECT
Converts the request connection to a transparent TCP/IP tunnel
HEAD
Asks for a response identical to that of a GET request, but without the response body
Useful for retrieving meta-information written in response headers
Without having to transport the entire content
PATCH
Method applies partial modifications to a resource
GET
Requests a representation of the specified resource
Should only retrieve data and should have no other effect