HTTP messages in HTTP messages

1. Composition of the header of the request message and the response message

Request Line:

Contains the requested method, request URI, and HTTP version.

Status line:

Contains status codes, reason phrases, and HTTP versions of the corresponding results.

Header field:

General header, request header, response header and entity header.

Other:

Headers (cookies, etc.) that are not defined in the RfC that contain HTTP.

2. Encoding increases transfer rate

Content encoding for compressed transmission: gzip,compress,deflate,identity.

The chunked transmission encoding of the split send.

3. Multi-part object collection for sending multiple data

Uses the MIME (Multipurpose Internet Mail Extension) mechanism to allow messages to handle multiple different types of data, such as text, pictures, and videos.

4. Get the scope request for partial content

For a range request, the response returns a response message with a status code of 206 Partial content, and if the server side is unable to respond to a range request, a status code of OK and full entity content is returned.

5. Content negotiation returns the most appropriate content

The content negotiation mechanism refers to the client and server to negotiate the content of the response, and then provides the most appropriate resources for the client.

Content negotiation technologies include:

A. Server-driven negotiation: content negotiation by the server side. With the request of the first field as a reference, on the server side automatic processing;

B. Client-driven negotiation: how content is negotiated by the client. The user selects manually from the list of selectable options displayed in the browser;

C. Transparent negotiation: A combination of server-driven and client-driven.