Changeset 2250 for draft-ietf-httpbis/latest
- Timestamp:
- 17/05/13 01:45:39 (10 years ago)
- Location:
- draft-ietf-httpbis/latest
- Files:
-
- 2 edited
Legend:
- Unmodified
- Added
- Removed
-
draft-ietf-httpbis/latest/p6-cache.html
r2249 r2250 452 452 } 453 453 @bottom-center { 454 content: "Expires November 9, 2013";454 content: "Expires November 18, 2013"; 455 455 } 456 456 @bottom-right { … … 492 492 <link href="p5-range.html" rel="prev"> 493 493 <link href="p7-auth.html" rel="next"> 494 <meta name="generator" content="http://greenbytes.de/tech/webdav/rfc2629.xslt, Revision 1.594, 2013/04/30 16:11:28, XSLT vendor: SAXON 8.9from Saxonica http://www.saxonica.com/">494 <meta name="generator" content="http://greenbytes.de/tech/webdav/rfc2629.xslt, Revision 1.594, 2013/04/30 16:11:28, XSLT vendor: SAXON 9.1.0.8 from Saxonica http://www.saxonica.com/"> 495 495 <link rel="schema.dct" href="http://purl.org/dc/terms/"> 496 496 <meta name="dct.creator" content="Fielding, R."> … … 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-05- 08">500 <meta name="dct.issued" scheme="ISO8601" content="2013-05-17"> 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: November 9, 2013</td>526 <td class="left">Expires: November 18, 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">May 8, 2013</td>535 <td class="right">May 17, 2013</td> 536 536 </tr> 537 537 </tbody> … … 559 559 in progress”. 560 560 </p> 561 <p>This Internet-Draft will expire on November 9, 2013.</p>561 <p>This Internet-Draft will expire on November 18, 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> … … 985 985 corrected_age_value = age_value + response_delay; 986 986 </pre><div id="rfc.figure.u.4"></div> 987 <p>These <em class="bcp14">SHOULD</em> be combined as 988 </p><pre class="text"> corrected_initial_age = max(apparent_age, corrected_age_value); 987 <p>These are combined as</p><pre class="text"> corrected_initial_age = max(apparent_age, corrected_age_value); 989 988 </pre><p id="rfc.section.4.1.3.p.11">unless the cache is confident in the value of the <a href="#header.age" class="smpl">Age</a> header field (e.g., because there are no HTTP/1.0 hops in the <a href="p1-messaging.html#header.via" class="smpl">Via</a> header field), in which case the corrected_age_value <em class="bcp14">MAY</em> be used as the corrected_initial_age. 990 989 </p> … … 1008 1007 </p> 1009 1008 <div id="rfc.iref.f.3"></div> 1010 <p id="rfc.section.4.1.4.p.5">Note that if a cache receives a <dfn>first-hand</dfn> response (one where the freshness model is not in use; i.e., its age is 0, whether it is an entire response, or a <a href="p4-conditional.html#status.304" class="smpl">304 (Not Modified)</a> response) that it would normally forward to the requesting client, and the received response is no longer fresh, the cache <em class="bcp14">MAY</em> forward it to the requesting client without adding a new <a href="#header.warning" class="smpl">Warning</a> (but without removing any existing Warning header fields). A cache shouldn't attempt to validate a response simply because1009 <p id="rfc.section.4.1.4.p.5">Note that if a cache receives a <dfn>first-hand</dfn> response (one where the freshness model is not in use; i.e., its age is 0, whether it is an entire response, or a <a href="p4-conditional.html#status.304" class="smpl">304 (Not Modified)</a> response) that it would normally forward to the requesting client, and the received response is no longer fresh, the cache <em class="bcp14">MAY</em> forward it to the requesting client without adding a new <a href="#header.warning" class="smpl">Warning</a> (but without removing any existing Warning header fields). A cache ought not attempt to validate a response simply because 1011 1010 that response became stale in transit. 1012 1011 </p> … … 1023 1022 </p> 1024 1023 <p id="rfc.section.4.2.p.4">Another is the <a href="p4-conditional.html#header.if-none-match" class="smpl">If-None-Match</a> header field, whose value is that of the <a href="p4-conditional.html#header.etag" class="smpl">ETag</a> header field(s) from relevant responses stored for the primary cache key, if present. However, if any of the stored responses 1025 contains only partial content, the cache shouldn't include its entity-tag in the If-None-Match header field unless the request1024 contains only partial content, the cache ought not include its entity-tag in the If-None-Match header field unless the request 1026 1025 is for a range that would be fully satisfied by that stored response. 1027 1026 </p> -
draft-ietf-httpbis/latest/p6-cache.xml
r2249 r2250 708 708 </figure> 709 709 <figure> 710 <preamble>These &SHOULD; be combined as</preamble>710 <preamble>These are combined as</preamble> 711 711 <artwork type="code"> 712 712 corrected_initial_age = max(apparent_age, corrected_age_value); … … 762 762 response is no longer fresh, the cache &MAY; forward it to the requesting 763 763 client without adding a new <x:ref>Warning</x:ref> (but without removing 764 any existing Warning header fields). A cache shouldn't attempt to validate764 any existing Warning header fields). A cache ought not attempt to validate 765 765 a response simply because that response became stale in transit. 766 766 </t> … … 796 796 relevant responses stored for the primary cache key, if present. However, 797 797 if any of the stored responses contains only partial content, the cache 798 shouldn't include its entity-tag in the If-None-Match header field unless798 ought not include its entity-tag in the If-None-Match header field unless 799 799 the request is for a range that would be fully satisfied by that stored 800 800 response.
Note: See TracChangeset
for help on using the changeset viewer.