HTTP Entity: Difference between revisions
Jump to navigation
Jump to search
| Line 17: | Line 17: | ||
* [[Entity HTTP Header Fields]] | * [[Entity HTTP Header Fields]] | ||
=Entity | =Entity Body= | ||
{{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 [[#HTTP_Entity_Header_Fields|entity-header fields]]. | |||
Revision as of 03:59, 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.
Subjects
Entity Body
The entity body (if any) sent with the HTTP request/response is in a format and encoding defined by the entity-header fields.