source: draft-ietf-httpbis/latest/p6-cache.xml @ 2169

Last change on this file since 2169 was 2169, checked in by julian.reschke@…, 8 years ago

Prepare release of -22 on 2013-01-28.

  • Property svn:eol-style set to native
  • Property svn:mime-type set to text/xml
File size: 106.2 KB
Line 
1<?xml version="1.0" encoding="utf-8"?>
2<?xml-stylesheet type='text/xsl' href='../myxml2rfc.xslt'?>
3<!DOCTYPE rfc [
4  <!ENTITY MAY "<bcp14 xmlns='http://purl.org/net/xml2rfc/ext'>MAY</bcp14>">
5  <!ENTITY MUST "<bcp14 xmlns='http://purl.org/net/xml2rfc/ext'>MUST</bcp14>">
6  <!ENTITY MUST-NOT "<bcp14 xmlns='http://purl.org/net/xml2rfc/ext'>MUST NOT</bcp14>">
7  <!ENTITY OPTIONAL "<bcp14 xmlns='http://purl.org/net/xml2rfc/ext'>OPTIONAL</bcp14>">
8  <!ENTITY RECOMMENDED "<bcp14 xmlns='http://purl.org/net/xml2rfc/ext'>RECOMMENDED</bcp14>">
9  <!ENTITY REQUIRED "<bcp14 xmlns='http://purl.org/net/xml2rfc/ext'>REQUIRED</bcp14>">
10  <!ENTITY SHALL "<bcp14 xmlns='http://purl.org/net/xml2rfc/ext'>SHALL</bcp14>">
11  <!ENTITY SHALL-NOT "<bcp14 xmlns='http://purl.org/net/xml2rfc/ext'>SHALL NOT</bcp14>">
12  <!ENTITY SHOULD "<bcp14 xmlns='http://purl.org/net/xml2rfc/ext'>SHOULD</bcp14>">
13  <!ENTITY SHOULD-NOT "<bcp14 xmlns='http://purl.org/net/xml2rfc/ext'>SHOULD NOT</bcp14>">
14  <!ENTITY ID-VERSION "latest">
15  <!ENTITY ID-MONTH "January">
16  <!ENTITY ID-YEAR "2013">
17  <!ENTITY mdash "&#8212;">
18  <!ENTITY Note "<x:h xmlns:x='http://purl.org/net/xml2rfc/ext'>Note:</x:h>">
19  <!ENTITY architecture                "<xref target='Part1' x:rel='#architecture' xmlns:x='http://purl.org/net/xml2rfc/ext'/>">
20  <!ENTITY conformance                 "<xref target='Part1' x:rel='#conformance' xmlns:x='http://purl.org/net/xml2rfc/ext'/>">
21  <!ENTITY notation                    "<xref target='Part1' x:rel='#notation' xmlns:x='http://purl.org/net/xml2rfc/ext'/>">
22  <!ENTITY acks                        "<xref target='Part1' x:rel='#acks' xmlns:x='http://purl.org/net/xml2rfc/ext'/>">
23  <!ENTITY whitespace                  "<xref target='Part1' x:rel='#whitespace' xmlns:x='http://purl.org/net/xml2rfc/ext'/>">
24  <!ENTITY field-components            "<xref target='Part1' x:rel='#field.components' xmlns:x='http://purl.org/net/xml2rfc/ext'/>">
25  <!ENTITY uri                         "<xref target='Part1' x:rel='#uri' xmlns:x='http://purl.org/net/xml2rfc/ext'/>">
26  <!ENTITY effective-request-uri       "<xref target='Part1' x:rel='#effective.request.uri' xmlns:x='http://purl.org/net/xml2rfc/ext'/>">
27  <!ENTITY messaging                   "<xref target='Part1' xmlns:x='http://purl.org/net/xml2rfc/ext'/>">
28  <!ENTITY semantics                   "<xref target='Part2' xmlns:x='http://purl.org/net/xml2rfc/ext'/>">
29  <!ENTITY conditional                 "<xref target='Part4' xmlns:x='http://purl.org/net/xml2rfc/ext'/>">
30  <!ENTITY partial                     "<xref target='Part5' xmlns:x='http://purl.org/net/xml2rfc/ext'/>">
31  <!ENTITY combining-byte-ranges       "<xref target='Part5' x:rel='#combining.byte.ranges' xmlns:x='http://purl.org/net/xml2rfc/ext'/>">
32  <!ENTITY http-date                   "<xref target='Part2' x:rel='#http.date' xmlns:x='http://purl.org/net/xml2rfc/ext'/>">
33  <!ENTITY header-authorization        "<xref target='Part7' x:rel='#header.authorization' xmlns:x='http://purl.org/net/xml2rfc/ext'/>">
34  <!ENTITY header-connection           "<xref target='Part1' x:rel='#header.connection' xmlns:x='http://purl.org/net/xml2rfc/ext'/>">
35  <!ENTITY header-date                 "<xref target='Part2' x:rel='#header.date' xmlns:x='http://purl.org/net/xml2rfc/ext'/>">
36  <!ENTITY header-last-modified        "<xref target='Part4' x:rel='#header.last-modified' xmlns:x='http://purl.org/net/xml2rfc/ext'/>">
37  <!ENTITY header-vary                 "<xref target='Part2' x:rel='#header.vary' xmlns:x='http://purl.org/net/xml2rfc/ext'/>">
38  <!ENTITY header-via                  "<xref target='Part1' x:rel='#header.via' xmlns:x='http://purl.org/net/xml2rfc/ext'/>">
39  <!ENTITY header-fields               "<xref target='Part1' x:rel='#header.fields' xmlns:x='http://purl.org/net/xml2rfc/ext'/>">
40  <!ENTITY GET                         "<xref target='Part2' x:rel='#GET' xmlns:x='http://purl.org/net/xml2rfc/ext'/>">
41  <!ENTITY safe-methods                "<xref target='Part2' x:rel='#safe.methods' xmlns:x='http://purl.org/net/xml2rfc/ext'/>">
42  <!ENTITY entity-tags                 "<xref target='Part4' x:rel='#header.etag' xmlns:x='http://purl.org/net/xml2rfc/ext'/>">
43  <!ENTITY weak-and-strong             "<xref target='Part4' x:rel='#weak.and.strong.validators' xmlns:x='http://purl.org/net/xml2rfc/ext'/>">
44  <!ENTITY lastmod-comparison          "<xref target='Part4' x:rel='#lastmod.comparison' xmlns:x='http://purl.org/net/xml2rfc/ext'/>">
45  <!ENTITY status-codes                "<xref target='Part2' x:rel='#status.codes' xmlns:x='http://purl.org/net/xml2rfc/ext'/>">
46  <!ENTITY status.2xx                  "<xref target='Part2' x:rel='#status.2xx' xmlns:x='http://purl.org/net/xml2rfc/ext'/>">
47  <!ENTITY transformations             "<xref target='Part1' x:rel='#message.transformations' xmlns:x='http://purl.org/net/xml2rfc/ext'/>">
48]>
49<?rfc toc="yes" ?>
50<?rfc symrefs="yes" ?>
51<?rfc sortrefs="yes" ?>
52<?rfc compact="yes"?>
53<?rfc subcompact="no" ?>
54<?rfc linkmailto="no" ?>
55<?rfc editing="no" ?>
56<?rfc comments="yes"?>
57<?rfc inline="yes"?>
58<?rfc rfcedstyle="yes"?>
59<?rfc-ext allow-markup-in-artwork="yes" ?>
60<?rfc-ext include-references-in-index="yes" ?>
61<rfc category="std" docName="draft-ietf-httpbis-p6-cache-&ID-VERSION;" ipr="pre5378Trust200902"
62  obsoletes="2616" x:maturity-level="proposed" xmlns:x="http://purl.org/net/xml2rfc/ext">
63<x:link rel="prev" basename="p5-range"/>
64<x:link rel="next" basename="p7-auth"/>
65<x:feedback template="mailto:ietf-http-wg@w3.org?subject={docname},%20%22{section}%22&amp;body=&lt;{ref}&gt;:"/>
66<front>
67
68  <title abbrev="HTTP/1.1 Caching">Hypertext Transfer Protocol (HTTP/1.1): Caching</title>
69
70  <author fullname="Roy T. Fielding" initials="R." role="editor" surname="Fielding">
71    <organization abbrev="Adobe">Adobe Systems Incorporated</organization>
72    <address>
73      <postal>
74        <street>345 Park Ave</street>
75        <city>San Jose</city>
76        <region>CA</region>
77        <code>95110</code>
78        <country>USA</country>
79      </postal>
80      <email>fielding@gbiv.com</email>
81      <uri>http://roy.gbiv.com/</uri>
82    </address>
83  </author>
84
85  <author fullname="Mark Nottingham" initials="M." role="editor" surname="Nottingham">
86    <organization>Akamai</organization>
87    <address>
88      <email>mnot@mnot.net</email>
89      <uri>http://www.mnot.net/</uri>
90    </address>
91  </author>
92
93  <author fullname="Julian F. Reschke" initials="J. F." role="editor" surname="Reschke">
94    <organization abbrev="greenbytes">greenbytes GmbH</organization>
95    <address>
96      <postal>
97        <street>Hafenweg 16</street>
98        <city>Muenster</city><region>NW</region><code>48155</code>
99        <country>Germany</country>
100      </postal>
101      <email>julian.reschke@greenbytes.de</email>
102      <uri>http://greenbytes.de/tech/webdav/</uri>
103    </address>
104  </author>
105
106  <date month="&ID-MONTH;" year="&ID-YEAR;" />
107  <workgroup>HTTPbis Working Group</workgroup>
108
109<abstract>
110<t>
111   The Hypertext Transfer Protocol (HTTP) is an application-level protocol for
112   distributed, collaborative, hypertext information systems. This document
113   defines requirements on HTTP caches and the associated header fields
114   that control cache behavior or indicate cacheable response messages.
115</t>
116</abstract>
117
118<note title="Editorial Note (To be removed by RFC Editor)">
119  <t>
120    Discussion of this draft takes place on the HTTPBIS working group
121    mailing list (ietf-http-wg@w3.org), which is archived at
122    <eref target="http://lists.w3.org/Archives/Public/ietf-http-wg/"/>.
123  </t>
124  <t>
125    The current issues list is at
126    <eref target="http://tools.ietf.org/wg/httpbis/trac/report/3"/> and related
127    documents (including fancy diffs) can be found at
128    <eref target="http://tools.ietf.org/wg/httpbis/"/>.
129  </t>
130  <t>
131    The changes in this draft are summarized in <xref target="changes.since.21"/>.
132  </t>
133</note>
134
135   </front>
136   <middle>
137
138<section anchor="caching" title="Introduction">
139<t>
140   HTTP is typically used for distributed information systems, where
141   performance can be improved by the use of response caches. This document
142   defines aspects of HTTP/1.1 related to caching and reusing response
143   messages.
144</t>
145
146<section anchor="intro.purpose" title="Purpose">
147<iref item="cache" />
148<t>
149   An HTTP <x:dfn>cache</x:dfn> is a local store of response messages and the
150   subsystem that controls its message storage, retrieval, and deletion. A
151   cache stores cacheable responses in order to reduce the response time and
152   network bandwidth consumption on future, equivalent requests. Any client or
153   server &MAY; employ a cache, though a cache cannot be used by a server that
154   is acting as a tunnel.
155</t>
156<t>
157   The goal of caching in HTTP/1.1 is to significantly improve performance
158   by reusing a prior response message to satisfy a current request.
159   A stored response is considered "fresh", as defined in
160   <xref target="expiration.model" />, if the response can be reused without
161   "validation" (checking with the origin server to see if the cached response
162   remains valid for this request).  A fresh cache response can therefore
163   reduce both latency and network transfers each time it is reused.
164   When a cached response is not fresh, it might still be reusable if it can
165   be freshened by validation (<xref target="validation.model" />) or if the
166   origin is unavailable.
167</t>
168</section>
169
170<section anchor="intro.terminology" title="Terminology">
171<t>
172   This specification uses a number of terms to refer to the roles played by
173   participants in, and objects of, HTTP caching.
174</t>
175<t>
176   <iref item="cache" />
177   <x:dfn>cache</x:dfn>
178   <list>
179      <t>A conformant implementation of an HTTP cache. Note that this implies
180        an HTTP/1.1 cache; this specification does not define conformance
181        for HTTP/1.0 caches.</t>
182   </list>
183</t>
184<t anchor="shared.and.non-shared.caches">
185   <iref item="shared cache" />
186   <x:dfn>shared cache</x:dfn>
187   <list>
188      <t>A cache that stores responses to be reused by more than one user;
189         usually (but not always) deployed as part of an intermediary.</t>
190   </list>
191</t>
192<t>
193   <iref item="private cache" />
194   <x:dfn>private cache</x:dfn>
195   <list>
196      <t>A cache that is dedicated to a single user.</t>
197   </list>
198</t>
199<t>
200   <iref item="cacheable" />
201   <x:dfn>cacheable</x:dfn>
202   <list>
203      <t>A response is cacheable if a cache is allowed to store a copy of the
204      response message for use in answering subsequent requests. Even when a
205      response is cacheable, there might be additional constraints on whether
206      a cache can use the stored copy to satisfy a particular request.</t>
207   </list>
208</t>
209<t>
210   <iref item="explicit expiration time" />
211   <x:dfn>explicit expiration time</x:dfn>
212   <list>
213      <t>The time at which the origin server intends that a stored response
214      no longer be used by a cache without further validation.</t>
215   </list>
216</t>
217<t>
218   <iref item="heuristic expiration time" />
219   <x:dfn>heuristic expiration time</x:dfn>
220   <list>
221      <t>An expiration time assigned by a cache when no explicit expiration
222      time is available.</t>
223   </list>
224</t>
225<t>
226   <iref item="age" />
227   <x:dfn>age</x:dfn>
228   <list>
229      <t>The age of a response is the time since it was sent by, or
230      successfully validated with, the origin server.</t>
231   </list>
232</t>
233<t>
234   <iref item="first-hand" />
235   <x:dfn>first-hand</x:dfn>
236   <list>
237      <t>A response is first-hand if the freshness model is not in use; i.e.,
238      its age is 0.</t>
239   </list>
240</t>
241<t>
242   <iref item="freshness lifetime" />
243   <x:dfn>freshness lifetime</x:dfn>
244   <list>
245      <t>The length of time between the generation of a response and its
246      expiration time.</t>
247   </list>
248</t>
249<t>
250   <iref item="fresh" />
251   <x:dfn>fresh</x:dfn>
252   <list>
253      <t>A response is fresh if its age has not yet exceeded its freshness
254      lifetime.</t>
255   </list>
256</t>
257<t>
258   <iref item="stale" />
259   <x:dfn>stale</x:dfn>
260   <list>
261      <t>A response is stale if its age has passed its freshness lifetime
262      (either explicit or heuristic).</t>
263   </list>
264</t>
265<t>
266   <iref item="validator" />
267   <x:dfn>validator</x:dfn>
268   <list>
269      <t>A protocol element (e.g., an entity-tag or a <x:ref>Last-Modified</x:ref>
270      time) that is used to find out whether a stored response is an equivalent
271      copy of a representation. See &weak-and-strong;.</t>
272   </list>
273</t>
274<t>
275   <iref item="strong validator" />
276   <iref item="validator" subitem="strong" />
277   <x:dfn>strong validator</x:dfn>
278   <list>
279      <t>A validator that is defined by the origin server such that its
280         current value will change if the representation data changes; i.e.,
281         an entity-tag that is not marked as weak (&entity-tags;) or,
282         if no entity-tag is provided, a <x:ref>Last-Modified</x:ref> value
283         that is strong in the sense defined by &lastmod-comparison;.</t>
284   </list>
285</t>
286</section>
287
288<section title="Conformance and Error Handling" anchor="conformance">
289<t>
290   The key words "MUST", "MUST NOT", "REQUIRED", "SHALL", "SHALL NOT",
291   "SHOULD", "SHOULD NOT", "RECOMMENDED", "MAY", and "OPTIONAL" in this
292   document are to be interpreted as described in <xref target="RFC2119"/>.
293</t>
294<t>
295   Conformance criteria and considerations regarding error handling
296   are defined in &conformance;.
297</t>
298</section>
299
300<section title="Syntax Notation" anchor="notation">
301<t>
302   This specification uses the Augmented Backus-Naur Form (ABNF) notation
303   of <xref target="RFC5234"/> with the list rule extension defined in
304   &notation;. <xref target="imported.abnf"/> describes rules imported from
305   other documents. <xref target="collected.abnf"/> shows the collected ABNF
306   with the list rule expanded.
307</t>
308
309<section title="Delta Seconds" anchor="delta-seconds">
310<t>
311   The delta-seconds rule specifies a non-negative integer, representing time
312   in seconds.
313</t>
314<figure><artwork type="abnf2616"><iref item="Grammar" primary="true" subitem="delta-seconds" />
315  <x:ref>delta-seconds</x:ref>  = 1*<x:ref>DIGIT</x:ref>
316</artwork></figure>
317<t>
318   If an implementation receives a delta-seconds value larger than the largest
319   positive integer it can represent, or if any of its subsequent calculations
320   overflows, it &MUST; consider the value to be 2147483648
321   (2<x:sup>31</x:sup>). Recipients parsing a delta-seconds value &MUST; use
322   an arithmetic type of at least 31 bits of range, and senders &MUST-NOT;
323   send delta-seconds with a value greater than 2147483648.
324</t>
325</section>
326
327</section>
328</section>
329
330<section anchor="caching.overview" title="Overview of Cache Operation">
331<iref item="cache entry" />
332<iref item="cache key" />
333<t>
334   Proper cache operation preserves the semantics of HTTP transfers
335   (&semantics;) while eliminating the transfer of information already held
336   in the cache.  Although caching is an entirely &OPTIONAL; feature of HTTP,
337   we assume that reusing the cached response is desirable and that such
338   reuse is the default behavior when no requirement or locally-desired
339   configuration prevents it.  Therefore, HTTP cache requirements are focused
340   on preventing a cache from either storing a non-reusable response or
341   reusing a stored response inappropriately.
342</t>
343<t>
344   Each <x:dfn>cache entry</x:dfn> consists of a cache key and one or more
345   HTTP responses corresponding to prior requests that used the same key. The
346   most common form of cache entry is a successful result of a retrieval
347   request: i.e., a <x:ref>200 (OK)</x:ref> response to a GET request, which
348   contains a representation of the resource identified by the request target
349   (&GET;). However, it is also possible to cache permanent redirects,
350   negative results (e.g., <x:ref>404 (Not Found)</x:ref>),
351   incomplete results (e.g., <x:ref>206 (Partial Content)</x:ref>), and
352   responses to methods other than GET if the method's definition allows such
353   caching and defines something suitable for use as a cache key.
354</t>
355<t>
356   The default <x:dfn>cache key</x:dfn> consists of the request method and
357   target URI.  However, since HTTP caches in common use today are typically
358   limited to caching responses to GET, many implementations simply decline
359   other methods and use only the URI as the key.
360</t>
361<t>
362   If a request target is subject to content negotiation, its cache entry
363   might consist of multiple stored responses, each differentiated by a
364   secondary key for the values of the original request's selecting header
365   fields (<xref target="caching.negotiated.responses"/>).
366</t>
367</section>
368
369<section anchor="response.cacheability" title="Storing Responses in Caches">
370<t>
371   A cache &MUST-NOT; store a response to any request, unless:
372   <list style="symbols">
373      <t>The request method is understood by the cache and defined as being
374      cacheable, and</t>
375      <t>the response status code is understood by the cache, and</t>
376      <t>the "no-store" cache directive (see <xref
377      target="header.cache-control" />) does not appear in request or response
378      header fields, and</t>
379      <t>the "private" cache response directive (see <xref
380      target="cache-response-directive.private" />) does not appear in the
381      response, if the cache is shared, and</t>
382      <t>the <x:ref>Authorization</x:ref> header field (see
383      &header-authorization;) does not appear in the request, if the cache is
384      shared, unless the response explicitly allows it (see <xref
385      target="caching.authenticated.responses" />), and</t>
386      <t>the response either:
387         <list style="symbols">
388            <t>contains an <x:ref>Expires</x:ref> header field (see
389            <xref target="header.expires"/>), or</t>
390            <t>contains a max-age response cache directive (see <xref
391            target="cache-response-directive.max-age" />), or</t>
392            <t>contains a s-maxage response cache directive and the cache is
393            shared, or</t>
394            <t>contains a Cache Control Extension (see <xref
395            target="cache.control.extensions" />) that allows it to be cached,
396            or</t>
397            <t>has a status code that can be served with heuristic freshness
398            (see <xref target="heuristic.freshness" />).</t>
399         </list>
400      </t>
401   </list>
402</t>
403<t>
404   Note that any of the requirements listed above can be overridden by a
405   cache-control extension; see <xref target="cache.control.extensions" />.
406</t>
407<t>
408   In this context, a cache has "understood" a request method or a response
409   status code if it recognizes it and implements any cache-specific
410   behavior.
411</t>
412<t>
413   Note that, in normal operation, many caches will not store a response that
414   has neither a cache validator nor an explicit expiration time, as such
415   responses are not usually useful to store. However, caches are not
416   prohibited from storing such responses.
417</t>
418
419<section anchor="incomplete.responses" title="Storing Incomplete Responses">
420<t>
421   A response message is considered complete when all of the octets indicated
422   by the message framing (&messaging;) are received prior to the connection
423   being closed. If the request is GET, the response status is <x:ref>200
424   (OK)</x:ref>, and the entire response header block has been received, a
425   cache &MAY; store an incomplete response message body if the cache entry is
426   recorded as incomplete. Likewise, a <x:ref>206 (Partial Content)</x:ref>
427   response &MAY; be stored as if it were an incomplete <x:ref>200
428   (OK)</x:ref> cache entry. However, a cache &MUST-NOT; store incomplete or
429   partial content responses if it does not support the <x:ref>Range</x:ref>
430   and <x:ref>Content-Range</x:ref> header fields or if it does not understand
431   the range units used in those fields.
432</t>
433<t>
434   A cache &MAY; complete a stored incomplete response by making a subsequent
435   range request (&partial;) and combining the successful response with the
436   stored entry, as defined in <xref target="combining.responses"/>. A cache
437   &MUST-NOT; use an incomplete response to answer requests unless the
438   response has been made complete or the request is partial and specifies a
439   range that is wholly within the incomplete response. A cache &MUST-NOT;
440   send a partial response to a client without explicitly marking it as such
441   using the <x:ref>206 (Partial Content)</x:ref> status code.
442</t>
443</section>
444
445
446<section anchor="caching.authenticated.responses"
447   title="Storing Responses to Authenticated Requests">
448<t>
449   A shared cache &MUST-NOT; use a cached response to a request with an
450   <x:ref>Authorization</x:ref> header field (&header-authorization;) to
451   satisfy any subsequent request unless a cache directive that allows such
452   responses to be stored is present in the response.
453</t>
454<t>
455   In this specification, the following <x:ref>Cache-Control</x:ref> response
456   directives (<xref target="cache-response-directive"/>) have such an effect:
457   must-revalidate, public, s-maxage.
458</t>
459<t>
460   Note that cached responses that contain the "must-revalidate" and/or
461   "s-maxage" response directives are not allowed to be served stale (<xref
462   target="serving.stale.responses"/>) by shared caches. In particular, a
463   response with either "max-age=0, must-revalidate" or "s-maxage=0" cannot be
464   used to satisfy a subsequent request without revalidating it on the origin
465   server.
466</t>
467</section>
468</section>
469
470
471<section anchor="constructing.responses.from.caches"
472   title="Constructing Responses from Caches">
473<t>
474   For a presented request, a cache &MUST-NOT; send a stored response,
475   unless:
476   <list style="symbols">
477      <t>The presented effective request URI (&effective-request-uri;) and
478      that of the stored response match, and</t>
479      <t>the request method associated with the stored response allows it to
480      be used for the presented request, and</t>
481      <t>selecting header fields nominated by the stored response (if any)
482      match those presented (see <xref target="caching.negotiated.responses"
483      />), and</t>
484      <t>the presented request does not contain the no-cache pragma (<xref
485      target="header.pragma"/>), nor the no-cache cache directive (<xref
486      target="cache-request-directive"/>), unless the stored response is
487      successfully validated (<xref target="validation.model"/>), and</t>
488      <t>the stored response does not contain the no-cache cache directive
489      (<xref target="cache-response-directive.no-cache"/>), unless it is
490      successfully validated (<xref target="validation.model"/>), and</t>
491      <t>the stored response is either:
492         <list style="symbols">
493            <t>fresh (see <xref target="expiration.model" />), or</t>
494            <t>allowed to be served stale (see <xref
495            target="serving.stale.responses" />), or</t>
496            <t>successfully validated (see <xref target="validation.model"
497            />).</t>
498         </list>
499      </t>
500  </list>
501</t>
502<t>
503   Note that any of the requirements listed above can be overridden by a
504   cache-control extension; see <xref target="cache.control.extensions" />.
505</t>
506<t>
507   When a stored response is used to satisfy a request without validation,
508   a cache &MUST; send a single <x:ref>Age</x:ref> header field
509   (<xref target="header.age"/>) in the response with a value equal to the
510   stored response's current_age; see <xref target="age.calculations" />.
511</t>
512<t>
513   A cache &MUST; write through requests with methods that are unsafe
514   (&safe-methods;) to the origin server; i.e., a cache is not allowed to
515   generate a reply to such a request before having forwarded the request and
516   having received a corresponding response.
517</t>
518<t>
519   Also, note that unsafe requests might invalidate already stored responses;
520   see <xref target="invalidation.after.updates.or.deletions" />.
521</t>
522<t>
523   When more than one suitable response is stored, a cache &MUST; use the
524   most recent response (as determined by the <x:ref>Date</x:ref> header
525   field). It can also forward a request with "Cache-Control: max-age=0" or
526   "Cache-Control: no-cache" to disambiguate which response to use.
527</t>
528<t>
529   A cache that does not have a clock available &MUST-NOT; use stored
530   responses without revalidating them on every use.
531</t>
532
533
534<section anchor="expiration.model" title="Freshness Model">
535<t>
536   When a response is "fresh" in the cache, it can be used to satisfy
537   subsequent requests without contacting the origin server, thereby improving
538   efficiency.
539</t>
540<t>
541   The primary mechanism for determining freshness is for an origin server to
542   provide an explicit expiration time in the future, using either the
543   <x:ref>Expires</x:ref> header field (<xref target="header.expires" />) or
544   the max-age response cache directive (<xref
545   target="cache-response-directive.max-age" />). Generally, origin servers will
546   assign future explicit expiration times to responses in the belief that the
547   representation is not likely to change in a semantically significant way
548   before the expiration time is reached.
549</t>
550<t>
551   If an origin server wishes to force a cache to validate every request, it
552   can assign an explicit expiration time in the past to indicate that the
553   response is already stale. Compliant caches will normally validate a stale
554   cached response before reusing it for subsequent requests (see <xref
555   target="serving.stale.responses" />).
556</t>
557<t>
558   Since origin servers do not always provide explicit expiration times, a
559   cache &MAY; assign a heuristic expiration time when an explicit time is not
560   specified, employing algorithms that use other header field values (such as
561   the <x:ref>Last-Modified</x:ref> time) to estimate a plausible expiration
562   time. This specification does not provide specific algorithms, but does
563   impose worst-case constraints on their results.
564</t>
565<figure>
566<preamble>
567  The calculation to determine if a response is fresh is:
568</preamble>
569<artwork type="code">
570   response_is_fresh = (freshness_lifetime &gt; current_age)
571</artwork>
572</figure>
573<t>
574   The freshness_lifetime is defined in <xref
575   target="calculating.freshness.lifetime" />; the current_age is defined in
576   <xref target="age.calculations" />.
577</t>
578<t>
579   Clients can send the max-age or min-fresh cache directives in a request to
580   constrain or relax freshness calculations for the corresponding response
581   (<xref target="cache-request-directive" />).
582</t>
583<t>
584   Note that freshness applies only to cache operation; it cannot be used to
585   force a user agent to refresh its display or reload a resource. See <xref
586   target="history.lists" /> for an explanation of the difference between
587   caches and history mechanisms.
588</t>
589
590<section anchor="calculating.freshness.lifetime"
591   title="Calculating Freshness Lifetime">
592<t>
593   A cache can calculate the freshness lifetime (denoted as
594   freshness_lifetime) of a response by using the first match of:
595   <list style="symbols">
596      <t>If the cache is shared and the s-maxage response cache directive
597      (<xref target="cache-response-directive.s-maxage" />) is present, use its value,
598      or</t>
599      <t>If the max-age response cache directive (<xref
600      target="cache-response-directive.max-age" />) is present, use its value, or</t>
601      <t>If the <x:ref>Expires</x:ref> response header field
602      (<xref target="header.expires" />) is present, use its value minus the
603      value of the <x:ref>Date</x:ref> response header field, or</t>
604      <t>Otherwise, no explicit expiration time is present in the response. A
605      heuristic freshness lifetime might be applicable; see <xref
606      target="heuristic.freshness" />.</t>
607   </list>
608</t>
609<t>
610   Note that this calculation is not vulnerable to clock skew, since all of
611   the information comes from the origin server.
612</t>
613<t>
614   When there is more than one value present for a given directive (e.g., two
615   <x:ref>Expires</x:ref> header fields, multiple Cache-Control: max-age
616   directives), it is considered invalid. Caches are encouraged to consider
617   responses that have invalid freshness information to be stale.
618</t>
619</section>
620
621<section anchor="heuristic.freshness" title="Calculating Heuristic Freshness">
622<t>
623   A cache &MUST-NOT; use heuristics to determine freshness unless no explicit
624   expiration time is present in a stored response and either the status code
625   is defined as cacheable by default (including the following in
626   &status-codes;: <x:ref>200 (OK)</x:ref>, <x:ref>203 (Non-Authoritative
627   Information)</x:ref>, <x:ref>206 (Partial Content)</x:ref>, <x:ref>300
628   (Multiple Choices)</x:ref>, <x:ref>301 (Moved Permanently)</x:ref> and
629   <x:ref>410 (Gone)</x:ref>) or the response has been explicitly marked as
630   cacheable (e.g., by using the public directive without a max-age).
631</t>
632<t>
633   When a heuristic is used to calculate freshness lifetime, a cache &SHOULD;
634   attach a <x:ref>Warning</x:ref> header field with a 113 warn-code to the
635   response if its current_age is more than 24 hours and such a warning is not
636   already present.
637</t>
638<t>
639   Also, if the response has a <x:ref>Last-Modified</x:ref> header field
640   (&header-last-modified;), caches are encouraged to use a heuristic
641   expiration value that is no more than some fraction of the interval since
642   that time. A typical setting of this fraction might be 10%.
643</t>
644<x:note>
645   <t>
646      &Note; <xref target="RFC2616" x:fmt="of" x:sec="13.9"/> prohibited caches
647      from calculating heuristic freshness for URIs with query components
648      (i.e., those containing '?'). In practice, this has not been widely
649      implemented. Therefore, servers are encouraged to send explicit
650      directives (e.g., Cache-Control: no-cache) if they wish to preclude
651      caching.
652   </t>
653</x:note>
654</section>
655
656<section anchor="age.calculations" title="Calculating Age">
657<t>
658   The <x:ref>Age</x:ref> header field is used to convey an estimated
659   age of the response message when obtained from a cache. The Age field value
660   is the cache's estimate of the number of seconds since the response was
661   generated or validated by the origin server. In essence, the Age value is
662   the sum of the time that the response has been resident in each of the
663   caches along the path from the origin server, plus the amount of time it
664   has been in transit along network paths.
665</t>
666<t>
667   The following data is used for the age calculation:
668</t>
669<t>
670   <x:dfn>age_value</x:dfn>
671   <list>
672      <t>
673         The term "age_value" denotes the value of the <x:ref>Age</x:ref>
674         header field (<xref target="header.age"/>), in a form appropriate for
675         arithmetic operation; or 0, if not available.
676      </t>
677   </list>
678</t>
679<t>
680   <x:dfn>date_value</x:dfn>
681   <list>
682      <t>
683         The term "date_value" denotes the value of
684         the Date header field, in a form appropriate for arithmetic
685         operations. See &header-date; for the definition of the Date header
686         field, and for requirements regarding responses without it.
687      </t>
688   </list>
689</t>
690<t>
691   <x:dfn>now</x:dfn>
692   <list>
693      <t>
694         The term "now" means "the current value of the clock at the host
695         performing the calculation". A host ought to use NTP (<xref
696         target="RFC1305"/>) or some similar protocol to synchronize its
697         clocks to Coordinated Universal Time.
698      </t>
699   </list>
700</t>
701<t>
702   <x:dfn>request_time</x:dfn>
703   <list>
704      <t>
705         The current value of the clock at the host at the time the request
706         resulting in the stored response was made.
707      </t>
708   </list>
709</t>
710<t>
711   <x:dfn>response_time</x:dfn>
712   <list>
713      <t>
714         The current value of the clock at the host at the time the response
715         was received.
716      </t>
717   </list>
718</t>
719<t>
720   A response's age can be calculated in two entirely independent ways:
721   <list style="numbers">
722      <t>the "apparent_age": response_time minus date_value, if the local
723      clock is reasonably well synchronized to the origin server's clock. If
724      the result is negative, the result is replaced by zero.</t>
725      <t>the "corrected_age_value", if all of the caches along the response
726      path implement HTTP/1.1. A cache &MUST; interpret this value relative
727      to the time the request was initiated, not the time that the response
728      was received.</t>
729   </list>
730</t>
731<figure>
732<artwork type="code">
733  apparent_age = max(0, response_time - date_value);
734
735  response_delay = response_time - request_time;
736  corrected_age_value = age_value + response_delay; 
737</artwork>
738</figure>
739<figure>
740<preamble>These &SHOULD; be combined as</preamble>
741<artwork type="code">
742  corrected_initial_age = max(apparent_age, corrected_age_value);
743</artwork></figure>
744<t>
745   unless the cache is confident in the value of the <x:ref>Age</x:ref> header
746   field (e.g., because there are no HTTP/1.0 hops in the <x:ref>Via</x:ref>
747   header field), in which case the corrected_age_value &MAY; be used as the
748   corrected_initial_age.</t>
749<t>
750   The current_age of a stored response can then be calculated by adding the
751   amount of time (in seconds) since the stored response was last validated by
752   the origin server to the corrected_initial_age.
753</t>
754<figure><artwork type="code">
755  resident_time = now - response_time;
756  current_age = corrected_initial_age + resident_time;
757</artwork></figure>
758<t>
759   Additionally, to avoid common problems in date parsing:
760</t>
761<t>
762  <list style="symbols">
763     <t>Although all date formats are specified to be case-sensitive,
764        cache recipients &SHOULD; match day, week and timezone names
765        case-insensitively.</t>
766             
767     <t>If a cache recipient's internal implementation of time has less
768        resolution than the value of an HTTP-date, the recipient &MUST;
769        internally represent a parsed <x:ref>Expires</x:ref> date as the
770        nearest time equal to or earlier than the received value.</t>
771
772     <t>Cache recipients &MUST-NOT; allow local time zones to influence the
773        calculation or comparison of an age or expiration time.</t>
774
775     <t>Cache recipients &SHOULD; consider a date with a zone abbreviation
776        other than "GMT" to be invalid for calculating expiration.</t>
777  </list>
778</t>
779</section>
780
781<section anchor="serving.stale.responses" title="Serving Stale Responses">
782<t>
783   A "stale" response is one that either has explicit expiry information or is
784   allowed to have heuristic expiry calculated, but is not fresh according to
785   the calculations in <xref target="expiration.model" />.
786</t>
787<t>
788   A cache &MUST-NOT; send a stale response if it is prohibited by an
789   explicit in-protocol directive (e.g., by a "no-store" or "no-cache" cache
790   directive, a "must-revalidate" cache-response-directive, or an applicable
791   "s-maxage" or "proxy-revalidate" cache-response-directive; see <xref
792   target="cache-response-directive"/>).
793</t>
794<t>
795   A cache &MUST-NOT; send stale responses unless it is disconnected
796   (i.e., it cannot contact the origin server or otherwise find a forward
797   path) or doing so is explicitly allowed (e.g., by the max-stale request
798   directive; see <xref target="cache-request-directive" />).
799</t>
800<t>
801   A cache &SHOULD; append a <x:ref>Warning</x:ref> header field with the 110
802   warn-code (see <xref target="header.warning"/>) to stale responses.
803   Likewise, a cache &SHOULD; add the 112 warn-code to stale responses if the
804   cache is disconnected.
805</t>
806<t>
807   If a cache receives a first-hand response (either an entire response, or a
808   <x:ref>304 (Not Modified)</x:ref> response) that it would normally forward
809   to the requesting client, and the received response is no longer fresh, the
810   cache can forward it to the requesting client without adding a new
811   <x:ref>Warning</x:ref> (but without removing any existing Warning header
812   fields). A cache shouldn't attempt to validate a response simply because
813   that response became stale in transit.
814</t>
815</section>
816</section>
817
818<section anchor="validation.model" title="Validation Model">
819<t>
820   When a cache has one or more stored responses for a requested URI, but
821   cannot serve any of them (e.g., because they are not fresh, or one cannot
822   be selected; see <xref target="caching.negotiated.responses"/>), it can use
823   the conditional request mechanism &conditional; in the forwarded request to
824   give the origin server an opportunity to both select a valid stored
825   response to be used, and to update it. This process is known as
826   "validating" or "revalidating" the stored response.
827</t>
828<t>
829   When sending such a conditional request, a cache adds an
830   <x:ref>If-Modified-Since</x:ref> header field whose value is that of the
831   <x:ref>Last-Modified</x:ref> header field from the selected
832   (see <xref target="caching.negotiated.responses"/>) stored response, if
833   available.
834</t>
835<t>
836   Additionally, a cache can add an <x:ref>If-None-Match</x:ref> header field
837   whose value is that of the <x:ref>ETag</x:ref> header field(s) from all
838   responses stored for the requested URI, if present. However, if any of the
839   stored responses contains only partial content, the cache shouldn't
840   include its entity-tag in the If-None-Match header field unless the request
841   is for a range that would be fully satisfied by that stored response.
842</t>
843
844<t>Cache handling of a response to a conditional request is dependent upon its
845status code:</t>
846
847<t>
848   <list style="symbols">
849      <t>
850         A <x:ref>304 (Not Modified)</x:ref> response status code indicates
851         that the stored response can be updated and reused; see <xref
852         target="freshening.responses"/>.
853      </t>
854      <t>
855         A full response (i.e., one with a payload body) indicates that none
856         of the stored responses nominated in the conditional request is
857         suitable. Instead, the cache can use the full response to
858         satisfy the request and &MAY; replace the stored response(s).
859      </t>
860      <t>
861         However, if a cache receives a <x:ref>5xx (Server Error)</x:ref>
862         response while attempting to validate a response, it can either
863         forward this response to the requesting client, or act as if the
864         server failed to respond. In the latter case, it can send a
865         previously stored response (see <xref
866         target="serving.stale.responses" />).
867      </t>
868   </list>
869</t>
870
871<section anchor="freshening.responses" title="Freshening Responses with 304 Not Modified">
872<t>
873   When a cache receives a <x:ref>304 (Not Modified)</x:ref> response and
874   already has one or more stored <x:ref>200 (OK)</x:ref> responses for the
875   same cache key, the cache needs to identify which of the stored responses
876   are updated by this new response and then update the stored response(s)
877   with the new information provided in the <x:ref>304</x:ref> response.
878</t>
879<t>
880   The stored response to update is identified by using the first match (if
881   any) of:
882   <list style="symbols">
883    <t>
884     If the new response contains a strong validator, then that strong
885     validator identifies the selected representation.  All of the stored
886     responses with the same strong validator are selected.
887     If none of the stored responses contain the same strong validator,
888     then the new response &MUST-NOT; be used to update any stored responses.
889    </t>
890    <t>
891     If the new response contains a weak validator and that validator
892     corresponds to one of the cache's stored responses, then the most
893     recent of those matching stored responses is selected.
894    </t>
895    <t>
896     If the new response does not include any form of validator (such as in
897     the case where a client generates an If-Modified-Since request from a
898     source other than the Last-Modified response header field), and there is
899     only one stored response, and that stored response also lacks a
900     validator, then that stored response is selected.
901    </t>
902   </list>
903</t>
904<t>
905   If a stored response is selected for update, the cache &MUST;:
906   <list style="symbols">
907      <t>delete any <x:ref>Warning</x:ref> header fields in the stored response
908         with warn-code 1xx (see <xref target="header.warning" />);</t>
909      <t>retain any <x:ref>Warning</x:ref> header fields in the stored response
910         with warn-code 2xx; and,</t>
911      <t>use other header fields provided in the <x:ref>304 (Not Modified)</x:ref>
912         response to replace all instances of the corresponding header
913         fields in the stored response.</t>
914   </list>
915</t>
916</section>
917
918</section>
919
920<section anchor="caching.negotiated.responses"
921   title="Using Negotiated Responses">
922<t>
923   When a cache receives a request that can be satisfied by a stored response
924   that has a <x:ref>Vary</x:ref> header field (&header-vary;),
925   it &MUST-NOT; use that response unless all of the selecting header fields
926   nominated by the Vary header field match in both the original request
927   (i.e., that associated with the stored response), and the presented
928   request.
929</t>
930<t>
931   The selecting header fields from two requests are defined to match if and
932   only if those in the first request can be transformed to those in the
933   second request by applying any of the following:
934   <list style="symbols">
935      <t>
936         adding or removing whitespace, where allowed in the header field's
937         syntax
938      </t>
939      <t>
940         combining multiple header fields with the same field name
941         (see &header-fields;)
942      </t>
943      <t>
944         normalizing both header field values in a way that is known to have
945         identical semantics, according to the header field's specification
946         (e.g., re-ordering field values when order is not significant;
947         case-normalization, where values are defined to be case-insensitive)
948      </t>
949  </list>
950</t>
951<t>
952   If (after any normalization that might take place) a header field is absent
953   from a request, it can only match another request if it is also absent
954   there.
955</t>
956<t>
957   A <x:ref>Vary</x:ref> header field-value of "*" always fails to match, and
958   subsequent requests to that resource can only be properly interpreted by the
959   origin server.
960</t>
961<t>
962   The stored response with matching selecting header fields is known as the
963   selected response.
964</t>
965<t>
966   If multiple selected responses are available, the most recent response
967   (as determined by the <x:ref>Date</x:ref> header field) is used; see <xref
968   target="constructing.responses.from.caches"/>.
969</t>
970<t>
971   If no selected response is available, the cache cannot satisfy the
972   presented request. Typically, it is forwarded to the origin server
973   in a (possibly conditional; see <xref target="validation.model"/>) request.
974</t>
975</section>
976
977
978<section anchor="combining.responses" title="Combining Partial Content">
979<t>
980   A response might transfer only a partial representation if the
981   connection closed prematurely or if the request used one or more Range
982   specifiers (&partial;).  After several such transfers, a cache might have
983   received several ranges of the same representation.  A cache &MAY; combine
984   these ranges into a single stored response, and reuse that response to
985   satisfy later requests, if they all share the same strong validator and
986   the cache complies with the client requirements in &combining-byte-ranges;.
987</t>
988<t>
989   When combining the new response with one or more stored responses, a
990   cache &MUST;:
991   <list style="symbols">
992      <t>delete any <x:ref>Warning</x:ref> header fields in the stored response
993         with warn-code 1xx (see <xref target="header.warning" />);</t>
994      <t>retain any <x:ref>Warning</x:ref> header fields in the stored response
995         with warn-code 2xx; and,</t>
996      <t>use other header fields provided in the new response, aside
997         from <x:ref>Content-Range</x:ref>, to replace all instances of the
998         corresponding header fields in the stored response.</t>
999   </list>
1000</t>
1001</section>
1002</section>
1003
1004
1005<section anchor="head.effects" title="Updating Caches with HEAD Responses">
1006<t>
1007   A response to the HEAD method is identical to what an equivalent request
1008   made with a GET would have been, except it lacks a body. This property
1009   of HEAD responses is used to both invalidate and update cached GET
1010   responses.
1011</t>
1012<t>
1013   If one or more stored GET responses can be selected (as per <xref
1014   target="caching.negotiated.responses"/>) for a HEAD request, and the
1015   <x:ref>Content-Length</x:ref>, <x:ref>ETag</x:ref> or
1016   <x:ref>Last-Modified</x:ref> value of a HEAD response differs from that in a
1017   selected GET response, the cache &MUST; consider that selected response to
1018   be stale.
1019</t>
1020<t>
1021   If the <x:ref>Content-Length</x:ref>, <x:ref>ETag</x:ref> and
1022   <x:ref>Last-Modified</x:ref> values of a HEAD response (when present) are
1023   the same as that in a selected GET response (as per
1024   <xref target="caching.negotiated.responses"/>), the cache &SHOULD; update
1025   the remaining header fields in the stored response using the following
1026   rules:
1027   <list style="symbols">
1028      <t>delete any <x:ref>Warning</x:ref> header fields in the stored response
1029         with warn-code 1xx (see <xref target="header.warning" />);</t>
1030      <t>retain any <x:ref>Warning</x:ref> header fields in the stored response
1031         with warn-code 2xx; and,</t>
1032      <t>use other header fields provided in the response to replace
1033         all instances of the corresponding header fields in the stored
1034         response.</t>
1035   </list>
1036</t>
1037
1038</section>
1039
1040
1041<section anchor="invalidation.after.updates.or.deletions"
1042   title="Request Methods that Invalidate">
1043<t>
1044   Because unsafe request methods (&safe-methods;) such as PUT, POST or DELETE
1045   have the potential for changing state on the origin server, intervening
1046   caches can use them to keep their contents up-to-date.
1047</t>
1048<t>
1049   A cache &MUST; invalidate the effective Request URI
1050   (&effective-request-uri;) as well as the URI(s) in the
1051   <x:ref>Location</x:ref> and <x:ref>Content-Location</x:ref> response header
1052   fields (if present) when a non-error response to a request with an unsafe
1053   method is received.
1054</t>
1055<t>
1056   However, a cache &MUST-NOT; invalidate a URI from a <x:ref>Location</x:ref>
1057   or <x:ref>Content-Location</x:ref> response header field if the host part of
1058   that URI differs from the host part in the effective request URI
1059   (&effective-request-uri;). This helps prevent denial of service attacks.
1060</t>
1061<t>
1062   A cache &MUST; invalidate the effective request URI
1063   (&effective-request-uri;) when it receives a non-error response
1064   to a request with a method whose safety is unknown.
1065</t>
1066<t>
1067   Here, a "non-error response" is one with a <x:ref>2xx (Successful)</x:ref>
1068   or <x:ref>3xx (Redirection)</x:ref> status code. "Invalidate" means that
1069   the cache will either remove all stored responses related to the effective
1070   request URI, or will mark these as "invalid" and in need of a mandatory
1071   validation before they can be sent in response to a subsequent request.
1072</t>
1073<t>
1074   Note that this does not guarantee that all appropriate responses are
1075   invalidated. For example, the request that caused the change at the origin
1076   server might not have gone through the cache where a response is stored.
1077</t>
1078</section>
1079
1080
1081
1082
1083<section anchor="header.field.definitions" title="Header Field Definitions">
1084<t>
1085   This section defines the syntax and semantics of HTTP/1.1 header fields
1086   related to caching.
1087</t>
1088
1089<section anchor="header.age" title="Age">
1090   <iref item="Age header field" primary="true" x:for-anchor="" />
1091   <x:anchor-alias value="Age"/>
1092   <x:anchor-alias value="age-value"/>
1093<t>
1094   The "Age" header field conveys the sender's estimate of the amount
1095   of time since the response was generated or successfully validated at the
1096   origin server. Age values are calculated as specified in <xref
1097   target="age.calculations" />.
1098</t>
1099<figure><artwork type="abnf2616"><iref primary="true" item="Grammar" subitem="Age"/>
1100  <x:ref>Age</x:ref> = <x:ref>delta-seconds</x:ref>
1101</artwork></figure>
1102<t>
1103  Age field-values are non-negative integers, representing time in seconds
1104  (see <xref target="delta-seconds"/>).
1105</t>
1106<t>
1107   The presence of an Age header field in a response implies that a response
1108   is not first-hand. However, the converse is not true, since HTTP/1.0 caches
1109   might not implement the Age header field.
1110</t>
1111</section>
1112
1113<section anchor="header.cache-control" title="Cache-Control">
1114   <iref item="Cache-Control header field" primary="true" x:for-anchor="" />
1115   <x:anchor-alias value="Cache-Control"/>
1116   <x:anchor-alias value="cache-directive"/>
1117<t>
1118   The "Cache-Control" header field is used to specify directives for
1119   caches along the request/response chain. Such cache directives are
1120   unidirectional in that the presence of a directive in a request does not
1121   imply that the same directive is to be given in the response.
1122</t>
1123<t>
1124   A cache &MUST; obey the requirements of the Cache-Control
1125   directives defined in this section. See <xref
1126   target="cache.control.extensions"/> for information about how Cache-Control
1127   directives defined elsewhere are handled.
1128</t>
1129<x:note>
1130   <t>
1131       &Note; HTTP/1.0 caches might not implement Cache-Control and
1132       might only implement Pragma: no-cache (see <xref target="header.pragma"
1133       />).
1134   </t>
1135</x:note>
1136<t>
1137   A proxy, whether or not it implements a cache, &MUST; pass cache directives
1138   through in forwarded messages, regardless of their
1139   significance to that application, since the directives might be applicable
1140   to all recipients along the request/response chain. It is not possible to
1141   target a directive to a specific cache.
1142</t>
1143<t>
1144   Cache directives are identified by a token, to be compared case-insensitively,
1145   and have an optional argument, that can use both token and quoted-string
1146   syntax. For the directives defined below that define arguments, recipients
1147   ought to accept both forms, even if one is documented to be preferred. For
1148   any directive not defined by this specification, recipients &MUST; accept
1149   both forms.
1150</t>
1151<figure><artwork type="abnf2616"><iref primary="true" item="Grammar" subitem="Cache-Control"/><iref primary="true" item="Grammar" subitem="cache-directive"/>
1152  <x:ref>Cache-Control</x:ref>   = 1#<x:ref>cache-directive</x:ref>
1153
1154  <x:ref>cache-directive</x:ref> = <x:ref>token</x:ref> [ "=" ( <x:ref>token</x:ref> / <x:ref>quoted-string</x:ref> ) ]
1155</artwork></figure>
1156<t>
1157   For the cache directives defined below, no argument is defined (nor allowed)
1158   otherwise stated otherwise.
1159</t>
1160
1161<section title="Request Cache-Control Directives" anchor="cache-request-directive">
1162
1163<section title="no-cache" anchor="cache-request-directive.no-cache">
1164   <iref item="no-cache (cache directive)" primary="true" />
1165<t>
1166   The "no-cache" request directive indicates that a cache &MUST-NOT;
1167   use a stored response to satisfy the request without successful
1168   validation on the origin server.
1169</t>
1170</section>
1171 
1172<section title="no-store" anchor="cache-request-directive.no-store">
1173   <iref item="no-store (cache directive)" primary="true" />
1174<t>
1175   The "no-store" request directive indicates that a cache &MUST-NOT;
1176   store any part of either this request or any response to it. This
1177   directive applies to both private and shared caches. "&MUST-NOT;
1178   store" in this context means that the cache &MUST-NOT; intentionally
1179   store the information in non-volatile storage, and &MUST; make a
1180   best-effort attempt to remove the information from volatile storage as
1181   promptly as possible after forwarding it.
1182</t>
1183<t>
1184   This directive is NOT a reliable or sufficient mechanism for ensuring
1185   privacy. In particular, malicious or compromised caches might not
1186   recognize or obey this directive, and communications networks might be
1187   vulnerable to eavesdropping.
1188</t>
1189<t>
1190   Note that if a request containing this directive is satisfied from a
1191   cache, the no-store request directive does not apply to the already
1192   stored response.
1193</t>
1194</section>
1195
1196<section title="max-age" anchor="cache-request-directive.max-age">
1197   <iref item="max-age (cache directive)" primary="true" />
1198<t>
1199   Argument syntax:
1200   <list>
1201      <t>
1202        <x:ref>delta-seconds</x:ref> (see <xref target="delta-seconds"/>)
1203      </t>
1204   </list>
1205</t>
1206<t>
1207   The "max-age" request directive indicates that the client is unwilling to
1208   accept a response whose age is greater than the specified number of
1209   seconds. Unless the max-stale request directive is also present, the
1210   client is not willing to accept a stale response.
1211</t>
1212<t>
1213   &Note; This directive uses the token form of the argument syntax;
1214   e.g., 'max-age=5', not 'max-age="5"'. Senders &SHOULD-NOT; use the
1215   quoted-string form.
1216</t>
1217</section>
1218
1219<section title="max-stale" anchor="cache-request-directive.max-stale">
1220   <iref item="max-stale (cache directive)" primary="true" />
1221<t>
1222   Argument syntax:
1223   <list>
1224      <t>
1225        <x:ref>delta-seconds</x:ref> (see <xref target="delta-seconds"/>)
1226      </t>
1227   </list>
1228</t>
1229<t>
1230   The "max-stale" request directive indicates that the client is willing
1231   to accept a response that has exceeded its expiration time. If max-stale
1232   is assigned a value, then the client is willing to accept a response
1233   that has exceeded its expiration time by no more than the specified
1234   number of seconds. If no value is assigned to max-stale, then the client
1235   is willing to accept a stale response of any age.
1236</t>
1237<t>
1238   &Note; This directive uses the token form of the argument syntax;
1239   e.g., 'max-stale=10', not 'max-stale="10"'. Senders &SHOULD-NOT; use the
1240   quoted-string form.
1241</t>
1242</section>
1243
1244<section title="min-fresh" anchor="cache-request-directive.min-fresh">
1245   <iref item="min-fresh (cache directive)" primary="true" />
1246<t>
1247   Argument syntax:
1248   <list>
1249      <t>
1250        <x:ref>delta-seconds</x:ref> (see <xref target="delta-seconds"/>)
1251      </t>
1252   </list>
1253</t>
1254<t>
1255   The "min-fresh" request directive indicates that the client is willing
1256   to accept a response whose freshness lifetime is no less than its
1257   current age plus the specified time in seconds. That is, the client
1258   wants a response that will still be fresh for at least the specified
1259   number of seconds.
1260</t>
1261<t>
1262   &Note; This directive uses the token form of the argument syntax;
1263   e.g., 'min-fresh=20', not 'min-fresh="20"'. Senders &SHOULD-NOT; use the
1264   quoted-string form.
1265</t>
1266</section>
1267
1268<section title="no-transform" anchor="cache-request-directive.no-transform">
1269   <iref item="no-transform (cache directive)" primary="true" />
1270<t>
1271   The "no-transform" request directive indicates that an intermediary
1272   (whether or not it implements a cache) &MUST-NOT; transform the payload,
1273   as defined in &transformations;.
1274</t>
1275</section>
1276
1277<section title="only-if-cached" anchor="cache-request-directive.only-if-cached">
1278   <iref item="only-if-cached (cache directive)" primary="true" />
1279<t>
1280   The "only-if-cached" request directive indicates that the client only wishes
1281   to obtain a stored response. If it receives this directive, a cache &SHOULD;
1282   either respond using a stored response that is consistent with the other
1283   constraints of the request, or respond with a <x:ref>504 (Gateway
1284   Timeout)</x:ref> status code. If a group of caches is being operated as a
1285   unified system with good internal connectivity, a member cache &MAY;
1286   forward such a request within that group of caches.
1287</t>
1288</section>
1289</section>
1290
1291<section anchor="cache-response-directive"
1292   title="Response Cache-Control Directives">
1293   <x:anchor-alias value="cache-response-directive" />
1294
1295<section title="public" anchor="cache-response-directive.public">
1296   <iref item="public (cache directive)" primary="true" />
1297<t>
1298   The "public" response directive indicates that a response whose
1299   associated request contains an 'Authentication' header &MAY; be
1300   stored (see <xref target="caching.authenticated.responses" />).
1301</t>
1302</section>
1303
1304<section title="private" anchor="cache-response-directive.private">
1305   <iref item="private (cache directive)" primary="true" />
1306<t>
1307   Argument syntax:
1308   <list>
1309      <t>
1310        #<x:ref>field-name</x:ref>
1311      </t>
1312   </list>
1313</t>
1314<t>
1315   The "private" response directive indicates that the response message is
1316   intended for a single user and &MUST-NOT; be stored by a shared cache. A
1317   private cache &MAY; store the response.
1318</t>
1319<t>
1320   If the private response directive specifies one or more field-names,
1321   this requirement is limited to the field-values associated with the
1322   listed response header fields. That is, a shared cache &MUST-NOT; store
1323   the specified field-names(s), whereas it &MAY; store the remainder of the
1324   response message.
1325</t>
1326<t>
1327   The field-names given are not limited to the set of standard header
1328   fields defined by this specification. Field names are case-insensitive.
1329</t>
1330<t>
1331   &Note; This usage of the word "private" only controls
1332   where the response can be stored; it cannot ensure the privacy of the
1333   message content. Also, private response directives with field-names are
1334   often handled by implementations as if an unqualified private directive
1335   was received; i.e., the special handling for the qualified form is not
1336   widely implemented.
1337</t>
1338<t>
1339   &Note; This directive uses the quoted-string form of the argument syntax.
1340   Senders &SHOULD-NOT; use the token form (even if quoting appears not to be
1341   needed for single-entry lists).
1342</t>
1343</section>
1344
1345<section title="no-cache" anchor="cache-response-directive.no-cache">
1346   <iref item="no-cache (cache directive)" primary="true" />
1347<t>
1348   Argument syntax:
1349   <list>
1350      <t>
1351        #<x:ref>field-name</x:ref>
1352      </t>
1353   </list>
1354</t>
1355<t>
1356   The "no-cache" response directive indicates that the response &MUST-NOT;
1357   be used to satisfy a subsequent request without successful validation on
1358   the origin server. This allows an origin server to prevent a cache from
1359   using it to satisfy a request without contacting it, even by caches that
1360   have been configured to send stale responses.
1361</t>
1362<t>
1363   If the no-cache response directive specifies one or more field-names,
1364   then a cache &MAY; use the response to satisfy a subsequent request,
1365   subject to any other restrictions on caching. However, any header fields
1366   in the response that have the field-name(s) listed &MUST-NOT; be sent
1367   in the response to a subsequent request without successful revalidation
1368   with the origin server. This allows an origin server to prevent the
1369   re-use of certain header fields in a response, while still allowing
1370   caching of the rest of the response.
1371</t>
1372<t>
1373   The field-names given are not limited to the set of standard header
1374   fields defined by this specification. Field names are case-insensitive.
1375</t>
1376<t>
1377   &Note; Many HTTP/1.0 caches will not recognize or obey
1378   this directive. Also, no-cache response directives with field-names are
1379   often handled by implementations as if an unqualified no-cache directive
1380   was received; i.e., the special handling for the qualified form is not
1381   widely implemented.
1382</t>
1383<t>
1384   &Note; This directive uses the quoted-string form of the argument syntax.
1385   Senders &SHOULD-NOT; use the token form (even if quoting appears not to be
1386   needed for single-entry lists).
1387</t>
1388</section>
1389
1390<section title="no-store" anchor="cache-response-directive.no-store">
1391   <iref item="no-store (cache directive)" primary="true" />
1392<t>
1393   The "no-store" response directive indicates that a cache &MUST-NOT;
1394   store any part of either the immediate request or response. This
1395   directive applies to both private and shared caches. "&MUST-NOT;
1396   store" in this context means that the cache &MUST-NOT; intentionally
1397   store the information in non-volatile storage, and &MUST; make a
1398   best-effort attempt to remove the information from volatile storage as
1399   promptly as possible after forwarding it.
1400</t>
1401<t>
1402   This directive is NOT a reliable or sufficient mechanism for ensuring
1403   privacy. In particular, malicious or compromised caches might not
1404   recognize or obey this directive, and communications networks might be
1405   vulnerable to eavesdropping.
1406</t>
1407</section>
1408
1409<section title="must-revalidate" anchor="cache-response-directive.must-revalidate">
1410   <iref item="must-revalidate (cache directive)" primary="true" />
1411<t>
1412   The "must-revalidate" response directive indicates that once it has
1413   become stale, a cache &MUST-NOT; use the response to satisfy subsequent
1414   requests without successful validation on the origin server.
1415</t>
1416<t>
1417   The must-revalidate directive is necessary to support reliable
1418   operation for certain protocol features. In all circumstances a
1419   cache &MUST; obey the must-revalidate directive; in particular,
1420   if a cache cannot reach the origin server for any reason, it &MUST;
1421   generate a <x:ref>504 (Gateway Timeout)</x:ref> response.
1422</t>
1423<t>
1424   The must-revalidate directive ought to be used by servers if and only
1425   if failure to validate a request on the representation could result in
1426   incorrect operation, such as a silently unexecuted financial
1427   transaction.
1428</t>
1429</section>
1430
1431<section title="proxy-revalidate" anchor="cache-response-directive.proxy-revalidate">
1432   <iref item="proxy-revalidate (cache directive)" primary="true" />
1433<t>
1434   The "proxy-revalidate" response directive has the same meaning as the
1435   must-revalidate response directive, except that it does not apply to
1436   private caches.
1437</t>
1438</section>
1439
1440<section title="max-age" anchor="cache-response-directive.max-age">
1441   <iref item="max-age (cache directive)" primary="true" />
1442<t>
1443   Argument syntax:
1444   <list>
1445      <t>
1446        <x:ref>delta-seconds</x:ref> (see <xref target="delta-seconds"/>)
1447      </t>
1448   </list>
1449</t>
1450<t>
1451   The "max-age" response directive indicates that the response is to be
1452   considered stale after its age is greater than the specified number of
1453   seconds.
1454</t>
1455<t>
1456   &Note; This directive uses the token form of the argument syntax;
1457   e.g., 'max-age=5', not 'max-age="5"'. Senders &SHOULD-NOT; use the
1458   quoted-string form.
1459</t>
1460</section>     
1461
1462<section title="s-maxage" anchor="cache-response-directive.s-maxage">
1463   <iref item="s-maxage (cache directive)" primary="true" />
1464<t>
1465   Argument syntax:
1466   <list>
1467      <t>
1468        <x:ref>delta-seconds</x:ref> (see <xref target="delta-seconds"/>)
1469      </t>
1470   </list>
1471</t>
1472<t>
1473   The "s-maxage" response directive indicates that, in shared caches, the
1474   maximum age specified by this directive overrides the maximum age
1475   specified by either the max-age directive or the <x:ref>Expires</x:ref>
1476   header field. The s-maxage directive also implies the semantics of the
1477   proxy-revalidate response directive.
1478</t>
1479<t>
1480   &Note; This directive uses the token form of the argument syntax;
1481   e.g., 's-maxage=10', not 's-maxage="10"'. Senders &SHOULD-NOT; use the
1482   quoted-string form.
1483</t>
1484</section>
1485
1486<section title="no-transform" anchor="cache-response-directive.no-transform">
1487   <iref item="no-transform (cache directive)" primary="true" />
1488<t>
1489   The "no-transform" response directive indicates that an intermediary
1490   (regardless of whether it implements a cache) &MUST-NOT; transform the
1491   payload, as defined in &transformations;.
1492</t>
1493</section>
1494
1495</section>
1496
1497<section anchor="cache.control.extensions" title="Cache Control Extensions">
1498<t>
1499   The Cache-Control header field can be extended through the use of one or
1500   more cache-extension tokens, each with an optional value. Informational
1501   extensions (those that do not require a change in cache behavior) can be
1502   added without changing the semantics of other directives. Behavioral
1503   extensions are designed to work by acting as modifiers to the existing base
1504   of cache directives. Both the new directive and the standard directive are
1505   supplied, such that applications that do not understand the new directive
1506   will default to the behavior specified by the standard directive, and those
1507   that understand the new directive will recognize it as modifying the
1508   requirements associated with the standard directive. In this way,
1509   extensions to the cache-control directives can be made without requiring
1510   changes to the base protocol.
1511</t>
1512<t>
1513   This extension mechanism depends on an HTTP cache obeying all of the
1514   cache-control directives defined for its native HTTP-version, obeying
1515   certain extensions, and ignoring all directives that it does not
1516   understand.
1517</t>
1518<t>
1519   For example, consider a hypothetical new response directive called
1520   "community" that acts as a modifier to the private directive. We define
1521   this new directive to mean that, in addition to any private cache, any
1522   cache that is shared only by members of the community named within its
1523   value is allowed to cache the response. An origin server wishing to allow
1524   the UCI community to use an otherwise private response in their shared
1525   cache(s) could do so by including
1526</t>
1527<figure><artwork type="example">
1528  Cache-Control: private, community="UCI"
1529</artwork></figure>
1530<t>
1531   A cache seeing this header field will act correctly even if the cache does
1532   not understand the community cache-extension, since it will also see and
1533   understand the private directive and thus default to the safe behavior.
1534</t>
1535<t>
1536   A cache &MUST; ignore unrecognized cache directives; it is assumed that any
1537   cache directive likely to be unrecognized by an HTTP/1.1 cache will be
1538   combined with standard directives (or the response's default cacheability)
1539   such that the cache behavior will remain minimally correct even if the
1540   cache does not understand the extension(s).
1541</t>
1542<t>
1543   New extension directives ought to consider defining:
1544</t>
1545<t>
1546   <list style="symbols">
1547      <t>What it means for a directive to be specified multiple times,</t>
1548      <t>When the directive does not take an argument, what it means when an
1549      argument is present,</t>
1550      <t>When the directive requires an argument, what it means when it is
1551      missing.</t>
1552   </list>
1553</t>
1554<t>
1555   The HTTP Cache Directive Registry defines the name space for the cache
1556   directives.
1557</t>
1558<t>
1559   A registration &MUST; include the following fields:
1560   <list style="symbols">
1561      <t>Cache Directive Name</t>
1562      <t>Pointer to specification text</t>
1563   </list>
1564</t>
1565<t>
1566   Values to be added to this name space require IETF Review (see <xref
1567   target="RFC5226" x:fmt="," x:sec="4.1"/>).
1568</t>
1569<t>
1570   The registry itself is maintained at <eref
1571   target="http://www.iana.org/assignments/http-cache-directives"/>.
1572</t>
1573</section>
1574
1575</section>
1576
1577<section anchor="header.expires" title="Expires">
1578   <iref item="Expires header field" primary="true" x:for-anchor="" />
1579   <x:anchor-alias value="Expires"/>
1580<t>
1581   The "Expires" header field gives the date/time after which the
1582   response is considered stale. See <xref target="expiration.model" /> for
1583   further discussion of the freshness model.
1584</t>
1585<t>
1586   The presence of an Expires field does not imply that the original resource
1587   will change or cease to exist at, before, or after that time.
1588</t>
1589<t>
1590   The Expires value is an HTTP-date timestamp, as defined in &http-date;.
1591</t>
1592<figure><artwork type="abnf2616"><iref primary="true" item="Grammar" subitem="Expires"/>
1593  <x:ref>Expires</x:ref> = <x:ref>HTTP-date</x:ref>
1594</artwork></figure>
1595<figure>
1596  <preamble>For example</preamble>
1597<artwork type="example">
1598  Expires: Thu, 01 Dec 1994 16:00:00 GMT
1599</artwork></figure>
1600<t>
1601   A cache recipient &MUST; interpret invalid date formats, especially the
1602   value "0", as representing a time in the past (i.e., "already expired").
1603</t>
1604<t>
1605   If a response includes a <x:ref>Cache-Control</x:ref> field with
1606   the max-age directive (<xref target="cache-response-directive.max-age"/>),
1607   a recipient &MUST; ignore the Expires field.
1608   Likewise, if a response includes the s-maxage directive
1609   (<xref target="cache-response-directive.s-maxage" />), a shared cache
1610   recipient &MUST; ignore the Expires field. In both these cases, the value
1611   in Expires is only intended for recipients that have not yet implemented
1612   the Cache-Control field.
1613</t>
1614<t>
1615   An origin server without a clock &MUST-NOT; generate an Expires field
1616   unless its value represents a fixed time in the past (always expired)
1617   or its value has been associated with the resource by a system or user
1618   with a reliable clock.
1619</t>
1620<t>
1621   Historically, HTTP required the Expires field-value to be no more than a
1622   year in the future. While longer freshness lifetimes are no longer
1623   prohibited, extremely large values have been demonstrated to cause
1624   problems (e.g., clock overflows due to use of 32-bit integers for
1625   time values), and many caches will evict a response far sooner than
1626   that.
1627</t>
1628</section>
1629
1630<section anchor="header.pragma" title="Pragma">
1631   <iref item="Pragma header field" primary="true" x:for-anchor="" />
1632   <x:anchor-alias value="extension-pragma"/>
1633   <x:anchor-alias value="Pragma"/>
1634   <x:anchor-alias value="pragma-directive"/>
1635<t>
1636   The "Pragma" header field allows backwards compatibility with HTTP/1.0
1637   caches, so that clients can specify a "no-cache" request that they will
1638   understand (as <x:ref>Cache-Control</x:ref> was not defined until HTTP/1.1).
1639   When the Cache-Control header field is also present and understood in a
1640   request, Pragma is ignored.
1641</t>
1642<t>
1643   In HTTP/1.0, Pragma was defined as an extensible field for
1644   implementation-specified directives for recipients. This specification
1645   deprecates such extensions to improve interoperability.
1646</t>
1647<figure><artwork type="abnf2616"><iref primary="true" item="Grammar" subitem="Pragma"/><iref primary="true" item="Grammar" subitem="pragma-directive"/><iref primary="true" item="Grammar" subitem="extension-pragma"/>
1648  <x:ref>Pragma</x:ref>           = 1#<x:ref>pragma-directive</x:ref>
1649  <x:ref>pragma-directive</x:ref> = "no-cache" / <x:ref>extension-pragma</x:ref>
1650  <x:ref>extension-pragma</x:ref> = <x:ref>token</x:ref> [ "=" ( <x:ref>token</x:ref> / <x:ref>quoted-string</x:ref> ) ]
1651</artwork></figure>
1652<t>
1653   When the <x:ref>Cache-Control</x:ref> header field is not present in a
1654   request, the no-cache request pragma-directive &MUST; have the same effect
1655   on caches as if "Cache-Control: no-cache" were present (see <xref
1656   target="cache-request-directive" />).
1657</t>
1658<t>
1659   When sending a no-cache request, a client ought to include both the pragma
1660   and cache-control directives, unless Cache-Control: no-cache is
1661   purposefully omitted to target other <x:ref>Cache-Control</x:ref> response
1662   directives at HTTP/1.1 caches. For example:
1663</t>
1664<figure>
1665<artwork type="message/http; msgtype=&#34;response&#34;" x:indent-with="  ">
1666GET / HTTP/1.1
1667Host: www.example.com
1668Cache-Control: max-age=30
1669Pragma: no-cache
1670
1671</artwork>
1672</figure>
1673<t>
1674   will constrain HTTP/1.1 caches to serve a response no older than 30
1675   seconds, while precluding implementations that do not understand
1676   <x:ref>Cache-Control</x:ref> from serving a cached response.
1677</t>
1678<x:note>
1679   <t>
1680      &Note; Because the meaning of "Pragma: no-cache" in responses is not
1681      specified, it does not provide a reliable replacement for
1682      "Cache-Control: no-cache" in them.
1683   </t>
1684</x:note>
1685</section>
1686
1687<section anchor="header.warning" title="Warning">
1688   <iref item="Warning header field" primary="true" x:for-anchor="" />
1689   <x:anchor-alias value="Warning"/>
1690   <x:anchor-alias value="warning-value"/>
1691   <x:anchor-alias value="warn-agent"/>
1692   <x:anchor-alias value="warn-code"/>
1693   <x:anchor-alias value="warn-date"/>
1694   <x:anchor-alias value="warn-text"/>
1695<t>
1696   The "Warning" header field is used to carry additional information
1697   about the status or transformation of a message that might not be reflected
1698   in the message. This information is typically used to warn about possible
1699   incorrectness introduced by caching operations or transformations applied
1700   to the payload of the message.
1701</t>
1702<t>
1703   Warnings can be used for other purposes, both cache-related and otherwise.
1704   The use of a warning, rather than an error status code, distinguishes these
1705   responses from true failures.
1706</t>
1707<t>
1708   Warning header fields can in general be applied to any message, however some
1709   warn-codes are specific to caches and can only be applied to response
1710   messages.
1711</t>
1712<figure><artwork type="abnf2616"><iref primary="true" item="Grammar" subitem="Warning"/><iref primary="true" item="Grammar" subitem="warning-value"/><iref primary="true" item="Grammar" subitem="warn-code"/><iref primary="true" item="Grammar" subitem="warn-agent"/><iref primary="true" item="Grammar" subitem="warn-text"/><iref primary="true" item="Grammar" subitem="warn-date"/>
1713  <x:ref>Warning</x:ref>       = 1#<x:ref>warning-value</x:ref>
1714 
1715  <x:ref>warning-value</x:ref> = <x:ref>warn-code</x:ref> <x:ref>SP</x:ref> <x:ref>warn-agent</x:ref> <x:ref>SP</x:ref> <x:ref>warn-text</x:ref>
1716                                        [<x:ref>SP</x:ref> <x:ref>warn-date</x:ref>]
1717 
1718  <x:ref>warn-code</x:ref>  = 3<x:ref>DIGIT</x:ref>
1719  <x:ref>warn-agent</x:ref> = ( <x:ref>uri-host</x:ref> [ ":" <x:ref>port</x:ref> ] ) / <x:ref>pseudonym</x:ref>
1720                  ; the name or pseudonym of the server adding
1721                  ; the Warning header field, for use in debugging
1722  <x:ref>warn-text</x:ref>  = <x:ref>quoted-string</x:ref>
1723  <x:ref>warn-date</x:ref>  = <x:ref>DQUOTE</x:ref> <x:ref>HTTP-date</x:ref> <x:ref>DQUOTE</x:ref>
1724</artwork></figure>
1725<t>
1726   Multiple warnings can be attached to a response (either by the origin
1727   server or by a cache), including multiple warnings with the same code
1728   number, only differing in warn-text.
1729</t>
1730<t>
1731   When this occurs, the user agent &SHOULD; inform the user of as many of
1732   them as possible, in the order that they appear in the response.
1733</t>
1734<t>
1735   Systems that generate multiple Warning header fields are encouraged to
1736   order them with this user agent behavior in mind. New Warning header fields
1737   are added after any existing Warning header fields.
1738</t>
1739<t>
1740   Warnings are assigned three digit warn-codes. The first digit indicates
1741   whether the Warning is required to be deleted from a stored response after
1742   validation:
1743   <list style="symbols">
1744      <t>1xx Warnings describe the freshness or validation status of the
1745      response, and so &MUST; be deleted by a cache after validation. They can
1746      only be generated by a cache when validating a cached entry, and
1747      &MUST-NOT; be generated in any other situation.</t>
1748      <t>2xx Warnings describe some aspect of the representation that is not
1749      rectified by a validation (for example, a lossy compression of the
1750      representation) and &MUST-NOT; be deleted by a cache after validation,
1751      unless a full response is sent, in which case they &MUST; be.</t>
1752   </list>
1753</t>
1754<t>
1755   If an implementation sends a message with one or more Warning header fields
1756   to a receiver whose version is HTTP/1.0 or lower, then the sender &MUST;
1757   include in each warning-value a warn-date that matches the
1758   <x:ref>Date</x:ref> header field in the message.
1759</t>
1760<t>
1761   If a system receives a message with a warning-value that includes a
1762   warn-date, and that warn-date is different from the <x:ref>Date</x:ref>
1763   value in the response, then that warning-value &MUST; be deleted from the
1764   message before storing, forwarding, or using it. (preventing the
1765   consequences of naive caching of Warning header fields.) If all of the
1766   warning-values are deleted for this reason, the Warning header field &MUST;
1767   be deleted as well.
1768</t>
1769<t>
1770   The following warn-codes are defined by this specification, each with a
1771   recommended warn-text in English, and a description of its meaning.
1772</t>
1773
1774<section title="110 Response is Stale" anchor="warn.110">
1775  <iref primary="true" item="110 Response is Stale (warn code)" x:for-anchor=""/>
1776<t>
1777   A cache &SHOULD; generate this whenever the sent response is stale.
1778</t>
1779</section>
1780
1781<section title="111 Revalidation Failed" anchor="warn.111">
1782  <iref primary="true" item="111 Revalidation Failed (warn code)" x:for-anchor=""/>
1783<t>
1784   A cache &SHOULD; generate this when sending a stale response because an
1785   attempt to validate the response failed, due to an inability to reach
1786   the server.
1787</t>
1788</section>
1789
1790<section title="112 Disconnected Operation" anchor="warn.112">
1791  <iref primary="true" item="112 Disconnected Operation (warn code)" x:for-anchor=""/>
1792<t>
1793   A cache &SHOULD; generate this if it is intentionally disconnected from
1794   the rest of the network for a period of time.
1795</t>
1796</section>
1797
1798<section title="113 Heuristic Expiration" anchor="warn.113">
1799  <iref primary="true" item="113 Heuristic Expiration (warn code)" x:for-anchor=""/>
1800<t>
1801   A cache &SHOULD; generate this if it heuristically chose a freshness
1802   lifetime greater than 24 hours and the response's age is greater than 24
1803   hours.
1804</t>
1805</section>
1806
1807<section title="199 Miscellaneous Warning" anchor="warn.199">
1808  <iref primary="true" item="199 Miscellaneous Warning (warn code)" x:for-anchor=""/>
1809<t>
1810   The warning text can include arbitrary information to be presented to
1811   a human user, or logged. A system receiving this warning &MUST-NOT; take
1812   any automated action, besides presenting the warning to the user.
1813</t>
1814</section>
1815
1816<section title="214 Transformation Applied" anchor="warn.214">
1817  <iref primary="true" item="214 Transformation Applied (warn code)" x:for-anchor=""/>
1818<t>
1819   &MUST; be added by a proxy if it applies any transformation to the
1820   representation, such as changing the content-coding, media-type, or
1821   modifying the representation data, unless this Warning code already appears
1822   in the response.
1823</t>
1824</section>
1825
1826<section title="299 Miscellaneous Persistent Warning" anchor="warn.299">
1827  <iref primary="true" item="299 Miscellaneous Persistent Warning (warn code)" x:for-anchor=""/>
1828<t>
1829   The warning text can include arbitrary information to be presented to
1830   a human user, or logged. A system receiving this warning &MUST-NOT; take
1831   any automated action.
1832</t>
1833</section>
1834
1835<section title="Warn Code Extensions" anchor="warn.code.extensions">
1836<t>
1837   The HTTP Warn Code Registry defines the name space for warn codes.
1838</t>
1839<t>
1840   A registration &MUST; include the following fields:
1841   <list style="symbols">
1842      <t>Warn Code (3 digits)</t>
1843      <t>Short Description</t>
1844      <t>Pointer to specification text</t>
1845   </list>
1846</t>
1847<t>
1848   Values to be added to this name space require IETF Review (see <xref
1849   target="RFC5226" x:fmt="," x:sec="4.1"/>).
1850</t>
1851<t>
1852   The registry itself is maintained at <eref
1853   target="http://www.iana.org/assignments/http-warn-codes"/>.
1854</t>
1855</section>
1856</section>
1857</section>
1858
1859<section anchor="history.lists" title="History Lists">
1860<t>
1861   User agents often have history mechanisms, such as "Back" buttons and
1862   history lists, that can be used to redisplay a representation retrieved
1863   earlier in a session.
1864</t>
1865<t>
1866   The freshness model (<xref target="expiration.model"/>) does not
1867   necessarily apply to history mechanisms. I.e., a history mechanism can
1868   display a previous representation even if it has expired.
1869</t>
1870<t>
1871   This does not prohibit the history mechanism from telling the user that a
1872   view might be stale, or from honoring cache directives (e.g.,
1873   Cache-Control: no-store).
1874</t>
1875</section>
1876
1877
1878<section anchor="IANA.considerations" title="IANA Considerations">
1879
1880<section title="Cache Directive Registry"
1881   anchor="cache.directive.registration">
1882<t>
1883   The registration procedure for HTTP Cache Directives is defined by <xref
1884   target="cache.control.extensions"/> of this document.
1885</t>
1886<t>
1887   The HTTP Cache Directive Registry shall be created at <eref
1888   target="http://www.iana.org/assignments/http-cache-directives"/> and be
1889   populated with the registrations below:
1890</t>
1891<?BEGININC p6-cache.cache-directives ?>
1892<!--AUTOGENERATED FROM extract-cache-directives-defs.xslt, do not edit manually-->
1893<texttable xmlns:my="#my" align="left" suppress-title="true"
1894           anchor="iana.cache.directive.registration.table">
1895   <ttcol>Cache Directive</ttcol>
1896   <ttcol>Reference</ttcol>
1897
1898   <c>max-age</c>
1899   <c>
1900      <xref target="cache-request-directive.max-age"/>, <xref target="cache-response-directive.max-age"/>
1901   </c>
1902   <c>max-stale</c>
1903   <c>
1904      <xref target="cache-request-directive.max-stale"/>
1905   </c>
1906   <c>min-fresh</c>
1907   <c>
1908      <xref target="cache-request-directive.min-fresh"/>
1909   </c>
1910   <c>must-revalidate</c>
1911   <c>
1912      <xref target="cache-response-directive.must-revalidate"/>
1913   </c>
1914   <c>no-cache</c>
1915   <c>
1916      <xref target="cache-request-directive.no-cache"/>, <xref target="cache-response-directive.no-cache"/>
1917   </c>
1918   <c>no-store</c>
1919   <c>
1920      <xref target="cache-request-directive.no-store"/>, <xref target="cache-response-directive.no-store"/>
1921   </c>
1922   <c>no-transform</c>
1923   <c>
1924      <xref target="cache-request-directive.no-transform"/>, <xref target="cache-response-directive.no-transform"/>
1925   </c>
1926   <c>only-if-cached</c>
1927   <c>
1928      <xref target="cache-request-directive.only-if-cached"/>
1929   </c>
1930   <c>private</c>
1931   <c>
1932      <xref target="cache-response-directive.private"/>
1933   </c>
1934   <c>proxy-revalidate</c>
1935   <c>
1936      <xref target="cache-response-directive.proxy-revalidate"/>
1937   </c>
1938   <c>public</c>
1939   <c>
1940      <xref target="cache-response-directive.public"/>
1941   </c>
1942   <c>s-maxage</c>
1943   <c>
1944      <xref target="cache-response-directive.s-maxage"/>
1945   </c>
1946   <c>stale-if-error</c>
1947   <c>
1948      <xref xmlns:x="http://purl.org/net/xml2rfc/ext" target="RFC5861" x:fmt="," x:sec="4"/>
1949   </c>
1950   <c>stale-while-revalidate</c>
1951   <c>
1952      <xref xmlns:x="http://purl.org/net/xml2rfc/ext" target="RFC5861" x:fmt="," x:sec="3"/>
1953   </c>
1954</texttable>
1955<!--(END)-->
1956<?ENDINC p6-cache.cache-directives ?>
1957</section>
1958
1959<section title="Warn Code Registry"
1960   anchor="warn.code.registration">
1961<t>
1962   The registration procedure for HTTP Warn Codes is defined by <xref
1963   target="warn.code.extensions"/> of this document.
1964</t>
1965<t>
1966   The HTTP Warn Code Registry shall be created at <eref
1967   target="http://www.iana.org/assignments/http-cache-directives"/> and be
1968   populated with the registrations below:
1969</t>
1970<?BEGININC p6-cache.iana-warn-codes ?>
1971<!--AUTOGENERATED FROM extract-warn-code-defs.xslt, do not edit manually-->
1972<texttable align="left" suppress-title="true" anchor="iana.warn.code.registration.table">
1973   <ttcol>Warn Code</ttcol>
1974   <ttcol>Short Description</ttcol>
1975   <ttcol>Reference</ttcol>
1976   <c>110</c>
1977   <c>Response is Stale</c>
1978   <c>
1979      <xref target="warn.110"/>
1980   </c>
1981   <c>111</c>
1982   <c>Revalidation Failed</c>
1983   <c>
1984      <xref target="warn.111"/>
1985   </c>
1986   <c>112</c>
1987   <c>Disconnected Operation</c>
1988   <c>
1989      <xref target="warn.112"/>
1990   </c>
1991   <c>113</c>
1992   <c>Heuristic Expiration</c>
1993   <c>
1994      <xref target="warn.113"/>
1995   </c>
1996   <c>199</c>
1997   <c>Miscellaneous Warning</c>
1998   <c>
1999      <xref target="warn.199"/>
2000   </c>
2001   <c>214</c>
2002   <c>Transformation Applied</c>
2003   <c>
2004      <xref target="warn.214"/>
2005   </c>
2006   <c>299</c>
2007   <c>Miscellaneous Persistent Warning</c>
2008   <c>
2009      <xref target="warn.299"/>
2010   </c>
2011</texttable>
2012<!--(END)-->
2013<?ENDINC p6-cache.iana-warn-codes ?>
2014</section>
2015
2016<section title="Header Field Registration" anchor="header.field.registration">
2017<t>
2018  The Message Header Field Registry located at <eref 
2019  target="http://www.iana.org/assignments/message-headers/message-header-index.html" />
2020  shall be updated with the permanent registrations below (see <xref target="BCP90" />):
2021</t>
2022<?BEGININC p6-cache.iana-headers ?>
2023<!--AUTOGENERATED FROM extract-header-defs.xslt, do not edit manually-->
2024<texttable align="left" suppress-title="true" anchor="iana.header.registration.table">
2025   <ttcol>Header Field Name</ttcol>
2026   <ttcol>Protocol</ttcol>
2027   <ttcol>Status</ttcol>
2028   <ttcol>Reference</ttcol>
2029
2030   <c>Age</c>
2031   <c>http</c>
2032   <c>standard</c>
2033   <c>
2034      <xref target="header.age"/>
2035   </c>
2036   <c>Cache-Control</c>
2037   <c>http</c>
2038   <c>standard</c>
2039   <c>
2040      <xref target="header.cache-control"/>
2041   </c>
2042   <c>Expires</c>
2043   <c>http</c>
2044   <c>standard</c>
2045   <c>
2046      <xref target="header.expires"/>
2047   </c>
2048   <c>Pragma</c>
2049   <c>http</c>
2050   <c>standard</c>
2051   <c>
2052      <xref target="header.pragma"/>
2053   </c>
2054   <c>Warning</c>
2055   <c>http</c>
2056   <c>standard</c>
2057   <c>
2058      <xref target="header.warning"/>
2059   </c>
2060</texttable>
2061<!--(END)-->
2062<?ENDINC p6-cache.iana-headers ?>
2063<t>
2064   The change controller is: "IETF (iesg@ietf.org) - Internet Engineering Task
2065   Force".
2066</t>
2067</section>
2068</section>
2069
2070<section anchor="security.considerations" title="Security Considerations">
2071<t>
2072   This section is meant to inform developers, information providers, and
2073   users of known security concerns specific to HTTP/1.1 caching.
2074   More general security considerations are addressed in HTTP messaging
2075   &messaging; and semantics &semantics;.
2076</t>
2077<t>
2078   Caches expose additional potential vulnerabilities, since the contents of
2079   the cache represent an attractive target for malicious exploitation.
2080   Because cache contents persist after an HTTP request is complete, an attack
2081   on the cache can reveal information long after a user believes that the
2082   information has been removed from the network. Therefore, cache contents
2083   need to be protected as sensitive information.
2084</t>
2085<t>
2086   Furthermore, the very use of a cache can bring about privacy concerns. For
2087   example, if two users share a cache, and the first one browses to a site,
2088   the second may be able to detect that the other has been to that site,
2089   because the resources from it load more quickly, thanks to the cache.
2090</t>
2091<t>
2092   Implementation flaws might allow attackers to insert content into a cache
2093   ("cache poisoning"), leading to compromise of clients that trust that
2094   content. Because of their nature, these attacks are difficult to mitigate.
2095</t>
2096<t>
2097   Likewise, implementation flaws (as well as misunderstanding of cache
2098   operation) might lead to caching of sensitive information (e.g.,
2099   authentication credentials) that is thought to be private, exposing it to
2100   unauthorized parties.
2101</t>
2102<t>
2103   Note that the Set-Cookie response header <xref target="RFC6265"/> does not
2104   inhibit caching; a cacheable response with a Set-Cookie header can be (and
2105   often is) used to satisfy subsequent requests to caches. Servers who wish
2106   to control caching of these responses are encouraged to emit appropriate
2107   Cache-Control response headers.
2108</t>
2109
2110</section>
2111
2112<section title="Acknowledgments" anchor="acks">
2113<t>
2114  See &acks;.
2115</t>
2116</section>
2117
2118</middle>
2119
2120<back>
2121<references title="Normative References">
2122
2123  <reference anchor="Part1">
2124    <front>
2125      <title>Hypertext Transfer Protocol (HTTP/1.1): Message Syntax and Routing</title>
2126      <author fullname="Roy T. Fielding" initials="R." role="editor" surname="Fielding">
2127        <organization abbrev="Adobe">Adobe Systems Incorporated</organization>
2128        <address><email>fielding@gbiv.com</email></address>
2129      </author>
2130      <author fullname="Julian F. Reschke" initials="J. F." role="editor" surname="Reschke">
2131        <organization abbrev="greenbytes">greenbytes GmbH</organization>
2132        <address><email>julian.reschke@greenbytes.de</email></address>
2133      </author>
2134      <date month="&ID-MONTH;" year="&ID-YEAR;" />
2135    </front>
2136    <seriesInfo name="Internet-Draft" value="draft-ietf-httpbis-p1-messaging-&ID-VERSION;" />
2137    <x:source basename="p1-messaging" href="p1-messaging.xml">
2138      <x:defines>Content-Length</x:defines>
2139      <x:defines>Via</x:defines>
2140    </x:source>
2141  </reference>
2142
2143  <reference anchor="Part2">
2144    <front>
2145      <title>Hypertext Transfer Protocol (HTTP/1.1): Semantics and Content</title>
2146      <author fullname="Roy T. Fielding" initials="R." role="editor" surname="Fielding">
2147        <organization abbrev="Adobe">Adobe Systems Incorporated</organization>
2148        <address><email>fielding@gbiv.com</email></address>
2149      </author>
2150      <author fullname="Julian F. Reschke" initials="J. F." role="editor" surname="Reschke">
2151        <organization abbrev="greenbytes">greenbytes GmbH</organization>
2152        <address><email>julian.reschke@greenbytes.de</email></address>
2153      </author>
2154      <date month="&ID-MONTH;" year="&ID-YEAR;" />
2155    </front>
2156    <seriesInfo name="Internet-Draft" value="draft-ietf-httpbis-p2-semantics-&ID-VERSION;" />
2157    <x:source basename="p2-semantics" href="p2-semantics.xml">
2158      <x:defines>2xx (Successful)</x:defines>
2159      <x:defines>200 (OK)</x:defines>
2160      <x:defines>203 (Non-Authoritative Information)</x:defines>
2161      <x:defines>3xx (Redirection)</x:defines>
2162      <x:defines>300 (Multiple Choices)</x:defines>
2163      <x:defines>301 (Moved Permanently)</x:defines>
2164      <x:defines>404 (Not Found)</x:defines>
2165      <x:defines>410 (Gone)</x:defines>
2166      <x:defines>5xx (Server Error)</x:defines>
2167      <x:defines>504 (Gateway Timeout)</x:defines>
2168      <x:defines>Content-Encoding</x:defines>
2169      <x:defines>Content-Location</x:defines>
2170      <x:defines>Content-Type</x:defines>
2171      <x:defines>Date</x:defines>
2172      <x:defines>Location</x:defines>
2173      <x:defines>Vary</x:defines>
2174    </x:source>
2175  </reference>
2176
2177  <reference anchor="Part4">
2178    <front>
2179      <title>Hypertext Transfer Protocol (HTTP/1.1): Conditional Requests</title>
2180      <author fullname="Roy T. Fielding" initials="R." role="editor" surname="Fielding">
2181        <organization abbrev="Adobe">Adobe Systems Incorporated</organization>
2182        <address><email>fielding@gbiv.com</email></address>
2183      </author>
2184      <author fullname="Julian F. Reschke" initials="J. F." role="editor" surname="Reschke">
2185        <organization abbrev="greenbytes">greenbytes GmbH</organization>
2186        <address><email>julian.reschke@greenbytes.de</email></address>
2187      </author>
2188      <date month="&ID-MONTH;" year="&ID-YEAR;" />
2189    </front>
2190    <seriesInfo name="Internet-Draft" value="draft-ietf-httpbis-p4-conditional-&ID-VERSION;" />
2191    <x:source basename="p4-conditional" href="p4-conditional.xml">
2192      <x:defines>304</x:defines>
2193      <x:defines>304 (Not Modified)</x:defines>
2194      <x:defines>ETag</x:defines>
2195      <x:defines>If-Modified-Since</x:defines>
2196      <x:defines>If-None-Match</x:defines>
2197      <x:defines>Last-Modified</x:defines>
2198    </x:source>
2199  </reference>
2200
2201  <reference anchor="Part5">
2202    <front>
2203      <title>Hypertext Transfer Protocol (HTTP/1.1): Range Requests</title>
2204      <author fullname="Roy T. Fielding" initials="R." role="editor" surname="Fielding">
2205        <organization abbrev="Adobe">Adobe Systems Incorporated</organization>
2206        <address><email>fielding@gbiv.com</email></address>
2207      </author>
2208      <author fullname="Yves Lafon" initials="Y." role="editor" surname="Lafon">
2209        <organization abbrev="W3C">World Wide Web Consortium</organization>
2210        <address><email>ylafon@w3.org</email></address>
2211      </author>
2212      <author fullname="Julian F. Reschke" initials="J. F." role="editor" surname="Reschke">
2213        <organization abbrev="greenbytes">greenbytes GmbH</organization>
2214        <address><email>julian.reschke@greenbytes.de</email></address>
2215      </author>
2216      <date month="&ID-MONTH;" year="&ID-YEAR;" />
2217    </front>
2218    <seriesInfo name="Internet-Draft" value="draft-ietf-httpbis-p5-range-&ID-VERSION;" />
2219    <x:source basename="p5-range" href="p5-range.xml">
2220      <x:defines>206 (Partial Content)</x:defines>
2221      <x:defines>Content-Range</x:defines>
2222      <x:defines>Range</x:defines>
2223    </x:source>
2224  </reference>
2225
2226  <reference anchor="Part7">
2227    <front>
2228      <title>Hypertext Transfer Protocol (HTTP/1.1): Authentication</title>
2229      <author fullname="Roy T. Fielding" initials="R." role="editor" surname="Fielding">
2230        <organization abbrev="Adobe">Adobe Systems Incorporated</organization>
2231        <address><email>fielding@gbiv.com</email></address>
2232      </author>
2233      <author fullname="Julian F. Reschke" initials="J. F." role="editor" surname="Reschke">
2234        <organization abbrev="greenbytes">greenbytes GmbH</organization>
2235        <address><email>julian.reschke@greenbytes.de</email></address>
2236      </author>
2237      <date month="&ID-MONTH;" year="&ID-YEAR;" />
2238    </front>
2239    <seriesInfo name="Internet-Draft" value="draft-ietf-httpbis-p7-auth-&ID-VERSION;" />
2240    <x:source basename="p7-auth" href="p7-auth.xml">
2241      <x:defines>Authorization</x:defines>
2242    </x:source>
2243  </reference>
2244
2245  <reference anchor="RFC2119">
2246    <front>
2247      <title>Key words for use in RFCs to Indicate Requirement Levels</title>
2248      <author fullname="Scott Bradner" initials="S." surname="Bradner">
2249        <organization>Harvard University</organization>
2250        <address><email>sob@harvard.edu</email></address>
2251      </author>
2252      <date month="March" year="1997" />
2253    </front>
2254    <seriesInfo name="BCP" value="14" />
2255    <seriesInfo name="RFC" value="2119" />
2256  </reference>
2257
2258  <reference anchor="RFC5234">
2259    <front>
2260      <title abbrev="ABNF for Syntax Specifications">Augmented BNF for Syntax Specifications: ABNF</title>
2261      <author initials="D." surname="Crocker" fullname="Dave Crocker" role="editor">
2262        <organization>Brandenburg InternetWorking</organization>
2263        <address>
2264          <email>dcrocker@bbiw.net</email>
2265        </address> 
2266      </author>
2267      <author initials="P." surname="Overell" fullname="Paul Overell">
2268        <organization>THUS plc.</organization>
2269        <address>
2270          <email>paul.overell@thus.net</email>
2271        </address>
2272      </author>
2273      <date month="January" year="2008"/>
2274    </front>
2275    <seriesInfo name="STD" value="68"/>
2276    <seriesInfo name="RFC" value="5234"/>
2277  </reference>
2278 
2279</references>
2280
2281<references title="Informative References">
2282
2283  <reference anchor="RFC1305">
2284    <front>
2285      <title>Network Time Protocol (Version 3) Specification, Implementation</title>
2286      <author fullname="David L. Mills" initials="D." surname="Mills">
2287        <organization>University of Delaware, Electrical Engineering Department</organization>
2288        <address><email>mills@udel.edu</email></address>
2289      </author>
2290      <date month="March" year="1992" />
2291    </front>
2292    <seriesInfo name="RFC" value="1305" />
2293  </reference>
2294
2295  <reference anchor="RFC2616">
2296    <front>
2297      <title>Hypertext Transfer Protocol -- HTTP/1.1</title>
2298      <author fullname="R. Fielding" initials="R." surname="Fielding">
2299        <organization>University of California, Irvine</organization>
2300        <address><email>fielding@ics.uci.edu</email></address>
2301      </author>
2302      <author fullname="J. Gettys" initials="J." surname="Gettys">
2303        <organization>W3C</organization>
2304        <address><email>jg@w3.org</email></address>
2305      </author>
2306      <author fullname="J. Mogul" initials="J." surname="Mogul">
2307        <organization>Compaq Computer Corporation</organization>
2308        <address><email>mogul@wrl.dec.com</email></address>
2309      </author>
2310      <author fullname="H. Frystyk" initials="H." surname="Frystyk">
2311        <organization>MIT Laboratory for Computer Science</organization>
2312        <address><email>frystyk@w3.org</email></address>
2313      </author>
2314      <author fullname="L. Masinter" initials="L." surname="Masinter">
2315        <organization>Xerox Corporation</organization>
2316        <address><email>masinter@parc.xerox.com</email></address>
2317      </author>
2318      <author fullname="P. Leach" initials="P." surname="Leach">
2319        <organization>Microsoft Corporation</organization>
2320        <address><email>paulle@microsoft.com</email></address>
2321      </author>
2322      <author fullname="T. Berners-Lee" initials="T." surname="Berners-Lee">
2323        <organization>W3C</organization>
2324        <address><email>timbl@w3.org</email></address>
2325      </author>
2326      <date month="June" year="1999" />
2327    </front>
2328    <seriesInfo name="RFC" value="2616" />
2329  </reference>
2330
2331  <reference anchor="BCP90">
2332    <front>
2333      <title>Registration Procedures for Message Header Fields</title>
2334      <author fullname="G. Klyne" initials="G." surname="Klyne">
2335        <organization>Nine by Nine</organization>
2336        <address><email>GK-IETF@ninebynine.org</email></address>
2337      </author>
2338      <author fullname="M. Nottingham" initials="M." surname="Nottingham">
2339        <organization>BEA Systems</organization>
2340        <address><email>mnot@pobox.com</email></address>
2341      </author>
2342      <author fullname="J. Mogul" initials="J." surname="Mogul">
2343        <organization>HP Labs</organization>
2344        <address><email>JeffMogul@acm.org</email></address>
2345      </author>
2346      <date month="September" year="2004" />
2347    </front>
2348    <seriesInfo name="BCP" value="90" />
2349    <seriesInfo name="RFC" value="3864" />
2350  </reference>
2351
2352  <reference anchor='RFC5226'>
2353    <front>
2354      <title>Guidelines for Writing an IANA Considerations Section in RFCs</title>
2355      <author initials='T.' surname='Narten' fullname='T. Narten'>
2356        <organization>IBM</organization>
2357        <address><email>narten@us.ibm.com</email></address>
2358      </author>
2359      <author initials='H.' surname='Alvestrand' fullname='H. Alvestrand'>
2360        <organization>Google</organization>
2361        <address><email>Harald@Alvestrand.no</email></address>
2362      </author>
2363      <date year='2008' month='May' />
2364    </front>
2365    <seriesInfo name='BCP' value='26' />
2366    <seriesInfo name='RFC' value='5226' />
2367  </reference>
2368
2369  <reference anchor='RFC5861'>
2370    <front>
2371      <title abbrev="HTTP stale controls">HTTP Cache-Control Extensions for Stale Content</title>
2372      <author initials="M." surname="Nottingham" fullname="Mark Nottingham">
2373        <organization>Yahoo! Inc.</organization>
2374        <address><email>mnot@yahoo-inc.com</email></address>
2375      </author>
2376      <date month="April" year="2010"/>
2377    </front>
2378    <seriesInfo name='RFC' value='5861' />
2379  </reference>
2380
2381  <reference anchor="RFC6265">
2382    <front>
2383      <title>HTTP State Management Mechanism</title>
2384      <author initials="A." surname="Barth" fullname="Adam Barth">
2385        <organization abbrev="U.C. Berkeley">
2386          University of California, Berkeley
2387        </organization>
2388        <address><email>abarth@eecs.berkeley.edu</email></address>
2389      </author>
2390      <date year="2011" month="April" />
2391    </front>
2392    <seriesInfo name="RFC" value="6265"/>
2393  </reference>
2394
2395</references>
2396
2397<section anchor="changes.from.rfc.2616" title="Changes from RFC 2616">
2398<t>
2399  Caching-related text has been substantially rewritten for clarity.
2400</t>
2401<t>
2402  The algorithm for calculating age is now less conservative.
2403  (<xref target="age.calculations"/>)
2404</t>
2405<t>
2406  Caches are now required to handle dates with timezones as if they're
2407  invalid, because it's not possible to accurately guess.
2408  (<xref target="age.calculations"/>)
2409</t>
2410<t>
2411  The <x:ref>Content-Location</x:ref> response header field is no longer used
2412  to determine the appropriate response to use when validating.
2413  (<xref target="validation.model" />)
2414</t>
2415<t>
2416  The algorithm for selecting a cached negotiated response to use has been
2417  clarified in several ways. In particular, it now explicitly allows
2418  header-specific canonicalization when processing selecting header fields.
2419  (<xref target="caching.negotiated.responses" />)
2420</t>
2421<t>
2422  Requirements regarding denial of service attack avoidance when performing
2423  invalidation have been clarified.
2424  (<xref target="invalidation.after.updates.or.deletions" />)
2425</t>
2426<t>
2427  Cache invalidation only occurs when a successful response is received.
2428  (<xref target="invalidation.after.updates.or.deletions" />)
2429</t>
2430<t>
2431  The conditions under which an authenticated response can be cached have been
2432  clarified.
2433  (<xref target="caching.authenticated.responses" />)
2434</t>
2435<t>
2436  The one-year limit on Expires header field values has been removed; instead,
2437  the reasoning for using a sensible value is given.
2438  (<xref target="header.expires" />)
2439</t>
2440<t>
2441  The Pragma header field is now only defined for backwards compatibility;
2442  future pragmas are deprecated.
2443  (<xref target="header.pragma" />)
2444</t>
2445<t>
2446  Cache directives are explicitly defined to be case-insensitive.
2447  (<xref target="header.cache-control" />)
2448</t>
2449<t>
2450  Handling of multiple instances of cache directives when only one is
2451  expected is now defined.
2452  (<xref target="header.cache-control" />)
2453</t>
2454<t>
2455  The qualified forms of the private and no-cache cache directives are noted
2456  to not be widely implemented; e.g., "private=foo" is interpreted by many
2457  caches as simply "private". Additionally, the meaning of the qualified
2458  form of no-cache has been clarified.
2459  (<xref target="cache-response-directive" />)
2460</t>
2461<t>
2462  The "no-store" cache request directive doesn't apply to responses; i.e.,
2463  a cache can satisfy a request with no-store on it, and does not invalidate
2464  it.
2465  (<xref target="cache-request-directive.no-store" />)
2466</t>
2467<t>
2468  The meaning of the "public" cache response directive has been refined to
2469  be less vague.
2470  (<xref target="cache-response-directive.public" />)
2471</t>
2472<t>
2473  The "no-cache" response cache directive's meaning has been clarified.
2474  (<xref target="cache-response-directive.no-cache" />)
2475</t>
2476<t>
2477  New status codes can now define that caches are allowed to use heuristic
2478  freshness with them.
2479  (<xref target="heuristic.freshness" />)
2480</t>
2481<t>
2482  Caches are now allow to calculate heuristic freshness for URLs with query
2483  components.
2484  (<xref target="heuristic.freshness" />)
2485</t>
2486<t>
2487  Some requirements regarding production of the <x:ref>Warning</x:ref>
2488  header have been relaxed, as it is not widely implemented.
2489  (<xref target="header.warning" />)
2490</t>
2491<t>
2492  The <x:ref>Warning</x:ref> header field no longer uses RFC 2047 encoding,
2493  nor allows multiple languages, as these aspects were not implemented.
2494  (<xref target="header.warning" />)
2495</t>
2496<t>
2497  This specification introduces the Cache Directive and Warn Code Registries,
2498  and defines considerations for new cache directives.
2499  (<xref target="cache.control.extensions"/> and <xref target="warn.code.extensions"/>)
2500</t>
2501</section>
2502
2503<section title="Imported ABNF" anchor="imported.abnf">
2504   <x:anchor-alias value="ALPHA"/>
2505   <x:anchor-alias value="CR"/>
2506   <x:anchor-alias value="DIGIT"/>
2507   <x:anchor-alias value="DQUOTE"/>
2508   <x:anchor-alias value="LF"/>
2509   <x:anchor-alias value="OCTET"/>
2510   <x:anchor-alias value="SP"/>
2511   <x:anchor-alias value="VCHAR"/>
2512   <x:anchor-alias value="quoted-string"/>
2513   <x:anchor-alias value="token"/>
2514   <x:anchor-alias value="OWS"/>
2515   <x:anchor-alias value="field-name"/>
2516   <x:anchor-alias value="HTTP-date"/>
2517   <x:anchor-alias value="port"/>
2518   <x:anchor-alias value="pseudonym"/>
2519   <x:anchor-alias value="uri-host"/>
2520<t>
2521   The following core rules are included by reference, as defined in <xref
2522   target="RFC5234" x:fmt="of" x:sec="B.1"/>: ALPHA (letters), CR (carriage
2523   return), CRLF (CR LF), CTL (controls), DIGIT (decimal 0-9), DQUOTE (double
2524   quote), HEXDIG (hexadecimal 0-9/A-F/a-f), LF (line feed), OCTET (any 8-bit
2525   sequence of data), SP (space), and VCHAR (any visible US-ASCII character).
2526</t>
2527<t>
2528   The rules below are defined in <xref target="Part1"/>:
2529</t>
2530<figure><artwork type="abnf2616">
2531  <x:ref>OWS</x:ref>           = &lt;OWS, defined in &whitespace;&gt;
2532  <x:ref>field-name</x:ref>    = &lt;field-name, defined in &header-fields;&gt;
2533  <x:ref>quoted-string</x:ref> = &lt;quoted-string, defined in &field-components;&gt;
2534  <x:ref>token</x:ref>         = &lt;token, defined in &field-components;&gt;
2535
2536  <x:ref>port</x:ref>          = &lt;port, defined in &uri;&gt;
2537  <x:ref>pseudonym</x:ref>     = &lt;pseudonym, defined in &header-via;&gt;
2538  <x:ref>uri-host</x:ref>      = &lt;uri-host, defined in &uri;&gt;
2539</artwork></figure>
2540<t>
2541   The rules below are defined in other parts:
2542</t>
2543<figure><artwork type="abnf2616">
2544  <x:ref>HTTP-date</x:ref>     = &lt;HTTP-date, defined in &http-date;&gt;
2545</artwork></figure>
2546</section>
2547
2548<?BEGININC p6-cache.abnf-appendix ?>
2549<section xmlns:x="http://purl.org/net/xml2rfc/ext" title="Collected ABNF" anchor="collected.abnf">
2550<figure>
2551<artwork type="abnf" name="p6-cache.parsed-abnf">
2552<x:ref>Age</x:ref> = delta-seconds
2553
2554<x:ref>Cache-Control</x:ref> = *( "," OWS ) cache-directive *( OWS "," [ OWS
2555 cache-directive ] )
2556
2557<x:ref>Expires</x:ref> = HTTP-date
2558
2559<x:ref>HTTP-date</x:ref> = &lt;HTTP-date, defined in [Part2], Section 7.1.1.1&gt;
2560
2561<x:ref>OWS</x:ref> = &lt;OWS, defined in [Part1], Section 3.2.3&gt;
2562
2563<x:ref>Pragma</x:ref> = *( "," OWS ) pragma-directive *( OWS "," [ OWS
2564 pragma-directive ] )
2565
2566<x:ref>Warning</x:ref> = *( "," OWS ) warning-value *( OWS "," [ OWS warning-value ]
2567 )
2568
2569<x:ref>cache-directive</x:ref> = token [ "=" ( token / quoted-string ) ]
2570
2571<x:ref>delta-seconds</x:ref> = 1*DIGIT
2572
2573<x:ref>extension-pragma</x:ref> = token [ "=" ( token / quoted-string ) ]
2574
2575<x:ref>field-name</x:ref> = &lt;field-name, defined in [Part1], Section 3.2&gt;
2576
2577<x:ref>port</x:ref> = &lt;port, defined in [Part1], Section 2.7&gt;
2578<x:ref>pragma-directive</x:ref> = "no-cache" / extension-pragma
2579<x:ref>pseudonym</x:ref> = &lt;pseudonym, defined in [Part1], Section 5.7.1&gt;
2580
2581<x:ref>quoted-string</x:ref> = &lt;quoted-string, defined in [Part1], Section 3.2.6&gt;
2582
2583<x:ref>token</x:ref> = &lt;token, defined in [Part1], Section 3.2.6&gt;
2584
2585<x:ref>uri-host</x:ref> = &lt;uri-host, defined in [Part1], Section 2.7&gt;
2586
2587<x:ref>warn-agent</x:ref> = ( uri-host [ ":" port ] ) / pseudonym
2588<x:ref>warn-code</x:ref> = 3DIGIT
2589<x:ref>warn-date</x:ref> = DQUOTE HTTP-date DQUOTE
2590<x:ref>warn-text</x:ref> = quoted-string
2591<x:ref>warning-value</x:ref> = warn-code SP warn-agent SP warn-text [ SP warn-date
2592 ]
2593</artwork>
2594</figure>
2595</section>
2596<?ENDINC p6-cache.abnf-appendix ?>
2597
2598<section anchor="change.log" title="Change Log (to be removed by RFC Editor before publication)">
2599<t>
2600  Changes up to the first Working Group Last Call draft are summarized
2601  in <eref target="http://trac.tools.ietf.org/html/draft-ietf-httpbis-p6-cache-19#appendix-C"/>.
2602</t>
2603
2604<section title="Since draft-ietf-httpbis-p6-cache-19" anchor="changes.since.19">
2605<t>
2606  Closed issues:
2607  <list style="symbols">
2608    <t>
2609      <eref target="http://tools.ietf.org/wg/httpbis/trac/ticket/307"/>:
2610      "untangle Cache-Control ABNF"
2611    </t>
2612    <t>
2613      <eref target="http://tools.ietf.org/wg/httpbis/trac/ticket/353"/>:
2614      "Multiple values in Cache-Control header fields"
2615    </t>
2616    <t>
2617      <eref target="http://tools.ietf.org/wg/httpbis/trac/ticket/355"/>:
2618      "Case sensitivity of header fields in CC values"
2619    </t>
2620    <t>
2621      <eref target="http://tools.ietf.org/wg/httpbis/trac/ticket/356"/>:
2622      "Spurious 'MAYs'"
2623    </t>
2624    <t>
2625      <eref target="http://tools.ietf.org/wg/httpbis/trac/ticket/360"/>:
2626      "enhance considerations for new cache control directives"
2627    </t>
2628    <t>
2629      <eref target="http://tools.ietf.org/wg/httpbis/trac/ticket/361"/>:
2630      "ABNF requirements for recipients"
2631    </t>
2632    <t>
2633      <eref target="http://tools.ietf.org/wg/httpbis/trac/ticket/368"/>:
2634      "note introduction of new IANA registries as normative changes"
2635    </t>
2636    <t>
2637      <eref target="http://tools.ietf.org/wg/httpbis/trac/ticket/373"/>:
2638      "broken prose in description of 'Vary'"
2639    </t>
2640  </list>
2641</t>
2642</section>
2643
2644<section title="Since draft-ietf-httpbis-p6-cache-20" anchor="changes.since.20">
2645<t>
2646  Closed issues:
2647  <list style="symbols">
2648    <t>
2649      <eref target="http://tools.ietf.org/wg/httpbis/trac/ticket/375"/>:
2650      "'Most Conservative'"
2651    </t>
2652  </list>
2653</t>
2654<t>
2655  Other changes:
2656  <list style="symbols">
2657    <t>
2658      Conformance criteria and considerations regarding error handling are
2659      now defined in Part 1.
2660    </t>
2661    <t>
2662      Move definition of "Vary" header field into Part 2.
2663    </t>
2664    <t>
2665      Add security considerations with respect to cache poisoning and
2666      the "Set-Cookie" header field.
2667    </t>
2668  </list>
2669</t>
2670</section>
2671
2672<section title="Since draft-ietf-httpbis-p6-cache-21" anchor="changes.since.21">
2673<t>
2674  Closed issues:
2675  <list style="symbols">
2676    <t>
2677      <eref target="http://tools.ietf.org/wg/httpbis/trac/ticket/223"/>:
2678      "Allowing heuristic caching for new status codes"
2679    </t>
2680    <t>
2681      <eref target="http://tools.ietf.org/wg/httpbis/trac/ticket/406"/>:
2682      "304 without validator"
2683    </t>
2684    <t>
2685      <eref target="http://tools.ietf.org/wg/httpbis/trac/ticket/418"/>:
2686      "No-Transform"
2687    </t>
2688  </list>
2689</t>
2690</section>
2691
2692<section title="Since draft-ietf-httpbis-p6-cache-22" anchor="changes.since.22">
2693<t>
2694  None yet.
2695</t>
2696</section>
2697</section>
2698  </back>
2699</rfc>
Note: See TracBrowser for help on using the repository browser.