Changeset 828
- Timestamp:
- 08/06/10 05:24:53 (12 years ago)
- Location:
- draft-ietf-httpbis/latest
- Files:
-
- 2 edited
Legend:
- Unmodified
- Added
- Removed
-
draft-ietf-httpbis/latest/p6-cache.html
r827 r828 402 402 <meta name="dct.creator" content="Reschke, J. F."> 403 403 <meta name="dct.identifier" content="urn:ietf:id:draft-ietf-httpbis-p6-cache-latest"> 404 <meta name="dct.issued" scheme="ISO8601" content="2010-06-0 7">404 <meta name="dct.issued" scheme="ISO8601" content="2010-06-08"> 405 405 <meta name="dct.replaces" content="urn:ietf:rfc:2616"> 406 406 <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 "HTTP/1.1" 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> 429 429 <tr> 430 <td class="left">Expires: December 9, 2010</td>430 <td class="left">Expires: December 10, 2010</td> 431 431 <td class="right">J. Mogul</td> 432 432 </tr> … … 489 489 <tr> 490 490 <td class="left"></td> 491 <td class="right">June 7, 2010</td>491 <td class="right">June 8, 2010</td> 492 492 </tr> 493 493 </tbody> … … 515 515 in progress”. 516 516 </p> 517 <p>This Internet-Draft will expire in December 9, 2010.</p>517 <p>This Internet-Draft will expire in December 10, 2010.</p> 518 518 <h1><a id="rfc.copyrightnotice" href="#rfc.copyrightnotice">Copyright Notice</a></h1> 519 519 <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%. 840 840 </p> 841 <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> 842 </p> 841 <div class="note" id="rfc.section.2.3.1.1.p.4"> 842 <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 843 practice, this has not been widely implemented. Therefore, servers are encouraged to send explicit directives (e.g., Cache-Control: 844 no-cache) if they wish to preclude caching. 845 </p> 846 </div> 843 847 <h3 id="rfc.section.2.3.2"><a href="#rfc.section.2.3.2">2.3.2</a> <a id="age.calculations" href="#age.calculations">Calculating Age</a></h3> 844 848 <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> Since RFC2616 1760 1764 </h2> 1761 <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>.1765 <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>. 1762 1766 </p> 1763 1767 <h2 id="rfc.section.C.2"><a href="#rfc.section.C.2">C.2</a> Since draft-ietf-httpbis-p6-cache-00 … … 1889 1893 </li> 1890 1894 <li> <<a href="http://tools.ietf.org/wg/httpbis/trac/ticket/208">http://tools.ietf.org/wg/httpbis/trac/ticket/208</a>>: "IANA registry for cache-control directives" 1895 </li> 1896 <li> <<a href="http://tools.ietf.org/wg/httpbis/trac/ticket/211">http://tools.ietf.org/wg/httpbis/trac/ticket/211</a>>: "Heuristic caching of URLs with query components" 1891 1897 </li> 1892 1898 </ul> … … 2082 2088 <li class="indline1"><em>RFC1305</em> <a class="iref" href="#rfc.xref.RFC1305.1">2.3.2</a>, <a class="iref" href="#RFC1305"><b>8.2</b></a></li> 2083 2089 <li class="indline1"><em>RFC2119</em> <a class="iref" href="#rfc.xref.RFC2119.1">1.3</a>, <a class="iref" href="#RFC2119"><b>8.1</b></a></li> 2084 <li class="indline1"><em>RFC2616</em> <a class="iref" href="#RFC2616"><b>8.2</b></a>, <a class="iref" href="#rfc.xref.RFC2616.1">C.1</a></li> 2090 <li class="indline1"><em>RFC2616</em> <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"> 2091 <li class="indline1"><em>Section 13.9</em> <a class="iref" href="#rfc.xref.RFC2616.1">2.3.1.1</a></li> 2092 </ul> 2093 </li> 2085 2094 <li class="indline1"><em>RFC3864</em> <a class="iref" href="#rfc.xref.RFC3864.1">5.2</a>, <a class="iref" href="#RFC3864"><b>8.2</b></a></li> 2086 2095 <li class="indline1"><em>RFC5226</em> <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
r827 r828 611 611 since that time. A typical setting of this fraction might be 10%. 612 612 </t> 613 <t> 614 <cref anchor="REVIEW-query-string-heuristics">took away HTTP/1.0 query string heuristic uncacheability.</cref> 615 </t> 613 <x:note> 614 <t> 615 <x:h>Note:</x:h> RFC 2616 (<xref target="RFC2616" x:fmt="," x:sec="13.9"/>) 616 required that caches do not calculate heuristic freshness for URLs with 617 query components (i.e., those containing '?'). In practice, this has not 618 been widely implemented. Therefore, servers are encouraged to send explicit 619 directives (e.g., Cache-Control: no-cache) if they wish to preclude 620 caching. 621 </t> 622 </x:note> 616 623 </section> 617 624 </section> … … 2474 2481 "IANA registry for cache-control directives" 2475 2482 </t> 2483 <t> 2484 <eref target="http://tools.ietf.org/wg/httpbis/trac/ticket/211" />: 2485 "Heuristic caching of URLs with query components" 2486 </t> 2476 2487 </list> 2477 2488 </t>
Note: See TracChangeset
for help on using the changeset viewer.