Changeset 1945
- Timestamp:
- 22/10/12 15:42:34 (8 years ago)
- Location:
- draft-ietf-httpbis/latest
- Files:
-
- 2 edited
Legend:
- Unmodified
- Added
- Removed
-
draft-ietf-httpbis/latest/p6-cache.html
r1931 r1945 452 452 } 453 453 @bottom-center { 454 content: "Expires April 6, 2013";454 content: "Expires April 25, 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-10- 03">500 <meta name="dct.issued" scheme="ISO8601" content="2012-10-22"> 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: April 6, 2013</td>526 <td class="left">Expires: April 25, 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">October 3, 2012</td>535 <td class="right">October 22, 2012</td> 536 536 </tr> 537 537 </tbody> … … 559 559 in progress”. 560 560 </p> 561 <p>This Internet-Draft will expire on April 6, 2013.</p>561 <p>This Internet-Draft will expire on April 25, 2013.</p> 562 562 <h1><a id="rfc.copyrightnotice" href="#rfc.copyrightnotice">Copyright Notice</a></h1> 563 563 <p>Copyright © 2012 IETF Trust and the persons identified as the document authors. All rights reserved.</p> … … 1431 1431 </p> 1432 1432 <div class="note" id="rfc.section.7.3.p.7"> 1433 <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 field in shared caches.1433 <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 field in shared caches. 1434 1434 </p> 1435 1435 </div> … … 1791 1791 </p> 1792 1792 <p id="rfc.section.10.p.3">Likewise, implementation flaws (as well as misunderstanding of cache operation) might lead to caching of sensitive information 1793 (e.g., authentication credentials) that is thought to be private, exposing it to unauthori sed parties.1793 (e.g., authentication credentials) that is thought to be private, exposing it to unauthorized parties. 1794 1794 </p> 1795 1795 <p id="rfc.section.10.p.4">Note that the Set-Cookie response header <a href="#RFC6265" id="rfc.xref.RFC6265.1"><cite title="HTTP State Management Mechanism">[RFC6265]</cite></a> does not inhibit caching; a cacheable response with a Set-Cookie header can be (and often is) used to satisfy subsequent requests -
draft-ietf-httpbis/latest/p6-cache.xml
r1929 r1945 1619 1619 that directive overrides the Expires field. Likewise, the s-maxage 1620 1620 directive (<xref target="cache-response-directive.s-maxage" />) overrides 1621 the <x:ref>Expires</x:ref> header field in shared caches.1621 the <x:ref>Expires</x:ref> header field in shared caches. 1622 1622 </t> 1623 1623 </x:note> … … 2099 2099 operation) might lead to caching of sensitive information (e.g., 2100 2100 authentication credentials) that is thought to be private, exposing it to 2101 unauthori sed parties.2101 unauthorized parties. 2102 2102 </t> 2103 2103 <t>
Note: See TracChangeset
for help on using the changeset viewer.