Source: https://trac.ietf.org/trac/httpbis/browser/draft-ietf-httpbis/latest/p6-cache.html?rev=1519
Timestamp: 2019-10-22 23:45:46
Document Index: 196245566

Matched Legal Cases: ['art 6', 'art 6', 'art 6', 'art4', 'art4', 'art 4', 'art4', 'art4', 'art4', 'art 4', 'art4', 'art4', 'art4', 'art 4', 'art4', 'art1', 'art1', 'art 1', 'art1', 'art1', 'art1', 'art 1', 'art1', 'art1', 'art1', 'art 1', 'art1', 'art1', 'art1', 'art 1', 'art1', 'art1', 'art1', 'art 1', 'art1', 'art2', 'art2', 'art 2', 'art2', 'art1', 'art1', 'art 1', 'art1', 'art1', 'art1', 'art 1', 'art1', 'art1', 'art1', 'art 1', 'art1', 'art2', 'art2', 'art 2', 'art2', 'art7', 'art7', 'art 7', 'art7', 'art1', 'art1', 'art 1', 'art1', 'art5', 'art5', 'art 5', 'art5', 'art1', 'art1', 'art 1', 'art1', 'art2', 'art2', 'art 2', 'art2', 'art2', 'art2', 'art 2', 'art2', 'art4', 'art4', 'art 4', 'art4', 'art2', 'art2', 'art 2', 'art2', 'art4', 'art4', 'art 4', 'art4', 'art2', 'art2', 'art 2', 'art2', 'art1', 'art1', 'art 1', 'art1', 'art1', 'art1', 'art 1', 'art1', 'art1', 'art1', 'art 1', 'art1', 'art7', 'art7', 'art 7', 'art7', 'art1', 'art1', 'art 1', 'art1', 'art5', 'art5', 'art 5', 'art5', 'art5', 'art5', 'art 5', 'art5', 'art2', 'art2', 'art 2', 'art2', 'art1', 'art1', 'art 1', 'art1', 'art 1', 'art 2', 'art 4', 'art 5', 'art 7', 'art2', 'art1', 'art1', 'art1', 'art1', 'art1', 'art1', 'art1', 'art1', 'art1', 'art1', 'art1', 'art1', 'art1', 'art1', 'art1', 'art1', 'art1', 'art1', 'art1', 'art1', 'art1', 'art1', 'art1', 'art1', 'art1', 'art1', 'art1', 'art1', 'art1', 'art1', 'art1', 'art1', 'art1', 'art1', 'art1', 'art1', 'art1', 'art1', 'art1', 'art1', 'art2', 'art2', 'art2', 'art2', 'art2', 'art2', 'art2', 'art2', 'art2', 'art2', 'art2', 'art2', 'art2', 'art2', 'art2', 'art4', 'art4', 'art4', 'art4', 'art4', 'art4', 'art4', 'art4', 'art4', 'art4', 'art4', 'art5', 'art5', 'art5', 'art5', 'art5', 'art5', 'art7', 'art7', 'art7', 'art7', 'art7', 'art7']

source: draft-ietf-httpbis/latest/p6-cache.html @ 1519
Last change on this file since 1519 was 1519, checked in by fielding@…, 8 years ago
update generated HTML
File size: 187.9 KB
content: "January 2012";
content: "Expires August 1, 2012";
<link rel="Chapter" title="2 Cache Operation" href="#rfc.section.2">
<link rel="Chapter" title="3 Header Field Definitions" href="#rfc.section.3">
<link rel="Chapter" title="4 History Lists" href="#rfc.section.4">
<link href="p5-range.html" rel="prev">
<link href="p7-auth.html" rel="next">
<meta name="generator" content="http://greenbytes.de/tech/webdav/rfc2629.xslt, Revision 1.561, 2011-12-24 13:06:50, XSLT vendor: SAXON 8.9 from Saxonica http://www.saxonica.com/">
<meta name="dct.issued" scheme="ISO8601" content="2012-01-29">
<meta name="description" content="The Hypertext Transfer Protocol (HTTP) is an application-level protocol for distributed, collaborative, hypertext information systems. HTTP has been in use by the World Wide Web global information initiative since 1990. This document is Part 6 of the seven-part specification that defines the protocol referred to as &#34;HTTP/1.1&#34; and, taken together, obsoletes RFC 2616. Part 6 defines requirements on HTTP caches and the associated header fields that control cache behavior or indicate cacheable response messages.">
<td class="left">Expires: August 1, 2012</td>
<td class="right">M. Nottingham, Editor</td>
<td class="right">Rackspace</td>
<td class="right">January 29, 2012</td>
<p>Part 6 defines requirements on HTTP caches and the associated header fields that control cache behavior or indicate cacheable
response messages.
<p>The changes in this draft are summarized in <a href="#changes.since.18" title="Since draft-ietf-httpbis-p6-cache-18">Appendix&nbsp;C.20</a>.
<p>This Internet-Draft will expire on August 1, 2012.</p>
<li>1.3&nbsp;&nbsp;&nbsp;<a href="#intro.conformance.and.error.handling">Conformance and Error Handling</a></li>
<li>1.4&nbsp;&nbsp;&nbsp;<a href="#notation">Syntax Notation</a><ul>
<li>1.4.1&nbsp;&nbsp;&nbsp;<a href="#core.rules">Core Rules</a></li>
<li>1.4.2&nbsp;&nbsp;&nbsp;<a href="#abnf.dependencies">ABNF Rules defined in other Parts of the Specification</a></li>
<li>1.5&nbsp;&nbsp;&nbsp;<a href="#delta-seconds">Delta Seconds</a></li>
<li>2.&nbsp;&nbsp;&nbsp;<a href="#caching.overview">Cache Operation</a><ul>
<li>2.1&nbsp;&nbsp;&nbsp;<a href="#response.cacheability">Response Cacheability</a></li>
<li>2.2&nbsp;&nbsp;&nbsp;<a href="#constructing.responses.from.caches">Constructing Responses from Caches</a></li>
<li>2.3&nbsp;&nbsp;&nbsp;<a href="#expiration.model">Freshness Model</a><ul>
<li>2.3.1&nbsp;&nbsp;&nbsp;<a href="#calculating.freshness.lifetime">Calculating Freshness Lifetime</a><ul>
<li>2.3.1.1&nbsp;&nbsp;&nbsp;<a href="#heuristic.freshness">Calculating Heuristic Freshness</a></li>
<li>2.3.2&nbsp;&nbsp;&nbsp;<a href="#age.calculations">Calculating Age</a></li>
<li>2.3.3&nbsp;&nbsp;&nbsp;<a href="#serving.stale.responses">Serving Stale Responses</a></li>
<li>2.4&nbsp;&nbsp;&nbsp;<a href="#validation.model">Validation Model</a><ul>
<li>2.4.1&nbsp;&nbsp;&nbsp;<a href="#freshening.responses">Freshening Responses</a></li>
<li>2.5&nbsp;&nbsp;&nbsp;<a href="#invalidation.after.updates.or.deletions">Request Methods that Invalidate</a></li>
<li>2.6&nbsp;&nbsp;&nbsp;<a href="#caching.authenticated.responses">Shared Caching of Authenticated Responses</a></li>
<li>2.7&nbsp;&nbsp;&nbsp;<a href="#caching.negotiated.responses">Caching Negotiated Responses</a></li>
<li>2.8&nbsp;&nbsp;&nbsp;<a href="#combining.responses">Combining Partial Content</a></li>
<li>3.&nbsp;&nbsp;&nbsp;<a href="#header.field.definitions">Header Field Definitions</a><ul>
<li>3.1&nbsp;&nbsp;&nbsp;<a href="#header.age">Age</a></li>
<li>3.2&nbsp;&nbsp;&nbsp;<a href="#header.cache-control">Cache-Control</a><ul>
<li>3.2.1&nbsp;&nbsp;&nbsp;<a href="#cache-request-directive">Request Cache-Control Directives</a></li>
<li>3.2.2&nbsp;&nbsp;&nbsp;<a href="#cache-response-directive">Response Cache-Control Directives</a></li>
<li>3.2.3&nbsp;&nbsp;&nbsp;<a href="#cache.control.extensions">Cache Control Extensions</a></li>
<li>3.3&nbsp;&nbsp;&nbsp;<a href="#header.expires">Expires</a></li>
<li>3.4&nbsp;&nbsp;&nbsp;<a href="#header.pragma">Pragma</a></li>
<li>3.5&nbsp;&nbsp;&nbsp;<a href="#header.vary">Vary</a></li>
<li>3.6&nbsp;&nbsp;&nbsp;<a href="#header.warning">Warning</a><ul>
<li>3.6.1&nbsp;&nbsp;&nbsp;<a href="#warn.110">110 Response is Stale</a></li>
<li>3.6.2&nbsp;&nbsp;&nbsp;<a href="#warn.111">111 Revalidation Failed</a></li>
<li>3.6.3&nbsp;&nbsp;&nbsp;<a href="#warn.112">112 Disconnected Operation</a></li>
<li>3.6.4&nbsp;&nbsp;&nbsp;<a href="#warn.113">113 Heuristic Expiration</a></li>
<li>3.6.5&nbsp;&nbsp;&nbsp;<a href="#warn.199">199 Miscellaneous Warning</a></li>
<li>3.6.6&nbsp;&nbsp;&nbsp;<a href="#warn.214">214 Transformation Applied</a></li>
<li>3.6.7&nbsp;&nbsp;&nbsp;<a href="#warn.299">299 Miscellaneous Persistent Warning</a></li>
<li>3.6.8&nbsp;&nbsp;&nbsp;<a href="#warn.code.extensions">Warn Code Extensions</a></li>
<li>4.&nbsp;&nbsp;&nbsp;<a href="#history.lists">History Lists</a></li>
<li>5.1&nbsp;&nbsp;&nbsp;<a href="#cache.directive.registration">Cache Directive Registry</a></li>
<li>5.2&nbsp;&nbsp;&nbsp;<a href="#warn.code.registration">Warn Code Registry</a></li>
<li>5.3&nbsp;&nbsp;&nbsp;<a href="#header.field.registration">Header Field Registration</a></li>
<li>C.2&nbsp;&nbsp;&nbsp;<a href="#rfc.section.C.2">Since draft-ietf-httpbis-p6-cache-00</a></li>
<li>C.3&nbsp;&nbsp;&nbsp;<a href="#rfc.section.C.3">Since draft-ietf-httpbis-p6-cache-01</a></li>
<li>C.4&nbsp;&nbsp;&nbsp;<a href="#changes.since.02">Since draft-ietf-httpbis-p6-cache-02</a></li>
<li>C.5&nbsp;&nbsp;&nbsp;<a href="#changes.since.03">Since draft-ietf-httpbis-p6-cache-03</a></li>
<li>C.6&nbsp;&nbsp;&nbsp;<a href="#changes.since.04">Since draft-ietf-httpbis-p6-cache-04</a></li>
<li>C.7&nbsp;&nbsp;&nbsp;<a href="#changes.since.05">Since draft-ietf-httpbis-p6-cache-05</a></li>
<li>C.8&nbsp;&nbsp;&nbsp;<a href="#changes.since.06">Since draft-ietf-httpbis-p6-cache-06</a></li>
<li>C.9&nbsp;&nbsp;&nbsp;<a href="#changes.since.07">Since draft-ietf-httpbis-p6-cache-07</a></li>
<li>C.10&nbsp;&nbsp;&nbsp;<a href="#changes.since.08">Since draft-ietf-httpbis-p6-cache-08</a></li>
<li>C.11&nbsp;&nbsp;&nbsp;<a href="#changes.since.09">Since draft-ietf-httpbis-p6-cache-09</a></li>
<li>C.12&nbsp;&nbsp;&nbsp;<a href="#changes.since.10">Since draft-ietf-httpbis-p6-cache-10</a></li>
<li>C.13&nbsp;&nbsp;&nbsp;<a href="#changes.since.11">Since draft-ietf-httpbis-p6-cache-11</a></li>
<li>C.14&nbsp;&nbsp;&nbsp;<a href="#changes.since.12">Since draft-ietf-httpbis-p6-cache-12</a></li>
<li>C.15&nbsp;&nbsp;&nbsp;<a href="#changes.since.13">Since draft-ietf-httpbis-p6-cache-13</a></li>
<li>C.16&nbsp;&nbsp;&nbsp;<a href="#changes.since.14">Since draft-ietf-httpbis-p6-cache-14</a></li>
<li>C.17&nbsp;&nbsp;&nbsp;<a href="#changes.since.15">Since draft-ietf-httpbis-p6-cache-15</a></li>
<li>C.18&nbsp;&nbsp;&nbsp;<a href="#changes.since.16">Since draft-ietf-httpbis-p6-cache-16</a></li>
<li>C.19&nbsp;&nbsp;&nbsp;<a href="#changes.since.17">Since draft-ietf-httpbis-p6-cache-17</a></li>
<li>C.20&nbsp;&nbsp;&nbsp;<a href="#changes.since.18">Since draft-ietf-httpbis-p6-cache-18</a></li>
<p id="rfc.section.1.p.1">HTTP is typically used for distributed information systems, where performance can be improved by the use of response caches.
This document defines aspects of HTTP/1.1 related to caching and reusing response messages.
Any client or server <em class="bcp14">MAY</em> employ a cache, though a cache cannot be used by a server that is acting as a tunnel.
<p id="rfc.section.1.1.p.2">The goal of caching in HTTP/1.1 is to significantly improve performance by reusing a prior response message to satisfy a current
request. A stored response is considered "fresh", as defined in <a href="#expiration.model" title="Freshness Model">Section&nbsp;2.3</a>, if the response can be reused without "validation" (checking with the origin server to see if the cached response remains
valid for this request). A fresh cache response can therefore reduce both latency and network transfers each time it is reused.
When a cached response is not fresh, it might still be reusable if it can be freshened by validation (<a href="#validation.model" title="Validation Model">Section&nbsp;2.4</a>) or if the origin is unavailable.
<p id="rfc.section.1.2.p.2"> <span id="rfc.iref.c.2"></span> <dfn>cache</dfn>
<li>A conformant implementation of a HTTP cache. Note that this implies an HTTP/1.1 cache; this specification does not define
conformance for HTTP/1.0 caches.
<div id="shared.and.non-shared.caches">
<p id="rfc.section.1.2.p.3"> <span id="rfc.iref.s.1"></span> <dfn>shared cache</dfn>
<li>A cache that stores responses to be reused by more than one user; usually (but not always) deployed as part of an intermediary.</li>
<p id="rfc.section.1.2.p.4"> <span id="rfc.iref.p.1"></span> <dfn>private cache</dfn>
<li>A cache that is dedicated to a single user.</li>
<p id="rfc.section.1.2.p.5"> <span id="rfc.iref.c.3"></span> <dfn>cacheable</dfn>
Even when a response is cacheable, there might be additional constraints on whether a cache can use the stored copy to satisfy
a particular request.
<p id="rfc.section.1.2.p.6"> <span id="rfc.iref.e.1"></span> <dfn>explicit expiration time</dfn>
<li>The time at which the origin server intends that a representation no longer be returned by a cache without further validation.</li>
<p id="rfc.section.1.2.p.7"> <span id="rfc.iref.h.1"></span> <dfn>heuristic expiration time</dfn>
<p id="rfc.section.1.2.p.8"> <span id="rfc.iref.a.1"></span> <dfn>age</dfn>
<p id="rfc.section.1.2.p.9"> <span id="rfc.iref.f.1"></span> <dfn>first-hand</dfn>
<li>A response is first-hand if the freshness model is not in use; i.e., its age is 0.</li>
<p id="rfc.section.1.2.p.10"> <span id="rfc.iref.f.2"></span> <dfn>freshness lifetime</dfn>
<p id="rfc.section.1.2.p.11"> <span id="rfc.iref.f.3"></span> <dfn>fresh</dfn>
<p id="rfc.section.1.2.p.12"> <span id="rfc.iref.s.2"></span> <dfn>stale</dfn>
<li>A response is stale if its age has passed its freshness lifetime (either explicit or heuristic).</li>
<p id="rfc.section.1.2.p.13"> <span id="rfc.iref.v.1"></span> <dfn>validator</dfn>
<li>A protocol element (e.g., an entity-tag or a Last-Modified time) that is used to find out whether a stored response is an
equivalent copy of a representation. See <a href="p4-conditional.html#weak.and.strong.validators" title="Weak versus Strong">Section 2.1</a> of <a href="#Part4" id="rfc.xref.Part4.1"><cite title="HTTP/1.1, part 4: Conditional Requests">[Part4]</cite></a>.
<p id="rfc.section.1.2.p.14"> <span id="rfc.iref.s.3"></span> <span id="rfc.iref.v.2"></span> <dfn>strong validator</dfn>
<li>A validator that is defined by the origin server such that its current value will change if the representation body changes;
i.e., an entity-tag that is not marked as weak (<a href="p4-conditional.html#header.etag" title="ETag">Section 2.3</a> of <a href="#Part4" id="rfc.xref.Part4.2"><cite title="HTTP/1.1, part 4: Conditional Requests">[Part4]</cite></a>) or, if no entity-tag is provided, a Last-Modified value that is strong in the sense defined by <a href="p4-conditional.html#lastmod.comparison" title="Comparison">Section 2.2.2</a> of <a href="#Part4" id="rfc.xref.Part4.3"><cite title="HTTP/1.1, part 4: Conditional Requests">[Part4]</cite></a>.
<h2 id="rfc.section.1.3"><a href="#rfc.section.1.3">1.3</a>&nbsp;<a id="intro.conformance.and.error.handling" href="#intro.conformance.and.error.handling">Conformance and Error Handling</a></h2>
<p id="rfc.section.1.3.p.2">This document defines conformance criteria for several roles in HTTP communication, including Senders, Recipients, Clients,
<p id="rfc.section.1.3.p.3">An implementation is considered conformant if it complies with all of the requirements associated with its role(s). Note that
<p id="rfc.section.1.3.p.4">This document also uses ABNF to define valid protocol elements (<a href="#notation" title="Syntax Notation">Section&nbsp;1.4</a>). In addition to the prose requirements placed upon them, Senders <em class="bcp14">MUST NOT</em> generate protocol elements that are invalid.
<p id="rfc.section.1.3.p.5">Unless noted otherwise, Recipients <em class="bcp14">MAY</em> take steps to recover a usable protocol element from an invalid construct. However, HTTP does not define specific error handling
<h2 id="rfc.section.1.4"><a href="#rfc.section.1.4">1.4</a>&nbsp;<a id="notation" href="#notation">Syntax Notation</a></h2>
<p id="rfc.section.1.4.p.1">This specification uses the Augmented Backus-Naur Form (ABNF) notation of <a href="#RFC5234" id="rfc.xref.RFC5234.1"><cite title="Augmented BNF for Syntax Specifications: ABNF">[RFC5234]</cite></a> with the list rule extension defined in <a href="p1-messaging.html#notation" title="Syntax Notation">Section 1.2</a> of <a href="#Part1" id="rfc.xref.Part1.2"><cite title="HTTP/1.1, part 1: URIs, Connections, and Message Parsing">[Part1]</cite></a>. <a href="#collected.abnf" title="Collected ABNF">Appendix&nbsp;B</a> shows the collected ABNF with the list rule expanded.
<p id="rfc.section.1.4.p.2">The following core rules are included by reference, as defined in <a href="#RFC5234" id="rfc.xref.RFC5234.2"><cite title="Augmented BNF for Syntax Specifications: ABNF">[RFC5234]</cite></a>, <a href="http://tools.ietf.org/html/rfc5234#appendix-B.1">Appendix B.1</a>: ALPHA (letters), CR (carriage return), CRLF (CR LF), CTL (controls), DIGIT (decimal 0-9), DQUOTE (double quote), HEXDIG
<h3 id="rfc.section.1.4.1"><a href="#rfc.section.1.4.1">1.4.1</a>&nbsp;<a id="core.rules" href="#core.rules">Core Rules</a></h3>
<p id="rfc.section.1.4.1.p.1">The core rules below are defined in <a href="#Part1" id="rfc.xref.Part1.3"><cite title="HTTP/1.1, part 1: URIs, Connections, and Message Parsing">[Part1]</cite></a>:
<a href="#core.rules" class="smpl">quoted-string</a> = &lt;quoted-string, defined in <a href="#Part1" id="rfc.xref.Part1.5"><cite title="HTTP/1.1, part 1: URIs, Connections, and Message Parsing">[Part1]</cite></a>, <a href="p1-messaging.html#field.components" title="Field value components">Section 3.2.4</a>&gt;
<a href="#core.rules" class="smpl">token</a> = &lt;token, defined in <a href="#Part1" id="rfc.xref.Part1.6"><cite title="HTTP/1.1, part 1: URIs, Connections, and Message Parsing">[Part1]</cite></a>, <a href="p1-messaging.html#field.components" title="Field value components">Section 3.2.4</a>&gt;
</pre><h3 id="rfc.section.1.4.2"><a href="#rfc.section.1.4.2">1.4.2</a>&nbsp;<a id="abnf.dependencies" href="#abnf.dependencies">ABNF Rules defined in other Parts of the Specification</a></h3>
<p id="rfc.section.1.4.2.p.1">The ABNF rules below are defined in other parts:</p>
<div id="rfc.figure.u.2"></div><pre class="inline"> <a href="#abnf.dependencies" class="smpl">field-name</a> = &lt;field-name, defined in <a href="#Part1" id="rfc.xref.Part1.7"><cite title="HTTP/1.1, part 1: URIs, Connections, and Message Parsing">[Part1]</cite></a>, <a href="p1-messaging.html#header.fields" title="Header Fields">Section 3.2</a>&gt;
<a href="#abnf.dependencies" class="smpl">HTTP-date</a> = &lt;HTTP-date, defined in <a href="#Part2" id="rfc.xref.Part2.1"><cite title="HTTP/1.1, part 2: Message Semantics">[Part2]</cite></a>, <a href="p2-semantics.html#http.date" title="Date/Time Formats">Section 8</a>&gt;
<a href="#abnf.dependencies" class="smpl">port</a> = &lt;port, defined in <a href="#Part1" id="rfc.xref.Part1.8"><cite title="HTTP/1.1, part 1: URIs, Connections, and Message Parsing">[Part1]</cite></a>, <a href="p1-messaging.html#uri" title="Uniform Resource Identifiers">Section 2.7</a>&gt;
<a href="#abnf.dependencies" class="smpl">pseudonym</a> = &lt;pseudonym, defined in <a href="#Part1" id="rfc.xref.Part1.9"><cite title="HTTP/1.1, part 1: URIs, Connections, and Message Parsing">[Part1]</cite></a>, <a href="p1-messaging.html#header.via" title="Via">Section 8.8</a>&gt;
<a href="#abnf.dependencies" class="smpl">uri-host</a> = &lt;uri-host, defined in <a href="#Part1" id="rfc.xref.Part1.10"><cite title="HTTP/1.1, part 1: URIs, Connections, and Message Parsing">[Part1]</cite></a>, <a href="p1-messaging.html#uri" title="Uniform Resource Identifiers">Section 2.7</a>&gt;
</pre><h2 id="rfc.section.1.5"><a href="#rfc.section.1.5">1.5</a>&nbsp;<a id="delta-seconds" href="#delta-seconds">Delta Seconds</a></h2>
<p id="rfc.section.1.5.p.1">The delta-seconds rule specifies a non-negative integer, representing time in seconds.</p>
<div id="rfc.figure.u.3"></div><pre class="inline"><span id="rfc.iref.g.1"></span> <a href="#delta-seconds" class="smpl">delta-seconds</a> = 1*<a href="#notation" class="smpl">DIGIT</a>
</pre><p id="rfc.section.1.5.p.3">If an implementation receives a delta-seconds value larger than the largest positive integer it can represent, or if any of
its subsequent calculations overflows, it <em class="bcp14">MUST</em> consider the value to be 2147483648 (2<sup>31</sup>). Recipients parsing a delta-seconds value <em class="bcp14">MUST</em> use an arithmetic type of at least 31 bits of range, and senders <em class="bcp14">MUST NOT</em> send delta-seconds with a value greater than 2147483648.
<h1 id="rfc.section.2"><a href="#rfc.section.2">2.</a>&nbsp;<a id="caching.overview" href="#caching.overview">Cache Operation</a></h1>
<p id="rfc.section.2.p.1">Proper cache operation preserves the semantics of HTTP transfers (<a href="#Part2" id="rfc.xref.Part2.2"><cite title="HTTP/1.1, part 2: Message Semantics">[Part2]</cite></a>) while eliminating the transfer of information already held in the cache. Although caching is an entirely <em class="bcp14">OPTIONAL</em> feature of HTTP, we assume that reusing the cached response is desirable and that such reuse is the default behavior when
no requirement or locally-desired configuration prevents it. Therefore, HTTP cache requirements are focused on preventing
a cache from either storing a non-reusable response or reusing a stored response inappropriately.
<p id="rfc.section.2.p.2">Each <dfn>cache entry</dfn> consists of a cache key and one or more HTTP responses corresponding to prior requests that used the same key. The most common
form of cache entry is a successful result of a retrieval request: i.e., a 200 (OK) response containing a representation of
the resource identified by the request target. However, it is also possible to cache negative results (e.g., 404 not found),
incomplete results (e.g., 206 partial content), and responses to safe methods other than GET if the method's definition allows
such caching and defines something suitable for use as a cache key.
<p id="rfc.section.2.p.3">The default <dfn>cache key</dfn> consists of the request method and target URI. However, since HTTP caches in common use today are typically limited to caching
responses to GET, most implementations simply decline other methods and use only the URI as the key.
<p id="rfc.section.2.p.4">If a request target is subject to content negotiation, its cache entry might consist of multiple stored responses, each differentiated
by a secondary key for the values of the original request's selecting header fields (<a href="#caching.negotiated.responses" title="Caching Negotiated Responses">Section&nbsp;2.7</a>).
<h2 id="rfc.section.2.1"><a href="#rfc.section.2.1">2.1</a>&nbsp;<a id="response.cacheability" href="#response.cacheability">Response Cacheability</a></h2>
<p id="rfc.section.2.1.p.1">A cache <em class="bcp14">MUST NOT</em> store a response to any request, unless:
<li>The request method is understood by the cache and defined as being cacheable, and</li>
<li>the response status code is understood by the cache, and</li>
<li>the "no-store" cache directive (see <a href="#header.cache-control" id="rfc.xref.header.cache-control.1" title="Cache-Control">Section&nbsp;3.2</a>) does not appear in request or response header fields, and
<li>the "private" cache response directive (see <a href="#cache-response-directive" title="Response Cache-Control Directives">Section&nbsp;3.2.2</a>) does not appear in the response, if the cache is shared, and
<li>the "Authorization" 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="HTTP/1.1, part 7: 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="Shared Caching of Authenticated Responses">Section&nbsp;2.6</a>), and
<li>the response either:
<li>contains an Expires header field (see <a href="#header.expires" id="rfc.xref.header.expires.1" title="Expires">Section&nbsp;3.3</a>), or
<li>contains a max-age response cache directive (see <a href="#cache-response-directive" title="Response Cache-Control Directives">Section&nbsp;3.2.2</a>), or
<li>contains a s-maxage response cache directive and the cache is shared, or</li>
<li>contains a Cache Control Extension (see <a href="#cache.control.extensions" title="Cache Control Extensions">Section&nbsp;3.2.3</a>) that allows it to be cached, or
<li>has a status code that can be served with heuristic freshness (see <a href="#heuristic.freshness" title="Calculating Heuristic Freshness">Section&nbsp;2.3.1.1</a>).
<p id="rfc.section.2.1.p.2">Note that any of the requirements listed above can be overridden by a cache-control extension; see <a href="#cache.control.extensions" title="Cache Control Extensions">Section&nbsp;3.2.3</a>.
<p id="rfc.section.2.1.p.3">In this context, a cache has "understood" a request method or a response status code if it recognizes it and implements any
cache-specific behavior.
<p id="rfc.section.2.1.p.4">Note that, in normal operation, most caches will not store a response that has neither a cache validator nor an explicit expiration
time, as such responses are not usually useful to store. However, caches are not prohibited from storing such responses.
<p id="rfc.section.2.1.p.5">A response message is considered complete when all of the octets indicated by the message framing (<a href="#Part1" id="rfc.xref.Part1.11"><cite title="HTTP/1.1, part 1: URIs, Connections, and Message Parsing">[Part1]</cite></a>) are received prior to the connection being closed. If the request is GET, the response status is 200 (OK), and the entire
response header block has been received, a cache <em class="bcp14">MAY</em> store an incomplete response message-body if the cache entry is recorded as incomplete. Likewise, a 206 (Partial Content)
response <em class="bcp14">MAY</em> be stored as if it were an incomplete 200 (OK) cache entry. However, a cache <em class="bcp14">MUST NOT</em> store incomplete or partial content responses if it does not support the Range and Content-Range header fields or if it does
not understand the range units used in those fields.
<p id="rfc.section.2.1.p.6">A cache <em class="bcp14">MAY</em> complete a stored incomplete response by making a subsequent range request (<a href="#Part5" id="rfc.xref.Part5.1"><cite title="HTTP/1.1, part 5: Range Requests and Partial Responses">[Part5]</cite></a>) and combining the successful response with the stored entry, as defined in <a href="#combining.responses" title="Combining Partial Content">Section&nbsp;2.8</a>. A cache <em class="bcp14">MUST NOT</em> use an incomplete response to answer requests unless the response has been made complete or the request is partial and specifies
a range that is wholly within the incomplete response. A cache <em class="bcp14">MUST NOT</em> send a partial response to a client without explicitly marking it as such using the 206 (Partial Content) status code.
<h2 id="rfc.section.2.2"><a href="#rfc.section.2.2">2.2</a>&nbsp;<a id="constructing.responses.from.caches" href="#constructing.responses.from.caches">Constructing Responses from Caches</a></h2>
<p id="rfc.section.2.2.p.1">For a presented request, a cache <em class="bcp14">MUST NOT</em> return a stored response, unless:
<li>The presented effective request URI (<a href="p1-messaging.html#effective.request.uri" title="Effective Request URI">Section 4.3</a> of <a href="#Part1" id="rfc.xref.Part1.12"><cite title="HTTP/1.1, part 1: URIs, Connections, and Message Parsing">[Part1]</cite></a>) and that of the stored response match, and
<li>the request method associated with the stored response allows it to be used for the presented request, and</li>
<li>selecting header fields nominated by the stored response (if any) match those presented (see <a href="#caching.negotiated.responses" title="Caching Negotiated Responses">Section&nbsp;2.7</a>), and
<li>the presented request does not contain the no-cache pragma (<a href="#header.pragma" id="rfc.xref.header.pragma.1" title="Pragma">Section&nbsp;3.4</a>), nor the no-cache cache directive (<a href="#cache-request-directive" title="Request Cache-Control Directives">Section&nbsp;3.2.1</a>), unless the stored response is successfully validated (<a href="#validation.model" title="Validation Model">Section&nbsp;2.4</a>), and
<li>the stored response does not contain the no-cache cache directive (<a href="#cache-response-directive" title="Response Cache-Control Directives">Section&nbsp;3.2.2</a>), unless it is successfully validated (<a href="#validation.model" title="Validation Model">Section&nbsp;2.4</a>), and
<li>the stored response is either:
<li>fresh (see <a href="#expiration.model" title="Freshness Model">Section&nbsp;2.3</a>), or
<li>allowed to be served stale (see <a href="#serving.stale.responses" title="Serving Stale Responses">Section&nbsp;2.3.3</a>), or
<li>successfully validated (see <a href="#validation.model" title="Validation Model">Section&nbsp;2.4</a>).
<p id="rfc.section.2.2.p.2">Note that any of the requirements listed above can be overridden by a cache-control extension; see <a href="#cache.control.extensions" title="Cache Control Extensions">Section&nbsp;3.2.3</a>.
<p id="rfc.section.2.2.p.3">When a stored response is used to satisfy a request without validation, a cache <em class="bcp14">MUST</em> include a single Age header field (<a href="#header.age" id="rfc.xref.header.age.1" title="Age">Section&nbsp;3.1</a>) in the response with a value equal to the stored response's current_age; see <a href="#age.calculations" title="Calculating Age">Section&nbsp;2.3.2</a>.
<p id="rfc.section.2.2.p.4">A cache <em class="bcp14">MUST</em> write through requests with methods that are unsafe (<a href="p2-semantics.html#safe.methods" title="Safe Methods">Section 6.1.1</a> of <a href="#Part2" id="rfc.xref.Part2.3"><cite title="HTTP/1.1, part 2: Message Semantics">[Part2]</cite></a>) to the origin server; i.e., a cache must not generate a reply to such a request before having forwarded the request and
having received a corresponding response.
<p id="rfc.section.2.2.p.5">Also, note that unsafe requests might invalidate already stored responses; see <a href="#invalidation.after.updates.or.deletions" title="Request Methods that Invalidate">Section&nbsp;2.5</a>.
<p id="rfc.section.2.2.p.6">When more than one suitable response is stored, a cache <em class="bcp14">MUST</em> use the most recent response (as determined by the Date header field). It can also forward a request with "Cache-Control:
max-age=0" or "Cache-Control: no-cache" to disambiguate which response to use.
<p id="rfc.section.2.2.p.7">A cache that does not have a clock available <em class="bcp14">MUST NOT</em> use stored responses without revalidating them on every use. A cache, especially a shared cache, <em class="bcp14">SHOULD</em> use a mechanism, such as NTP <a href="#RFC1305" id="rfc.xref.RFC1305.1"><cite title="Network Time Protocol (Version 3) Specification, Implementation">[RFC1305]</cite></a>, to synchronize its clock with a reliable external standard.
<h2 id="rfc.section.2.3"><a href="#rfc.section.2.3">2.3</a>&nbsp;<a id="expiration.model" href="#expiration.model">Freshness Model</a></h2>
<p id="rfc.section.2.3.p.1">When a response is "fresh" in the cache, it can be used to satisfy subsequent requests without contacting the origin server,
thereby improving efficiency.
<p id="rfc.section.2.3.p.2">The primary mechanism for determining freshness is for an origin server to provide an explicit expiration time in the future,
using either the Expires header field (<a href="#header.expires" id="rfc.xref.header.expires.2" title="Expires">Section&nbsp;3.3</a>) or the max-age response cache directive (<a href="#cache-response-directive" title="Response Cache-Control Directives">Section&nbsp;3.2.2</a>). Generally, origin servers will assign future explicit expiration times to responses in the belief that the representation
is not likely to change in a semantically significant way before the expiration time is reached.
<p id="rfc.section.2.3.p.3">If an origin server wishes to force a cache to validate every request, it can assign an explicit expiration time in the past
to indicate that the response is already stale. Compliant caches will normally validate the cached response before reusing
it for subsequent requests (see <a href="#serving.stale.responses" title="Serving Stale Responses">Section&nbsp;2.3.3</a>).
<p id="rfc.section.2.3.p.4">Since origin servers do not always provide explicit expiration times, a cache <em class="bcp14">MAY</em> assign a heuristic expiration time when an explicit time is not specified, employing algorithms that use other header field
values (such as the Last-Modified time) to estimate a plausible expiration time. This specification does not provide specific
algorithms, but does impose worst-case constraints on their results.
<p>The calculation to determine if a response is fresh is:</p> <pre class="text"> response_is_fresh = (freshness_lifetime &gt; current_age)
</pre> <p id="rfc.section.2.3.p.6">The freshness_lifetime is defined in <a href="#calculating.freshness.lifetime" title="Calculating Freshness Lifetime">Section&nbsp;2.3.1</a>; the current_age is defined in <a href="#age.calculations" title="Calculating Age">Section&nbsp;2.3.2</a>.
<p id="rfc.section.2.3.p.7">Additionally, clients can influence freshness calculation -- either constraining it relaxing it -- by using the max-age and
min-fresh request cache directives. See <a href="#cache-request-directive" title="Request Cache-Control Directives">Section&nbsp;3.2.1</a> for details.
<p id="rfc.section.2.3.p.8">Note that freshness applies only to cache operation; it cannot be used to force a user agent to refresh its display or reload
a resource. See <a href="#history.lists" title="History Lists">Section&nbsp;4</a> for an explanation of the difference between caches and history mechanisms.
<h3 id="rfc.section.2.3.1"><a href="#rfc.section.2.3.1">2.3.1</a>&nbsp;<a id="calculating.freshness.lifetime" href="#calculating.freshness.lifetime">Calculating Freshness Lifetime</a></h3>
<p id="rfc.section.2.3.1.p.1">A cache can calculate the freshness lifetime (denoted as freshness_lifetime) of a response by using the first match of: </p>
<li>If the cache is shared and the s-maxage response cache directive (<a href="#cache-response-directive" title="Response Cache-Control Directives">Section&nbsp;3.2.2</a>) is present, use its value, or
<li>If the max-age response cache directive (<a href="#cache-response-directive" title="Response Cache-Control Directives">Section&nbsp;3.2.2</a>) is present, use its value, or
<li>If the Expires response header field (<a href="#header.expires" id="rfc.xref.header.expires.3" title="Expires">Section&nbsp;3.3</a>) is present, use its value minus the value of the Date response header field, or
<li>Otherwise, no explicit expiration time is present in the response. A heuristic freshness lifetime might be applicable; see <a href="#heuristic.freshness" title="Calculating Heuristic Freshness">Section&nbsp;2.3.1.1</a>.
<p id="rfc.section.2.3.1.p.2">Note that this calculation is not vulnerable to clock skew, since all of the information comes from the origin server.</p>
<h4 id="rfc.section.2.3.1.1"><a href="#rfc.section.2.3.1.1">2.3.1.1</a>&nbsp;<a id="heuristic.freshness" href="#heuristic.freshness">Calculating Heuristic Freshness</a></h4>
<p id="rfc.section.2.3.1.1.p.1">If no explicit expiration time is present in a stored response that has a status code whose definition allows heuristic freshness
to be used (including the following in <a href="p2-semantics.html#status.codes" title="Status Code Definitions">Section 7</a> of <a href="#Part2" id="rfc.xref.Part2.4"><cite title="HTTP/1.1, part 2: Message Semantics">[Part2]</cite></a>: 200, 203, 206, 300, 301 and 410), a cache <em class="bcp14">MAY</em> calculate a heuristic expiration time. A cache <em class="bcp14">MUST NOT</em> use heuristics to determine freshness for responses with status codes that do not explicitly allow it.
<p id="rfc.section.2.3.1.1.p.2">When a heuristic is used to calculate freshness lifetime, a cache <em class="bcp14">SHOULD</em> attach a Warning header field with a 113 warn-code to the response if its current_age is more than 24 hours and such a warning
is not already present.
<p id="rfc.section.2.3.1.1.p.3">Also, if the response has a Last-Modified 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.4"><cite title="HTTP/1.1, part 4: 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
time. A typical setting of this fraction might be 10%.
<div class="note" id="rfc.section.2.3.1.1.p.4">
<p> <b>Note:</b> RFC 2616 (<a href="#RFC2616" id="rfc.xref.RFC2616.1"><cite title="Hypertext Transfer Protocol -- HTTP/1.1">[RFC2616]</cite></a>, <a href="http://tools.ietf.org/html/rfc2616#section-13.9">Section 13.9</a>) required that caches do not calculate heuristic freshness for URIs with query components (i.e., those containing '?'). In
practice, this has not been widely implemented. Therefore, servers are encouraged to send explicit directives (e.g., Cache-Control:
no-cache) if they wish to preclude caching.
<h3 id="rfc.section.2.3.2"><a href="#rfc.section.2.3.2">2.3.2</a>&nbsp;<a id="age.calculations" href="#age.calculations">Calculating Age</a></h3>
<p id="rfc.section.2.3.2.p.1">HTTP/1.1 uses the Age header field to convey the estimated age of the response message when obtained from a cache. The Age
field value is the cache's estimate of the amount of time since the response was generated or validated by the origin server.
In essence, the Age value is the sum of the time that the response has been resident in each of the caches along the path
<p id="rfc.section.2.3.2.p.2">The following data is used for the age calculation:</p>
<p id="rfc.section.2.3.2.p.3"> <dfn>age_value</dfn>
<li>The term "age_value" denotes the value of the Age header field (<a href="#header.age" id="rfc.xref.header.age.2" title="Age">Section&nbsp;3.1</a>), in a form appropriate for arithmetic operation; or 0, if not available.
<p id="rfc.section.2.3.2.p.4"> <dfn>date_value</dfn>
<li>HTTP/1.1 requires origin servers to send a Date header field, if possible, with every response, giving the time at which the
response was generated. The term "date_value" denotes the value of the Date header field, in a form appropriate for arithmetic
operations. See <a href="p2-semantics.html#header.date" title="Date">Section 9.2</a> of <a href="#Part2" id="rfc.xref.Part2.5"><cite title="HTTP/1.1, part 2: Message Semantics">[Part2]</cite></a> for the definition of the Date header field, and for requirements regarding responses without it.
<p id="rfc.section.2.3.2.p.5"> <dfn>now</dfn>
<li>The term "now" means "the current value of the clock at the host performing the calculation". A cache <em class="bcp14">SHOULD</em> use NTP (<a href="#RFC1305" id="rfc.xref.RFC1305.2"><cite title="Network Time Protocol (Version 3) Specification, Implementation">[RFC1305]</cite></a>) or some similar protocol to synchronize its clocks to a globally accurate time standard.
<p id="rfc.section.2.3.2.p.6"> <dfn>request_time</dfn>
<li>The current value of the clock at the host at the time the request resulting in the stored response was made.</li>
<p id="rfc.section.2.3.2.p.7"> <dfn>response_time</dfn>
<li>The current value of the clock at the host at the time the response was received.</li>
<p id="rfc.section.2.3.2.p.8">A response's age can be calculated in two entirely independent ways: </p>
<li>the "apparent_age": response_time minus date_value, if the local clock is reasonably well synchronized to the origin server's
clock. If the result is negative, the result is replaced by zero.
<li>the "corrected_age_value", if all of the caches along the response path implement HTTP/1.1. A cache <em class="bcp14">MUST</em> interpret this value relative to the time the request was initiated, not the time that the response was received.
<div id="rfc.figure.u.5"></div> <pre class="text"> apparent_age = max(0, response_time - date_value);
</pre> <div id="rfc.figure.u.6"></div>
<p>These <em class="bcp14">SHOULD</em> be combined as
</p> <pre class="text"> corrected_initial_age = max(apparent_age, corrected_age_value);
</pre><p id="rfc.section.2.3.2.p.11">unless the cache is confident in the value of the Age header (e.g., because there are no HTTP/1.0 hops in the Via header),
in which case the corrected_age_value <em class="bcp14">MAY</em> be used as the corrected_initial_age.
<p id="rfc.section.2.3.2.p.12">The current_age of a stored response can then be calculated by adding the amount of time (in seconds) since the stored response
was last validated by the origin server to the corrected_initial_age.
<div id="rfc.figure.u.7"></div><pre class="text"> resident_time = now - response_time;
</pre><p id="rfc.section.2.3.2.p.14">Additionally, to avoid common problems in date parsing:</p>
<p id="rfc.section.2.3.2.p.15"> </p>
<li>HTTP/1.1 clients and caches <em class="bcp14">SHOULD</em> assume that an RFC-850 date which appears to be more than 50 years in the future is in fact in the past (this helps solve
the "year 2000" problem).
<li>Although all date formats are specified to be case-sensitive, recipients <em class="bcp14">SHOULD</em> match day, week and timezone names case-insensitively.
<li>An HTTP/1.1 implementation <em class="bcp14">MAY</em> internally represent a parsed Expires date as earlier than the proper value, but <em class="bcp14">MUST NOT</em> internally represent a parsed Expires date as later than the proper value.
<li>All expiration-related calculations <em class="bcp14">MUST</em> be done in GMT. The local time zone <em class="bcp14">MUST NOT</em> influence the calculation or comparison of an age or expiration time.
<li>If an HTTP header field incorrectly carries a date value with a time zone other than GMT, it <em class="bcp14">MUST</em> be converted into GMT using the most conservative possible conversion.
<h3 id="rfc.section.2.3.3"><a href="#rfc.section.2.3.3">2.3.3</a>&nbsp;<a id="serving.stale.responses" href="#serving.stale.responses">Serving Stale Responses</a></h3>
<p id="rfc.section.2.3.3.p.1">A "stale" response is one that either has explicit expiry information or is allowed to have heuristic expiry calculated, but
is not fresh according to the calculations in <a href="#expiration.model" title="Freshness Model">Section&nbsp;2.3</a>.
<p id="rfc.section.2.3.3.p.2">A cache <em class="bcp14">MUST NOT</em> return a stale response if it is prohibited by an explicit in-protocol directive (e.g., by a "no-store" or "no-cache" cache
directive, a "must-revalidate" cache-response-directive, or an applicable "s-maxage" or "proxy-revalidate" cache-response-directive;
see <a href="#cache-response-directive" title="Response Cache-Control Directives">Section&nbsp;3.2.2</a>).
<p id="rfc.section.2.3.3.p.3">A cache <em class="bcp14">MUST NOT</em> return stale responses unless it is disconnected (i.e., it cannot contact the origin server or otherwise find a forward path)
or doing so is explicitly allowed (e.g., by the max-stale request directive; see <a href="#cache-request-directive" title="Request Cache-Control Directives">Section&nbsp;3.2.1</a>).
<p id="rfc.section.2.3.3.p.4">A cache <em class="bcp14">SHOULD</em> append a Warning header field with the 110 warn-code (see <a href="#header.warning" id="rfc.xref.header.warning.1" title="Warning">Section&nbsp;3.6</a>) to stale responses. Likewise, a cache <em class="bcp14">SHOULD</em> add the 112 warn-code to stale responses if the cache is disconnected.
<p id="rfc.section.2.3.3.p.5">If a cache receives a first-hand response (either an entire response, or a 304 (Not Modified) response) that it would normally
forward to the requesting client, and the received response is no longer fresh, the cache can forward it to the requesting
client without adding a new Warning (but without removing any existing Warning header fields). A cache shouldn't attempt to
validate a response simply because that response became stale in transit.
<h2 id="rfc.section.2.4"><a href="#rfc.section.2.4">2.4</a>&nbsp;<a id="validation.model" href="#validation.model">Validation Model</a></h2>
<p id="rfc.section.2.4.p.1">When a cache has one or more stored responses for a requested URI, but cannot serve any of them (e.g., because they are not
fresh, or one cannot be selected; see <a href="#caching.negotiated.responses" title="Caching Negotiated Responses">Section&nbsp;2.7</a>), it can use the conditional request mechanism <a href="#Part4" id="rfc.xref.Part4.5"><cite title="HTTP/1.1, part 4: Conditional Requests">[Part4]</cite></a> in the forwarded request to give the origin server an opportunity to both select a valid stored response to be used, and to
update it. This process is known as "validating" or "revalidating" the stored response.
<p id="rfc.section.2.4.p.2">When sending such a conditional request, a cache adds an If-Modified-Since header field whose value is that of the Last-Modified
header field from the selected (see <a href="#caching.negotiated.responses" title="Caching Negotiated Responses">Section&nbsp;2.7</a>) stored response, if available.
<p id="rfc.section.2.4.p.3">Additionally, a cache can add an If-None-Match header field whose value is that of the ETag header field(s) from all responses
stored for the requested URI, if present. However, if any of the stored responses contains only partial content, the cache
shouldn't include its entity-tag in the If-None-Match header field unless the request is for a range that would be fully satisfied
by that stored response.
<p id="rfc.section.2.4.p.4">Cache handling of a response to a conditional request is dependent upon its status code:</p>
<p id="rfc.section.2.4.p.5"> </p>
<li>A 304 (Not Modified) response status code indicates that the stored response can be updated and reused; see <a href="#freshening.responses" title="Freshening Responses">Section&nbsp;2.4.1</a>.
<li>A full response (i.e., one with a response body) indicates that none of the stored responses nominated in the conditional
request is suitable. Instead, the cache can use the full response to satisfy the request and <em class="bcp14">MAY</em> replace the stored response(s).
<li>However, if a cache receives a 5xx response while attempting to validate a response, it can either forward this response to
the requesting client, or act as if the server failed to respond. In the latter case, it can return a previously stored response
(see <a href="#serving.stale.responses" title="Serving Stale Responses">Section&nbsp;2.3.3</a>).
<h3 id="rfc.section.2.4.1"><a href="#rfc.section.2.4.1">2.4.1</a>&nbsp;<a id="freshening.responses" href="#freshening.responses">Freshening Responses</a></h3>
<p id="rfc.section.2.4.1.p.1">When a cache receives a 304 (Not Modified) response and already has one or more stored 200 (OK) responses for the same cache
key, the cache needs to identify which of the stored responses are updated by this new response and then update the stored
response(s) with the new information provided in the 304 response.
<li>If the new response contains a strong validator, then that strong validator identifies the selected representation. All of
the stored responses with the same strong validator are selected. If none of the stored responses contain the same strong
validator, then this new response corresponds to a new selected representation and <em class="bcp14">MUST NOT</em> update the existing stored responses.
<li>If the new response contains a weak validator and that validator corresponds to one of the cache's stored responses, then
the most recent of those matching stored responses is selected.
<li>If the new response does not include any form of validator, there is only one stored response, and that stored response also
lacks a validator, then that stored response is selected.
<p id="rfc.section.2.4.1.p.2">If a stored response is selected for update, the cache <em class="bcp14">MUST</em>:
<li>delete any Warning header fields in the stored response with warn-code 1xx (see <a href="#header.warning" id="rfc.xref.header.warning.2" title="Warning">Section&nbsp;3.6</a>);
<li>retain any Warning header fields in the stored response with warn-code 2xx; and,</li>
<li>use other header fields provided in the 304 response to replace all instances of the corresponding header fields in the stored
<h2 id="rfc.section.2.5"><a href="#rfc.section.2.5">2.5</a>&nbsp;<a id="invalidation.after.updates.or.deletions" href="#invalidation.after.updates.or.deletions">Request Methods that Invalidate</a></h2>
<p id="rfc.section.2.5.p.1">Because unsafe request methods (<a href="p2-semantics.html#safe.methods" title="Safe Methods">Section 6.1.1</a> of <a href="#Part2" id="rfc.xref.Part2.6"><cite title="HTTP/1.1, part 2: Message Semantics">[Part2]</cite></a>) such as PUT, POST or DELETE have the potential for changing state on the origin server, intervening caches can use them
to keep their contents up-to-date.
<p id="rfc.section.2.5.p.2">A cache <em class="bcp14">MUST</em> invalidate the effective Request URI (<a href="p1-messaging.html#effective.request.uri" title="Effective Request URI">Section 4.3</a> of <a href="#Part1" id="rfc.xref.Part1.13"><cite title="HTTP/1.1, part 1: URIs, Connections, and Message Parsing">[Part1]</cite></a>) as well as the URI(s) in the Location and Content-Location header fields (if present) when a non-error response to a request
with an unsafe method is received.
<p id="rfc.section.2.5.p.3">However, a cache <em class="bcp14">MUST NOT</em> invalidate a URI from a Location or Content-Location header field if the host part of that URI differs from the host part
in the effective request URI (<a href="p1-messaging.html#effective.request.uri" title="Effective Request URI">Section 4.3</a> of <a href="#Part1" id="rfc.xref.Part1.14"><cite title="HTTP/1.1, part 1: URIs, Connections, and Message Parsing">[Part1]</cite></a>). This helps prevent denial of service attacks.
<p id="rfc.section.2.5.p.4">A cache <em class="bcp14">MUST</em> invalidate the effective request URI (<a href="p1-messaging.html#effective.request.uri" title="Effective Request URI">Section 4.3</a> of <a href="#Part1" id="rfc.xref.Part1.15"><cite title="HTTP/1.1, part 1: URIs, Connections, and Message Parsing">[Part1]</cite></a>) when it receives a non-error response to a request with a method whose safety is unknown.
<p id="rfc.section.2.5.p.5">Here, a "non-error response" is one with a 2xx or 3xx status code. "Invalidate" means that the cache will either remove all
stored responses related to the effective request URI, or will mark these as "invalid" and in need of a mandatory validation
<p id="rfc.section.2.5.p.6">Note that this does not guarantee that all appropriate responses are invalidated. For example, the request that caused the
change at the origin server might not have gone through the cache where a response is stored.
<h2 id="rfc.section.2.6"><a href="#rfc.section.2.6">2.6</a>&nbsp;<a id="caching.authenticated.responses" href="#caching.authenticated.responses">Shared Caching of Authenticated Responses</a></h2>
<p id="rfc.section.2.6.p.1">A shared cache <em class="bcp14">MUST NOT</em> use a cached response to a request with an Authorization header field (<a href="p7-auth.html#header.authorization" title="Authorization">Section 4.1</a> of <a href="#Part7" id="rfc.xref.Part7.2"><cite title="HTTP/1.1, part 7: Authentication">[Part7]</cite></a>) to satisfy any subsequent request unless a cache directive that allows such responses to be stored is present in the response.
<p id="rfc.section.2.6.p.2">In this specification, the following Cache-Control response directives (<a href="#cache-response-directive" title="Response Cache-Control Directives">Section&nbsp;3.2.2</a>) have such an effect: must-revalidate, public, s-maxage.
<p id="rfc.section.2.6.p.3">Note that cached responses that contain the "must-revalidate" and/or "s-maxage" response directives are not allowed to be
served stale (<a href="#serving.stale.responses" title="Serving Stale Responses">Section&nbsp;2.3.3</a>) by shared caches. In particular, a response with either "max-age=0, must-revalidate" or "s-maxage=0" cannot be used to satisfy
a subsequent request without revalidating it on the origin server.
<h2 id="rfc.section.2.7"><a href="#rfc.section.2.7">2.7</a>&nbsp;<a id="caching.negotiated.responses" href="#caching.negotiated.responses">Caching Negotiated Responses</a></h2>
<p id="rfc.section.2.7.p.1">When a cache receives a request that can be satisfied by a stored response that has a Vary header field (<a href="#header.vary" id="rfc.xref.header.vary.1" title="Vary">Section&nbsp;3.5</a>), it <em class="bcp14">MUST NOT</em> use that response unless all of the selecting header fields nominated by the Vary header field match in both the original
request (i.e., that associated with the stored response), and the presented request.
<p id="rfc.section.2.7.p.2">The selecting header fields from two requests are defined to match if and only if those in the first request can be transformed
to those in the second request by applying any of the following:
<li>adding or removing whitespace, where allowed in the header field's syntax</li>
<li>combining multiple header fields with the same field name (see <a href="p1-messaging.html#header.fields" title="Header Fields">Section 3.2</a> of <a href="#Part1" id="rfc.xref.Part1.16"><cite title="HTTP/1.1, part 1: URIs, Connections, and Message Parsing">[Part1]</cite></a>)
<li>normalizing both header field values in a way that is known to have identical semantics, according to the header field's specification
(e.g., re-ordering field values when order is not significant; case-normalization, where values are defined to be case-insensitive)
<p id="rfc.section.2.7.p.3">If (after any normalization that might take place) a header field is absent from a request, it can only match another request
if it is also absent there.
<p id="rfc.section.2.7.p.4">A Vary header field-value of "*" always fails to match, and subsequent requests to that resource can only be properly interpreted
<p id="rfc.section.2.7.p.5">The stored response with matching selecting header fields is known as the selected response.</p>
<p id="rfc.section.2.7.p.6">If multiple selected responses are available, the most recent response (as determined by the Date header field) is used; see <a href="#constructing.responses.from.caches" title="Constructing Responses from Caches">Section&nbsp;2.2</a>.
<p id="rfc.section.2.7.p.7">If no selected response is available, the cache can forward the presented request to the origin server in a conditional request;
see <a href="#validation.model" title="Validation Model">Section&nbsp;2.4</a>.
<h2 id="rfc.section.2.8"><a href="#rfc.section.2.8">2.8</a>&nbsp;<a id="combining.responses" href="#combining.responses">Combining Partial Content</a></h2>
<p id="rfc.section.2.8.p.1">A response might transfer only a partial representation if the connection closed prematurely or if the request used one or
more Range specifiers (<a href="#Part5" id="rfc.xref.Part5.2"><cite title="HTTP/1.1, part 5: Range Requests and Partial Responses">[Part5]</cite></a>). After several such transfers, a cache might have received several ranges of the same representation. A cache <em class="bcp14">MAY</em> combine these ranges into a single stored response, and reuse that response to satisfy later requests, if they all share the
same strong validator and the cache complies with the client requirements in <a href="p5-range.html#combining.byte.ranges" title="Combining Ranges">Section 4</a> of <a href="#Part5" id="rfc.xref.Part5.3"><cite title="HTTP/1.1, part 5: Range Requests and Partial Responses">[Part5]</cite></a>.
<p id="rfc.section.2.8.p.2">When combining the new response with one or more stored responses, a cache <em class="bcp14">MUST</em>:
<li>delete any Warning header fields in the stored response with warn-code 1xx (see <a href="#header.warning" id="rfc.xref.header.warning.3" title="Warning">Section&nbsp;3.6</a>);
<li>use other header fields provided in the new response, aside from Content-Range, to replace all instances of the corresponding
<h1 id="rfc.section.3"><a href="#rfc.section.3">3.</a>&nbsp;<a id="header.field.definitions" href="#header.field.definitions">Header Field Definitions</a></h1>
<p id="rfc.section.3.p.1">This section defines the syntax and semantics of HTTP/1.1 header fields related to caching.</p>
<h2 id="rfc.section.3.1"><a href="#rfc.section.3.1">3.1</a>&nbsp;<a id="header.age" href="#header.age">Age</a></h2>
<p id="rfc.section.3.1.p.1">The "Age" header field conveys the sender's estimate of the amount of time since the response was generated or successfully
validated at the origin server. Age values are calculated as specified in <a href="#age.calculations" title="Calculating Age">Section&nbsp;2.3.2</a>.
<div id="rfc.figure.u.8"></div><pre class="inline"><span id="rfc.iref.g.2"></span> <a href="#header.age" class="smpl">Age</a> = <a href="#delta-seconds" class="smpl">delta-seconds</a>
</pre><p id="rfc.section.3.1.p.3">Age field-values are non-negative integers, representing time in seconds (see <a href="#delta-seconds" title="Delta Seconds">Section&nbsp;1.5</a>).
<p id="rfc.section.3.1.p.4">The presence of an Age header field in a response implies that a response is not first-hand. However, the converse is not
true, since HTTP/1.0 caches might not implement the Age header field.
<h2 id="rfc.section.3.2"><a href="#rfc.section.3.2">3.2</a>&nbsp;<a id="header.cache-control" href="#header.cache-control">Cache-Control</a></h2>
<p id="rfc.section.3.2.p.1">The "Cache-Control" header field is used to specify directives for caches along the request/response chain. Such cache directives
are unidirectional in that the presence of a directive in a request does not imply that the same directive is to be given
<p id="rfc.section.3.2.p.2">A cache <em class="bcp14">MUST</em> obey the requirements of the Cache-Control directives defined in this section. See <a href="#cache.control.extensions" title="Cache Control Extensions">Section&nbsp;3.2.3</a> for information about how Cache-Control directives defined elsewhere are handled.
<div class="note" id="rfc.section.3.2.p.3">
<p> <b>Note:</b> HTTP/1.0 caches might not implement Cache-Control and might only implement Pragma: no-cache (see <a href="#header.pragma" id="rfc.xref.header.pragma.2" title="Pragma">Section&nbsp;3.4</a>).
<p id="rfc.section.3.2.p.4">A proxy, whether or not it implements a cache, <em class="bcp14">MUST</em> pass cache directives through in forwarded messages, regardless of their significance to that application, since the directives
might be applicable to all recipients along the request/response chain. It is not possible to target a directive to a specific
<p id="rfc.section.3.2.p.5">Cache directives are identified by a token, to be compared case-insensitively, and have an optional argument.</p>
<div id="rfc.figure.u.9"></div><pre class="inline"><span id="rfc.iref.g.3"></span><span id="rfc.iref.g.4"></span> <a href="#header.cache-control" class="smpl">Cache-Control</a> = 1#<a href="#header.cache-control" class="smpl">cache-directive</a>
/ <a href="#header.cache-control" class="smpl">cache-response-directive</a>
<a href="#header.cache-control" class="smpl">cache-extension</a> = <a href="#core.rules" class="smpl">token</a> [ "=" ( <a href="#core.rules" class="smpl">token</a> / <a href="#core.rules" class="smpl">quoted-string</a> ) ]
</pre><h3 id="rfc.section.3.2.1"><a href="#rfc.section.3.2.1">3.2.1</a>&nbsp;<a id="cache-request-directive" href="#cache-request-directive">Request Cache-Control Directives</a></h3>
<div id="rfc.figure.u.10"></div><pre class="inline"><span id="rfc.iref.g.5"></span> <a href="#header.cache-control" class="smpl">cache-request-directive</a> =
/ "max-age" "=" <a href="#delta-seconds" class="smpl">delta-seconds</a>
/ "max-stale" [ "=" <a href="#delta-seconds" class="smpl">delta-seconds</a> ]
/ "min-fresh" "=" <a href="#delta-seconds" class="smpl">delta-seconds</a>
/ <a href="#header.cache-control" class="smpl">cache-extension</a>
</pre><p id="rfc.section.3.2.1.p.2"> <dfn>no-cache</dfn> <span id="rfc.iref.c.7"></span> <span id="rfc.iref.n.1"></span>
<li>The no-cache request directive indicates that a cache <em class="bcp14">MUST NOT</em> use a stored response to satisfy the request without successful validation on the origin server.
<p id="rfc.section.3.2.1.p.3"> <dfn>no-store</dfn> <span id="rfc.iref.c.8"></span> <span id="rfc.iref.n.2"></span>
<li>The no-store request directive indicates that a cache <em class="bcp14">MUST NOT</em> store any part of either this request or any response to it. This directive applies to both private and shared caches. "<em class="bcp14">MUST NOT</em> store" in this context means that the cache <em class="bcp14">MUST NOT</em> intentionally store the information in non-volatile storage, and <em class="bcp14">MUST</em> make a best-effort attempt to remove the information from volatile storage as promptly as possible after forwarding it.
<li>This directive is NOT a reliable or sufficient mechanism for ensuring privacy. In particular, malicious or compromised caches
might not recognize or obey this directive, and communications networks might be vulnerable to eavesdropping.
<li>Note that if a request containing this directive is satisfied from a cache, the no-store request directive does not apply
to the already stored response.
<p id="rfc.section.3.2.1.p.4"> <dfn>max-age</dfn> <span id="rfc.iref.c.9"></span> <span id="rfc.iref.m.1"></span>
<li>The max-age request directive indicates that the client is unwilling to accept a response whose age is greater than the specified
number of seconds. Unless the max-stale request directive is also present, the client is not willing to accept a stale response.
<p id="rfc.section.3.2.1.p.5"> <dfn>max-stale</dfn> <span id="rfc.iref.c.10"></span> <span id="rfc.iref.m.2"></span>
<li>The max-stale request directive indicates that the client is willing to accept a response that has exceeded its expiration
time. If max-stale is assigned a value, then the client is willing to accept a response that has exceeded its expiration time
by no more than the specified number of seconds. If no value is assigned to max-stale, then the client is willing to accept
a stale response of any age.
<p id="rfc.section.3.2.1.p.6"> <dfn>min-fresh</dfn> <span id="rfc.iref.c.11"></span> <span id="rfc.iref.m.3"></span>
<li>The min-fresh request directive indicates that the client is willing to accept a response whose freshness lifetime is no less
than its current age plus the specified time in seconds. That is, the client wants a response that will still be fresh for
at least the specified number of seconds.
<p id="rfc.section.3.2.1.p.7"> <dfn>no-transform</dfn> <span id="rfc.iref.c.12"></span> <span id="rfc.iref.n.3"></span>
<li>The no-transform request directive indicates that an intermediary (whether or not it implements a cache) <em class="bcp14">MUST NOT</em> change the Content-Encoding, Content-Range or Content-Type request header fields, nor the request representation.
<p id="rfc.section.3.2.1.p.8"> <dfn>only-if-cached</dfn> <span id="rfc.iref.c.13"></span> <span id="rfc.iref.o.1"></span>
<li>The only-if-cached request directive indicates that the client only wishes to obtain a stored response. If it receives this
directive, a cache <em class="bcp14">SHOULD</em> either respond using a stored response that is consistent with the other constraints of the request, or respond with a 504
(Gateway Timeout) status code. If a group of caches is being operated as a unified system with good internal connectivity,
a member cache <em class="bcp14">MAY</em> forward such a request within that group of caches.
<h3 id="rfc.section.3.2.2"><a href="#rfc.section.3.2.2">3.2.2</a>&nbsp;<a id="cache-response-directive" href="#cache-response-directive">Response Cache-Control Directives</a></h3>
<div id="rfc.figure.u.11"></div><pre class="inline"><span id="rfc.iref.g.6"></span> <a href="#header.cache-control" class="smpl">cache-response-directive</a> =
/ "private" [ "=" <a href="#notation" class="smpl">DQUOTE</a> 1#<a href="#abnf.dependencies" class="smpl">field-name</a> <a href="#notation" class="smpl">DQUOTE</a> ]
/ "no-cache" [ "=" <a href="#notation" class="smpl">DQUOTE</a> 1#<a href="#abnf.dependencies" class="smpl">field-name</a> <a href="#notation" class="smpl">DQUOTE</a> ]
/ "s-maxage" "=" <a href="#delta-seconds" class="smpl">delta-seconds</a>
</pre><p id="rfc.section.3.2.2.p.2"> <dfn>public</dfn> <span id="rfc.iref.c.14"></span> <span id="rfc.iref.p.2"></span>
<li>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="Shared Caching of Authenticated Responses">Section&nbsp;2.6</a>).
<p id="rfc.section.3.2.2.p.3"> <dfn>private</dfn> <span id="rfc.iref.c.15"></span> <span id="rfc.iref.p.3"></span>
<li>The private response directive indicates that the response message is intended for a single user and <em class="bcp14">MUST NOT</em> be stored by a shared cache. A private cache <em class="bcp14">MAY</em> store the response.
<li>If the private response directive specifies one or more field-names, this requirement is limited to the field-values associated
with the listed response header fields. That is, a shared cache <em class="bcp14">MUST NOT</em> store the specified field-names(s), whereas it <em class="bcp14">MAY</em> store the remainder of the response message.
<li> <b>Note:</b> This usage of the word private only controls where the response can be stored; it cannot ensure the privacy of the message
content. Also, private response directives with field-names are often handled by implementations as if an unqualified private
directive was received; i.e., the special handling for the qualified form is not widely implemented.
<p id="rfc.section.3.2.2.p.4"> <dfn>no-cache</dfn> <span id="rfc.iref.c.16"></span> <span id="rfc.iref.n.4"></span>
with the listed response header fields. That is, a cache <em class="bcp14">MUST NOT</em> send the specified field-name(s) in the response to a subsequent request without successful validation on the origin server.
This allows an origin server to prevent the re-use of certain header fields in a response, while still allowing caching of
the rest of the response.
<li> <b>Note:</b> Most HTTP/1.0 caches will not recognize or obey this directive. Also, no-cache response directives with field-names are often
handled by implementations as if an unqualified no-cache directive was received; i.e., the special handling for the qualified
form is not widely implemented.
<p id="rfc.section.3.2.2.p.5"> <dfn>no-store</dfn> <span id="rfc.iref.c.17"></span> <span id="rfc.iref.n.5"></span>
<li>The no-store response directive indicates that a cache <em class="bcp14">MUST NOT</em> store any part of either the immediate request or response. This directive applies to both private and shared caches. "<em class="bcp14">MUST NOT</em> store" in this context means that the cache <em class="bcp14">MUST NOT</em> intentionally store the information in non-volatile storage, and <em class="bcp14">MUST</em> make a best-effort attempt to remove the information from volatile storage as promptly as possible after forwarding it.
<p id="rfc.section.3.2.2.p.6"> <dfn>must-revalidate</dfn> <span id="rfc.iref.c.18"></span> <span id="rfc.iref.m.4"></span>
<li>The must-revalidate response directive indicates that once it has become stale, a cache <em class="bcp14">MUST NOT</em> use the response to satisfy subsequent requests without successful validation on the origin server.
a cache <em class="bcp14">MUST</em> obey the must-revalidate directive; in particular, if a cache cannot reach the origin server for any reason, it <em class="bcp14">MUST</em> generate a 504 (Gateway Timeout) response.
<li>The must-revalidate directive ought to be used by servers if and only if failure to validate a request on the representation
could result in incorrect operation, such as a silently unexecuted financial transaction.
<p id="rfc.section.3.2.2.p.7"> <dfn>proxy-revalidate</dfn> <span id="rfc.iref.c.19"></span> <span id="rfc.iref.p.4"></span>
<li>The proxy-revalidate response directive has the same meaning as the must-revalidate response directive, except that it does
not apply to private caches.
<p id="rfc.section.3.2.2.p.8"> <dfn>max-age</dfn> <span id="rfc.iref.c.20"></span> <span id="rfc.iref.m.5"></span>
<li>The max-age response directive indicates that the response is to be considered stale after its age is greater than the specified
<p id="rfc.section.3.2.2.p.9"> <dfn>s-maxage</dfn> <span id="rfc.iref.c.21"></span> <span id="rfc.iref.s.4"></span>
<li>The s-maxage response directive indicates that, in shared caches, the maximum age specified by this directive overrides the
maximum age specified by either the max-age directive or the Expires header field. The s-maxage directive also implies the
semantics of the proxy-revalidate response directive.
<p id="rfc.section.3.2.2.p.10"> <dfn>no-transform</dfn> <span id="rfc.iref.c.22"></span> <span id="rfc.iref.n.6"></span>
<li>The no-transform response directive indicates that an intermediary (regardless of whether it implements a cache) <em class="bcp14">MUST NOT</em> change the Content-Encoding, Content-Range or Content-Type response header fields, nor the response representation.
<h3 id="rfc.section.3.2.3"><a href="#rfc.section.3.2.3">3.2.3</a>&nbsp;<a id="cache.control.extensions" href="#cache.control.extensions">Cache Control Extensions</a></h3>
<p id="rfc.section.3.2.3.p.1">The Cache-Control header field can be extended through the use of one or more cache-extension tokens, each with an optional
value. Informational extensions (those that do not require a change in cache behavior) can be added without changing the semantics
of other directives. Behavioral extensions are designed to work by acting as modifiers to the existing base of cache directives.
Both the new directive and the standard directive are supplied, such that applications that do not understand the new directive
will default to the behavior specified by the standard directive, and those that understand the new directive will recognize
it as modifying the requirements associated with the standard directive. In this way, extensions to the cache-control directives
can be made without requiring changes to the base protocol.
<p id="rfc.section.3.2.3.p.2">This extension mechanism depends on an HTTP cache obeying all of the cache-control directives defined for its native HTTP-version,
<p id="rfc.section.3.2.3.p.3">For example, consider a hypothetical new response directive called "community" that acts as a modifier to the private directive.
We define this new directive to mean that, in addition to any private cache, any cache that is shared only by members of the
community named within its value may cache the response. An origin server wishing to allow the UCI community to use an otherwise
private response in their shared cache(s) could do so by including
</pre><p id="rfc.section.3.2.3.p.5">A cache seeing this header field will act correctly even if the cache does not understand the community cache-extension, since
<p id="rfc.section.3.2.3.p.6">A cache <em class="bcp14">MUST</em> ignore unrecognized cache directives; it is assumed that any cache directive likely to be unrecognized by an HTTP/1.1 cache
will be combined with standard directives (or the response's default cacheability) such that the cache behavior will remain
minimally correct even if the cache does not understand the extension(s).
<p id="rfc.section.3.2.3.p.7">The HTTP Cache Directive Registry defines the name space for the cache directives.</p>
<p id="rfc.section.3.2.3.p.8">A registration <em class="bcp14">MUST</em> include the following fields:
<li>Cache Directive Name</li>
<p id="rfc.section.3.2.3.p.9">Values to be added to this name space are subject to IETF review (<a href="#RFC5226" id="rfc.xref.RFC5226.1"><cite title="Guidelines for Writing an IANA Considerations Section in RFCs">[RFC5226]</cite></a>, <a href="http://tools.ietf.org/html/rfc5226#section-4.1">Section 4.1</a>).
<p id="rfc.section.3.2.3.p.10">The registry itself is maintained at &lt;<a href="http://www.iana.org/assignments/http-cache-directives">http://www.iana.org/assignments/http-cache-directives</a>&gt;.
<h2 id="rfc.section.3.3"><a href="#rfc.section.3.3">3.3</a>&nbsp;<a id="header.expires" href="#header.expires">Expires</a></h2>
<p id="rfc.section.3.3.p.1">The "Expires" header field gives the date/time after which the response is considered stale. See <a href="#expiration.model" title="Freshness Model">Section&nbsp;2.3</a> for further discussion of the freshness model.
<p id="rfc.section.3.3.p.2">The presence of an Expires field does not imply that the original resource will change or cease to exist at, before, or after
<p id="rfc.section.3.3.p.3">The field-value is an absolute date and time as defined by HTTP-date in <a href="p2-semantics.html#http.date" title="Date/Time Formats">Section 8</a> of <a href="#Part2" id="rfc.xref.Part2.7"><cite title="HTTP/1.1, part 2: Message Semantics">[Part2]</cite></a>; a sender <em class="bcp14">MUST</em> use the rfc1123-date format.
<div id="rfc.figure.u.13"></div><pre class="inline"><span id="rfc.iref.g.7"></span> <a href="#header.expires" class="smpl">Expires</a> = <a href="#abnf.dependencies" class="smpl">HTTP-date</a>
<p>For example</p> <pre class="text"> Expires: Thu, 01 Dec 1994 16:00:00 GMT
</pre><p id="rfc.section.3.3.p.6">A cache <em class="bcp14">MUST</em> treat other invalid date formats, especially including the value "0", as in the past (i.e., "already expired").
<div class="note" id="rfc.section.3.3.p.7">
<p> <b>Note:</b> If a response includes a Cache-Control field with the max-age directive (see <a href="#cache-response-directive" title="Response Cache-Control Directives">Section&nbsp;3.2.2</a>), that directive overrides the Expires field. Likewise, the s-maxage directive overrides Expires in shared caches.
<p id="rfc.section.3.3.p.8">Historically, HTTP required the Expires field-value to be no more than a year in the future. While longer freshness lifetimes
are no longer prohibited, extremely large values have been demonstrated to cause problems (e.g., clock overflows due to use
of 32-bit integers for time values), and most caches will evict a response far sooner than that. Therefore, senders ought
not produce them.
<p id="rfc.section.3.3.p.9">An origin server without a clock <em class="bcp14">MUST NOT</em> assign Expires values to a response unless these values were associated with the resource by a system or user with a reliable
clock. It <em class="bcp14">MAY</em> assign an Expires value that is known, at or before server configuration time, to be in the past (this allows "pre-expiration"
of responses without storing separate Expires values for each resource).
<div id="rfc.iref.p.5"></div>
<h2 id="rfc.section.3.4"><a href="#rfc.section.3.4">3.4</a>&nbsp;<a id="header.pragma" href="#header.pragma">Pragma</a></h2>
<p id="rfc.section.3.4.p.1">The "Pragma" header field allows backwards compatibility with HTTP/1.0 caches, so that clients can specify a "no-cache" request
that they will understand (as Cache-Control was not defined until HTTP/1.1). When the Cache-Control header is also present
and understood in a request, Pragma is ignored.
<p id="rfc.section.3.4.p.2">In HTTP/1.0, Pragma was defined as an extensible field for implementation-specified directives for recipients. This specification
deprecates such extensions to improve interoperability.
<div id="rfc.figure.u.15"></div><pre class="inline"><span id="rfc.iref.g.8"></span><span id="rfc.iref.g.9"></span><span id="rfc.iref.g.10"></span> <a href="#header.pragma" class="smpl">Pragma</a> = 1#<a href="#header.pragma" class="smpl">pragma-directive</a>
<a href="#header.pragma" class="smpl">pragma-directive</a> = "no-cache" / <a href="#header.pragma" class="smpl">extension-pragma</a>
<a href="#header.pragma" class="smpl">extension-pragma</a> = <a href="#core.rules" class="smpl">token</a> [ "=" ( <a href="#core.rules" class="smpl">token</a> / <a href="#core.rules" class="smpl">quoted-string</a> ) ]
</pre><p id="rfc.section.3.4.p.4">When the Cache-Control header is not present in a request, the no-cache request pragma-directive <em class="bcp14">MUST</em> have the same effect on caches as if "Cache-Control: no-cache" were present (see <a href="#cache-request-directive" title="Request Cache-Control Directives">Section&nbsp;3.2.1</a>).
<p id="rfc.section.3.4.p.5">When sending a no-cache request, a client ought to include both the pragma and cache-control directives, unless Cache-Control:
no-cache is purposefully omitted to target other Cache-Control response directives at HTTP/1.1 caches. For example:
<div id="rfc.figure.u.16"></div> <pre class="text">GET / HTTP/1.1
</pre> <p id="rfc.section.3.4.p.7">will constrain HTTP/1.1 caches to serve a response no older than 30 seconds, while precluding implementations that do not
understand Cache-Control from serving a cached response.
<div class="note" id="rfc.section.3.4.p.8">
<p> <b>Note:</b> Because the meaning of "Pragma: no-cache" in responses is not specified, it does not provide a reliable replacement for "Cache-Control:
no-cache" in them.
<h2 id="rfc.section.3.5"><a href="#rfc.section.3.5">3.5</a>&nbsp;<a id="header.vary" href="#header.vary">Vary</a></h2>
<p id="rfc.section.3.5.p.1">The "Vary" header field conveys the set of header fields that were used to select the representation.</p>
<p id="rfc.section.3.5.p.2">Caches use this information, in part, to determine whether a stored response can be used to satisfy a given request; see <a href="#caching.negotiated.responses" title="Caching Negotiated Responses">Section&nbsp;2.7</a>. determines, while the response is fresh, whether a cache is permitted to use the response to reply to a subsequent request
without validation; see <a href="#caching.negotiated.responses" title="Caching Negotiated Responses">Section&nbsp;2.7</a>.
<p id="rfc.section.3.5.p.3">In uncacheable or stale responses, the Vary field value advises the user agent about the criteria that were used to select
the representation.
<div id="rfc.figure.u.17"></div><pre class="inline"><span id="rfc.iref.g.11"></span> <a href="#header.vary" class="smpl">Vary</a> = "*" / 1#<a href="#abnf.dependencies" class="smpl">field-name</a>
</pre><p id="rfc.section.3.5.p.5">The set of header fields named by the Vary field value is known as the selecting header fields.</p>
<p id="rfc.section.3.5.p.6">A server <em class="bcp14">SHOULD</em> include a Vary header field with any cacheable response that is subject to server-driven negotiation. Doing so allows a cache
<p id="rfc.section.3.5.p.7">A Vary field value of "*" signals that unspecified parameters not limited to the header fields (e.g., the network address
of the client), play a role in the selection of the response representation; therefore, a cache cannot determine whether this
response is appropriate. A proxy <em class="bcp14">MUST NOT</em> generate the "*" value.
<p id="rfc.section.3.5.p.8">The field-names given are not limited to the set of standard header fields defined by this specification. Field names are
<h2 id="rfc.section.3.6"><a href="#rfc.section.3.6">3.6</a>&nbsp;<a id="header.warning" href="#header.warning">Warning</a></h2>
<p id="rfc.section.3.6.p.1">The "Warning" header field is used to carry additional information about the status or transformation of a message that might
not be reflected in the message. This information is typically used to warn about possible incorrectness introduced by caching
operations or transformations applied to the payload of the message.
<p id="rfc.section.3.6.p.2">Warnings can be used for other purposes, both cache-related and otherwise. The use of a warning, rather than an error status
code, distinguishes these responses from true failures.
<p id="rfc.section.3.6.p.3">Warning header fields can in general be applied to any message, however some warn-codes are specific to caches and can only
be applied to response messages.
<div id="rfc.figure.u.18"></div><pre class="inline"><span id="rfc.iref.g.12"></span><span id="rfc.iref.g.13"></span><span id="rfc.iref.g.14"></span><span id="rfc.iref.g.15"></span><span id="rfc.iref.g.16"></span><span id="rfc.iref.g.17"></span> <a href="#header.warning" class="smpl">Warning</a> = 1#<a href="#header.warning" class="smpl">warning-value</a>
<a href="#header.warning" class="smpl">warn-agent</a> = ( <a href="#abnf.dependencies" class="smpl">uri-host</a> [ ":" <a href="#abnf.dependencies" class="smpl">port</a> ] ) / <a href="#abnf.dependencies" class="smpl">pseudonym</a>
; the Warning header field, for use in debugging
<a href="#header.warning" class="smpl">warn-text</a> = <a href="#core.rules" class="smpl">quoted-string</a>
</pre><p id="rfc.section.3.6.p.5">Multiple warnings can be attached to a response (either by the origin server or by a cache), including multiple warnings with
the same code number, only differing in warn-text.
<p id="rfc.section.3.6.p.6">When this occurs, the user agent <em class="bcp14">SHOULD</em> inform the user of as many of them as possible, in the order that they appear in the response.
<p id="rfc.section.3.6.p.7">Systems that generate multiple Warning header fields are encouraged to order them with this user agent behavior in mind. New
Warning header fields are added after any existing Warning headers fields.
<p id="rfc.section.3.6.p.8">Warnings are assigned three digit warn-codes. The first digit indicates whether the Warning is required to be deleted from
a stored response after validation:
<li>1xx Warnings describe the freshness or validation status of the response, and so <em class="bcp14">MUST</em> be deleted by a cache after validation. They can only be generated by a cache when validating a cached entry, and <em class="bcp14">MUST NOT</em> be generated in any other situation.
<li>2xx Warnings describe some aspect of the representation that is not rectified by a validation (for example, a lossy compression
of the representation) and <em class="bcp14">MUST NOT</em> be deleted by a cache after validation, unless a full response is returned, in which case they <em class="bcp14">MUST</em> be.
<p id="rfc.section.3.6.p.9">If an implementation sends a message with one or more Warning header fields to a receiver whose version is HTTP/1.0 or lower,
then the sender <em class="bcp14">MUST</em> include in each warning-value a warn-date that matches the Date header field in the message.
<p id="rfc.section.3.6.p.10">If a system receives a message with a warning-value that includes a warn-date, and that warn-date is different from the Date
value in the response, then that warning-value <em class="bcp14">MUST</em> be deleted from the message before storing, forwarding, or using it. (preventing the consequences of naive caching of Warning
header fields.) If all of the warning-values are deleted for this reason, the Warning header field <em class="bcp14">MUST</em> be deleted as well.
<p id="rfc.section.3.6.p.11">The following warn-codes are defined by this specification, each with a recommended warn-text in English, and a description
of its meaning.
<div id="rfc.iref.78"></div>
<div id="rfc.iref.w.2"></div>
<h3 id="rfc.section.3.6.1"><a href="#rfc.section.3.6.1">3.6.1</a>&nbsp;<a id="warn.110" href="#warn.110">110 Response is Stale</a></h3>
<p id="rfc.section.3.6.1.p.1">A cache <em class="bcp14">SHOULD</em> include this whenever the returned response is stale.
<div id="rfc.iref.79"></div>
<div id="rfc.iref.w.3"></div>
<h3 id="rfc.section.3.6.2"><a href="#rfc.section.3.6.2">3.6.2</a>&nbsp;<a id="warn.111" href="#warn.111">111 Revalidation Failed</a></h3>
<p id="rfc.section.3.6.2.p.1">A cache <em class="bcp14">SHOULD</em> include this when returning a stale response because an attempt to validate the response failed, due to an inability to reach
<div id="rfc.iref.80"></div>
<div id="rfc.iref.w.4"></div>
<h3 id="rfc.section.3.6.3"><a href="#rfc.section.3.6.3">3.6.3</a>&nbsp;<a id="warn.112" href="#warn.112">112 Disconnected Operation</a></h3>
<p id="rfc.section.3.6.3.p.1">A cache <em class="bcp14">SHOULD</em> include this if it is intentionally disconnected from the rest of the network for a period of time.
<div id="rfc.iref.81"></div>
<div id="rfc.iref.w.5"></div>
<h3 id="rfc.section.3.6.4"><a href="#rfc.section.3.6.4">3.6.4</a>&nbsp;<a id="warn.113" href="#warn.113">113 Heuristic Expiration</a></h3>
<p id="rfc.section.3.6.4.p.1">A cache <em class="bcp14">SHOULD</em> include this if it heuristically chose a freshness lifetime greater than 24 hours and the response's age is greater than 24
<div id="rfc.iref.82"></div>
<div id="rfc.iref.w.6"></div>
<h3 id="rfc.section.3.6.5"><a href="#rfc.section.3.6.5">3.6.5</a>&nbsp;<a id="warn.199" href="#warn.199">199 Miscellaneous Warning</a></h3>
<p id="rfc.section.3.6.5.p.1">The warning text can include arbitrary information to be presented to a human user, or logged. A system receiving this warning <em class="bcp14">MUST NOT</em> take any automated action, besides presenting the warning to the user.
<div id="rfc.iref.83"></div>
<div id="rfc.iref.w.7"></div>
<h3 id="rfc.section.3.6.6"><a href="#rfc.section.3.6.6">3.6.6</a>&nbsp;<a id="warn.214" href="#warn.214">214 Transformation Applied</a></h3>
<p id="rfc.section.3.6.6.p.1"> <em class="bcp14">MUST</em> be added by a proxy if it applies any transformation to the representation, such as changing the content-coding, media-type,
or modifying the representation data, unless this Warning code already appears in the response.
<div id="rfc.iref.84"></div>
<div id="rfc.iref.w.8"></div>
<h3 id="rfc.section.3.6.7"><a href="#rfc.section.3.6.7">3.6.7</a>&nbsp;<a id="warn.299" href="#warn.299">299 Miscellaneous Persistent Warning</a></h3>
<p id="rfc.section.3.6.7.p.1">The warning text can include arbitrary information to be presented to a human user, or logged. A system receiving this warning <em class="bcp14">MUST NOT</em> take any automated action.
<h3 id="rfc.section.3.6.8"><a href="#rfc.section.3.6.8">3.6.8</a>&nbsp;<a id="warn.code.extensions" href="#warn.code.extensions">Warn Code Extensions</a></h3>
<p id="rfc.section.3.6.8.p.1">The HTTP Warn Code Registry defines the name space for warn codes.</p>
<p id="rfc.section.3.6.8.p.2">A registration <em class="bcp14">MUST</em> include the following fields:
<li>Warn Code (3 digits)</li>
<li>Short Description</li>
<p id="rfc.section.3.6.8.p.3">Values to be added to this name space are subject to IETF review (<a href="#RFC5226" id="rfc.xref.RFC5226.2"><cite title="Guidelines for Writing an IANA Considerations Section in RFCs">[RFC5226]</cite></a>, <a href="http://tools.ietf.org/html/rfc5226#section-4.1">Section 4.1</a>).
<p id="rfc.section.3.6.8.p.4">The registry itself is maintained at &lt;<a href="http://www.iana.org/assignments/http-warn-codes">http://www.iana.org/assignments/http-warn-codes</a>&gt;.
<h1 id="rfc.section.4"><a href="#rfc.section.4">4.</a>&nbsp;<a id="history.lists" href="#history.lists">History Lists</a></h1>
<p id="rfc.section.4.p.1">User agents often have history mechanisms, such as "Back" buttons and history lists, that can be used to redisplay a representation
<p id="rfc.section.4.p.2">The freshness model (<a href="#expiration.model" title="Freshness Model">Section&nbsp;2.3</a>) does not necessarily apply to history mechanisms. I.e., a history mechanism can display a previous representation even if
it has expired.
<p id="rfc.section.4.p.3">This does not prohibit the history mechanism from telling the user that a view might be stale, or from honoring cache directives
(e.g., Cache-Control: no-store).
<h2 id="rfc.section.5.1"><a href="#rfc.section.5.1">5.1</a>&nbsp;<a id="cache.directive.registration" href="#cache.directive.registration">Cache Directive Registry</a></h2>
<p id="rfc.section.5.1.p.1">The registration procedure for HTTP Cache Directives is defined by <a href="#cache.control.extensions" title="Cache Control Extensions">Section&nbsp;3.2.3</a> of this document.
<p id="rfc.section.5.1.p.2">The HTTP Cache Directive Registry shall be created at &lt;<a href="http://www.iana.org/assignments/http-cache-directives">http://www.iana.org/assignments/http-cache-directives</a>&gt; and be populated with the registrations below:
<div id="iana.cache.directive.registration.table"></div>
<th>Cache Directive</th>
<td class="left">max-age</td>
<td class="left"> <a href="#cache-request-directive" title="Request Cache-Control Directives">Section&nbsp;3.2.1</a>, <a href="#cache-response-directive" title="Response Cache-Control Directives">Section&nbsp;3.2.2</a>
<td class="left">max-stale</td>
<td class="left"> <a href="#cache-request-directive" title="Request Cache-Control Directives">Section&nbsp;3.2.1</a>
<td class="left">min-fresh</td>
<td class="left">must-revalidate</td>
<td class="left"> <a href="#cache-response-directive" title="Response Cache-Control Directives">Section&nbsp;3.2.2</a>
<td class="left">no-cache</td>
<td class="left">no-store</td>
<td class="left">no-transform</td>
<td class="left">only-if-cached</td>
<td class="left">private</td>
<td class="left">proxy-revalidate</td>
<td class="left">public</td>
<td class="left">s-maxage</td>
<td class="left">stale-if-error</td>
<td class="left"> <a href="#RFC5861" id="rfc.xref.RFC5861.1"><cite title="HTTP Cache-Control Extensions for Stale Content">[RFC5861]</cite></a>, <a href="http://tools.ietf.org/html/rfc5861#section-4">Section 4</a>
<td class="left">stale-while-revalidate</td>
<td class="left"> <a href="#RFC5861" id="rfc.xref.RFC5861.2"><cite title="HTTP Cache-Control Extensions for Stale Content">[RFC5861]</cite></a>, <a href="http://tools.ietf.org/html/rfc5861#section-3">Section 3</a>
<h2 id="rfc.section.5.2"><a href="#rfc.section.5.2">5.2</a>&nbsp;<a id="warn.code.registration" href="#warn.code.registration">Warn Code Registry</a></h2>
<p id="rfc.section.5.2.p.1">The registration procedure for HTTP Warn Codes is defined by <a href="#warn.code.extensions" title="Warn Code Extensions">Section&nbsp;3.6.8</a> of this document.
<p id="rfc.section.5.2.p.2">The HTTP Warn Code Registry shall be created at &lt;<a href="http://www.iana.org/assignments/http-cache-directives">http://www.iana.org/assignments/http-cache-directives</a>&gt; and be populated with the registrations below:
<div id="iana.warn.code.registration.table"></div>
<th>Warn Code</th>
<th>Short Description</th>
<td class="left">110</td>
<td class="left">Response is Stale</td>
<td class="left"> <a href="#warn.110" id="rfc.xref.warn.110.1" title="110 Response is Stale">Section&nbsp;3.6.1</a>
<td class="left">111</td>
<td class="left">Revalidation Failed</td>
<td class="left"> <a href="#warn.111" id="rfc.xref.warn.111.1" title="111 Revalidation Failed">Section&nbsp;3.6.2</a>
<td class="left">112</td>
<td class="left">Disconnected Operation</td>
<td class="left"> <a href="#warn.112" id="rfc.xref.warn.112.1" title="112 Disconnected Operation">Section&nbsp;3.6.3</a>
<td class="left">113</td>
<td class="left">Heuristic Expiration</td>
<td class="left"> <a href="#warn.113" id="rfc.xref.warn.113.1" title="113 Heuristic Expiration">Section&nbsp;3.6.4</a>
<td class="left">199</td>
<td class="left">Miscellaneous Warning</td>
<td class="left"> <a href="#warn.199" id="rfc.xref.warn.199.1" title="199 Miscellaneous Warning">Section&nbsp;3.6.5</a>
<td class="left">214</td>
<td class="left">Transformation Applied</td>
<td class="left"> <a href="#warn.214" id="rfc.xref.warn.214.1" title="214 Transformation Applied">Section&nbsp;3.6.6</a>
<td class="left">299</td>
<td class="left">Miscellaneous Persistent Warning</td>
<td class="left"> <a href="#warn.299" id="rfc.xref.warn.299.1" title="299 Miscellaneous Persistent Warning">Section&nbsp;3.6.7</a>
<h2 id="rfc.section.5.3"><a href="#rfc.section.5.3">5.3</a>&nbsp;<a id="header.field.registration" href="#header.field.registration">Header Field Registration</a></h2>
<p id="rfc.section.5.3.p.1">The Message Header Field Registry located at &lt;<a href="http://www.iana.org/assignments/message-headers/message-header-index.html">http://www.iana.org/assignments/message-headers/message-header-index.html</a>&gt; shall be updated with the permanent registrations below (see <a href="#RFC3864" id="rfc.xref.RFC3864.1"><cite title="Registration Procedures for Message Header Fields">[RFC3864]</cite></a>):
<td class="left"> <a href="#header.age" id="rfc.xref.header.age.3" title="Age">Section&nbsp;3.1</a>
<td class="left"> <a href="#header.cache-control" id="rfc.xref.header.cache-control.2" title="Cache-Control">Section&nbsp;3.2</a>
<td class="left"> <a href="#header.expires" id="rfc.xref.header.expires.4" title="Expires">Section&nbsp;3.3</a>
<td class="left"> <a href="#header.pragma" id="rfc.xref.header.pragma.3" title="Pragma">Section&nbsp;3.4</a>
<td class="left"> <a href="#header.vary" id="rfc.xref.header.vary.2" title="Vary">Section&nbsp;3.5</a>
<td class="left"> <a href="#header.warning" id="rfc.xref.header.warning.4" title="Warning">Section&nbsp;3.6</a>
<p id="rfc.section.5.3.p.2">The change controller is: "IETF (iesg@ietf.org) - Internet Engineering Task Force".</p>
<p id="rfc.section.6.p.1">Caches expose additional potential vulnerabilities, since the contents of the cache represent an attractive target for malicious
exploitation. Because cache contents persist after an HTTP request is complete, an attack on the cache can reveal information
long after a user believes that the information has been removed from the network. Therefore, cache contents need to be protected
as sensitive information.
<p id="rfc.section.7.p.1">See <a href="p1-messaging.html#acks" title="Acknowledgments">Section 11</a> of <a href="#Part1" id="rfc.xref.Part1.17"><cite title="HTTP/1.1, part 1: URIs, Connections, and Message Parsing">[Part1]</cite></a>.
<td class="top"><a href="mailto:fielding@gbiv.com" title="Adobe Systems Incorporated">Fielding, R., Ed.</a>, <a href="mailto:jg@freedesktop.org" title="Alcatel-Lucent Bell Labs">Gettys, J.</a>, <a href="mailto:JeffMogul@acm.org" title="Hewlett-Packard Company">Mogul, J.</a>, <a href="mailto:henrikn@microsoft.com" title="Microsoft Corporation">Frystyk, H.</a>, <a href="mailto:LMM@acm.org" title="Adobe Systems Incorporated">Masinter, L.</a>, <a href="mailto:paulle@microsoft.com" title="Microsoft Corporation">Leach, P.</a>, <a href="mailto:timbl@w3.org" title="World Wide Web Consortium">Berners-Lee, T.</a>, <a href="mailto:ylafon@w3.org" title="World Wide Web Consortium">Lafon, Y., Ed.</a>, and <a href="mailto:julian.reschke@greenbytes.de" title="greenbytes GmbH">J. Reschke, Ed.</a>, “<a href="http://tools.ietf.org/html/draft-ietf-httpbis-p1-messaging-latest">HTTP/1.1, part 1: URIs, Connections, and Message Parsing</a>”, Internet-Draft&nbsp;draft-ietf-httpbis-p1-messaging-latest (work in progress), January&nbsp;2012.
<td class="top"><a href="mailto:fielding@gbiv.com" title="Adobe Systems Incorporated">Fielding, R., Ed.</a>, <a href="mailto:jg@freedesktop.org" title="Alcatel-Lucent Bell Labs">Gettys, J.</a>, <a href="mailto:JeffMogul@acm.org" title="Hewlett-Packard Company">Mogul, J.</a>, <a href="mailto:henrikn@microsoft.com" title="Microsoft Corporation">Frystyk, H.</a>, <a href="mailto:LMM@acm.org" title="Adobe Systems Incorporated">Masinter, L.</a>, <a href="mailto:paulle@microsoft.com" title="Microsoft Corporation">Leach, P.</a>, <a href="mailto:timbl@w3.org" title="World Wide Web Consortium">Berners-Lee, T.</a>, <a href="mailto:ylafon@w3.org" title="World Wide Web Consortium">Lafon, Y., Ed.</a>, and <a href="mailto:julian.reschke@greenbytes.de" title="greenbytes GmbH">J. Reschke, Ed.</a>, “<a href="http://tools.ietf.org/html/draft-ietf-httpbis-p2-semantics-latest">HTTP/1.1, part 2: Message Semantics</a>”, Internet-Draft&nbsp;draft-ietf-httpbis-p2-semantics-latest (work in progress), January&nbsp;2012.
<td class="top"><a href="mailto:fielding@gbiv.com" title="Adobe Systems Incorporated">Fielding, R., Ed.</a>, <a href="mailto:jg@freedesktop.org" title="Alcatel-Lucent Bell Labs">Gettys, J.</a>, <a href="mailto:JeffMogul@acm.org" title="Hewlett-Packard Company">Mogul, J.</a>, <a href="mailto:henrikn@microsoft.com" title="Microsoft Corporation">Frystyk, H.</a>, <a href="mailto:LMM@acm.org" title="Adobe Systems Incorporated">Masinter, L.</a>, <a href="mailto:paulle@microsoft.com" title="Microsoft Corporation">Leach, P.</a>, <a href="mailto:timbl@w3.org" title="World Wide Web Consortium">Berners-Lee, T.</a>, <a href="mailto:ylafon@w3.org" title="World Wide Web Consortium">Lafon, Y., Ed.</a>, and <a href="mailto:julian.reschke@greenbytes.de" title="greenbytes GmbH">J. Reschke, Ed.</a>, “<a href="http://tools.ietf.org/html/draft-ietf-httpbis-p4-conditional-latest">HTTP/1.1, part 4: Conditional Requests</a>”, Internet-Draft&nbsp;draft-ietf-httpbis-p4-conditional-latest (work in progress), January&nbsp;2012.
<td class="top"><a href="mailto:fielding@gbiv.com" title="Adobe Systems Incorporated">Fielding, R., Ed.</a>, <a href="mailto:jg@freedesktop.org" title="Alcatel-Lucent Bell Labs">Gettys, J.</a>, <a href="mailto:JeffMogul@acm.org" title="Hewlett-Packard Company">Mogul, J.</a>, <a href="mailto:henrikn@microsoft.com" title="Microsoft Corporation">Frystyk, H.</a>, <a href="mailto:LMM@acm.org" title="Adobe Systems Incorporated">Masinter, L.</a>, <a href="mailto:paulle@microsoft.com" title="Microsoft Corporation">Leach, P.</a>, <a href="mailto:timbl@w3.org" title="World Wide Web Consortium">Berners-Lee, T.</a>, <a href="mailto:ylafon@w3.org" title="World Wide Web Consortium">Lafon, Y., Ed.</a>, and <a href="mailto:julian.reschke@greenbytes.de" title="greenbytes GmbH">J. Reschke, Ed.</a>, “<a href="http://tools.ietf.org/html/draft-ietf-httpbis-p5-range-latest">HTTP/1.1, part 5: Range Requests and Partial Responses</a>”, Internet-Draft&nbsp;draft-ietf-httpbis-p5-range-latest (work in progress), January&nbsp;2012.
<td class="top"><a href="mailto:fielding@gbiv.com" title="Adobe Systems Incorporated">Fielding, R., Ed.</a>, <a href="mailto:jg@freedesktop.org" title="Alcatel-Lucent Bell Labs">Gettys, J.</a>, <a href="mailto:JeffMogul@acm.org" title="Hewlett-Packard Company">Mogul, J.</a>, <a href="mailto:henrikn@microsoft.com" title="Microsoft Corporation">Frystyk, H.</a>, <a href="mailto:LMM@acm.org" title="Adobe Systems Incorporated">Masinter, L.</a>, <a href="mailto:paulle@microsoft.com" title="Microsoft Corporation">Leach, P.</a>, <a href="mailto:timbl@w3.org" title="World Wide Web Consortium">Berners-Lee, T.</a>, <a href="mailto:ylafon@w3.org" title="World Wide Web Consortium">Lafon, Y., Ed.</a>, and <a href="mailto:julian.reschke@greenbytes.de" title="greenbytes GmbH">J. Reschke, Ed.</a>, “<a href="http://tools.ietf.org/html/draft-ietf-httpbis-p7-auth-latest">HTTP/1.1, part 7: Authentication</a>”, Internet-Draft&nbsp;draft-ietf-httpbis-p7-auth-latest (work in progress), January&nbsp;2012.
<td class="reference"><b id="RFC5861">[RFC5861]</b></td>
<td class="top"><a href="mailto:mnot@yahoo-inc.com" title="Yahoo! Inc.">Nottingham, M.</a>, “<a href="http://tools.ietf.org/html/rfc5861">HTTP Cache-Control Extensions for Stale Content</a>”, RFC&nbsp;5861, April&nbsp;2010.
<address class="vcard"><span class="vcardline"><span class="fn">Mark Nottingham</span>
<span class="n hidden"><span class="family-name">Nottingham</span><span class="given-name">Mark</span></span></span><span class="org vcardline">Rackspace</span><span class="vcardline">Email: <a href="mailto:mnot@mnot.net"><span class="email">mnot@mnot.net</span></a></span><span class="vcardline">URI: <a href="http://www.mnot.net/" class="url">http://www.mnot.net/</a></span></address>
<p id="rfc.section.A.p.1">Make the specified age calculation algorithm less conservative. (<a href="#age.calculations" title="Calculating Age">Section&nbsp;2.3.2</a>)
<p id="rfc.section.A.p.2">Remove requirement to consider Content-Location in successful responses in order to determine the appropriate response to
use. (<a href="#validation.model" title="Validation Model">Section&nbsp;2.4</a>)
<p id="rfc.section.A.p.3">Clarify denial of service attack avoidance requirement. (<a href="#invalidation.after.updates.or.deletions" title="Request Methods that Invalidate">Section&nbsp;2.5</a>)
<p id="rfc.section.A.p.4">Change ABNF productions for header fields to only define the field value. (<a href="#header.field.definitions" title="Header Field Definitions">Section&nbsp;3</a>)
<p id="rfc.section.A.p.5">Do not mention RFC 2047 encoding and multiple languages in Warning header fields anymore, as these aspects never were implemented.
(<a href="#header.warning" id="rfc.xref.header.warning.5" title="Warning">Section&nbsp;3.6</a>)
<div id="rfc.figure.u.19"></div> <pre class="inline"><a href="#header.age" class="smpl">Age</a> = delta-seconds
<a href="#header.cache-control" class="smpl">Cache-Control</a> = *( "," OWS ) cache-directive *( OWS "," [ OWS
<a href="#header.expires" class="smpl">Expires</a> = HTTP-date
<a href="#abnf.dependencies" class="smpl">HTTP-date</a> = &lt;HTTP-date, defined in [Part2], Section 8&gt;
<a href="#header.pragma" class="smpl">Pragma</a> = *( "," OWS ) pragma-directive *( OWS "," [ OWS
<a href="#header.vary" class="smpl">Vary</a> = "*" / ( *( "," OWS ) field-name *( OWS "," [ OWS field-name ]
<a href="#header.warning" class="smpl">Warning</a> = *( "," OWS ) warning-value *( OWS "," [ OWS warning-value ]
<a href="#header.cache-control" class="smpl">cache-directive</a> = cache-request-directive / cache-response-directive
<a href="#header.cache-control" class="smpl">cache-extension</a> = token [ "=" ( token / quoted-string ) ]
<a href="#header.cache-control" class="smpl">cache-request-directive</a> = "no-cache" / "no-store" / ( "max-age="
<a href="#header.cache-control" class="smpl">cache-response-directive</a> = "public" / ( "private" [ "=" DQUOTE *( ","
<a href="#delta-seconds" class="smpl">delta-seconds</a> = 1*DIGIT
<a href="#header.pragma" class="smpl">extension-pragma</a> = token [ "=" ( token / quoted-string ) ]
<a href="#abnf.dependencies" class="smpl">field-name</a> = &lt;field-name, defined in [Part1], Section 3.2&gt;
<a href="#abnf.dependencies" class="smpl">port</a> = &lt;port, defined in [Part1], Section 2.7&gt;
<a href="#header.pragma" class="smpl">pragma-directive</a> = "no-cache" / extension-pragma
<a href="#abnf.dependencies" class="smpl">pseudonym</a> = &lt;pseudonym, defined in [Part1], Section 8.8&gt;
<a href="#core.rules" class="smpl">quoted-string</a> = &lt;quoted-string, defined in [Part1], Section 3.2.3&gt;
<a href="#core.rules" class="smpl">token</a> = &lt;token, defined in [Part1], Section 3.2.3&gt;
<a href="#abnf.dependencies" class="smpl">uri-host</a> = &lt;uri-host, defined in [Part1], Section 2.7&gt;
<a href="#header.warning" class="smpl">warn-agent</a> = ( uri-host [ ":" port ] ) / pseudonym
<a href="#header.warning" class="smpl">warn-code</a> = 3DIGIT
<a href="#header.warning" class="smpl">warn-date</a> = DQUOTE HTTP-date DQUOTE
<a href="#header.warning" class="smpl">warn-text</a> = quoted-string
<a href="#header.warning" class="smpl">warning-value</a> = warn-code SP warn-agent SP warn-text [ SP warn-date
</pre> <div id="rfc.figure.u.20"></div>
<p>ABNF diagnostics:</p><pre class="inline">; Age defined but not used
<h2 id="rfc.section.C.2"><a href="#rfc.section.C.2">C.2</a>&nbsp;Since draft-ietf-httpbis-p6-cache-00
<li> &lt;<a href="http://tools.ietf.org/wg/httpbis/trac/ticket/9">http://tools.ietf.org/wg/httpbis/trac/ticket/9</a>&gt;: "Trailer" (&lt;<a href="http://purl.org/NET/http-errata#trailer-hop">http://purl.org/NET/http-errata#trailer-hop</a>&gt;)
<li> &lt;<a href="http://tools.ietf.org/wg/httpbis/trac/ticket/12">http://tools.ietf.org/wg/httpbis/trac/ticket/12</a>&gt;: "Invalidation after Update or Delete" (&lt;<a href="http://purl.org/NET/http-errata#invalidupd">http://purl.org/NET/http-errata#invalidupd</a>&gt;)
<li> &lt;<a href="http://tools.ietf.org/wg/httpbis/trac/ticket/48">http://tools.ietf.org/wg/httpbis/trac/ticket/48</a>&gt;: "Date reference typo"
<li> &lt;<a href="http://tools.ietf.org/wg/httpbis/trac/ticket/49">http://tools.ietf.org/wg/httpbis/trac/ticket/49</a>&gt;: "Connection header text"
<li> &lt;<a href="http://tools.ietf.org/wg/httpbis/trac/ticket/87">http://tools.ietf.org/wg/httpbis/trac/ticket/87</a>&gt;: "typo in 13.2.2"
<li>Use names of RFC4234 core rules DQUOTE and HTAB (work in progress on &lt;<a href="http://tools.ietf.org/wg/httpbis/trac/ticket/36">http://tools.ietf.org/wg/httpbis/trac/ticket/36</a>&gt;)
<h2 id="rfc.section.C.3"><a href="#rfc.section.C.3">C.3</a>&nbsp;Since draft-ietf-httpbis-p6-cache-01
<li> &lt;<a href="http://tools.ietf.org/wg/httpbis/trac/ticket/82">http://tools.ietf.org/wg/httpbis/trac/ticket/82</a>&gt;: "rel_path not used"
<p id="rfc.section.C.3.p.2">Other changes: </p>
<li>Get rid of duplicate BNF rule names ("host" -&gt; "uri-host") (work in progress on &lt;<a href="http://tools.ietf.org/wg/httpbis/trac/ticket/36">http://tools.ietf.org/wg/httpbis/trac/ticket/36</a>&gt;)
<h2 id="rfc.section.C.4"><a href="#rfc.section.C.4">C.4</a>&nbsp;<a id="changes.since.02" href="#changes.since.02">Since draft-ietf-httpbis-p6-cache-02</a></h2>
<p id="rfc.section.C.4.p.1">Ongoing work on IANA Message Header Field Registration (&lt;<a href="http://tools.ietf.org/wg/httpbis/trac/ticket/40">http://tools.ietf.org/wg/httpbis/trac/ticket/40</a>&gt;):
<h2 id="rfc.section.C.5"><a href="#rfc.section.C.5">C.5</a>&nbsp;<a id="changes.since.03" href="#changes.since.03">Since draft-ietf-httpbis-p6-cache-03</a></h2>
<li> &lt;<a href="http://tools.ietf.org/wg/httpbis/trac/ticket/106">http://tools.ietf.org/wg/httpbis/trac/ticket/106</a>&gt;: "Vary header classification"
<h2 id="rfc.section.C.6"><a href="#rfc.section.C.6">C.6</a>&nbsp;<a id="changes.since.04" href="#changes.since.04">Since draft-ietf-httpbis-p6-cache-04</a></h2>
<h2 id="rfc.section.C.7"><a href="#rfc.section.C.7">C.7</a>&nbsp;<a id="changes.since.05" href="#changes.since.05">Since draft-ietf-httpbis-p6-cache-05</a></h2>
<p id="rfc.section.C.7.p.1">This is a total rewrite of this part of the specification.</p>
<p id="rfc.section.C.7.p.2">Affected issues: </p>
<li> &lt;<a href="http://tools.ietf.org/wg/httpbis/trac/ticket/54">http://tools.ietf.org/wg/httpbis/trac/ticket/54</a>&gt;: "Definition of 1xx Warn-Codes"
<li> &lt;<a href="http://tools.ietf.org/wg/httpbis/trac/ticket/60">http://tools.ietf.org/wg/httpbis/trac/ticket/60</a>&gt;: "Placement of 13.5.1 and 13.5.2"
<li> &lt;<a href="http://tools.ietf.org/wg/httpbis/trac/ticket/138">http://tools.ietf.org/wg/httpbis/trac/ticket/138</a>&gt;: "The role of Warning and Semantic Transparency in Caching"
<li> &lt;<a href="http://tools.ietf.org/wg/httpbis/trac/ticket/139">http://tools.ietf.org/wg/httpbis/trac/ticket/139</a>&gt;: "Methods and Caching"
<p id="rfc.section.C.7.p.3">In addition: Final work on ABNF conversion (&lt;<a href="http://tools.ietf.org/wg/httpbis/trac/ticket/36">http://tools.ietf.org/wg/httpbis/trac/ticket/36</a>&gt;):
<h2 id="rfc.section.C.8"><a href="#rfc.section.C.8">C.8</a>&nbsp;<a id="changes.since.06" href="#changes.since.06">Since draft-ietf-httpbis-p6-cache-06</a></h2>
<p id="rfc.section.C.8.p.2">Affected issues: </p>
<li> &lt;<a href="http://tools.ietf.org/wg/httpbis/trac/ticket/37">http://tools.ietf.org/wg/httpbis/trac/ticket/37</a>&gt;: "Vary and non-existant headers"
<h2 id="rfc.section.C.9"><a href="#rfc.section.C.9">C.9</a>&nbsp;<a id="changes.since.07" href="#changes.since.07">Since draft-ietf-httpbis-p6-cache-07</a></h2>
<li> &lt;<a href="http://tools.ietf.org/wg/httpbis/trac/ticket/169">http://tools.ietf.org/wg/httpbis/trac/ticket/169</a>&gt;: "private and no-cache CC directives with headers"
<li> &lt;<a href="http://tools.ietf.org/wg/httpbis/trac/ticket/187">http://tools.ietf.org/wg/httpbis/trac/ticket/187</a>&gt;: "RFC2047 and warn-text"
<h2 id="rfc.section.C.10"><a href="#rfc.section.C.10">C.10</a>&nbsp;<a id="changes.since.08" href="#changes.since.08">Since draft-ietf-httpbis-p6-cache-08</a></h2>
<p id="rfc.section.C.10.p.1">Closed issues: </p>
<li> &lt;<a href="http://tools.ietf.org/wg/httpbis/trac/ticket/147">http://tools.ietf.org/wg/httpbis/trac/ticket/147</a>&gt;: "serving negotiated responses from cache: header-specific canonicalization"
<li> &lt;<a href="http://tools.ietf.org/wg/httpbis/trac/ticket/197">http://tools.ietf.org/wg/httpbis/trac/ticket/197</a>&gt;: "Effect of CC directives on history lists"
<li> &lt;<a href="http://tools.ietf.org/wg/httpbis/trac/ticket/291">http://tools.ietf.org/wg/httpbis/trac/ticket/291</a>&gt;: "Cache Extensions can override no-store, etc."
<p id="rfc.section.C.10.p.2">Affected issues: </p>
<li> &lt;<a href="http://tools.ietf.org/wg/httpbis/trac/ticket/199">http://tools.ietf.org/wg/httpbis/trac/ticket/199</a>&gt;: Status codes and caching
<p id="rfc.section.C.10.p.3">Partly resolved issues: </p>
<h2 id="rfc.section.C.11"><a href="#rfc.section.C.11">C.11</a>&nbsp;<a id="changes.since.09" href="#changes.since.09">Since draft-ietf-httpbis-p6-cache-09</a></h2>
<p id="rfc.section.C.11.p.1">Closed issues: </p>
<li> &lt;<a href="http://tools.ietf.org/wg/httpbis/trac/ticket/29">http://tools.ietf.org/wg/httpbis/trac/ticket/29</a>&gt;: "Age calculation"
<li> &lt;<a href="http://tools.ietf.org/wg/httpbis/trac/ticket/168">http://tools.ietf.org/wg/httpbis/trac/ticket/168</a>&gt;: "Clarify differences between / requirements for request and response CC directives"
<li> &lt;<a href="http://tools.ietf.org/wg/httpbis/trac/ticket/174">http://tools.ietf.org/wg/httpbis/trac/ticket/174</a>&gt;: "Caching authenticated responses"
<li> &lt;<a href="http://tools.ietf.org/wg/httpbis/trac/ticket/208">http://tools.ietf.org/wg/httpbis/trac/ticket/208</a>&gt;: "IANA registry for cache-control directives"
<li> &lt;<a href="http://tools.ietf.org/wg/httpbis/trac/ticket/211">http://tools.ietf.org/wg/httpbis/trac/ticket/211</a>&gt;: "Heuristic caching of URLs with query components"
<p id="rfc.section.C.11.p.2">Partly resolved issues: </p>
<h2 id="rfc.section.C.12"><a href="#rfc.section.C.12">C.12</a>&nbsp;<a id="changes.since.10" href="#changes.since.10">Since draft-ietf-httpbis-p6-cache-10</a></h2>
<li> &lt;<a href="http://tools.ietf.org/wg/httpbis/trac/ticket/223">http://tools.ietf.org/wg/httpbis/trac/ticket/223</a>&gt;: "Allowing heuristic caching for new status codes"
<li>Clean up TODOs and prose in "Combining Responses."</li>
<h2 id="rfc.section.C.13"><a href="#rfc.section.C.13">C.13</a>&nbsp;<a id="changes.since.11" href="#changes.since.11">Since draft-ietf-httpbis-p6-cache-11</a></h2>
<p id="rfc.section.C.13.p.1">Closed issues: </p>
<li> &lt;<a href="http://tools.ietf.org/wg/httpbis/trac/ticket/204">http://tools.ietf.org/wg/httpbis/trac/ticket/204</a>&gt;: "Text about clock requirement for caches belongs in p6"
<h2 id="rfc.section.C.14"><a href="#rfc.section.C.14">C.14</a>&nbsp;<a id="changes.since.12" href="#changes.since.12">Since draft-ietf-httpbis-p6-cache-12</a></h2>
<li> &lt;<a href="http://tools.ietf.org/wg/httpbis/trac/ticket/268">http://tools.ietf.org/wg/httpbis/trac/ticket/268</a>&gt;: "Clarify 'public'"
<h2 id="rfc.section.C.15"><a href="#rfc.section.C.15">C.15</a>&nbsp;<a id="changes.since.13" href="#changes.since.13">Since draft-ietf-httpbis-p6-cache-13</a></h2>
<h2 id="rfc.section.C.16"><a href="#rfc.section.C.16">C.16</a>&nbsp;<a id="changes.since.14" href="#changes.since.14">Since draft-ietf-httpbis-p6-cache-14</a></h2>
<p id="rfc.section.C.16.p.1">Closed issues: </p>
<li> &lt;<a href="http://tools.ietf.org/wg/httpbis/trac/ticket/38">http://tools.ietf.org/wg/httpbis/trac/ticket/38</a>&gt;: "Mismatch Vary"
<li> &lt;<a href="http://tools.ietf.org/wg/httpbis/trac/ticket/235">http://tools.ietf.org/wg/httpbis/trac/ticket/235</a>&gt;: "Cache Invalidation only happens upon successful responses"
<li> &lt;<a href="http://tools.ietf.org/wg/httpbis/trac/ticket/282">http://tools.ietf.org/wg/httpbis/trac/ticket/282</a>&gt;: "Recommend minimum sizes for protocol elements"
<li> &lt;<a href="http://tools.ietf.org/wg/httpbis/trac/ticket/289">http://tools.ietf.org/wg/httpbis/trac/ticket/289</a>&gt;: "Proxies don't 'understand' methods"
<li> &lt;<a href="http://tools.ietf.org/wg/httpbis/trac/ticket/292">http://tools.ietf.org/wg/httpbis/trac/ticket/292</a>&gt;: "Pragma"
<h2 id="rfc.section.C.17"><a href="#rfc.section.C.17">C.17</a>&nbsp;<a id="changes.since.15" href="#changes.since.15">Since draft-ietf-httpbis-p6-cache-15</a></h2>
<li> &lt;<a href="http://tools.ietf.org/wg/httpbis/trac/ticket/290">http://tools.ietf.org/wg/httpbis/trac/ticket/290</a>&gt;: "Motivate one-year limit for Expires"
<h2 id="rfc.section.C.18"><a href="#rfc.section.C.18">C.18</a>&nbsp;<a id="changes.since.16" href="#changes.since.16">Since draft-ietf-httpbis-p6-cache-16</a></h2>
<li> &lt;<a href="http://tools.ietf.org/wg/httpbis/trac/ticket/317">http://tools.ietf.org/wg/httpbis/trac/ticket/317</a>&gt;: "Cache-Control directive case sensitivity"
<h2 id="rfc.section.C.19"><a href="#rfc.section.C.19">C.19</a>&nbsp;<a id="changes.since.17" href="#changes.since.17">Since draft-ietf-httpbis-p6-cache-17</a></h2>
<li> &lt;<a href="http://tools.ietf.org/wg/httpbis/trac/ticket/293">http://tools.ietf.org/wg/httpbis/trac/ticket/293</a>&gt;: "Interaction of request and response Cache-Control"
<li> &lt;<a href="http://tools.ietf.org/wg/httpbis/trac/ticket/212">http://tools.ietf.org/wg/httpbis/trac/ticket/212</a>&gt;: "Refining age for 1.1 proxy chains"
<li> &lt;<a href="http://tools.ietf.org/wg/httpbis/trac/ticket/274">http://tools.ietf.org/wg/httpbis/trac/ticket/274</a>&gt;: "warn-code registry"
<h2 id="rfc.section.C.20"><a href="#rfc.section.C.20">C.20</a>&nbsp;<a id="changes.since.18" href="#changes.since.18">Since draft-ietf-httpbis-p6-cache-18</a></h2>
<p id="rfc.section.C.20.p.1">None yet.</p>
<p class="noprint"><a href="#rfc.index.1">1</a> <a href="#rfc.index.2">2</a> <a href="#rfc.index.A">A</a> <a href="#rfc.index.C">C</a> <a href="#rfc.index.E">E</a> <a href="#rfc.index.F">F</a> <a href="#rfc.index.G">G</a> <a href="#rfc.index.H">H</a> <a href="#rfc.index.M">M</a> <a href="#rfc.index.N">N</a> <a href="#rfc.index.O">O</a> <a href="#rfc.index.P">P</a> <a href="#rfc.index.R">R</a> <a href="#rfc.index.S">S</a> <a href="#rfc.index.V">V</a> <a href="#rfc.index.W">W</a>
<li><a id="rfc.index.1" href="#rfc.index.1"><b>1</b></a><ul>
<li>110 Response is Stale (warn code)&nbsp;&nbsp;<a href="#rfc.iref.78"><b>3.6.1</b></a>, <a href="#rfc.xref.warn.110.1">5.2</a></li>
<li>111 Revalidation Failed (warn code)&nbsp;&nbsp;<a href="#rfc.iref.79"><b>3.6.2</b></a>, <a href="#rfc.xref.warn.111.1">5.2</a></li>
<li>112 Disconnected Operation (warn code)&nbsp;&nbsp;<a href="#rfc.iref.80"><b>3.6.3</b></a>, <a href="#rfc.xref.warn.112.1">5.2</a></li>
<li>113 Heuristic Expiration (warn code)&nbsp;&nbsp;<a href="#rfc.iref.81"><b>3.6.4</b></a>, <a href="#rfc.xref.warn.113.1">5.2</a></li>
<li>199 Miscellaneous Warning (warn code)&nbsp;&nbsp;<a href="#rfc.iref.82"><b>3.6.5</b></a>, <a href="#rfc.xref.warn.199.1">5.2</a></li>
<li>214 Transformation Applied (warn code)&nbsp;&nbsp;<a href="#rfc.iref.83"><b>3.6.6</b></a>, <a href="#rfc.xref.warn.214.1">5.2</a></li>
<li>299 Miscellaneous Persistent Warning (warn code)&nbsp;&nbsp;<a href="#rfc.iref.84"><b>3.6.7</b></a>, <a href="#rfc.xref.warn.299.1">5.2</a></li>
<li>Age header field&nbsp;&nbsp;<a href="#rfc.xref.header.age.1">2.2</a>, <a href="#rfc.xref.header.age.2">2.3.2</a>, <a href="#rfc.iref.a.2"><b>3.1</b></a>, <a href="#rfc.xref.header.age.3">5.3</a></li>
<li>cache&nbsp;&nbsp;<a href="#rfc.iref.c.1">1.1</a>, <a href="#rfc.iref.c.2">1.2</a></li>
<li>max-age&nbsp;&nbsp;<a href="#rfc.iref.c.9"><b>3.2.1</b></a>, <a href="#rfc.iref.c.20"><b>3.2.2</b></a></li>
<li>max-stale&nbsp;&nbsp;<a href="#rfc.iref.c.10"><b>3.2.1</b></a></li>
<li>min-fresh&nbsp;&nbsp;<a href="#rfc.iref.c.11"><b>3.2.1</b></a></li>
<li>must-revalidate&nbsp;&nbsp;<a href="#rfc.iref.c.18"><b>3.2.2</b></a></li>
<li>no-cache&nbsp;&nbsp;<a href="#rfc.iref.c.7"><b>3.2.1</b></a>, <a href="#rfc.iref.c.16"><b>3.2.2</b></a></li>
<li>no-store&nbsp;&nbsp;<a href="#rfc.iref.c.8"><b>3.2.1</b></a>, <a href="#rfc.iref.c.17"><b>3.2.2</b></a></li>
<li>no-transform&nbsp;&nbsp;<a href="#rfc.iref.c.12"><b>3.2.1</b></a>, <a href="#rfc.iref.c.22"><b>3.2.2</b></a></li>
<li>only-if-cached&nbsp;&nbsp;<a href="#rfc.iref.c.13"><b>3.2.1</b></a></li>
<li>private&nbsp;&nbsp;<a href="#rfc.iref.c.15"><b>3.2.2</b></a></li>
<li>proxy-revalidate&nbsp;&nbsp;<a href="#rfc.iref.c.19"><b>3.2.2</b></a></li>
<li>public&nbsp;&nbsp;<a href="#rfc.iref.c.14"><b>3.2.2</b></a></li>
<li>s-maxage&nbsp;&nbsp;<a href="#rfc.iref.c.21"><b>3.2.2</b></a></li>
<li>cache entry&nbsp;&nbsp;<a href="#rfc.iref.c.4">2</a></li>
<li>cache key&nbsp;&nbsp;<a href="#rfc.iref.c.5">2</a></li>
<li>Cache-Control header field&nbsp;&nbsp;<a href="#rfc.xref.header.cache-control.1">2.1</a>, <a href="#rfc.iref.c.6"><b>3.2</b></a>, <a href="#rfc.xref.header.cache-control.2">5.3</a></li>
<li>cacheable&nbsp;&nbsp;<a href="#rfc.iref.c.3">1.2</a></li>
<li>Expires header field&nbsp;&nbsp;<a href="#rfc.xref.header.expires.1">2.1</a>, <a href="#rfc.xref.header.expires.2">2.3</a>, <a href="#rfc.xref.header.expires.3">2.3.1</a>, <a href="#rfc.iref.e.2"><b>3.3</b></a>, <a href="#rfc.xref.header.expires.4">5.3</a></li>
<li><tt>Age</tt>&nbsp;&nbsp;<a href="#rfc.iref.g.2"><b>3.1</b></a></li>
<li><tt>Cache-Control</tt>&nbsp;&nbsp;<a href="#rfc.iref.g.3"><b>3.2</b></a></li>
<li><tt>cache-extension</tt>&nbsp;&nbsp;<a href="#rfc.iref.g.4"><b>3.2</b></a></li>
<li><tt>cache-request-directive</tt>&nbsp;&nbsp;<a href="#rfc.iref.g.5"><b>3.2.1</b></a></li>
<li><tt>cache-response-directive</tt>&nbsp;&nbsp;<a href="#rfc.iref.g.6"><b>3.2.2</b></a></li>
<li><tt>delta-seconds</tt>&nbsp;&nbsp;<a href="#rfc.iref.g.1"><b>1.5</b></a></li>
<li><tt>Expires</tt>&nbsp;&nbsp;<a href="#rfc.iref.g.7"><b>3.3</b></a></li>
<li><tt>extension-pragma</tt>&nbsp;&nbsp;<a href="#rfc.iref.g.10"><b>3.4</b></a></li>
<li><tt>Pragma</tt>&nbsp;&nbsp;<a href="#rfc.iref.g.8"><b>3.4</b></a></li>
<li><tt>pragma-directive</tt>&nbsp;&nbsp;<a href="#rfc.iref.g.9"><b>3.4</b></a></li>
<li><tt>Vary</tt>&nbsp;&nbsp;<a href="#rfc.iref.g.11"><b>3.5</b></a></li>
<li><tt>warn-agent</tt>&nbsp;&nbsp;<a href="#rfc.iref.g.15"><b>3.6</b></a></li>
<li><tt>warn-code</tt>&nbsp;&nbsp;<a href="#rfc.iref.g.14"><b>3.6</b></a></li>
<li><tt>warn-date</tt>&nbsp;&nbsp;<a href="#rfc.iref.g.17"><b>3.6</b></a></li>
<li><tt>warn-text</tt>&nbsp;&nbsp;<a href="#rfc.iref.g.16"><b>3.6</b></a></li>
<li><tt>Warning</tt>&nbsp;&nbsp;<a href="#rfc.iref.g.12"><b>3.6</b></a></li>
<li><tt>warning-value</tt>&nbsp;&nbsp;<a href="#rfc.iref.g.13"><b>3.6</b></a></li>
<li>Age&nbsp;&nbsp;<a href="#rfc.xref.header.age.1">2.2</a>, <a href="#rfc.xref.header.age.2">2.3.2</a>, <a href="#rfc.iref.h.2"><b>3.1</b></a>, <a href="#rfc.xref.header.age.3">5.3</a></li>
<li>Cache-Control&nbsp;&nbsp;<a href="#rfc.xref.header.cache-control.1">2.1</a>, <a href="#rfc.iref.h.3"><b>3.2</b></a>, <a href="#rfc.xref.header.cache-control.2">5.3</a></li>
<li>Expires&nbsp;&nbsp;<a href="#rfc.xref.header.expires.1">2.1</a>, <a href="#rfc.xref.header.expires.2">2.3</a>, <a href="#rfc.xref.header.expires.3">2.3.1</a>, <a href="#rfc.iref.h.4"><b>3.3</b></a>, <a href="#rfc.xref.header.expires.4">5.3</a></li>
<li>Pragma&nbsp;&nbsp;<a href="#rfc.xref.header.pragma.1">2.2</a>, <a href="#rfc.xref.header.pragma.2">3.2</a>, <a href="#rfc.iref.h.5"><b>3.4</b></a>, <a href="#rfc.xref.header.pragma.3">5.3</a></li>
<li>Vary&nbsp;&nbsp;<a href="#rfc.xref.header.vary.1">2.7</a>, <a href="#rfc.iref.h.6"><b>3.5</b></a>, <a href="#rfc.xref.header.vary.2">5.3</a></li>
<li>Warning&nbsp;&nbsp;<a href="#rfc.xref.header.warning.1">2.3.3</a>, <a href="#rfc.xref.header.warning.2">2.4.1</a>, <a href="#rfc.xref.header.warning.3">2.8</a>, <a href="#rfc.iref.h.7"><b>3.6</b></a>, <a href="#rfc.xref.header.warning.4">5.3</a>, <a href="#rfc.xref.header.warning.5">A</a></li>
<li>Cache Directive&nbsp;&nbsp;<a href="#rfc.iref.m.1"><b>3.2.1</b></a>, <a href="#rfc.iref.m.5"><b>3.2.2</b></a></li>
<li>Cache Directive&nbsp;&nbsp;<a href="#rfc.iref.m.2"><b>3.2.1</b></a></li>
<li>Cache Directive&nbsp;&nbsp;<a href="#rfc.iref.m.3"><b>3.2.1</b></a></li>
<li>Cache Directive&nbsp;&nbsp;<a href="#rfc.iref.m.4"><b>3.2.2</b></a></li>
<li>Cache Directive&nbsp;&nbsp;<a href="#rfc.iref.n.1"><b>3.2.1</b></a>, <a href="#rfc.iref.n.4"><b>3.2.2</b></a></li>
<li>Cache Directive&nbsp;&nbsp;<a href="#rfc.iref.n.2"><b>3.2.1</b></a>, <a href="#rfc.iref.n.5"><b>3.2.2</b></a></li>
<li>Cache Directive&nbsp;&nbsp;<a href="#rfc.iref.n.3"><b>3.2.1</b></a>, <a href="#rfc.iref.n.6"><b>3.2.2</b></a></li>
<li>Cache Directive&nbsp;&nbsp;<a href="#rfc.iref.o.1"><b>3.2.1</b></a></li>
<li><em>Part1</em>&nbsp;&nbsp;<a href="#rfc.xref.Part1.1">1.3</a>, <a href="#rfc.xref.Part1.2">1.4</a>, <a href="#rfc.xref.Part1.3">1.4.1</a>, <a href="#rfc.xref.Part1.4">1.4.1</a>, <a href="#rfc.xref.Part1.5">1.4.1</a>, <a href="#rfc.xref.Part1.6">1.4.1</a>, <a href="#rfc.xref.Part1.7">1.4.2</a>, <a href="#rfc.xref.Part1.8">1.4.2</a>, <a href="#rfc.xref.Part1.9">1.4.2</a>, <a href="#rfc.xref.Part1.10">1.4.2</a>, <a href="#rfc.xref.Part1.11">2.1</a>, <a href="#rfc.xref.Part1.12">2.2</a>, <a href="#rfc.xref.Part1.13">2.5</a>, <a href="#rfc.xref.Part1.14">2.5</a>, <a href="#rfc.xref.Part1.15">2.5</a>, <a href="#rfc.xref.Part1.16">2.7</a>, <a href="#rfc.xref.Part1.17">7</a>, <a href="#Part1"><b>8.1</b></a><ul>
<li><em>Section 1.2</em>&nbsp;&nbsp;<a href="#rfc.xref.Part1.2">1.4</a></li>
<li><em>Section 2</em>&nbsp;&nbsp;<a href="#rfc.xref.Part1.1">1.3</a></li>
<li><em>Section 2.7</em>&nbsp;&nbsp;<a href="#rfc.xref.Part1.8">1.4.2</a>, <a href="#rfc.xref.Part1.10">1.4.2</a></li>
<li><em>Section 3.2.1</em>&nbsp;&nbsp;<a href="#rfc.xref.Part1.4">1.4.1</a></li>
<li><em>Section 3.2</em>&nbsp;&nbsp;<a href="#rfc.xref.Part1.7">1.4.2</a>, <a href="#rfc.xref.Part1.16">2.7</a></li>
<li><em>Section 3.2.4</em>&nbsp;&nbsp;<a href="#rfc.xref.Part1.5">1.4.1</a>, <a href="#rfc.xref.Part1.6">1.4.1</a></li>
<li><em>Section 4.3</em>&nbsp;&nbsp;<a href="#rfc.xref.Part1.12">2.2</a>, <a href="#rfc.xref.Part1.13">2.5</a>, <a href="#rfc.xref.Part1.14">2.5</a>, <a href="#rfc.xref.Part1.15">2.5</a></li>
<li><em>Section 8.8</em>&nbsp;&nbsp;<a href="#rfc.xref.Part1.9">1.4.2</a></li>
<li><em>Section 11</em>&nbsp;&nbsp;<a href="#rfc.xref.Part1.17">7</a></li>
<li><em>Part2</em>&nbsp;&nbsp;<a href="#rfc.xref.Part2.1">1.4.2</a>, <a href="#rfc.xref.Part2.2">2</a>, <a href="#rfc.xref.Part2.3">2.2</a>, <a href="#rfc.xref.Part2.4">2.3.1.1</a>, <a href="#rfc.xref.Part2.5">2.3.2</a>, <a href="#rfc.xref.Part2.6">2.5</a>, <a href="#rfc.xref.Part2.7">3.3</a>, <a href="#Part2"><b>8.1</b></a><ul>
<li><em>Section 6.1.1</em>&nbsp;&nbsp;<a href="#rfc.xref.Part2.3">2.2</a>, <a href="#rfc.xref.Part2.6">2.5</a></li>
<li><em>Section 7</em>&nbsp;&nbsp;<a href="#rfc.xref.Part2.4">2.3.1.1</a></li>
<li><em>Section 8</em>&nbsp;&nbsp;<a href="#rfc.xref.Part2.1">1.4.2</a>, <a href="#rfc.xref.Part2.7">3.3</a></li>
<li><em>Section 9.2</em>&nbsp;&nbsp;<a href="#rfc.xref.Part2.5">2.3.2</a></li>
<li><em>Part4</em>&nbsp;&nbsp;<a href="#rfc.xref.Part4.1">1.2</a>, <a href="#rfc.xref.Part4.2">1.2</a>, <a href="#rfc.xref.Part4.3">1.2</a>, <a href="#rfc.xref.Part4.4">2.3.1.1</a>, <a href="#rfc.xref.Part4.5">2.4</a>, <a href="#Part4"><b>8.1</b></a><ul>
<li><em>Section 2.1</em>&nbsp;&nbsp;<a href="#rfc.xref.Part4.1">1.2</a></li>
<li><em>Section 2.2</em>&nbsp;&nbsp;<a href="#rfc.xref.Part4.4">2.3.1.1</a></li>
<li><em>Section 2.2.2</em>&nbsp;&nbsp;<a href="#rfc.xref.Part4.3">1.2</a></li>
<li><em>Section 2.3</em>&nbsp;&nbsp;<a href="#rfc.xref.Part4.2">1.2</a></li>
<li><em>Part5</em>&nbsp;&nbsp;<a href="#rfc.xref.Part5.1">2.1</a>, <a href="#rfc.xref.Part5.2">2.8</a>, <a href="#rfc.xref.Part5.3">2.8</a>, <a href="#Part5"><b>8.1</b></a><ul>
<li><em>Section 4</em>&nbsp;&nbsp;<a href="#rfc.xref.Part5.3">2.8</a></li>
<li><em>Part7</em>&nbsp;&nbsp;<a href="#rfc.xref.Part7.1">2.1</a>, <a href="#rfc.xref.Part7.2">2.6</a>, <a href="#Part7"><b>8.1</b></a><ul>
<li><em>Section 4.1</em>&nbsp;&nbsp;<a href="#rfc.xref.Part7.1">2.1</a>, <a href="#rfc.xref.Part7.2">2.6</a></li>
<li>Pragma header field&nbsp;&nbsp;<a href="#rfc.xref.header.pragma.1">2.2</a>, <a href="#rfc.xref.header.pragma.2">3.2</a>, <a href="#rfc.iref.p.5"><b>3.4</b></a>, <a href="#rfc.xref.header.pragma.3">5.3</a></li>
<li>Cache Directive&nbsp;&nbsp;<a href="#rfc.iref.p.3"><b>3.2.2</b></a></li>
<li>private cache&nbsp;&nbsp;<a href="#rfc.iref.p.1">1.2</a></li>
<li>Cache Directive&nbsp;&nbsp;<a href="#rfc.iref.p.4"><b>3.2.2</b></a></li>
<li>Cache Directive&nbsp;&nbsp;<a href="#rfc.iref.p.2"><b>3.2.2</b></a></li>
<li><em>RFC1305</em>&nbsp;&nbsp;<a href="#rfc.xref.RFC1305.1">2.2</a>, <a href="#rfc.xref.RFC1305.2">2.3.2</a>, <a href="#RFC1305"><b>8.2</b></a></li>
<li><em>RFC2119</em>&nbsp;&nbsp;<a href="#rfc.xref.RFC2119.1">1.3</a>, <a href="#RFC2119"><b>8.1</b></a></li>
<li><em>RFC2616</em>&nbsp;&nbsp;<a href="#rfc.xref.RFC2616.1">2.3.1.1</a>, <a href="#RFC2616"><b>8.2</b></a>, <a href="#rfc.xref.RFC2616.2">C.1</a><ul>
<li><em>Section 13.9</em>&nbsp;&nbsp;<a href="#rfc.xref.RFC2616.1">2.3.1.1</a></li>
<li><em>RFC5226</em>&nbsp;&nbsp;<a href="#rfc.xref.RFC5226.1">3.2.3</a>, <a href="#rfc.xref.RFC5226.2">3.6.8</a>, <a href="#RFC5226"><b>8.2</b></a><ul>
<li><em>Section 4.1</em>&nbsp;&nbsp;<a href="#rfc.xref.RFC5226.1">3.2.3</a>, <a href="#rfc.xref.RFC5226.2">3.6.8</a></li>
<li><em>RFC5234</em>&nbsp;&nbsp;<a href="#rfc.xref.RFC5234.1">1.4</a>, <a href="#rfc.xref.RFC5234.2">1.4</a>, <a href="#RFC5234"><b>8.1</b></a><ul>
<li><em>Appendix B.1</em>&nbsp;&nbsp;<a href="#rfc.xref.RFC5234.2">1.4</a></li>
<li><em>RFC5861</em>&nbsp;&nbsp;<a href="#rfc.xref.RFC5861.1">5.1</a>, <a href="#rfc.xref.RFC5861.2">5.1</a>, <a href="#RFC5861"><b>8.2</b></a><ul>
<li><em>Section 3</em>&nbsp;&nbsp;<a href="#rfc.xref.RFC5861.2">5.1</a></li>
<li><em>Section 4</em>&nbsp;&nbsp;<a href="#rfc.xref.RFC5861.1">5.1</a></li>
<li>Cache Directive&nbsp;&nbsp;<a href="#rfc.iref.s.4"><b>3.2.2</b></a></li>
<li>shared cache&nbsp;&nbsp;<a href="#rfc.iref.s.1">1.2</a></li>
<li>strong validator&nbsp;&nbsp;<a href="#rfc.iref.s.3">1.2</a></li>
<li>validator&nbsp;&nbsp;<a href="#rfc.iref.v.1">1.2</a><ul>
<li>strong&nbsp;&nbsp;<a href="#rfc.iref.v.2">1.2</a></li>
<li>Vary header field&nbsp;&nbsp;<a href="#rfc.xref.header.vary.1">2.7</a>, <a href="#rfc.iref.v.3"><b>3.5</b></a>, <a href="#rfc.xref.header.vary.2">5.3</a></li>
<li>Warn Codes&nbsp;&nbsp;
<li>110 Response is Stale&nbsp;&nbsp;<a href="#rfc.iref.w.2"><b>3.6.1</b></a>, <a href="#rfc.xref.warn.110.1">5.2</a></li>
<li>111 Revalidation Failed&nbsp;&nbsp;<a href="#rfc.iref.w.3"><b>3.6.2</b></a>, <a href="#rfc.xref.warn.111.1">5.2</a></li>
<li>112 Disconnected Operation&nbsp;&nbsp;<a href="#rfc.iref.w.4"><b>3.6.3</b></a>, <a href="#rfc.xref.warn.112.1">5.2</a></li>
<li>113 Heuristic Expiration&nbsp;&nbsp;<a href="#rfc.iref.w.5"><b>3.6.4</b></a>, <a href="#rfc.xref.warn.113.1">5.2</a></li>
<li>199 Miscellaneous Warning&nbsp;&nbsp;<a href="#rfc.iref.w.6"><b>3.6.5</b></a>, <a href="#rfc.xref.warn.199.1">5.2</a></li>
<li>214 Transformation Applied&nbsp;&nbsp;<a href="#rfc.iref.w.7"><b>3.6.6</b></a>, <a href="#rfc.xref.warn.214.1">5.2</a></li>
<li>299 Miscellaneous Persistent Warning&nbsp;&nbsp;<a href="#rfc.iref.w.8"><b>3.6.7</b></a>, <a href="#rfc.xref.warn.299.1">5.2</a></li>
<li>Warning header field&nbsp;&nbsp;<a href="#rfc.xref.header.warning.1">2.3.3</a>, <a href="#rfc.xref.header.warning.2">2.4.1</a>, <a href="#rfc.xref.header.warning.3">2.8</a>, <a href="#rfc.iref.w.1"><b>3.6</b></a>, <a href="#rfc.xref.header.warning.4">5.3</a>, <a href="#rfc.xref.header.warning.5">A</a></li>