Changeset 944 for draft-ietf-httpbis/latest/p6-cache.html
- Timestamp:
- 27/07/10 13:49:49 (11 years ago)
- File:
-
- 1 edited
Legend:
- Unmodified
- Added
- Removed
-
draft-ietf-httpbis/latest/p6-cache.html
r939 r944 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-07-2 4">404 <meta name="dct.issued" scheme="ISO8601" content="2010-07-27"> 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: January 2 5, 2011</td>430 <td class="left">Expires: January 28, 2011</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">July 2 4, 2010</td>491 <td class="right">July 27, 2010</td> 492 492 </tr> 493 493 </tbody> … … 515 515 in progress”. 516 516 </p> 517 <p>This Internet-Draft will expire in January 2 5, 2011.</p>517 <p>This Internet-Draft will expire in January 28, 2011.</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> … … 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. 940 940 </p> 941 <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):941 <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): 942 942 </p> 943 943 <ul> … … 1903 1903 <li> <<a href="http://tools.ietf.org/wg/httpbis/trac/ticket/223">http://tools.ietf.org/wg/httpbis/trac/ticket/223</a>>: "Allowing heuristic caching for new status codes" 1904 1904 </li> 1905 <li> <<a href="http://tools.ietf.org/wg/httpbis/trac/ticket/223">http://tools.ietf.org/wg/httpbis/trac/ticket/223</a>>: "Allowing heuristic caching for new status codes" 1906 </li> 1907 <li> <<a href="http://tools.ietf.org/wg/httpbis/trac/ticket/235">http://tools.ietf.org/wg/httpbis/trac/ticket/235</a>>: "Cache Invalidation only happens upon successful responses" 1908 </li> 1905 1909 <li>Clean up TODOs and prose in "Combining Responses."</li> 1906 1910 </ul> … … 2053 2057 </ul> 2054 2058 </li> 2055 <li class="indline1"><em>Part2</em> <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">2059 <li class="indline1"><em>Part2</em> <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"> 2056 2060 <li class="indline1"><em>Section 7.1.1</em> <a class="iref" href="#rfc.xref.Part2.1">2.2</a>, <a class="iref" href="#rfc.xref.Part2.3">2.5</a></li> 2057 2061 <li class="indline1"><em>Section 8</em> <a class="iref" href="#rfc.xref.Part2.2">2.3.1.1</a></li> 2062 <li class="indline1"><em>Section 8.2</em> <a class="iref" href="#rfc.xref.Part2.4">2.5</a></li> 2058 2063 </ul> 2059 2064 </li>
Note: See TracChangeset
for help on using the changeset viewer.