HTTP Knowledge Popularity series: HTTP messages within HTTP messages

1. HTTP messages are information that is used for HTTP protocol interactions.
2. Structure of request message and response message:
   1. Request Line
   2. Status line
   3. Header field
      1. General Header
      2. Request Header
      3. Response header
      4. Entity Header
   4. Other
3. Several ways to encode common content
   1. Gzip (GNU Zip)
   2. Compress (standard compression of UNIX systems)
   3. Deflate (zlib)
   4. Identity (not coded)
4. The function of the block of the entity body becomes the chunked transmission code, each chunk is marked with hexadecimal to the size of the block, and the last piece of the entity body uses "0 (CR+LF)"
5. Gets the scope request for a partial content that requires the specified downloaded entity scope for this function to be implemented. If the server is unable to respond to the request scope, a status code of OK and full entity content is returned.
6. 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 serves as a benchmark for determining the language, character set, and encoding of the response resource.

HTTP Knowledge Popularity series: HTTP messages within HTTP messages