Changeset 951

Timestamp:

27/07/10 15:31:13 (12 years ago)

Author:

julian.reschke@…

Message:

Note we undid change in [943] relating to issue 235 (see #235), regen HTML.

Location:

draft-ietf-httpbis/latest

Files:

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

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

@@ -939 +939 @@
       <p id="rfc.section.2.5.p.1">Because unsafe 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">In a succesful exchange (<a href="p2-semantics.html#status.2xx" title="Successful 2xx">Section 8.2</a> of <a href="#Part2" id="rfc.xref.Part2.4"><cite title="HTTP/1.1, part 2: Message Semantics">[Part2]</cite></a>), the following HTTP methods <em class="bcp14">MUST</em> cause a cache to 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 headers (if present): 
+      <p id="rfc.section.2.5.p.2">The following HTTP methods <em class="bcp14">MUST</em> cause a cache to 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 headers (if present): 
       </p>
       <ul>
@@ -1905 +1905 @@
          <li> &lt;<a href="http://tools.ietf.org/wg/httpbis/trac/ticket/223">http://tools.ietf.org/wg/httpbis/trac/ticket/223</a>&gt;: "Allowing heuristic caching for new status codes"
          </li>
-         <li> &lt;<a href="http://tools.ietf.org/wg/httpbis/trac/ticket/235">http://tools.ietf.org/wg/httpbis/trac/ticket/235</a>&gt;: "Cache Invalidation only happens upon successful responses"
-         </li>
          <li>Clean up TODOs and prose in "Combining Responses."</li>
       </ul>
@@ -2057 +2055 @@
                      </ul>
                   </li>
-                  <li class="indline1"><em>Part2</em>&nbsp;&nbsp;<a class="iref" href="#rfc.xref.Part2.1">2.2</a>, <a class="iref" href="#rfc.xref.Part2.2">2.3.1.1</a>, <a class="iref" href="#rfc.xref.Part2.3">2.5</a>, <a class="iref" href="#rfc.xref.Part2.4">2.5</a>, <a class="iref" href="#Part2"><b>8.1</b></a><ul class="ind">
+                  <li class="indline1"><em>Part2</em>&nbsp;&nbsp;<a class="iref" href="#rfc.xref.Part2.1">2.2</a>, <a class="iref" href="#rfc.xref.Part2.2">2.3.1.1</a>, <a class="iref" href="#rfc.xref.Part2.3">2.5</a>, <a class="iref" href="#Part2"><b>8.1</b></a><ul class="ind">
                         <li class="indline1"><em>Section 7.1.1</em>&nbsp;&nbsp;<a class="iref" href="#rfc.xref.Part2.1">2.2</a>, <a class="iref" href="#rfc.xref.Part2.3">2.5</a></li>
                         <li class="indline1"><em>Section 8</em>&nbsp;&nbsp;<a class="iref" href="#rfc.xref.Part2.2">2.3.1.1</a></li>
-                        <li class="indline1"><em>Section 8.2</em>&nbsp;&nbsp;<a class="iref" href="#rfc.xref.Part2.4">2.5</a></li>
                      </ul>
                   </li>

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

@@ -2620 +2620 @@
     </t>
     <t>
-      <eref target="http://tools.ietf.org/wg/httpbis/trac/ticket/235"/>:
-      "Cache Invalidation only happens upon successful responses"
-    </t>
-    <t>
       Clean up TODOs and prose in "Combining Responses."
     </t>