Ignore:
Timestamp:
Jul 27, 2010, 8:46:23 PM (9 years ago)
Author:
fielding@…
Message:

(editorial) move sentence down to keep paragraph topics simple.

File:
1 edited

Legend:

Unmodified
Added
Removed
  • draft-ietf-httpbis/latest/p1-messaging.xml

    r957 r958  
    12501250<t>
    12511251   The message-body (if any) of an HTTP message is used to carry the
    1252    payload body associated with the request or response. The message-body
    1253    differs from the payload body only when a transfer-coding has been
    1254    applied, as indicated by the Transfer-Encoding header field (<xref target="header.transfer-encoding"/>).
     1252   payload body associated with the request or response.
    12551253</t>
    12561254<figure><artwork type="abnf2616"><iref primary="true" item="Grammar" subitem="message-body"/>
     
    12581256</artwork></figure>
    12591257<t>
    1260    When one or more transfer-codings are applied to a payload body,
    1261    usually for the sake of stream-delimiting or data compression, the
    1262    Transfer-Encoding header field &MUST; be provided with the list of
     1258   The message-body differs from the payload body only when a transfer-coding
     1259   has been applied, as indicated by the Transfer-Encoding header field (<xref target="header.transfer-encoding"/>).  When one or more transfer-codings are
     1260   applied to a payload in order to form the message-body, the
     1261   Transfer-Encoding header field &MUST; contain the list of
    12631262   transfer-codings applied. Transfer-Encoding is a property of the message,
    12641263   not of the payload, and thus &MAY; be added or removed by any implementation
Note: See TracChangeset for help on using the changeset viewer.