Changeset 2020
- Timestamp:
- 29/11/12 02:49:57 (9 years ago)
- Location:
- draft-ietf-httpbis/latest
- Files:
-
- 3 edited
Legend:
- Unmodified
- Added
- Removed
-
draft-ietf-httpbis/latest/p6-cache.html
r2018 r2020 625 625 </li> 626 626 <li><a href="#rfc.section.7.2.2">7.2.2</a> <a href="#cache-response-directive">Response Cache-Control Directives</a><ul> 627 <li><a href="#rfc.section.7.2.2.1">7.2.2.1</a> <a href="#cache-response-directive. only-if-cached">public</a></li>627 <li><a href="#rfc.section.7.2.2.1">7.2.2.1</a> <a href="#cache-response-directive.public">public</a></li> 628 628 <li><a href="#rfc.section.7.2.2.2">7.2.2.2</a> <a href="#cache-response-directive.private">private</a></li> 629 629 <li><a href="#rfc.section.7.2.2.3">7.2.2.3</a> <a href="#cache-response-directive.no-cache">no-cache</a></li> … … 1275 1275 <h3 id="rfc.section.7.2.2"><a href="#rfc.section.7.2.2">7.2.2</a> <a id="cache-response-directive" href="#cache-response-directive">Response Cache-Control Directives</a></h3> 1276 1276 <div id="rfc.iref.p.2"></div> 1277 <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. only-if-cached" href="#cache-response-directive.only-if-cached">public</a></h4>1277 <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> 1278 1278 <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>). 1279 1279 </p> … … 1645 1645 <tr> 1646 1646 <td class="left">public</td> 1647 <td class="left"> <a href="#cache-response-directive. only-if-cached" title="public">Section 7.2.2.1</a>1647 <td class="left"> <a href="#cache-response-directive.public" title="public">Section 7.2.2.1</a> 1648 1648 </td> 1649 1649 </tr> … … 1892 1892 </div> 1893 1893 <h1 id="rfc.section.A" class="np"><a href="#rfc.section.A">A.</a> <a id="changes.from.rfc.2616" href="#changes.from.rfc.2616">Changes from RFC 2616</a></h1> 1894 <p id="rfc.section.A.p.1">The algorithm for calculating age is now less conservative. (<a href="#age.calculations" title="Calculating Age">Section 4.1.3</a>) 1895 </p> 1896 <p id="rfc.section.A.p.2">The <a href="p2-semantics.html#header.content-location" class="smpl">Content-Location</a> response header field is no longer used to determine the appropriate response to use. (<a href="#validation.model" title="Validation Model">Section 4.2</a>) 1897 </p> 1898 <p id="rfc.section.A.p.3">Requirements regarding denial of service attack avoidance have been clarified. (<a href="#invalidation.after.updates.or.deletions" title="Request Methods that Invalidate">Section 6</a>) 1899 </p> 1900 <p id="rfc.section.A.p.4">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>) 1901 </p> 1902 <p id="rfc.section.A.p.5">This specification introduces the Cache Directive and Warn Code Registries. (<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>) 1894 <p id="rfc.section.A.p.1">Caching-related text has been substantially rewritten for clarity.</p> 1895 <p id="rfc.section.A.p.2">The algorithm for calculating age is now less conservative. (<a href="#age.calculations" title="Calculating Age">Section 4.1.3</a>) 1896 </p> 1897 <p id="rfc.section.A.p.3">Caches are now required to handle dates with timezones as if they're invalid, because it's not possible to accurately guess. 1898 (<a href="#age.calculations" title="Calculating Age">Section 4.1.3</a>) 1899 </p> 1900 <p id="rfc.section.A.p.4">The <a href="p2-semantics.html#header.content-location" class="smpl">Content-Location</a> response header field is no longer used to determine the appropriate response to use when validating. (<a href="#validation.model" title="Validation Model">Section 4.2</a>) 1901 </p> 1902 <p id="rfc.section.A.p.5">The algorithm for selecting a cached negotiated response to use has been clarified in several ways. In particular, it now 1903 explicitly allows header-specific canonicalization when processing selecting header fields. (<a href="#caching.negotiated.responses" title="Using Negotiated Responses">Section 4.3</a>) 1904 </p> 1905 <p id="rfc.section.A.p.6">Requirements regarding denial of service attack avoidance when performing invalidation have been clarified. (<a href="#invalidation.after.updates.or.deletions" title="Request Methods that Invalidate">Section 6</a>) 1906 </p> 1907 <p id="rfc.section.A.p.7">Cache invalidation only occurs when a successful response is received. (<a href="#invalidation.after.updates.or.deletions" title="Request Methods that Invalidate">Section 6</a>) 1908 </p> 1909 <p id="rfc.section.A.p.8">The conditions under which an authenticated response can be cached have been clarified. (<a href="#caching.authenticated.responses" title="Storing Responses to Authenticated Requests">Section 3.2</a>) 1910 </p> 1911 <p id="rfc.section.A.p.9">The one-year limit on Expires header field values has been removed; instead, the reasoning for using a sensible value is given. 1912 (<a href="#header.expires" id="rfc.xref.header.expires.5" title="Expires">Section 7.3</a>) 1913 </p> 1914 <p id="rfc.section.A.p.10">The Pragma header field is now only defined for backwards compatibility; future pragmas are deprecated. (<a href="#header.pragma" id="rfc.xref.header.pragma.4" title="Pragma">Section 7.4</a>) 1915 </p> 1916 <p id="rfc.section.A.p.11">Cache directives are explicitly defined to be case-insensitive. (<a href="#header.cache-control" id="rfc.xref.header.cache-control.3" title="Cache-Control">Section 7.2</a>) 1917 </p> 1918 <p id="rfc.section.A.p.12">Handling of multiple instances of cache directives when only one is expected is now defined. (<a href="#header.cache-control" id="rfc.xref.header.cache-control.4" title="Cache-Control">Section 7.2</a>) 1919 </p> 1920 <p id="rfc.section.A.p.13">The qualified forms of the private and no-cache cache directives are noted to not be widely implemented; e.g., "private=foo" 1921 is interpreted by many caches as simply "private". Additionally, the meaning of the qualified form of no-cache has been clarified. 1922 (<a href="#cache-response-directive" title="Response Cache-Control Directives">Section 7.2.2</a>) 1923 </p> 1924 <p id="rfc.section.A.p.14">The "no-store" cache request directive doesn't apply to responses; i.e., a cache can satisfy a request with no-store on it, 1925 and does not invalidate it. (<a href="#cache-request-directive.no-store" title="no-store">Section 7.2.1.2</a>) 1926 </p> 1927 <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>) 1928 </p> 1929 <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>) 1930 </p> 1931 <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>) 1932 </p> 1933 <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>) 1934 </p> 1935 <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>) 1936 </p> 1937 <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>) 1938 </p> 1939 <p id="rfc.section.A.p.21">This specification introduces the Cache Directive and Warn Code Registries, and defines considerations for new cache directives. 1940 (<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>) 1903 1941 </p> 1904 1942 <h1 id="rfc.section.B"><a href="#rfc.section.B">B.</a> <a id="imported.abnf" href="#imported.abnf">Imported ABNF</a></h1> … … 2025 2063 <li>cache entry <a href="#rfc.iref.c.4">2</a></li> 2026 2064 <li>cache key <a href="#rfc.iref.c.5">2</a></li> 2027 <li>Cache-Control header field <a href="#rfc.xref.header.cache-control.1">3</a>, <a href="#rfc.iref.c.6"><b>7.2</b></a>, <a href="#rfc.xref.header.cache-control.2">9.3</a> </li>2065 <li>Cache-Control header field <a href="#rfc.xref.header.cache-control.1">3</a>, <a href="#rfc.iref.c.6"><b>7.2</b></a>, <a href="#rfc.xref.header.cache-control.2">9.3</a>, <a href="#rfc.xref.header.cache-control.3">A</a>, <a href="#rfc.xref.header.cache-control.4">A</a></li> 2028 2066 <li>cacheable <a href="#rfc.iref.c.3">1.2</a></li> 2029 2067 </ul> 2030 2068 </li> 2031 2069 <li><a id="rfc.index.E" href="#rfc.index.E"><b>E</b></a><ul> 2032 <li>Expires header field <a href="#rfc.xref.header.expires.1">3</a>, <a href="#rfc.xref.header.expires.2">4.1</a>, <a href="#rfc.xref.header.expires.3">4.1.1</a>, <a href="#rfc.iref.e.2"><b>7.3</b></a>, <a href="#rfc.xref.header.expires.4">9.3</a> </li>2070 <li>Expires header field <a href="#rfc.xref.header.expires.1">3</a>, <a href="#rfc.xref.header.expires.2">4.1</a>, <a href="#rfc.xref.header.expires.3">4.1.1</a>, <a href="#rfc.iref.e.2"><b>7.3</b></a>, <a href="#rfc.xref.header.expires.4">9.3</a>, <a href="#rfc.xref.header.expires.5">A</a></li> 2033 2071 <li>explicit expiration time <a href="#rfc.iref.e.1">1.2</a></li> 2034 2072 </ul> … … 2118 2156 </ul> 2119 2157 </li> 2120 <li>Pragma header field <a href="#rfc.xref.header.pragma.1">4</a>, <a href="#rfc.xref.header.pragma.2">7.2</a>, <a href="#rfc.iref.p.5"><b>7.4</b></a>, <a href="#rfc.xref.header.pragma.3">9.3</a> </li>2158 <li>Pragma header field <a href="#rfc.xref.header.pragma.1">4</a>, <a href="#rfc.xref.header.pragma.2">7.2</a>, <a href="#rfc.iref.p.5"><b>7.4</b></a>, <a href="#rfc.xref.header.pragma.3">9.3</a>, <a href="#rfc.xref.header.pragma.4">A</a></li> 2121 2159 <li>private (cache directive) <a href="#rfc.iref.p.3"><b>7.2.2.2</b></a></li> 2122 2160 <li>private cache <a href="#rfc.iref.p.1">1.2</a></li> … … 2164 2202 </li> 2165 2203 <li><a id="rfc.index.W" href="#rfc.index.W"><b>W</b></a><ul> 2166 <li>Warning header field <a href="#rfc.xref.header.warning.1">4.1.4</a>, <a href="#rfc.xref.header.warning.2">4.2.1</a>, <a href="#rfc.xref.header.warning.3">4.4</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>2204 <li>Warning header field <a href="#rfc.xref.header.warning.1">4.1.4</a>, <a href="#rfc.xref.header.warning.2">4.2.1</a>, <a href="#rfc.xref.header.warning.3">4.4</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> 2167 2205 </ul> 2168 2206 </li> -
draft-ietf-httpbis/latest/p6-cache.xml
r2016 r2020 1298 1298 <x:anchor-alias value="cache-response-directive" /> 1299 1299 1300 <section title="public" anchor="cache-response-directive. only-if-cached">1300 <section title="public" anchor="cache-response-directive.public"> 1301 1301 <iref item="public (cache directive)" primary="true" /> 1302 1302 <t> … … 1949 1949 <c>public</c> 1950 1950 <c> 1951 <xref target="cache-response-directive. only-if-cached"/>1951 <xref target="cache-response-directive.public"/> 1952 1952 </c> 1953 1953 <c>s-maxage</c> … … 2402 2402 <section anchor="changes.from.rfc.2616" title="Changes from RFC 2616"> 2403 2403 <t> 2404 Caching-related text has been substantially rewritten for clarity. 2405 </t> 2406 <t> 2404 2407 The algorithm for calculating age is now less conservative. 2405 2408 (<xref target="age.calculations"/>) 2406 2409 </t> 2407 2410 <t> 2411 Caches are now required to handle dates with timezones as if they're 2412 invalid, because it's not possible to accurately guess. 2413 (<xref target="age.calculations"/>) 2414 </t> 2415 <t> 2408 2416 The <x:ref>Content-Location</x:ref> response header field is no longer used 2409 to determine the appropriate response to use .2417 to determine the appropriate response to use when validating. 2410 2418 (<xref target="validation.model" />) 2411 2419 </t> 2412 2420 <t> 2413 Requirements regarding denial of service attack avoidance have been 2421 The algorithm for selecting a cached negotiated response to use has been 2422 clarified in several ways. In particular, it now explicitly allows 2423 header-specific canonicalization when processing selecting header fields. 2424 (<xref target="caching.negotiated.responses" />) 2425 </t> 2426 <t> 2427 Requirements regarding denial of service attack avoidance when performing 2428 invalidation have been clarified. 2429 (<xref target="invalidation.after.updates.or.deletions" />) 2430 </t> 2431 <t> 2432 Cache invalidation only occurs when a successful response is received. 2433 (<xref target="invalidation.after.updates.or.deletions" />) 2434 </t> 2435 <t> 2436 The conditions under which an authenticated response can be cached have been 2414 2437 clarified. 2415 (<xref target="invalidation.after.updates.or.deletions" />) 2438 (<xref target="caching.authenticated.responses" />) 2439 </t> 2440 <t> 2441 The one-year limit on Expires header field values has been removed; instead, 2442 the reasoning for using a sensible value is given. 2443 (<xref target="header.expires" />) 2444 </t> 2445 <t> 2446 The Pragma header field is now only defined for backwards compatibility; 2447 future pragmas are deprecated. 2448 (<xref target="header.pragma" />) 2449 </t> 2450 <t> 2451 Cache directives are explicitly defined to be case-insensitive. 2452 (<xref target="header.cache-control" />) 2453 </t> 2454 <t> 2455 Handling of multiple instances of cache directives when only one is 2456 expected is now defined. 2457 (<xref target="header.cache-control" />) 2458 </t> 2459 <t> 2460 The qualified forms of the private and no-cache cache directives are noted 2461 to not be widely implemented; e.g., "private=foo" is interpreted by many 2462 caches as simply "private". Additionally, the meaning of the qualified 2463 form of no-cache has been clarified. 2464 (<xref target="cache-response-directive" />) 2465 </t> 2466 <t> 2467 The "no-store" cache request directive doesn't apply to responses; i.e., 2468 a cache can satisfy a request with no-store on it, and does not invalidate 2469 it. 2470 (<xref target="cache-request-directive.no-store" />) 2471 </t> 2472 <t> 2473 The meaning of the "public" cache response directive has been refined to 2474 be less vague. 2475 (<xref target="cache-response-directive.public" />) 2476 </t> 2477 <t> 2478 The "no-cache" response cache directive's meaning has been clarified. 2479 (<xref target="cache-response-directive.no-cache" />) 2480 </t> 2481 <t> 2482 New status codes can now define that caches are allowed to use heuristic 2483 freshness with them. 2484 (<xref target="heuristic.freshness" />) 2485 </t> 2486 <t> 2487 Caches are now allow to calculate heuristic freshness for URLs with query 2488 components. 2489 (<xref target="heuristic.freshness" />) 2490 </t> 2491 <t> 2492 Some requirements regarding production of the <x:ref>Warning</x:ref> 2493 header have been relaxed, as it is not widely implemented. 2494 (<xref target="header.warning" />) 2416 2495 </t> 2417 2496 <t> … … 2421 2500 </t> 2422 2501 <t> 2423 This specification introduces the Cache Directive and Warn Code Registries. 2502 This specification introduces the Cache Directive and Warn Code Registries, 2503 and defines considerations for new cache directives. 2424 2504 (<xref target="cache.control.extensions"/> and <xref target="warn.code.extensions"/>) 2425 2505 </t> -
draft-ietf-httpbis/latest/p7-auth.html
r2018 r2020 1045 1045 </div> 1046 1046 <h1 id="rfc.section.A" class="np"><a href="#rfc.section.A">A.</a> <a id="changes.from.rfc.2616" href="#changes.from.rfc.2616">Changes from RFCs 2616 and 2617</a></h1> 1047 <p id="rfc.section.A.p.1">The "realm" parameter is no longer always required; consequently, the ABNF allows challenges without any auth parameters. 1047 <p id="rfc.section.A.p.1">The framework for HTTP Authentication is now defined by this document, rather than RFC 2617.</p> 1048 <p id="rfc.section.A.p.2">The "realm" parameter is no longer always required on challenges; consequently, the ABNF allows challenges without any auth 1049 parameters. (<a href="#access.authentication.framework" title="Access Authentication Framework">Section 2</a>) 1050 </p> 1051 <p id="rfc.section.A.p.3">The "token68" alternative to auth-param lists has been added for consistency with legacy authentication schemes such as "Basic". 1048 1052 (<a href="#access.authentication.framework" title="Access Authentication Framework">Section 2</a>) 1049 1053 </p> 1050 <p id="rfc.section.A.p.2">The "token68" alternative to auth-param lists has been added for consistency with legacy authentication schemes such as "Basic". 1051 (<a href="#access.authentication.framework" title="Access Authentication Framework">Section 2</a>) 1052 </p> 1053 <p id="rfc.section.A.p.3">This specification introduces the Authentication Scheme Registry. (<a href="#authentication.scheme.registry" title="Authentication Scheme Registry">Section 2.3</a>) 1054 <p id="rfc.section.A.p.4">This specification introduces the Authentication Scheme Registry, along with considerations for new authentication schemes. 1055 (<a href="#authentication.scheme.registry" title="Authentication Scheme Registry">Section 2.3</a>) 1054 1056 </p> 1055 1057 <h1 id="rfc.section.B"><a href="#rfc.section.B">B.</a> <a id="imported.abnf" href="#imported.abnf">Imported ABNF</a></h1>
Note: See TracChangeset
for help on using the changeset viewer.