Ignore:
Timestamp:
Feb 20, 2012, 6:12:49 PM (8 years ago)
Author:
fielding@…
Message:

For consistency and readability, do not hyphenate "message body"
unless we are referring to the message-body ABNF rule.

File:
1 edited

Legend:

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

    r1543 r1544  
    416416        Content-Length header field is present in the response, its
    417417        value &MUST; match the actual number of octets transmitted in the
    418         message-body.
     418        message body.
    419419    </t>
    420420    <t>
     
    556556</t>
    557557<t>
    558    The combined response message-body consists of the union of partial
     558   The combined response message body consists of the union of partial
    559559   content ranges in the new response and each of the selected responses.
    560560   If the union consists of the entire range of the representation, then the
     
    786786<t>
    787787   Byte range specifications in HTTP apply to the sequence of bytes in
    788    the representation body (not necessarily the same as the message-body).
     788   the representation body (not necessarily the same as the message body).
    789789</t>
    790790<t anchor="rule.ranges-specifier">
     
    14091409   content of multiple ranges (a response to a request for multiple
    14101410   non-overlapping ranges), these are transmitted as a multipart
    1411    message-body (<xref target="RFC2046" x:fmt="," x:sec="5.1"/>). The media type for this purpose is called
     1411   message body (<xref target="RFC2046" x:fmt="," x:sec="5.1"/>). The media type for this purpose is called
    14121412   "multipart/byteranges".  The following is to be registered with IANA <xref target="RFC4288"/>.
    14131413</t>
Note: See TracChangeset for help on using the changeset viewer.