Changeset 828

Timestamp:

Jun 7, 2010, 10:24:53 PM (9 years ago)

Author:

julian.reschke@…

Message:

add note about heuristic caching when query component is present (point out the history of it) (see #211)

Location:

draft-ietf-httpbis/latest

Files:

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

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

@@ -402 +402 @@
       <meta name="dct.creator" content="Reschke, J. F.">
       <meta name="dct.identifier" content="urn:ietf:id:draft-ietf-httpbis-p6-cache-latest">
-      <meta name="dct.issued" scheme="ISO8601" content="2010-06-07">
+      <meta name="dct.issued" scheme="ISO8601" content="2010-06-08">
       <meta name="dct.replaces" content="urn:ietf:rfc:2616">
       <meta name="dct.abstract" content="The Hypertext Transfer Protocol (HTTP) is an application-level protocol for distributed, collaborative, hypermedia information systems. This document is Part 6 of the seven-part specification that defines the protocol referred to as &#34;HTTP/1.1&#34; and, taken together, obsoletes RFC 2616. Part 6 defines requirements on HTTP caches and the associated header fields that control cache behavior or indicate cacheable response messages.">
@@ -428 +428 @@
             </tr>
             <tr>
-               <td class="left">Expires: December 9, 2010</td>
+               <td class="left">Expires: December 10, 2010</td>
                <td class="right">J. Mogul</td>
             </tr>
@@ -489 +489 @@
             <tr>
                <td class="left"></td>
-               <td class="right">June 7, 2010</td>
+               <td class="right">June 8, 2010</td>
             </tr>
          </tbody>
@@ -515 +515 @@
          in progress”.
       </p>
-      <p>This Internet-Draft will expire in December 9, 2010.</p>
+      <p>This Internet-Draft will expire in December 10, 2010.</p>
       <h1><a id="rfc.copyrightnotice" href="#rfc.copyrightnotice">Copyright Notice</a></h1>
       <p>Copyright © 2010 IETF Trust and the persons identified as the document authors. All rights reserved.</p>
@@ -839 +839 @@
       <p id="rfc.section.2.3.1.1.p.3">Also, if the response has a Last-Modified header (<a href="p4-conditional.html#header.last-modified" title="Last-Modified">Section 6.6</a> of <a href="#Part4" id="rfc.xref.Part4.1"><cite title="HTTP/1.1, part 4: Conditional Requests">[Part4]</cite></a>), the heuristic expiration value <em class="bcp14">SHOULD</em> be no more than some fraction of the interval since that time. A typical setting of this fraction might be 10%.
       </p>
-      <p id="rfc.section.2.3.1.1.p.4"> <span class="comment" id="REVIEW-query-string-heuristics">[<a href="#REVIEW-query-string-heuristics" class="smpl">REVIEW-query-string-heuristics</a>: took away HTTP/1.0 query string heuristic uncacheability.]</span> 
-      </p>
+      <div class="note" id="rfc.section.2.3.1.1.p.4"> 
+         <p> <b>Note:</b> RFC 2616 (<a href="#RFC2616" id="rfc.xref.RFC2616.1"><cite title="Hypertext Transfer Protocol -- HTTP/1.1">[RFC2616]</cite></a>, <a href="http://tools.ietf.org/html/rfc2616#section-13.9">Section 13.9</a>) required that caches do not calculate heuristic freshness for URLs with query components (i.e., those containing '?'). In
+            practice, this has not been widely implemented. Therefore, servers are encouraged to send explicit directives (e.g., Cache-Control:
+            no-cache) if they wish to preclude caching.
+         </p> 
+      </div>
       <h3 id="rfc.section.2.3.2"><a href="#rfc.section.2.3.2">2.3.2</a>&nbsp;<a id="age.calculations" href="#age.calculations">Calculating Age</a></h3>
       <p id="rfc.section.2.3.2.p.1">HTTP/1.1 uses the Age response-header to convey the estimated age of the response message when obtained from a cache. The
@@ -1759 +1763 @@
       <h2 id="rfc.section.C.1"><a href="#rfc.section.C.1">C.1</a>&nbsp;Since RFC2616
       </h2>
-      <p id="rfc.section.C.1.p.1">Extracted relevant partitions from <a href="#RFC2616" id="rfc.xref.RFC2616.1"><cite title="Hypertext Transfer Protocol -- HTTP/1.1">[RFC2616]</cite></a>.
+      <p id="rfc.section.C.1.p.1">Extracted relevant partitions from <a href="#RFC2616" id="rfc.xref.RFC2616.2"><cite title="Hypertext Transfer Protocol -- HTTP/1.1">[RFC2616]</cite></a>.
       </p>
       <h2 id="rfc.section.C.2"><a href="#rfc.section.C.2">C.2</a>&nbsp;Since draft-ietf-httpbis-p6-cache-00
@@ -1889 +1893 @@
          </li>
          <li> &lt;<a href="http://tools.ietf.org/wg/httpbis/trac/ticket/208">http://tools.ietf.org/wg/httpbis/trac/ticket/208</a>&gt;: "IANA registry for cache-control directives"
+         </li>
+         <li> &lt;<a href="http://tools.ietf.org/wg/httpbis/trac/ticket/211">http://tools.ietf.org/wg/httpbis/trac/ticket/211</a>&gt;: "Heuristic caching of URLs with query components"
          </li>
       </ul>
@@ -2082 +2088 @@
                   <li class="indline1"><em>RFC1305</em>&nbsp;&nbsp;<a class="iref" href="#rfc.xref.RFC1305.1">2.3.2</a>, <a class="iref" href="#RFC1305"><b>8.2</b></a></li>
                   <li class="indline1"><em>RFC2119</em>&nbsp;&nbsp;<a class="iref" href="#rfc.xref.RFC2119.1">1.3</a>, <a class="iref" href="#RFC2119"><b>8.1</b></a></li>
-                  <li class="indline1"><em>RFC2616</em>&nbsp;&nbsp;<a class="iref" href="#RFC2616"><b>8.2</b></a>, <a class="iref" href="#rfc.xref.RFC2616.1">C.1</a></li>
+                  <li class="indline1"><em>RFC2616</em>&nbsp;&nbsp;<a class="iref" href="#rfc.xref.RFC2616.1">2.3.1.1</a>, <a class="iref" href="#RFC2616"><b>8.2</b></a>, <a class="iref" href="#rfc.xref.RFC2616.2">C.1</a><ul class="ind">
+                        <li class="indline1"><em>Section 13.9</em>&nbsp;&nbsp;<a class="iref" href="#rfc.xref.RFC2616.1">2.3.1.1</a></li>
+                     </ul>
+                  </li>
                   <li class="indline1"><em>RFC3864</em>&nbsp;&nbsp;<a class="iref" href="#rfc.xref.RFC3864.1">5.2</a>, <a class="iref" href="#RFC3864"><b>8.2</b></a></li>
                   <li class="indline1"><em>RFC5226</em>&nbsp;&nbsp;<a class="iref" href="#rfc.xref.RFC5226.1">3.2.3</a>, <a class="iref" href="#RFC5226"><b>8.2</b></a><ul class="ind">

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

@@ -611 +611 @@
   since that time. A typical setting of this fraction might be 10%.
 </t>
-<t>
-  <cref anchor="REVIEW-query-string-heuristics">took away HTTP/1.0 query string heuristic uncacheability.</cref>
-</t>
+<x:note>
+  <t>
+    <x:h>Note:</x:h> RFC 2616 (<xref target="RFC2616" x:fmt="," x:sec="13.9"/>)
+    required that caches do not calculate heuristic freshness for URLs with
+    query components (i.e., those containing '?'). In practice, this has not
+    been widely implemented. Therefore, servers are encouraged to send explicit
+    directives (e.g., Cache-Control: no-cache) if they wish to preclude
+    caching.
+  </t>
+</x:note>
 </section>
 </section>
@@ -2474 +2481 @@
       "IANA registry for cache-control directives"
     </t>
+    <t>
+      <eref target="http://tools.ietf.org/wg/httpbis/trac/ticket/211" />:
+      "Heuristic caching of URLs with query components"
+    </t>
   </list>
 </t>