Changeset 2172 for draft-ietf-httpbis/latest/p6-cache.html
- Timestamp:
- 30/01/13 08:35:18 (10 years ago)
- File:
-
- 1 edited
Legend:
- Unmodified
- Added
- Removed
-
draft-ietf-httpbis/latest/p6-cache.html
r2169 r2172 452 452 } 453 453 @bottom-center { 454 content: "Expires July 31, 2013";454 content: "Expires August 3, 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="2013-01- 27">500 <meta name="dct.issued" scheme="ISO8601" content="2013-01-30"> 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. This document 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: July 31, 2013</td>526 <td class="left">Expires: August 3, 2013</td> 527 527 <td class="right">J. Reschke, Editor</td> 528 528 </tr> … … 533 533 <tr> 534 534 <td class="left"></td> 535 <td class="right">January 27, 2013</td>535 <td class="right">January 30, 2013</td> 536 536 </tr> 537 537 </tbody> … … 559 559 in progress”. 560 560 </p> 561 <p>This Internet-Draft will expire on July 31, 2013.</p>561 <p>This Internet-Draft will expire on August 3, 2013.</p> 562 562 <h1><a id="rfc.copyrightnotice" href="#rfc.copyrightnotice">Copyright Notice</a></h1> 563 563 <p>Copyright © 2013 IETF Trust and the persons identified as the document authors. All rights reserved.</p> … … 1272 1272 <div id="rfc.iref.p.2"></div> 1273 1273 <h4 id="rfc.section.7.2.2.1"><a href="#rfc.section.7.2.2.1">7.2.2.1</a> <a id="cache-response-directive.public" href="#cache-response-directive.public">public</a></h4> 1274 <p id="rfc.section.7.2.2.1.p.1">The "public" response directive indicates that a response whose associated request contains an 'Authentication' header <em class="bcp14">MAY</em> be stored (see <a href="#caching.authenticated.responses" title="Storing Responses to Authenticated Requests">Section 3.2</a>). 1274 <p id="rfc.section.7.2.2.1.p.1">The "public" response directive indicates that any cache <em class="bcp14">MAY</em> store the response and reuse it for later requests, even if the response would normally be non-cacheable or cacheable only 1275 within a non-shared cache. (See <a href="#caching.authenticated.responses" title="Storing Responses to Authenticated Requests">Section 3.2</a> for additional details related to the use of public in response to a request containing <a href="p7-auth.html#header.authorization" class="smpl">Authorization</a>.) 1275 1276 </p> 1276 1277 <div id="rfc.iref.p.3"></div> … … 1281 1282 </li> 1282 1283 </ul> 1283 <p id="rfc.section.7.2.2.2.p.2">The "private" response directive indicates that the response message is intended for a single user and <em class="bcp14">MUST NOT</em> be stored by a shared cache. A private cache <em class="bcp14">MAY</em> store the response .1284 <p id="rfc.section.7.2.2.2.p.2">The "private" response directive indicates that the response message is intended for a single user and <em class="bcp14">MUST NOT</em> be stored by a shared cache. A private cache <em class="bcp14">MAY</em> store the response and reuse it for later requests, even if the response would normally be non-cacheable. 1284 1285 </p> 1285 1286 <p id="rfc.section.7.2.2.2.p.3">If the private response directive specifies one or more field-names, this requirement is limited to the field-values associated … … 1921 1922 and does not invalidate it. (<a href="#cache-request-directive.no-store" title="no-store">Section 7.2.1.2</a>) 1922 1923 </p> 1923 <p id="rfc.section.A.p.15">The meaning of the "public" cache response directive has been refined to be less vague. (<a href="#cache-response-directive.public" title="public">Section 7.2.2.1</a>) 1924 </p> 1925 <p id="rfc.section.A.p.16">The "no-cache" response cache directive's meaning has been clarified. (<a href="#cache-response-directive.no-cache" title="no-cache">Section 7.2.2.3</a>) 1926 </p> 1927 <p id="rfc.section.A.p.17">New status codes can now define that caches are allowed to use heuristic freshness with them. (<a href="#heuristic.freshness" title="Calculating Heuristic Freshness">Section 4.1.2</a>) 1928 </p> 1929 <p id="rfc.section.A.p.18">Caches are now allow to calculate heuristic freshness for URLs with query components. (<a href="#heuristic.freshness" title="Calculating Heuristic Freshness">Section 4.1.2</a>) 1930 </p> 1931 <p id="rfc.section.A.p.19">Some requirements regarding production of the <a href="#header.warning" class="smpl">Warning</a> header have been relaxed, as it is not widely implemented. (<a href="#header.warning" id="rfc.xref.header.warning.6" title="Warning">Section 7.5</a>) 1932 </p> 1933 <p id="rfc.section.A.p.20">The <a href="#header.warning" class="smpl">Warning</a> header field no longer uses RFC 2047 encoding, nor allows multiple languages, as these aspects were not implemented. (<a href="#header.warning" id="rfc.xref.header.warning.7" title="Warning">Section 7.5</a>) 1934 </p> 1935 <p id="rfc.section.A.p.21">This specification introduces the Cache Directive and Warn Code Registries, and defines considerations for new cache directives. 1924 <p id="rfc.section.A.p.15">The "no-cache" response cache directive's meaning has been clarified. (<a href="#cache-response-directive.no-cache" title="no-cache">Section 7.2.2.3</a>) 1925 </p> 1926 <p id="rfc.section.A.p.16">New status codes can now define that caches are allowed to use heuristic freshness with them. (<a href="#heuristic.freshness" title="Calculating Heuristic Freshness">Section 4.1.2</a>) 1927 </p> 1928 <p id="rfc.section.A.p.17">Caches are now allow to calculate heuristic freshness for URLs with query components. (<a href="#heuristic.freshness" title="Calculating Heuristic Freshness">Section 4.1.2</a>) 1929 </p> 1930 <p id="rfc.section.A.p.18">Some requirements regarding production of the <a href="#header.warning" class="smpl">Warning</a> header have been relaxed, as it is not widely implemented. (<a href="#header.warning" id="rfc.xref.header.warning.6" title="Warning">Section 7.5</a>) 1931 </p> 1932 <p id="rfc.section.A.p.19">The <a href="#header.warning" class="smpl">Warning</a> header field no longer uses RFC 2047 encoding, nor allows multiple languages, as these aspects were not implemented. (<a href="#header.warning" id="rfc.xref.header.warning.7" title="Warning">Section 7.5</a>) 1933 </p> 1934 <p id="rfc.section.A.p.20">This specification introduces the Cache Directive and Warn Code Registries, and defines considerations for new cache directives. 1936 1935 (<a href="#cache.control.extensions" title="Cache Control Extensions">Section 7.2.3</a> and <a href="#warn.code.extensions" title="Warn Code Extensions">Section 7.5.8</a>) 1937 1936 </p> … … 2038 2037 </li> 2039 2038 <li> <<a href="http://tools.ietf.org/wg/httpbis/trac/ticket/418">http://tools.ietf.org/wg/httpbis/trac/ticket/418</a>>: "No-Transform" 2039 </li> 2040 <li> <<a href="http://tools.ietf.org/wg/httpbis/trac/ticket/430">http://tools.ietf.org/wg/httpbis/trac/ticket/430</a>>: "Revert prior change to the meaning of the public cache response directive. 2040 2041 </li> 2041 2042 </ul>
Note: See TracChangeset
for help on using the changeset viewer.