Changeset 2524
- Timestamp:
- 27/12/13 11:58:04 (9 years ago)
- Location:
- draft-ietf-httpbis/latest
- Files:
-
- 2 edited
Legend:
- Unmodified
- Added
- Removed
-
draft-ietf-httpbis/latest/p6-cache.html
r2508 r2524 451 451 } 452 452 @bottom-center { 453 content: "Expires June 16, 2014";453 content: "Expires June 30, 2014"; 454 454 } 455 455 @bottom-right { … … 495 495 <meta name="dct.creator" content="Reschke, J. F."> 496 496 <meta name="dct.identifier" content="urn:ietf:id:draft-ietf-httpbis-p6-cache-latest"> 497 <meta name="dct.issued" scheme="ISO8601" content="2013-12- 13">497 <meta name="dct.issued" scheme="ISO8601" content="2013-12-27"> 498 498 <meta name="dct.replaces" content="urn:ietf:rfc:2616"> 499 499 <meta name="dct.abstract" content="The Hypertext Transfer Protocol (HTTP) is an application-level protocol for distributed, collaborative, hypertext information systems. This document defines HTTP caches and the associated header fields that control cache behavior or indicate cacheable response messages."> … … 521 521 </tr> 522 522 <tr> 523 <td class="left">Expires: June 16, 2014</td>523 <td class="left">Expires: June 30, 2014</td> 524 524 <td class="right">J. Reschke, Editor</td> 525 525 </tr> … … 530 530 <tr> 531 531 <td class="left"></td> 532 <td class="right">December 13, 2013</td>532 <td class="right">December 27, 2013</td> 533 533 </tr> 534 534 </tbody> … … 557 557 in progress”. 558 558 </p> 559 <p>This Internet-Draft will expire on June 16, 2014.</p>559 <p>This Internet-Draft will expire on June 30, 2014.</p> 560 560 </div> 561 561 <div id="rfc.copyrightnotice"> … … 703 703 <div id="shared.and.private.caches"> 704 704 <p id="rfc.section.1.p.3">A <dfn>shared cache</dfn> is a cache that stores responses to be reused by more than one user; shared caches are usually (but not always) deployed as 705 a part of an intermediary. A <dfn>private cache</dfn>, in contrast, is dedicated to a single user .705 a part of an intermediary. A <dfn>private cache</dfn>, in contrast, is dedicated to a single user; often, they are deployed as a component of a user agent. 706 706 </p> 707 707 </div> … … 771 771 <li>the "no-store" cache directive (see <a href="#header.cache-control" id="rfc.xref.header.cache-control.1" title="Cache-Control">Section 5.2</a>) does not appear in request or response header fields, and 772 772 </li> 773 <li>the "private" cacheresponse directive (see <a href="#cache-response-directive.private" title="private">Section 5.2.2.6</a>) does not appear in the response, if the cache is shared, and773 <li>the "private" response directive (see <a href="#cache-response-directive.private" title="private">Section 5.2.2.6</a>) does not appear in the response, if the cache is shared, and 774 774 </li> 775 775 <li>the <a href="p7-auth.html#header.authorization" class="smpl">Authorization</a> header field (see <a href="p7-auth.html#header.authorization" title="Authorization">Section 4.1</a> of <a href="#Part7" id="rfc.xref.Part7.1"><cite title="Hypertext Transfer Protocol (HTTP/1.1): Authentication">[Part7]</cite></a>) does not appear in the request, if the cache is shared, unless the response explicitly allows it (see <a href="#caching.authenticated.responses" title="Storing Responses to Authenticated Requests">Section 3.2</a>), and … … 779 779 <li>contains an <a href="#header.expires" class="smpl">Expires</a> header field (see <a href="#header.expires" id="rfc.xref.header.expires.1" title="Expires">Section 5.3</a>), or 780 780 </li> 781 <li>contains a max-age response cachedirective (see <a href="#cache-response-directive.max-age" title="max-age">Section 5.2.2.8</a>), or782 </li> 783 <li>contains a s-maxage response cachedirective (see <a href="#cache-response-directive.s-maxage" title="s-maxage">Section 5.2.2.9</a>) and the cache is shared, or781 <li>contains a max-age response directive (see <a href="#cache-response-directive.max-age" title="max-age">Section 5.2.2.8</a>), or 782 </li> 783 <li>contains a s-maxage response directive (see <a href="#cache-response-directive.s-maxage" title="s-maxage">Section 5.2.2.9</a>) and the cache is shared, or 784 784 </li> 785 785 <li>contains a Cache Control Extension (see <a href="#cache.control.extensions" title="Cache Control Extensions">Section 5.2.3</a>) that allows it to be cached, or … … 787 787 <li>has a status code that is defined as cacheable by default (see <a href="#heuristic.freshness" title="Calculating Heuristic Freshness">Section 4.2.2</a>), or 788 788 </li> 789 <li>contains a public response cachedirective (see <a href="#cache-response-directive.public" title="public">Section 5.2.2.5</a>).789 <li>contains a public response directive (see <a href="#cache-response-directive.public" title="public">Section 5.2.2.5</a>). 790 790 </li> 791 791 </ul> … … 925 925 </p> 926 926 <p id="rfc.section.4.2.p.5">The primary mechanism for determining freshness is for an origin server to provide an explicit expiration time in the future, 927 using either the <a href="#header.expires" class="smpl">Expires</a> header field (<a href="#header.expires" id="rfc.xref.header.expires.2" title="Expires">Section 5.3</a>) or the max-age response cachedirective (<a href="#cache-response-directive.max-age" title="max-age">Section 5.2.2.8</a>). Generally, origin servers will assign future explicit expiration times to responses in the belief that the representation927 using either the <a href="#header.expires" class="smpl">Expires</a> header field (<a href="#header.expires" id="rfc.xref.header.expires.2" title="Expires">Section 5.3</a>) or the max-age response directive (<a href="#cache-response-directive.max-age" title="max-age">Section 5.2.2.8</a>). Generally, origin servers will assign future explicit expiration times to responses in the belief that the representation 928 928 is not likely to change in a semantically significant way before the expiration time is reached. 929 929 </p> … … 961 961 <p id="rfc.section.4.2.1.p.1">A cache can calculate the freshness lifetime (denoted as freshness_lifetime) of a response by using the first match of: </p> 962 962 <ul> 963 <li>If the cache is shared and the s-maxage response cachedirective (<a href="#cache-response-directive.s-maxage" title="s-maxage">Section 5.2.2.9</a>) is present, use its value, or964 </li> 965 <li>If the max-age response cachedirective (<a href="#cache-response-directive.max-age" title="max-age">Section 5.2.2.8</a>) is present, use its value, or963 <li>If the cache is shared and the s-maxage response directive (<a href="#cache-response-directive.s-maxage" title="s-maxage">Section 5.2.2.9</a>) is present, use its value, or 964 </li> 965 <li>If the max-age response directive (<a href="#cache-response-directive.max-age" title="max-age">Section 5.2.2.8</a>) is present, use its value, or 966 966 </li> 967 967 <li>If the <a href="#header.expires" class="smpl">Expires</a> response header field (<a href="#header.expires" id="rfc.xref.header.expires.3" title="Expires">Section 5.3</a>) is present, use its value minus the value of the <a href="p2-semantics.html#header.date" class="smpl">Date</a> response header field, or … … 984 984 in <a href="#response.cacheability" title="Storing Responses in Caches">Section 3</a>, this means that, effectively, heuristics can only be used on responses without explicit freshness whose status codes are 985 985 defined as cacheable by default (see <a href="p2-semantics.html#overview.of.status.codes" title="Overview of Status Codes">Section 6.1</a> of <a href="#Part2" id="rfc.xref.Part2.5"><cite title="Hypertext Transfer Protocol (HTTP/1.1): Semantics and Content">[Part2]</cite></a>), and those responses without explicit freshness that have been marked as explicitly cacheable (e.g., with a "public" response 986 cachedirective).986 directive). 987 987 </p> 988 988 <p id="rfc.section.4.2.2.p.3">If the response has a <a href="p4-conditional.html#header.last-modified" class="smpl">Last-Modified</a> header field (<a href="p4-conditional.html#header.last-modified" title="Last-Modified">Section 2.2</a> of <a href="#Part4" id="rfc.xref.Part4.1"><cite title="Hypertext Transfer Protocol (HTTP/1.1): Conditional Requests">[Part4]</cite></a>), caches are encouraged to use a heuristic expiration value that is no more than some fraction of the interval since that … … 1592 1592 Warning: 112 - "network down" "Sat, 25 Aug 2012 23:34:45 GMT" 1593 1593 1594 </pre><p id="rfc.section.5.5.p.10">If a recipient that uses, evaluates, or displays Warning header fields receives a warn-date that is different from the <a href="p2-semantics.html#header.date" class="smpl">Date</a> value in the same message, the recipient <em class="bcp14">MUST</em> exclude the warning-value containing that warn-date before storing, forwarding, or using the message. This allows recipients 1594 </pre><p id="rfc.section.5.5.p.10">Warnings have accompanying warn-text that describes the error, e.g., for logging. It is advisory only, and its content does 1595 not affect interpretation of the warn-code. 1596 </p> 1597 <p id="rfc.section.5.5.p.11">If a recipient that uses, evaluates, or displays Warning header fields receives a warn-date that is different from the <a href="p2-semantics.html#header.date" class="smpl">Date</a> value in the same message, the recipient <em class="bcp14">MUST</em> exclude the warning-value containing that warn-date before storing, forwarding, or using the message. This allows recipients 1595 1598 to exclude warning-values that were improperly retained after a cache validation. If all of the warning-values are excluded, 1596 1599 the recipient <em class="bcp14">MUST</em> exclude the Warning header field as well. 1597 1600 </p> 1598 <p id="rfc.section.5.5.p.1 1">The following warn-codes are defined by this specification, each with a recommended warn-text in English, and a description1601 <p id="rfc.section.5.5.p.12">The following warn-codes are defined by this specification, each with a recommended warn-text in English, and a description 1599 1602 of its meaning. The procedure for defining additional warn codes is described in <a href="#warn.code.registry.procedure" title="Procedure">Section 7.2.1</a>. 1600 1603 </p> … … 1931 1934 as sensitive information. 1932 1935 </p> 1933 <p id="rfc.section.8.p.3">Furthermore, the very use of a cache can bring about privacy concerns. For example, if two users share a cache, and the first 1936 <p id="rfc.section.8.p.3">In particular, various attacks might be amplified by being stored in a shared cache; such "cache poisoning" attacks use the 1937 cache to distribute a malicious payload to many clients, and are especially effective when an attacker can use implmentation 1938 flaws, elevated priviledges or other techniques to insert such a response into a cache. One common attack vector for cache 1939 poisoning is to exploit differences in message parsing on proxies and in user agents; see <a href="p1-messaging.html#message.body.length" title="Message Body Length">Section 3.3.3</a> of <a href="#Part1" id="rfc.xref.Part1.12"><cite title="Hypertext Transfer Protocol (HTTP/1.1): Message Syntax and Routing">[Part1]</cite></a> for the relevant requirements. 1940 </p> 1941 <p id="rfc.section.8.p.4">Likewise, implementation flaws (as well as misunderstanding of cache operation) might lead to caching of sensitive information 1942 (e.g., authentication credentials) that is thought to be private, exposing it to unauthorized parties. 1943 </p> 1944 <p id="rfc.section.8.p.5">Furthermore, the very use of a cache can bring about privacy concerns. For example, if two users share a cache, and the first 1934 1945 one browses to a site, the second may be able to detect that the other has been to that site, because the resources from it 1935 1946 load more quickly, thanks to the cache. 1936 </p>1937 <p id="rfc.section.8.p.4">Implementation flaws might allow attackers to insert content into a cache ("cache poisoning"), leading to compromise of clients1938 that trust that content. Because of their nature, these attacks are difficult to mitigate.1939 </p>1940 <p id="rfc.section.8.p.5">Likewise, implementation flaws (as well as misunderstanding of cache operation) might lead to caching of sensitive information1941 (e.g., authentication credentials) that is thought to be private, exposing it to unauthorized parties.1942 1947 </p> 1943 1948 <p id="rfc.section.8.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 … … 1948 1953 <div id="acks"> 1949 1954 <h1 id="rfc.section.9"><a href="#rfc.section.9">9.</a> <a href="#acks">Acknowledgments</a></h1> 1950 <p id="rfc.section.9.p.1">See <a href="p1-messaging.html#acks" title="Acknowledgments">Section 10</a> of <a href="#Part1" id="rfc.xref.Part1.1 2"><cite title="Hypertext Transfer Protocol (HTTP/1.1): Message Syntax and Routing">[Part1]</cite></a>.1955 <p id="rfc.section.9.p.1">See <a href="p1-messaging.html#acks" title="Acknowledgments">Section 10</a> of <a href="#Part1" id="rfc.xref.Part1.13"><cite title="Hypertext Transfer Protocol (HTTP/1.1): Message Syntax and Routing">[Part1]</cite></a>. 1951 1956 </p> 1952 1957 </div> … … 2061 2066 one is expected is now defined. (<a href="#header.cache-control" id="rfc.xref.header.cache-control.3" title="Cache-Control">Section 5.2</a>) 2062 2067 </p> 2063 <p id="rfc.section.A.p.10">The "no-store" cache request directive doesn't apply to responses; i.e., a cache can satisfy a request with no-store on it,2064 anddoes not invalidate it. (<a href="#cache-request-directive.no-store" title="no-store">Section 5.2.1.5</a>)2068 <p id="rfc.section.A.p.10">The "no-store" request directive doesn't apply to responses; i.e., a cache can satisfy a request with no-store on it, and 2069 does not invalidate it. (<a href="#cache-request-directive.no-store" title="no-store">Section 5.2.1.5</a>) 2065 2070 </p> 2066 2071 <p id="rfc.section.A.p.11">The qualified forms of the private and no-cache cache directives are noted to not be widely implemented; e.g., "private=foo" … … 2068 2073 (<a href="#cache-response-directive" title="Response Cache-Control Directives">Section 5.2.2</a>) 2069 2074 </p> 2070 <p id="rfc.section.A.p.12">The "no-cache" response cachedirective's meaning has been clarified. (<a href="#cache-response-directive.no-cache" title="no-cache">Section 5.2.2.2</a>)2075 <p id="rfc.section.A.p.12">The "no-cache" response directive's meaning has been clarified. (<a href="#cache-response-directive.no-cache" title="no-cache">Section 5.2.2.2</a>) 2071 2076 </p> 2072 2077 <p id="rfc.section.A.p.13">The one-year limit on <a href="#header.expires" class="smpl">Expires</a> header field values has been removed; instead, the reasoning for using a sensible value is given. (<a href="#header.expires" id="rfc.xref.header.expires.5" title="Expires">Section 5.3</a>) … … 2086 2091 character). 2087 2092 </p> 2088 <p id="rfc.section.B.p.2">The rules below are defined in <a href="#Part1" id="rfc.xref.Part1.1 3"><cite title="Hypertext Transfer Protocol (HTTP/1.1): Message Syntax and Routing">[Part1]</cite></a>:2089 </p> 2090 <div id="rfc.figure.u.15"></div><pre class="inline"> <a href="#imported.abnf" class="smpl">OWS</a> = <OWS, defined in <a href="#Part1" id="rfc.xref.Part1.1 4"><cite title="Hypertext Transfer Protocol (HTTP/1.1): Message Syntax and Routing">[Part1]</cite></a>, <a href="p1-messaging.html#whitespace" title="Whitespace">Section 3.2.3</a>>2091 <a href="#imported.abnf" class="smpl">field-name</a> = <field-name, defined in <a href="#Part1" id="rfc.xref.Part1.1 5"><cite title="Hypertext Transfer Protocol (HTTP/1.1): Message Syntax and Routing">[Part1]</cite></a>, <a href="p1-messaging.html#header.fields" title="Header Fields">Section 3.2</a>>2092 <a href="#imported.abnf" class="smpl">quoted-string</a> = <quoted-string, defined in <a href="#Part1" id="rfc.xref.Part1.1 6"><cite title="Hypertext Transfer Protocol (HTTP/1.1): Message Syntax and Routing">[Part1]</cite></a>, <a href="p1-messaging.html#field.components" title="Field value components">Section 3.2.6</a>>2093 <a href="#imported.abnf" class="smpl">token</a> = <token, defined in <a href="#Part1" id="rfc.xref.Part1.1 7"><cite title="Hypertext Transfer Protocol (HTTP/1.1): Message Syntax and Routing">[Part1]</cite></a>, <a href="p1-messaging.html#field.components" title="Field value components">Section 3.2.6</a>>2094 2095 <a href="#imported.abnf" class="smpl">port</a> = <port, defined in <a href="#Part1" id="rfc.xref.Part1.1 8"><cite title="Hypertext Transfer Protocol (HTTP/1.1): Message Syntax and Routing">[Part1]</cite></a>, <a href="p1-messaging.html#uri" title="Uniform Resource Identifiers">Section 2.7</a>>2096 <a href="#imported.abnf" class="smpl">pseudonym</a> = <pseudonym, defined in <a href="#Part1" id="rfc.xref.Part1. 19"><cite title="Hypertext Transfer Protocol (HTTP/1.1): Message Syntax and Routing">[Part1]</cite></a>, <a href="p1-messaging.html#header.via" title="Via">Section 5.7.1</a>>2097 <a href="#imported.abnf" class="smpl">uri-host</a> = <uri-host, defined in <a href="#Part1" id="rfc.xref.Part1.2 0"><cite title="Hypertext Transfer Protocol (HTTP/1.1): Message Syntax and Routing">[Part1]</cite></a>, <a href="p1-messaging.html#uri" title="Uniform Resource Identifiers">Section 2.7</a>>2093 <p id="rfc.section.B.p.2">The rules below are defined in <a href="#Part1" id="rfc.xref.Part1.14"><cite title="Hypertext Transfer Protocol (HTTP/1.1): Message Syntax and Routing">[Part1]</cite></a>: 2094 </p> 2095 <div id="rfc.figure.u.15"></div><pre class="inline"> <a href="#imported.abnf" class="smpl">OWS</a> = <OWS, defined in <a href="#Part1" id="rfc.xref.Part1.15"><cite title="Hypertext Transfer Protocol (HTTP/1.1): Message Syntax and Routing">[Part1]</cite></a>, <a href="p1-messaging.html#whitespace" title="Whitespace">Section 3.2.3</a>> 2096 <a href="#imported.abnf" class="smpl">field-name</a> = <field-name, defined in <a href="#Part1" id="rfc.xref.Part1.16"><cite title="Hypertext Transfer Protocol (HTTP/1.1): Message Syntax and Routing">[Part1]</cite></a>, <a href="p1-messaging.html#header.fields" title="Header Fields">Section 3.2</a>> 2097 <a href="#imported.abnf" class="smpl">quoted-string</a> = <quoted-string, defined in <a href="#Part1" id="rfc.xref.Part1.17"><cite title="Hypertext Transfer Protocol (HTTP/1.1): Message Syntax and Routing">[Part1]</cite></a>, <a href="p1-messaging.html#field.components" title="Field value components">Section 3.2.6</a>> 2098 <a href="#imported.abnf" class="smpl">token</a> = <token, defined in <a href="#Part1" id="rfc.xref.Part1.18"><cite title="Hypertext Transfer Protocol (HTTP/1.1): Message Syntax and Routing">[Part1]</cite></a>, <a href="p1-messaging.html#field.components" title="Field value components">Section 3.2.6</a>> 2099 2100 <a href="#imported.abnf" class="smpl">port</a> = <port, defined in <a href="#Part1" id="rfc.xref.Part1.19"><cite title="Hypertext Transfer Protocol (HTTP/1.1): Message Syntax and Routing">[Part1]</cite></a>, <a href="p1-messaging.html#uri" title="Uniform Resource Identifiers">Section 2.7</a>> 2101 <a href="#imported.abnf" class="smpl">pseudonym</a> = <pseudonym, defined in <a href="#Part1" id="rfc.xref.Part1.20"><cite title="Hypertext Transfer Protocol (HTTP/1.1): Message Syntax and Routing">[Part1]</cite></a>, <a href="p1-messaging.html#header.via" title="Via">Section 5.7.1</a>> 2102 <a href="#imported.abnf" class="smpl">uri-host</a> = <uri-host, defined in <a href="#Part1" id="rfc.xref.Part1.21"><cite title="Hypertext Transfer Protocol (HTTP/1.1): Message Syntax and Routing">[Part1]</cite></a>, <a href="p1-messaging.html#uri" title="Uniform Resource Identifiers">Section 2.7</a>> 2098 2103 </pre><p id="rfc.section.B.p.4">The rules below are defined in other parts:</p> 2099 2104 <div id="rfc.figure.u.16"></div><pre class="inline"> <a href="#imported.abnf" class="smpl">HTTP-date</a> = <HTTP-date, defined in <a href="#Part2" id="rfc.xref.Part2.10"><cite title="Hypertext Transfer Protocol (HTTP/1.1): Semantics and Content">[Part2]</cite></a>, <a href="p2-semantics.html#http.date" title="Date/Time Formats">Section 7.1.1.1</a>> … … 2101 2106 <div id="collected.abnf"> 2102 2107 <h1 id="rfc.section.C"><a href="#rfc.section.C">C.</a> <a href="#collected.abnf">Collected ABNF</a></h1> 2103 <p id="rfc.section.C.p.1">In the collected ABNF below, list rules are expanded as per <a href="p1-messaging.html#notation" title="Syntax Notation">Section 1.2</a> of <a href="#Part1" id="rfc.xref.Part1.2 1"><cite title="Hypertext Transfer Protocol (HTTP/1.1): Message Syntax and Routing">[Part1]</cite></a>.2108 <p id="rfc.section.C.p.1">In the collected ABNF below, list rules are expanded as per <a href="p1-messaging.html#notation" title="Syntax Notation">Section 1.2</a> of <a href="#Part1" id="rfc.xref.Part1.22"><cite title="Hypertext Transfer Protocol (HTTP/1.1): Message Syntax and Routing">[Part1]</cite></a>. 2104 2109 </p> 2105 2110 <div id="rfc.figure.u.17"></div><pre class="inline"><a href="#header.age" class="smpl">Age</a> = delta-seconds … … 2163 2168 <div id="changes.since.25"> 2164 2169 <h2 id="rfc.section.D.2"><a href="#rfc.section.D.2">D.2</a> <a href="#changes.since.25">Since draft-ietf-httpbis-p6-cache-25</a></h2> 2165 <p id="rfc.section.D.2.p.1">None yet.</p> 2170 <p id="rfc.section.D.2.p.1">Partly closed issues: </p> 2171 <ul> 2172 <li><<a href="http://tools.ietf.org/wg/httpbis/trac/ticket/535">http://tools.ietf.org/wg/httpbis/trac/ticket/535</a>>: "IESG ballot on draft-ietf-httpbis-p6-cache-25" 2173 </li> 2174 </ul> 2166 2175 </div> 2167 2176 </div> … … 2260 2269 </li> 2261 2270 <li><a id="rfc.index.P" href="#rfc.index.P"><b>P</b></a><ul> 2262 <li><em>Part1</em> <a href="#rfc.xref.Part1.1">1.1</a>, <a href="#rfc.xref.Part1.2">1.2</a>, <a href="#rfc.xref.Part1.3">3.1</a>, <a href="#rfc.xref.Part1.4">4</a>, <a href="#rfc.xref.Part1.5">4.1</a>, <a href="#rfc.xref.Part1.6">4.4</a>, <a href="#rfc.xref.Part1.7">4.4</a>, <a href="#rfc.xref.Part1.8">4.4</a>, <a href="#rfc.xref.Part1.9">5.2.1.6</a>, <a href="#rfc.xref.Part1.10">5.2.2.4</a>, <a href="#rfc.xref.Part1.11">8</a>, <a href="#rfc.xref.Part1.12"> 9</a>, <a href="#Part1"><b>10.1</b></a>, <a href="#rfc.xref.Part1.13">B</a>, <a href="#rfc.xref.Part1.14">B</a>, <a href="#rfc.xref.Part1.15">B</a>, <a href="#rfc.xref.Part1.16">B</a>, <a href="#rfc.xref.Part1.17">B</a>, <a href="#rfc.xref.Part1.18">B</a>, <a href="#rfc.xref.Part1.19">B</a>, <a href="#rfc.xref.Part1.20">B</a>, <a href="#rfc.xref.Part1.21">C</a><ul>2263 <li><em>Section 1.2</em> <a href="#rfc.xref.Part1.2 1">C</a></li>2271 <li><em>Part1</em> <a href="#rfc.xref.Part1.1">1.1</a>, <a href="#rfc.xref.Part1.2">1.2</a>, <a href="#rfc.xref.Part1.3">3.1</a>, <a href="#rfc.xref.Part1.4">4</a>, <a href="#rfc.xref.Part1.5">4.1</a>, <a href="#rfc.xref.Part1.6">4.4</a>, <a href="#rfc.xref.Part1.7">4.4</a>, <a href="#rfc.xref.Part1.8">4.4</a>, <a href="#rfc.xref.Part1.9">5.2.1.6</a>, <a href="#rfc.xref.Part1.10">5.2.2.4</a>, <a href="#rfc.xref.Part1.11">8</a>, <a href="#rfc.xref.Part1.12">8</a>, <a href="#rfc.xref.Part1.13">9</a>, <a href="#Part1"><b>10.1</b></a>, <a href="#rfc.xref.Part1.14">B</a>, <a href="#rfc.xref.Part1.15">B</a>, <a href="#rfc.xref.Part1.16">B</a>, <a href="#rfc.xref.Part1.17">B</a>, <a href="#rfc.xref.Part1.18">B</a>, <a href="#rfc.xref.Part1.19">B</a>, <a href="#rfc.xref.Part1.20">B</a>, <a href="#rfc.xref.Part1.21">B</a>, <a href="#rfc.xref.Part1.22">C</a><ul> 2272 <li><em>Section 1.2</em> <a href="#rfc.xref.Part1.22">C</a></li> 2264 2273 <li><em>Section 2.5</em> <a href="#rfc.xref.Part1.1">1.1</a></li> 2265 <li><em>Section 2.7</em> <a href="#rfc.xref.Part1.18">B</a>, <a href="#rfc.xref.Part1.20">B</a></li> 2266 <li><em>Section 3.2</em> <a href="#rfc.xref.Part1.5">4.1</a>, <a href="#rfc.xref.Part1.15">B</a></li> 2267 <li><em>Section 3.2.3</em> <a href="#rfc.xref.Part1.14">B</a></li> 2268 <li><em>Section 3.2.6</em> <a href="#rfc.xref.Part1.16">B</a>, <a href="#rfc.xref.Part1.17">B</a></li> 2274 <li><em>Section 2.7</em> <a href="#rfc.xref.Part1.19">B</a>, <a href="#rfc.xref.Part1.21">B</a></li> 2275 <li><em>Section 3.2</em> <a href="#rfc.xref.Part1.5">4.1</a>, <a href="#rfc.xref.Part1.16">B</a></li> 2276 <li><em>Section 3.2.3</em> <a href="#rfc.xref.Part1.15">B</a></li> 2277 <li><em>Section 3.2.6</em> <a href="#rfc.xref.Part1.17">B</a>, <a href="#rfc.xref.Part1.18">B</a></li> 2278 <li><em>Section 3.3.3</em> <a href="#rfc.xref.Part1.12">8</a></li> 2269 2279 <li><em>Section 5.5</em> <a href="#rfc.xref.Part1.4">4</a>, <a href="#rfc.xref.Part1.6">4.4</a>, <a href="#rfc.xref.Part1.7">4.4</a>, <a href="#rfc.xref.Part1.8">4.4</a></li> 2270 <li><em>Section 5.7.1</em> <a href="#rfc.xref.Part1. 19">B</a></li>2280 <li><em>Section 5.7.1</em> <a href="#rfc.xref.Part1.20">B</a></li> 2271 2281 <li><em>Section 5.7.2</em> <a href="#rfc.xref.Part1.9">5.2.1.6</a>, <a href="#rfc.xref.Part1.10">5.2.2.4</a></li> 2272 2282 <li><em>Section 7</em> <a href="#rfc.xref.Part1.2">1.2</a></li> 2273 <li><em>Section 10</em> <a href="#rfc.xref.Part1.1 2">9</a></li>2283 <li><em>Section 10</em> <a href="#rfc.xref.Part1.13">9</a></li> 2274 2284 </ul> 2275 2285 </li> -
draft-ietf-httpbis/latest/p6-cache.xml
r2523 r2524 55 55 <!ENTITY status.2xx "<xref target='Part2' x:rel='#status.2xx' xmlns:x='http://purl.org/net/xml2rfc/ext'/>"> 56 56 <!ENTITY transformations "<xref target='Part1' x:rel='#message.transformations' xmlns:x='http://purl.org/net/xml2rfc/ext'/>"> 57 <!ENTITY body.length "<xref target='Part1' x:rel='#message.body.len th' xmlns:x='http://purl.org/net/xml2rfc/ext'/>">57 <!ENTITY body.length "<xref target='Part1' x:rel='#message.body.length' xmlns:x='http://purl.org/net/xml2rfc/ext'/>"> 58 58 ]> 59 59 <?rfc toc="yes" ?> … … 2700 2700 <section title="Since draft-ietf-httpbis-p6-cache-25" anchor="changes.since.25"> 2701 2701 <t> 2702 None yet. 2702 Partly closed issues: 2703 <list style="symbols"> 2704 <t> 2705 <eref target="http://tools.ietf.org/wg/httpbis/trac/ticket/535"/>: 2706 "IESG ballot on draft-ietf-httpbis-p6-cache-25" 2707 </t> 2708 </list> 2703 2709 </t> 2704 2710 </section>
Note: See TracChangeset
for help on using the changeset viewer.