Changeset 2268 for draft-ietf-httpbis/latest
- Timestamp:
- 21/05/13 17:18:06 (10 years ago)
- Location:
- draft-ietf-httpbis/latest
- Files:
-
- 2 edited
Legend:
- Unmodified
- Added
- Removed
-
draft-ietf-httpbis/latest/p6-cache.html
r2267 r2268 1086 1086 </p> 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 <p id="rfc.section.4.3.p.6">If multiple selected responses are available (potentially including responses without a Vary header ), the cache will need1089 to choose one to use. When a selecting headerhas 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>.1088 <p id="rfc.section.4.3.p.6">If multiple selected responses are available (potentially including responses without a Vary header field), the cache will 1089 need to choose one to use. When a selecting header field 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 … … 1755 1755 (e.g., authentication credentials) that is thought to be private, exposing it to unauthorized parties. 1756 1756 </p> 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 requests1758 to caches. Servers who wish to control caching of these responses are encouraged to emit appropriate Cache-Control response1759 header fields.1757 <p id="rfc.section.10.p.6">Note that the Set-Cookie response header field <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 field can be (and often is) used to satisfy subsequent 1758 requests to caches. Servers who wish to control caching of these responses are encouraged to emit appropriate Cache-Control 1759 response 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> … … 1889 1889 <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>) 1890 1890 </p> 1891 <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>) 1892 </p> 1893 <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>) 1894 </p> 1895 <p id="rfc.section.A.p.20">This specification introduces the Cache Directive and Warn Code Registries, and defines considerations for new cache directives. 1891 <p id="rfc.section.A.p.18">Some requirements regarding production of the <a href="#header.warning" class="smpl">Warning</a> header fields have been relaxed, as it is not widely implemented. Furthermore, 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.6" title="Warning">Section 7.5</a>) 1892 </p> 1893 <p id="rfc.section.A.p.19">This specification introduces the Cache Directive and Warn Code Registries, and defines considerations for new cache directives. 1896 1894 (<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>) 1897 1895 </p> … … 2182 2180 </li> 2183 2181 <li><a id="rfc.index.W" href="#rfc.index.W"><b>W</b></a><ul> 2184 <li>Warning header field <a href="#rfc.xref.header.warning.1">3.3</a>, <a href="#rfc.xref.header.warning.2">4.1.4</a>, <a href="#rfc.xref.header.warning.3">4.2.1</a>, <a href="#rfc.xref.header.warning.4">5</a>, <a href="#rfc.iref.w.1"><b>7.5</b></a>, <a href="#rfc.xref.header.warning.5">9.3</a>, <a href="#rfc.xref.header.warning.6">A</a> , <a href="#rfc.xref.header.warning.7">A</a></li>2182 <li>Warning header field <a href="#rfc.xref.header.warning.1">3.3</a>, <a href="#rfc.xref.header.warning.2">4.1.4</a>, <a href="#rfc.xref.header.warning.3">4.2.1</a>, <a href="#rfc.xref.header.warning.4">5</a>, <a href="#rfc.iref.w.1"><b>7.5</b></a>, <a href="#rfc.xref.header.warning.5">9.3</a>, <a href="#rfc.xref.header.warning.6">A</a></li> 2185 2183 </ul> 2186 2184 </li> -
draft-ietf-httpbis/latest/p6-cache.xml
r2267 r2268 924 924 <t> 925 925 If multiple selected responses are available (potentially including 926 responses without a Vary header ), the cache will need to choose one to use.927 When a selecting header has a known mechanism for doing so (e.g., qvalues on926 responses without a Vary header field), the cache will need to choose one to use. 927 When a selecting header field has a known mechanism for doing so (e.g., qvalues on 928 928 <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 … … 2051 2051 </t> 2052 2052 <t> 2053 Note that the Set-Cookie response header <xref target="RFC6265"/> does not2054 inhibit caching; a cacheable response with a Set-Cookie header can be (and2053 Note that the Set-Cookie response header field <xref target="RFC6265"/> does not 2054 inhibit caching; a cacheable response with a Set-Cookie header field can be (and 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 … … 2432 2432 <t> 2433 2433 Some requirements regarding production of the <x:ref>Warning</x:ref> 2434 header have been relaxed, as it is not widely implemented. 2435 (<xref target="header.warning" />) 2436 </t> 2437 <t> 2438 The <x:ref>Warning</x:ref> header field no longer uses RFC 2047 encoding, 2434 header fields have been relaxed, as it is not widely implemented. 2435 Furthermore, the <x:ref>Warning</x:ref> header field no longer uses RFC 2047 encoding, 2439 2436 nor allows multiple languages, as these aspects were not implemented. 2440 2437 (<xref target="header.warning" />)
Note: See TracChangeset
for help on using the changeset viewer.