HTTP Entity: Difference between revisions
| Line 19: | Line 19: | ||
=Entity Body= | =Entity Body= | ||
{{External|https://www.w3.org/Protocols/rfc2616/rfc2616-sec7.html#sec7.2}} | {{External|Message Body: https://www.w3.org/Protocols/rfc2616/rfc2616-sec4.html#sec4.3}} | ||
{{External|Entity Body: https://www.w3.org/Protocols/rfc2616/rfc2616-sec7.html#sec7.2}} | |||
The entity body (if any) sent with the HTTP request/response is in a format and encoding defined by the [[Entity HTTP Header Fields|Entity Headers]]. | The entity body (if any) sent with the HTTP request/response is in a format and encoding defined by the [[Entity HTTP Header Fields|Entity Headers]]. | ||
Revision as of 04:19, 6 January 2017
External
- RFC 2616 Entity https://www.w3.org/Protocols/rfc2616/rfc2616-sec7.html
Internal
Overview
The HTTP request/response may optionally transfer an entity. An entity consists of entity header fields, which are grouped together with the other headers of the request or response, and an entity-body.
The HTTP protocol requires that requests/response which include a body either use chunked transfer encoding or send a Content-Length request header.
Entity Headers
Entity Body
The entity body (if any) sent with the HTTP request/response is in a format and encoding defined by the Entity Headers.
Entity Body Type
When an entity body is included with a message, the data type of that body is determined from the entity header fields Content-Type and Content-Encoding. These define a two-layer, ordered encoding model:
entity-body = Content-Encoding(Content-Type(data))
Entity Body Length
7.2.2 Entity Length
The length of a entity is the length of the message body before any transfer encodings have been applied.