Changeset 1793 for draft-ietf-httpbis/latest/p6-cache.html
- Timestamp:
- 15/07/12 17:51:16 (9 years ago)
- File:
-
- 1 edited
Legend:
- Unmodified
- Added
- Removed
-
draft-ietf-httpbis/latest/p6-cache.html
r1779 r1793 452 452 } 453 453 @bottom-center { 454 content: "Expires January 1 5, 2013";454 content: "Expires January 16, 2013"; 455 455 } 456 456 @bottom-right { … … 498 498 <meta name="dct.creator" content="Reschke, J. F."> 499 499 <meta name="dct.identifier" content="urn:ietf:id:draft-ietf-httpbis-p6-cache-latest"> 500 <meta name="dct.issued" scheme="ISO8601" content="2012-07-1 4">500 <meta name="dct.issued" scheme="ISO8601" content="2012-07-15"> 501 501 <meta name="dct.replaces" content="urn:ietf:rfc:2616"> 502 502 <meta name="dct.abstract" content="The Hypertext Transfer Protocol (HTTP) is an application-level protocol for distributed, collaborative, hypertext information systems. HTTP has been in use by the World Wide Web global information initiative since 1990. 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."> … … 524 524 </tr> 525 525 <tr> 526 <td class="left">Expires: January 1 5, 2013</td>526 <td class="left">Expires: January 16, 2013</td> 527 527 <td class="right">M. Nottingham, Editor</td> 528 528 </tr> … … 541 541 <tr> 542 542 <td class="left"></td> 543 <td class="right">July 1 4, 2012</td>543 <td class="right">July 15, 2012</td> 544 544 </tr> 545 545 </tbody> … … 570 570 in progress”. 571 571 </p> 572 <p>This Internet-Draft will expire on January 1 5, 2013.</p>572 <p>This Internet-Draft will expire on January 16, 2013.</p> 573 573 <h1><a id="rfc.copyrightnotice" href="#rfc.copyrightnotice">Copyright Notice</a></h1> 574 574 <p>Copyright © 2012 IETF Trust and the persons identified as the document authors. All rights reserved.</p> … … 860 860 <li>the "no-store" cache directive (see <a href="#header.cache-control" id="rfc.xref.header.cache-control.1" title="Cache-Control">Section 7.2</a>) does not appear in request or response header fields, and 861 861 </li> 862 <li>the "private" cache response directive (see <a href="#cache-response-directive " title="Response Cache-Control Directives">Section 7.2.2</a>) does not appear in the response, if the cache is shared, and862 <li>the "private" cache response directive (see <a href="#cache-response-directive.private" title="private">Section 7.2.2.2</a>) does not appear in the response, if the cache is shared, and 863 863 </li> 864 864 <li>the <a href="p7-auth.html#header.authorization" class="smpl">Authorization</a> header field (see <a href="p7-auth.html#header.authorization" title="Authorization">Section 4.1</a> of <a href="#Part7" id="rfc.xref.Part7.1"><cite title="HTTP/1.1, part 7: Authentication">[Part7]</cite></a>) does not appear in the request, if the cache is shared, unless the response explicitly allows it (see <a href="#caching.authenticated.responses" title="Storing Responses to Authenticated Requests">Section 3.2</a>), and … … 868 868 <li>contains an <a href="#header.expires" class="smpl">Expires</a> header field (see <a href="#header.expires" id="rfc.xref.header.expires.1" title="Expires">Section 7.3</a>), or 869 869 </li> 870 <li>contains a max-age response cache directive (see <a href="#cache-response-directive " title="Response Cache-Control Directives">Section 7.2.2</a>), or870 <li>contains a max-age response cache directive (see <a href="#cache-response-directive.max-age" title="max-age">Section 7.2.2.7</a>), or 871 871 </li> 872 872 <li>contains a s-maxage response cache directive and the cache is shared, or</li> … … 914 914 <li>the presented request does not contain the no-cache pragma (<a href="#header.pragma" id="rfc.xref.header.pragma.1" title="Pragma">Section 7.4</a>), nor the no-cache cache directive (<a href="#cache-request-directive" title="Request Cache-Control Directives">Section 7.2.1</a>), unless the stored response is successfully validated (<a href="#validation.model" title="Validation Model">Section 4.2</a>), and 915 915 </li> 916 <li>the stored response does not contain the no-cache cache directive (<a href="#cache-response-directive " title="Response Cache-Control Directives">Section 7.2.2</a>), unless it is successfully validated (<a href="#validation.model" title="Validation Model">Section 4.2</a>), and916 <li>the stored response does not contain the no-cache cache directive (<a href="#cache-response-directive.no-cache" title="no-cache">Section 7.2.2.3</a>), unless it is successfully validated (<a href="#validation.model" title="Validation Model">Section 4.2</a>), and 917 917 </li> 918 918 <li>the stored response is either: … … 946 946 </p> 947 947 <p id="rfc.section.4.1.p.2">The primary mechanism for determining freshness is for an origin server to provide an explicit expiration time in the future, 948 using either the <a href="#header.expires" class="smpl">Expires</a> header field (<a href="#header.expires" id="rfc.xref.header.expires.2" title="Expires">Section 7.3</a>) or the max-age response cache directive (<a href="#cache-response-directive " title="Response Cache-Control Directives">Section 7.2.2</a>). Generally, origin servers will assign future explicit expiration times to responses in the belief that the representation948 using either the <a href="#header.expires" class="smpl">Expires</a> header field (<a href="#header.expires" id="rfc.xref.header.expires.2" title="Expires">Section 7.3</a>) or the max-age response cache directive (<a href="#cache-response-directive.max-age" title="max-age">Section 7.2.2.7</a>). Generally, origin servers will assign future explicit expiration times to responses in the belief that the representation 949 949 is not likely to change in a semantically significant way before the expiration time is reached. 950 950 </p> … … 970 970 <p id="rfc.section.4.1.1.p.1">A cache can calculate the freshness lifetime (denoted as freshness_lifetime) of a response by using the first match of: </p> 971 971 <ul> 972 <li>If the cache is shared and the s-maxage response cache directive (<a href="#cache-response-directive " title="Response Cache-Control Directives">Section 7.2.2</a>) is present, use its value, or973 </li> 974 <li>If the max-age response cache directive (<a href="#cache-response-directive " title="Response Cache-Control Directives">Section 7.2.2</a>) is present, use its value, or972 <li>If the cache is shared and the s-maxage response cache directive (<a href="#cache-response-directive.s-maxage" title="s-maxage">Section 7.2.2.8</a>) is present, use its value, or 973 </li> 974 <li>If the max-age response cache directive (<a href="#cache-response-directive.max-age" title="max-age">Section 7.2.2.7</a>) is present, use its value, or 975 975 </li> 976 976 <li>If the <a href="#header.expires" class="smpl">Expires</a> response header field (<a href="#header.expires" id="rfc.xref.header.expires.3" title="Expires">Section 7.3</a>) is present, use its value minus the value of the <a href="p2-semantics.html#header.date" class="smpl">Date</a> response header field, or … … 1495 1495 </p> 1496 1496 <div class="note" id="rfc.section.7.3.p.7"> 1497 <p> <b>Note:</b> If a response includes a <a href="#header.cache-control" class="smpl">Cache-Control</a> field with the max-age directive (see <a href="#cache-response-directive " title="Response Cache-Control Directives">Section 7.2.2</a>), that directive overrides the Expires field. Likewise, the s-maxage directive overrides Expiresin shared caches.1497 <p> <b>Note:</b> If a response includes a <a href="#header.cache-control" class="smpl">Cache-Control</a> field with the max-age directive (see <a href="#cache-response-directive.max-age" title="max-age">Section 7.2.2.7</a>), that directive overrides the Expires field. Likewise, the s-maxage directive (<a href="#cache-response-directive.s-maxage" title="s-maxage">Section 7.2.2.8</a>) overrides the <a href="#header.expires" class="smpl">Expires</a> header fieldin shared caches. 1498 1498 </p> 1499 1499 </div>
Note: See TracChangeset
for help on using the changeset viewer.