Changeset 1261 for draft-ietf-httpbis/latest/p2-semantics.xml

Timestamp:

07/04/11 01:08:58 (10 years ago)

Author:

mnot@…

Message:

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

File:

• draft-ietf-httpbis/latest/p2-semantics.xml (modified) (6 diffs)

draft-ietf-httpbis/latest/p2-semantics.xml

@@ -458 +458 @@
 <t>
    New method definitions need to indicate whether they are safe (<xref
-   target="safe.methods"/>) and whether they are idempotent (<xref
-   target="idempotent.methods"/>). They also need to state whether they can be
-   cached (&caching;); in particular what conditions a cache may store the
-   response, and under what conditions such a stored response may be used to
-   satisfy a subsequent request.
+   target="safe.methods"/>), what semantics (if any) the request body has,
+   and whether they are idempotent (<xref target="idempotent.methods"/>). 
+   They also need to state whether they can be cached (&caching;); in 
+   particular what conditions a cache may store the response, and under what 
+   conditions such a stored response may be used to satisfy a subsequent 
+   request.
 </t>
 </section>
@@ -880 +881 @@
    completed without transferring data already held by the client.
 </t>
+<t>Bodies on GET requests have no defined semantics. Note that sending a body
+  on a GET request might cause some existing implementations to reject the
+  request.
+</t>
 <t>
    The response to a GET request is cacheable and &MAY; be used to satisfy
@@ -913 +918 @@
    or Last-Modified), then the cache &MUST; treat the cache entry as
    stale.
+</t>
+<t>Bodies on HEAD requests have no defined semantics. Note that sending a body
+  on a HEAD request might cause some existing implementations to reject the
+  request.
 </t>
 </section>
@@ -1114 +1123 @@
    but the response does not include a representation.
 </t>
+<t>Bodies on DELETE requests have no defined semantics. Note that sending a body
+  on a DELETE request might cause some existing implementations to reject the
+  request.
+</t>
 <t>
    Responses to the DELETE method are not cacheable. If a DELETE request 
@@ -1188 +1201 @@
 
 </artwork></figure>
+<t>Bodies on CONNECT requests have no defined semantics. Note that sending a body
+  on a CONNECT request might cause some existing implementations to reject the
+  request.
+</t>
 <t>
    Like any other pipelined HTTP/1.1 request, data to be tunnel may be
@@ -4086 +4103 @@
       "untangle ABNFs for header fields"
     </t>
+    <t>
+      <eref target="http://tools.ietf.org/wg/httpbis/trac/ticket/251"/>:
+      "message-body in CONNECT request"
+    </t>
   </list>
 </t>