Changeset 1279
- Timestamp:
- 02/05/11 10:15:29 (10 years ago)
- File:
-
- 1 edited
Legend:
- Unmodified
- Added
- Removed
-
draft-ietf-httpbis/latest/p6-cache.html
r1276 r1279 362 362 } 363 363 @bottom-center { 364 content: "Expires November 2, 2011";364 content: "Expires November 3, 2011"; 365 365 } 366 366 @bottom-right { … … 408 408 <meta name="dct.creator" content="Reschke, J. F."> 409 409 <meta name="dct.identifier" content="urn:ietf:id:draft-ietf-httpbis-p6-cache-latest"> 410 <meta name="dct.issued" scheme="ISO8601" content="2011-05-0 1">410 <meta name="dct.issued" scheme="ISO8601" content="2011-05-02"> 411 411 <meta name="dct.replaces" content="urn:ietf:rfc:2616"> 412 412 <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."> … … 434 434 </tr> 435 435 <tr> 436 <td class="left">Expires: November 2, 2011</td>436 <td class="left">Expires: November 3, 2011</td> 437 437 <td class="right">J. Mogul</td> 438 438 </tr> … … 495 495 <tr> 496 496 <td class="left"></td> 497 <td class="right">May 1, 2011</td>497 <td class="right">May 2, 2011</td> 498 498 </tr> 499 499 </tbody> … … 523 523 in progress”. 524 524 </p> 525 <p>This Internet-Draft will expire on November 2, 2011.</p>525 <p>This Internet-Draft will expire on November 3, 2011.</p> 526 526 <h1><a id="rfc.copyrightnotice" href="#rfc.copyrightnotice">Copyright Notice</a></h1> 527 527 <p>Copyright © 2011 IETF Trust and the persons identified as the document authors. All rights reserved.</p> … … 809 809 <p id="rfc.section.2.2.p.4">Also, note that unsafe requests might invalidate already stored responses; see <a href="#invalidation.after.updates.or.deletions" title="Request Methods that Invalidate">Section 2.5</a>. 810 810 </p> 811 <p id="rfc.section.2.2.p.5"> A cache <em class="bcp14">MUST</em> use the most recent response (as determined by the Date header field) when more than one suitable response is stored. It can812 also forward a request with "Cache-Control:max-age=0" or "Cache-Control: no-cache" to disambiguate which response to use.811 <p id="rfc.section.2.2.p.5">When more than one suitable response is stored, a cache <em class="bcp14">MUST</em> use the most recent response (as determined by the Date header field). It can also forward a request with "Cache-Control: 812 max-age=0" or "Cache-Control: no-cache" to disambiguate which response to use. 813 813 </p> 814 814 <p id="rfc.section.2.2.p.6">A cache that does not have a clock available <em class="bcp14">MUST NOT</em> use stored responses without revalidating them on every use. A cache, especially a shared cache, <em class="bcp14">SHOULD</em> use a mechanism, such as NTP <a href="#RFC1305" id="rfc.xref.RFC1305.1"><cite title="Network Time Protocol (Version 3) Specification, Implementation">[RFC1305]</cite></a>, to synchronize its clock with a reliable external standard. … … 1142 1142 </p> 1143 1143 <ul class="empty"> 1144 <li>The only-if-cached request directive indicates that the client only wishes to return a stored response. If it receives this1144 <li>The only-if-cached request directive indicates that the client only wishes to obtain a stored response. If it receives this 1145 1145 directive, a cache <em class="bcp14">SHOULD</em> either respond using a stored response that is consistent with the other constraints of the request, or respond with a 504 1146 1146 (Gateway Timeout) status code. If a group of caches is being operated as a unified system with good internal connectivity,
Note: See TracChangeset
for help on using the changeset viewer.