Changeset 2266 for draft-ietf-httpbis/latest
- Timestamp:
- 20/05/13 21:51:33 (10 years ago)
- Location:
- draft-ietf-httpbis/latest
- Files:
-
- 2 edited
Legend:
- Unmodified
- Added
- Removed
-
draft-ietf-httpbis/latest/p6-cache.html
r2265 r2266 1087 1087 <p id="rfc.section.4.3.p.5">The stored response with matching selecting header fields is known as the selected response.</p> 1088 1088 <p id="rfc.section.4.3.p.6">If multiple selected responses are available (potentially including responses without a Vary header), the cache will need 1089 to choose one to use. When a selecting header has a known mechanism for doing so (e.g., qvalues on <a href="p2-semantics.html#header.accept" class="smpl">Accept</a> and similar request header s), that mechanism <em class="bcp14">MAY</em> be used to select preferred responses; of the remainder, the most recent response (as determined by the <a href="p2-semantics.html#header.date" class="smpl">Date</a> header field) is used, as per <a href="#constructing.responses.from.caches" title="Constructing Responses from Caches">Section 4</a>.1089 to choose one to use. When a selecting header has a known mechanism for doing so (e.g., qvalues on <a href="p2-semantics.html#header.accept" class="smpl">Accept</a> and similar request header fields), that mechanism <em class="bcp14">MAY</em> be used to select preferred responses; of the remainder, the most recent response (as determined by the <a href="p2-semantics.html#header.date" class="smpl">Date</a> header field) is used, as per <a href="#constructing.responses.from.caches" title="Constructing Responses from Caches">Section 4</a>. 1090 1090 </p> 1091 1091 <p id="rfc.section.4.3.p.7">If no selected response is available, the cache cannot satisfy the presented request. Typically, it is forwarded to the origin … … 1757 1757 <p id="rfc.section.10.p.6">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 1758 1758 to caches. Servers who wish to control caching of these responses are encouraged to emit appropriate Cache-Control response 1759 header s.1759 header fields. 1760 1760 </p> 1761 1761 <h1 id="rfc.section.11"><a href="#rfc.section.11">11.</a> <a id="acks" href="#acks">Acknowledgments</a></h1> -
draft-ietf-httpbis/latest/p6-cache.xml
r2265 r2266 926 926 responses without a Vary header), the cache will need to choose one to use. 927 927 When a selecting header has a known mechanism for doing so (e.g., qvalues on 928 <x:ref>Accept</x:ref> and similar request header s), that mechanism &MAY; be928 <x:ref>Accept</x:ref> and similar request header fields), that mechanism &MAY; be 929 929 used to select preferred responses; of the remainder, the most recent 930 930 response (as determined by the <x:ref>Date</x:ref> header field) is used, as … … 2055 2055 often is) used to satisfy subsequent requests to caches. Servers who wish 2056 2056 to control caching of these responses are encouraged to emit appropriate 2057 Cache-Control response header s.2057 Cache-Control response header fields. 2058 2058 </t> 2059 2059
Note: See TracChangeset
for help on using the changeset viewer.