Ignore:
Timestamp:
Jul 16, 2010, 10:56:53 PM (9 years ago)
Author:
fielding@…
Message:

Changed message-body ABNF to be *OCTET. Specifying the actual
number of octets will have to be done in prose.

Moved mistitled "Message Length" section into the Message Body
section, since it only explains how many octets are in the body.
Deleted useless "Entity Length" section and transfer-length term.

Addresses #28: Connection closing

Removed redundant mention of terminating by connection close
and rewrote explanation so that it doesn't self-contradict.

Addresses #90: Delimiting messages with multipart/byteranges

Removed message-delimiting paragraphs of multipart/byteranges
from p1 and p3.

Addresses #95: Handling multiple Content-Length headers

Added requirements for what to do if multiple or invalid
Content-Length is received.

Rephrased requirements for Transfer-Encoding to only apply
when a transfer-coding is present. Clarify that Transfer-Encoding
overrides Content-Length and treat receiving both as an error.
Clarify that only the chunked transfer-coding can delimit a
message (the original design allowed other self-descriptive
encodings, but that was abandoned in 2616).

Addresses #109: Clarify entity / representation / variant terminology

Entity-body terminology changed to payload in order to clarify that
it is what gets packaged (as a message-body) into a message,
allowing us to (eventually) distinguish between messages containing
whole representations and messages containing only partial
representations. Reduce use of the same terms for other things
(e.g., in explanation of dates).

File:
1 edited

Legend:

Unmodified
Added
Removed
  • draft-ietf-httpbis/latest/p5-range.xml

    r848 r852  
    357357        Content-Type including Content-Range fields for each part. If a
    358358        Content-Length header field is present in the response, its
    359         value &MUST; match the actual number of OCTETs transmitted in the
     359        value &MUST; match the actual number of octets transmitted in the
    360360        message-body.
    361361    </t>
Note: See TracChangeset for help on using the changeset viewer.