Ignore:
Timestamp:
Apr 6, 2011, 6:08:58 PM (9 years ago)
Author:
mnot@…
Message:

Identify methods that don't define semantics for request bodies, and warn for interop #251

File:
1 edited

Legend:

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

    r1257 r1261  
    458458<t>
    459459   New method definitions need to indicate whether they are safe (<xref
    460    target="safe.methods"/>) and whether they are idempotent (<xref
    461    target="idempotent.methods"/>). They also need to state whether they can be
    462    cached (&caching;); in particular what conditions a cache may store the
    463    response, and under what conditions such a stored response may be used to
    464    satisfy a subsequent request.
     460   target="safe.methods"/>), what semantics (if any) the request body has,
     461   and whether they are idempotent (<xref target="idempotent.methods"/>).
     462   They also need to state whether they can be cached (&caching;); in
     463   particular what conditions a cache may store the response, and under what
     464   conditions such a stored response may be used to satisfy a subsequent
     465   request.
    465466</t>
    466467</section>
     
    880881   completed without transferring data already held by the client.
    881882</t>
     883<t>Bodies on GET requests have no defined semantics. Note that sending a body
     884  on a GET request might cause some existing implementations to reject the
     885  request.
     886</t>
    882887<t>
    883888   The response to a GET request is cacheable and &MAY; be used to satisfy
     
    913918   or Last-Modified), then the cache &MUST; treat the cache entry as
    914919   stale.
     920</t>
     921<t>Bodies on HEAD requests have no defined semantics. Note that sending a body
     922  on a HEAD request might cause some existing implementations to reject the
     923  request.
    915924</t>
    916925</section>
     
    11141123   but the response does not include a representation.
    11151124</t>
     1125<t>Bodies on DELETE requests have no defined semantics. Note that sending a body
     1126  on a DELETE request might cause some existing implementations to reject the
     1127  request.
     1128</t>
    11161129<t>
    11171130   Responses to the DELETE method are not cacheable. If a DELETE request
     
    11881201
    11891202</artwork></figure>
     1203<t>Bodies on CONNECT requests have no defined semantics. Note that sending a body
     1204  on a CONNECT request might cause some existing implementations to reject the
     1205  request.
     1206</t>
    11901207<t>
    11911208   Like any other pipelined HTTP/1.1 request, data to be tunnel may be
     
    40864103      "untangle ABNFs for header fields"
    40874104    </t>
     4105    <t>
     4106      <eref target="http://tools.ietf.org/wg/httpbis/trac/ticket/251"/>:
     4107      "message-body in CONNECT request"
     4108    </t>
    40884109  </list>
    40894110</t>
Note: See TracChangeset for help on using the changeset viewer.