Ignore:
Timestamp:
Jan 13, 2013, 1:28:45 AM (7 years ago)
Author:
fielding@…
Message:

reorder paragraphs in method descriptions for consistency; note that CONNECT is not cacheable; partly addresses #426

File:
1 edited

Legend:

Unmodified
Added
Removed
  • draft-ietf-httpbis/latest/p2-semantics.xml

    r2117 r2118  
    12741274</t>
    12751275<t>
     1276   A payload within a GET request message has no defined semantics;
     1277   sending a payload body on a GET request might cause some existing
     1278   implementations to reject the request.
     1279</t>
     1280<t>
    12761281   The response to a GET request is cacheable; a cache &MAY; use it to satisfy
    12771282   subsequent GET and HEAD requests unless otherwise indicated by the
    12781283   Cache-Control header field (&header-cache-control;).
    1279 </t>
    1280 <t>
    1281    A payload within a GET request message has no defined semantics;
    1282    sending a payload body on a GET request might cause some existing
    1283    implementations to reject the request.
    12841284</t>
    12851285</section>
     
    13031303</t>
    13041304<t>
     1305   A payload within a HEAD request message has no defined semantics;
     1306   sending a payload body on a HEAD request might cause some existing
     1307   implementations to reject the request.
     1308</t>
     1309<t>
    13051310   The response to a HEAD request is cacheable; a cache &MAY; use it to
    13061311   satisfy subsequent HEAD requests unless otherwise indicated by the
    13071312   Cache-Control header field (&header-cache-control;). A HEAD response might
    13081313   also have an effect on previously cached responses to GET; see &p6-head;.
    1309 </t>
    1310 <t>
    1311    A payload within a HEAD request message has no defined semantics;
    1312    sending a payload body on a HEAD request might cause some existing
    1313    implementations to reject the request.
    13141314</t>
    13151315</section>
     
    16281628</artwork></figure>
    16291629<t>
    1630    A payload within a CONNECT request message has no defined semantics;
    1631    sending a payload body on a CONNECT request might cause some existing
    1632    implementations to reject the request.
    1633 </t>
    1634 <t>
    16351630   When a tunnel intermediary detects that either side has closed its
    16361631   connection, any outstanding data that came from that side will first be
     
    16381633   connections. If there is outstanding data left undelivered,
    16391634   that data will be discarded.
     1635</t>
     1636<t>
     1637   A payload within a CONNECT request message has no defined semantics;
     1638   sending a payload body on a CONNECT request might cause some existing
     1639   implementations to reject the request.
     1640</t>
     1641<t>
     1642   Responses to the CONNECT method are not cacheable.
    16401643</t>
    16411644</section>
     
    16531656   determine the options and/or requirements associated with a resource,
    16541657   or the capabilities of a server, without implying a resource action.
    1655 </t>
    1656 <t>
    1657    Responses to the OPTIONS method are not cacheable.
    1658 </t>
    1659 <t>
    1660    A client that generates an OPTIONS request containing a payload body
    1661    &MUST; send a valid <x:ref>Content-Type</x:ref> header field describing
    1662    the representation media type. Although this specification does not define
    1663    any use for such a payload, future extensions to HTTP might use the OPTIONS
    1664    body to make more detailed queries about the target resource.
    16651658</t>
    16661659<t>
     
    16971690   was received with a Max-Forwards field.
    16981691</t>
     1692<t>
     1693   A client that generates an OPTIONS request containing a payload body
     1694   &MUST; send a valid <x:ref>Content-Type</x:ref> header field describing
     1695   the representation media type. Although this specification does not define
     1696   any use for such a payload, future extensions to HTTP might use the OPTIONS
     1697   body to make more detailed queries about the target resource.
     1698</t>
     1699<t>
     1700   Responses to the OPTIONS method are not cacheable.
     1701</t>
    16991702</section>
    17001703
     
    17161719</t>
    17171720<t>
    1718    A client &MUST-NOT; send a message body in a TRACE request.
    1719 </t>
    1720 <t>
    17211721   A client &MUST-NOT; send header fields in a TRACE request containing
    17221722   sensitive data that might be disclosed by the response. For example, it
     
    17341734   limit the length of the request chain, which is useful for testing a chain
    17351735   of proxies forwarding messages in an infinite loop.
     1736</t>
     1737<t>
     1738   A client &MUST-NOT; send a message body in a TRACE request.
    17361739</t>
    17371740<t>
Note: See TracChangeset for help on using the changeset viewer.