HTTP Entity: Difference between revisions
Jump to navigation
Jump to search
No edit summary |
|||
Line 6: | Line 6: | ||
* [[HTTP#Subjects|HTTP]] | * [[HTTP#Subjects|HTTP]] | ||
=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= | =Subjects= |
Revision as of 03:58, 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.