HTTP Entity: Difference between revisions
Jump to navigation
Jump to search
| Line 21: | Line 21: | ||
{{External|https://www.w3.org/Protocols/rfc2616/rfc2616-sec7.html#sec7.2}} | {{External|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 [[ | 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:03, 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.