HTTP Entity Header Content-Length: Difference between revisions

From NovaOrdis Knowledge Base
Jump to navigation Jump to search
Line 12: Line 12:
The Content-Length indicates the size of the entity body sent, sent to the recipient, in bytes. In the case of the HEAD method, the size of the entity body that would have been sent had the request been a GET. Note that the meaning of this field is significantly different from the corresponding definition in MIME, where it is an optional field used within the "message/external-body" content-type. In HTTP, it must be sent whenever the message's length can be determined prior to being transferred, unless this is prohibited by the rules in section 4.4.
The Content-Length indicates the size of the entity body sent, sent to the recipient, in bytes. In the case of the HEAD method, the size of the entity body that would have been sent had the request been a GET. Note that the meaning of this field is significantly different from the corresponding definition in MIME, where it is an optional field used within the "message/external-body" content-type. In HTTP, it must be sent whenever the message's length can be determined prior to being transferred, unless this is prohibited by the rules in section 4.4.


<font color=red>Process and reconcile "Message Length" </font>
<font color=red>Process and reconcile "Message Length" https://www.w3.org/Protocols/rfc2616/rfc2616-sec4.html#sec4.4</font>

Revision as of 07:43, 6 January 2017

External

Internal

Overview

The Content-Length indicates the size of the entity body sent, sent to the recipient, in bytes. In the case of the HEAD method, the size of the entity body that would have been sent had the request been a GET. Note that the meaning of this field is significantly different from the corresponding definition in MIME, where it is an optional field used within the "message/external-body" content-type. In HTTP, it must be sent whenever the message's length can be determined prior to being transferred, unless this is prohibited by the rules in section 4.4.

Process and reconcile "Message Length" https://www.w3.org/Protocols/rfc2616/rfc2616-sec4.html#sec4.4