Changeset 1290 for draft-ietf-httpbis/latest

Timestamp:

May 26, 2011, 9:06:18 PM (9 years ago)

Author:

mnot@…

Message:

Don't talk about "understanding" methods in invalidation; #289

Location:

draft-ietf-httpbis/latest

Files:

• p6-cache.html (modified) (2 diffs)
• p6-cache.xml (modified) (3 diffs)

draft-ietf-httpbis/latest/p6-cache.html

@@ -961 +961 @@
       </p>
       <h2 id="rfc.section.2.5"><a href="#rfc.section.2.5">2.5</a>&nbsp;<a id="invalidation.after.updates.or.deletions" href="#invalidation.after.updates.or.deletions">Request Methods that Invalidate</a></h2>
-      <p id="rfc.section.2.5.p.1">Because unsafe request methods (<a href="p2-semantics.html#safe.methods" title="Safe Methods">Section 7.1.1</a> of <a href="#Part2" id="rfc.xref.Part2.3"><cite title="HTTP/1.1, part 2: Message Semantics">[Part2]</cite></a>) have the potential for changing state on the origin server, intervening caches can use them to keep their contents up-to-date.
-      </p>
-      <p id="rfc.section.2.5.p.2">A cache <em class="bcp14">MUST</em> invalidate the effective Request URI (<a href="p1-messaging.html#effective.request.uri" title="Effective Request URI">Section 4.3</a> of <a href="#Part1" id="rfc.xref.Part1.13"><cite title="HTTP/1.1, part 1: URIs, Connections, and Message Parsing">[Part1]</cite></a>) as well as the URI(s) in the Location and Content-Location header fields (if present) when the following request methods
-         are received: 
-      </p>
-      <ul>
-         <li>PUT</li>
-         <li>DELETE</li>
-         <li>POST</li>
-      </ul>
+      <p id="rfc.section.2.5.p.1">Because unsafe request methods (<a href="p2-semantics.html#safe.methods" title="Safe Methods">Section 7.1.1</a> of <a href="#Part2" id="rfc.xref.Part2.3"><cite title="HTTP/1.1, part 2: Message Semantics">[Part2]</cite></a>) such as PUT, POST or DELETE have the potential for changing state on the origin server, intervening caches can use them
+         to keep their contents up-to-date.
+      </p>
+      <p id="rfc.section.2.5.p.2">A cache <em class="bcp14">MUST</em> invalidate the effective Request URI (<a href="p1-messaging.html#effective.request.uri" title="Effective Request URI">Section 4.3</a> of <a href="#Part1" id="rfc.xref.Part1.13"><cite title="HTTP/1.1, part 1: URIs, Connections, and Message Parsing">[Part1]</cite></a>) as well as the URI(s) in the Location and Content-Location header fields (if present) when requests with unsafe methods
+         are received.
+      </p>
       <p id="rfc.section.2.5.p.3">However, a cache <em class="bcp14">MUST NOT</em> invalidate a URI from a Location or Content-Location header field if the host part of that URI differs from the host part
          in the effective request URI (<a href="p1-messaging.html#effective.request.uri" title="Effective Request URI">Section 4.3</a> of <a href="#Part1" id="rfc.xref.Part1.14"><cite title="HTTP/1.1, part 1: URIs, Connections, and Message Parsing">[Part1]</cite></a>). This helps prevent denial of service attacks.
       </p>
-      <p id="rfc.section.2.5.p.4">A cache that passes through requests with methods it does not understand <em class="bcp14">SHOULD</em> invalidate the effective request URI (<a href="p1-messaging.html#effective.request.uri" title="Effective Request URI">Section 4.3</a> of <a href="#Part1" id="rfc.xref.Part1.15"><cite title="HTTP/1.1, part 1: URIs, Connections, and Message Parsing">[Part1]</cite></a>).
+      <p id="rfc.section.2.5.p.4">A cache <em class="bcp14">SHOULD</em> invalidate the effective request URI (<a href="p1-messaging.html#effective.request.uri" title="Effective Request URI">Section 4.3</a> of <a href="#Part1" id="rfc.xref.Part1.15"><cite title="HTTP/1.1, part 1: URIs, Connections, and Message Parsing">[Part1]</cite></a>) when passing through requests with methods whose safety is unknown.
       </p>
       <p id="rfc.section.2.5.p.5">Here, "invalidate" means that the cache will either remove all stored responses related to the effective request URI, or will
@@ -1967 +1963 @@
          <li> &lt;<a href="http://tools.ietf.org/wg/httpbis/trac/ticket/38">http://tools.ietf.org/wg/httpbis/trac/ticket/38</a>&gt;: "Mismatch Vary"
          </li>
+         <li> &lt;<a href="http://tools.ietf.org/wg/httpbis/trac/ticket/289">http://tools.ietf.org/wg/httpbis/trac/ticket/289</a>&gt;: "Proxies don't 'understand' methods"
+         </li>
       </ul>
       <h1 id="rfc.index"><a href="#rfc.index">Index</a></h1>

draft-ietf-httpbis/latest/p6-cache.xml

@@ -870 +870 @@
    title="Request Methods that Invalidate">
 <t>
-   Because unsafe request methods (&safe-methods;) have the potential for changing
-   state on the origin server, intervening caches can use them to keep their
-   contents up-to-date.
+   Because unsafe request methods (&safe-methods;) such as PUT, POST or DELETE
+   have the potential for changing state on the origin server, intervening
+   caches can use them to keep their contents up-to-date.
 </t>
 <t>
    A cache &MUST; invalidate the effective Request URI 
    (&effective-request-uri;) as well as the URI(s) in the Location
-   and Content-Location header fields (if present) when the following
-   request methods are received:
-   <list style="symbols">
-      <t>PUT</t>
-      <t>DELETE</t>
-      <t>POST</t>
-   </list>
+   and Content-Location header fields (if present) when requests with
+   unsafe methods are received.
 </t>
 <t>
@@ -892 +887 @@
 </t>
 <t>
-   A cache that passes through requests with methods it does not understand
-   &SHOULD; invalidate the effective request URI (&effective-request-uri;).
+         A cache &SHOULD; invalidate the effective request URI 
+         (&effective-request-uri;) when passing through requests with methods
+         whose safety is unknown.
 </t>
 <t>
@@ -2711 +2707 @@
             "Mismatch Vary"
           </t>
+          <t>
+                  <eref target="http://tools.ietf.org/wg/httpbis/trac/ticket/289"/>:
+                  "Proxies don't 'understand' methods"
+                </t>
   </list>
 </t>