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/p2-semantics.xml

    r1539 r1544  
    482482<t>
    483483   Due to the parsing rules defined in &message-body;, definitions of HTTP
    484    methods cannot prohibit the presence of a message-body on either the request
     484   methods cannot prohibit the presence of a message body on either the request
    485485   or the response message (with responses to HEAD requests being the single
    486486   exception). Definitions of new methods cannot change this rule, but they can
     
    813813</t>
    814814<t>
    815    A representation body is only present in a message when a message-body is
     815   A representation body is only present in a message when a message body is
    816816   present, as described in &message-body;. The representation body is obtained
    817    from the message-body by decoding any Transfer-Encoding that might
     817   from the message body by decoding any Transfer-Encoding that might
    818818   have been applied to ensure safe and proper transfer of the message.
    819819</t>
     
    929929</t>
    930930<t>
    931    If the OPTIONS request includes a message-body (as indicated by the
     931   If the OPTIONS request includes a message body (as indicated by the
    932932   presence of Content-Length or Transfer-Encoding), then the media type
    933933   &MUST; be indicated by a Content-Type field. Although this
     
    10261026<t>
    10271027   The HEAD method is identical to GET except that the server &MUST-NOT;
    1028    return a message-body in the response. The metadata contained
     1028   return a message body in the response. The metadata contained
    10291029   in the HTTP header fields in response to a HEAD request &SHOULD; be identical
    10301030   to the information sent in response to a GET request. This method can
     
    12711271   of the request message. The final recipient of the request
    12721272   &SHOULD; reflect the message received back to the client as the
    1273    message-body of a 200 (OK) response. The final recipient is either the
     1273   message body of a 200 (OK) response. The final recipient is either the
    12741274   origin server or the first proxy to receive a Max-Forwards
    12751275   value of zero (0) in the request (see <xref target="header.max-forwards"/>).
    1276    A TRACE request &MUST-NOT; include a message-body.
     1276   A TRACE request &MUST-NOT; include a message body.
    12771277</t>
    12781278<t>
     
    12871287<t>
    12881288   If the request is valid, the response &SHOULD; have a Content-Type of
    1289    "message/http" (see &media-type-message-http;) and contain a message-body
     1289   "message/http" (see &media-type-message-http;) and contain a message body
    12901290   that encloses a copy of the entire request message.
    12911291   Responses to the TRACE method are not cacheable.
     
    14871487    </t>
    14881488    <t hangText="HEAD">
    1489       the same representation as GET, except without the message-body;
     1489      the same representation as GET, except without the message body;
    14901490    </t>
    14911491    <t hangText="POST">
     
    16041604</t>
    16051605<t>
    1606    The 204 response &MUST-NOT; include a message-body, and thus is always
     1606   The 204 response &MUST-NOT; include a message body, and thus is always
    16071607   terminated by the first empty line after the header fields.
    16081608</t>
     
    16201620</t>
    16211621<t>   
    1622    The message-body included with the response &MUST; be empty. Note that
     1622   The message body included with the response &MUST; be empty. Note that
    16231623   receivers still need to parse the response according to the algorithm defined
    16241624   in &message-body;.
     
    20492049   The server refuses to accept the request without a defined Content-Length.
    20502050   The client &MAY; repeat the request if it adds a valid
    2051    Content-Length header field containing the length of the message-body
     2051   Content-Length header field containing the length of the message body
    20522052   in the request message.
    20532053</t>
     
    45864586    <t>
    45874587      <eref target="http://tools.ietf.org/wg/httpbis/trac/ticket/251"/>:
    4588       "message-body in CONNECT request"
     4588      "message body in CONNECT request"
    45894589    </t>
    45904590  </list>
Note: See TracChangeset for help on using the changeset viewer.