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

Last change on this file since 482 was 482, checked in by mnot@…, 11 years ago

shorten wordy text

  • Property svn:eol-style set to native
File size: 109.8 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 "March">
16  <!ENTITY ID-YEAR "2009">
17  <!ENTITY notation                    "<xref target='Part1' x:rel='#notation' xmlns:x='http://purl.org/net/xml2rfc/ext'/>">
18  <!ENTITY basic-rules                 "<xref target='Part1' x:rel='#basic.rules' xmlns:x='http://purl.org/net/xml2rfc/ext'/>">
19  <!ENTITY uri                         "<xref target='Part1' x:rel='#uri' xmlns:x='http://purl.org/net/xml2rfc/ext'/>">
20  <!ENTITY messaging                   "<xref target='Part1' xmlns:x='http://purl.org/net/xml2rfc/ext'/>">
21  <!ENTITY conditional                 "<xref target='Part4' xmlns:x='http://purl.org/net/xml2rfc/ext'/>">
22  <!ENTITY partial                     "<xref target='Part5' xmlns:x='http://purl.org/net/xml2rfc/ext'/>">
23  <!ENTITY combining-byte-ranges       "<xref target='Part5' x:rel='#combining.byte.ranges' xmlns:x='http://purl.org/net/xml2rfc/ext'/>">
24  <!ENTITY entity-length               "<xref target='Part3' x:rel='#entity.length' xmlns:x='http://purl.org/net/xml2rfc/ext'/>">
25  <!ENTITY full-date                   "<xref target='Part1' x:rel='#full.date' xmlns:x='http://purl.org/net/xml2rfc/ext'/>">
26  <!ENTITY header-authorization        "<xref target='Part7' x:rel='#header.authorization' xmlns:x='http://purl.org/net/xml2rfc/ext'/>">
27  <!ENTITY header-connection           "<xref target='Part1' x:rel='#header.connection' xmlns:x='http://purl.org/net/xml2rfc/ext'/>">
28  <!ENTITY header-date                 "<xref target='Part1' x:rel='#header.date' xmlns:x='http://purl.org/net/xml2rfc/ext'/>">
29  <!ENTITY header-via                  "<xref target='Part1' x:rel='#header.via' xmlns:x='http://purl.org/net/xml2rfc/ext'/>">
30  <!ENTITY header-last-modified        "<xref target='Part4' x:rel='#header.last-modified' xmlns:x='http://purl.org/net/xml2rfc/ext'/>">
31  <!ENTITY message-headers             "<xref target='Part1' x:rel='#message.headers' xmlns:x='http://purl.org/net/xml2rfc/ext'/>">
32  <!ENTITY message-length              "<xref target='Part1' x:rel='#message.length' xmlns:x='http://purl.org/net/xml2rfc/ext'/>">
33  <!ENTITY safe-methods                "<xref target='Part2' x:rel='#safe.methods' xmlns:x='http://purl.org/net/xml2rfc/ext'/>">
34  <!ENTITY server-driven-negotiation   "<xref target='Part3' x:rel='#server-driven.negotiation' xmlns:x='http://purl.org/net/xml2rfc/ext'/>">
35]>
36<?rfc toc="yes" ?>
37<?rfc symrefs="yes" ?>
38<?rfc sortrefs="yes" ?>
39<?rfc compact="yes"?>
40<?rfc subcompact="no" ?>
41<?rfc linkmailto="no" ?>
42<?rfc editing="no" ?>
43<?rfc comments="yes"?>
44<?rfc inline="yes"?>
45<?rfc-ext allow-markup-in-artwork="yes" ?>
46<?rfc-ext include-references-in-index="yes" ?>
47<?oxygen RNGSchema="../../rfc2629xslt/rfc2629-ext.rnc" type="compact"?>
48<rfc category="std" docName="draft-ietf-httpbis-p6-cache-&ID-VERSION;" ipr="pre5378Trust200902"
49  obsoletes="2616" x:maturity-level="draft" xmlns:x="http://purl.org/net/xml2rfc/ext">
50  <front>
51
52    <title abbrev="HTTP/1.1, Part 6">HTTP/1.1, part 6: Caching</title>
53
54    <author fullname="Roy T. Fielding" initials="R." role="editor" surname="Fielding">
55      <organization abbrev="Day Software">Day Software</organization>
56      <address>
57      <postal>
58        <street>23 Corporate Plaza DR, Suite 280</street>
59        <city>Newport Beach</city>
60        <region>CA</region>
61        <code>92660</code>
62        <country>USA</country>
63      </postal>
64      <phone>+1-949-706-5300</phone>
65      <facsimile>+1-949-706-5305</facsimile>
66      <email>fielding@gbiv.com</email>
67      <uri>http://roy.gbiv.com/</uri>
68    </address>
69    </author>
70
71    <author fullname="Jim Gettys" initials="J." surname="Gettys">
72      <organization>One Laptop per Child</organization>
73      <address>
74      <postal>
75        <street>21 Oak Knoll Road</street>
76        <city>Carlisle</city>
77        <region>MA</region>
78        <code>01741</code>
79        <country>USA</country>
80      </postal>
81      <email>jg@laptop.org</email>
82      <uri>http://www.laptop.org/</uri>
83    </address>
84    </author>
85
86    <author fullname="Jeffrey C. Mogul" initials="J." surname="Mogul">
87      <organization abbrev="HP">Hewlett-Packard Company</organization>
88      <address>
89      <postal>
90        <street>HP Labs, Large Scale Systems Group</street>
91        <street>1501 Page Mill Road, MS 1177</street>
92        <city>Palo Alto</city>
93        <region>CA</region>
94        <code>94304</code>
95        <country>USA</country>
96      </postal>
97      <email>JeffMogul@acm.org</email>
98    </address>
99    </author>
100
101    <author fullname="Henrik Frystyk Nielsen" initials="H." surname="Frystyk">
102      <organization abbrev="Microsoft">Microsoft Corporation</organization>
103      <address>
104      <postal>
105        <street>1 Microsoft Way</street>
106        <city>Redmond</city>
107        <region>WA</region>
108        <code>98052</code>
109        <country>USA</country>
110      </postal>
111      <email>henrikn@microsoft.com</email>
112    </address>
113    </author>
114
115    <author fullname="Larry Masinter" initials="L." surname="Masinter">
116      <organization abbrev="Adobe Systems">Adobe Systems, Incorporated</organization>
117      <address>
118      <postal>
119        <street>345 Park Ave</street>
120        <city>San Jose</city>
121        <region>CA</region>
122        <code>95110</code>
123        <country>USA</country>
124      </postal>
125      <email>LMM@acm.org</email>
126      <uri>http://larry.masinter.net/</uri>
127    </address>
128    </author>
129
130    <author fullname="Paul J. Leach" initials="P." surname="Leach">
131      <organization abbrev="Microsoft">Microsoft Corporation</organization>
132      <address>
133      <postal>
134        <street>1 Microsoft Way</street>
135        <city>Redmond</city>
136        <region>WA</region>
137        <code>98052</code>
138      </postal>
139      <email>paulle@microsoft.com</email>
140    </address>
141    </author>
142
143    <author fullname="Tim Berners-Lee" initials="T." surname="Berners-Lee">
144      <organization abbrev="W3C/MIT">World Wide Web Consortium</organization>
145      <address>
146      <postal>
147        <street>MIT Computer Science and Artificial Intelligence Laboratory</street>
148        <street>The Stata Center, Building 32</street>
149        <street>32 Vassar Street</street>
150        <city>Cambridge</city>
151        <region>MA</region>
152        <code>02139</code>
153        <country>USA</country>
154      </postal>
155      <email>timbl@w3.org</email>
156      <uri>http://www.w3.org/People/Berners-Lee/</uri>
157    </address>
158    </author>
159
160    <author fullname="Yves Lafon" initials="Y." role="editor" surname="Lafon">
161      <organization abbrev="W3C">World Wide Web Consortium</organization>
162      <address>
163      <postal>
164        <street>W3C / ERCIM</street>
165        <street>2004, rte des Lucioles</street>
166        <city>Sophia-Antipolis</city>
167        <region>AM</region>
168        <code>06902</code>
169        <country>France</country>
170      </postal>
171      <email>ylafon@w3.org</email>
172      <uri>http://www.raubacapeu.net/people/yves/</uri>
173    </address>
174    </author>
175
176    <author fullname="Julian F. Reschke" initials="J. F." role="editor" surname="Reschke">
177      <organization abbrev="greenbytes">greenbytes GmbH</organization>
178      <address>
179      <postal>
180        <street>Hafenweg 16</street>
181        <city>Muenster</city><region>NW</region><code>48155</code>
182        <country>Germany</country>
183      </postal>
184      <phone>+49 251 2807760</phone>   
185      <facsimile>+49 251 2807761</facsimile>   
186      <email>julian.reschke@greenbytes.de</email>       
187      <uri>http://greenbytes.de/tech/webdav/</uri>     
188    </address>
189    </author>
190
191    <date month="&ID-MONTH;" year="&ID-YEAR;" />
192    <workgroup>HTTPbis Working Group</workgroup>
193
194    <abstract>
195      <t>The Hypertext Transfer Protocol (HTTP) is an application-level protocol for distributed,
196        collaborative, hypermedia information systems. This document is Part 6 of the seven-part
197        specification that defines the protocol referred to as "HTTP/1.1" and, taken together,
198        obsoletes RFC 2616. Part 6 defines requirements on HTTP caches and the associated header
199        fields that control cache behavior or indicate cacheable response messages.</t>
200    </abstract>
201
202    <note title="Editorial Note (To be removed by RFC Editor)">
203      <t>Discussion of this draft should take place on the HTTPBIS working group mailing list
204        (ietf-http-wg@w3.org). The current issues list is at <eref
205          target="http://tools.ietf.org/wg/httpbis/trac/report/11" /> and related documents
206        (including fancy diffs) can be found at <eref target="http://tools.ietf.org/wg/httpbis/" />.</t>
207      <t>The changes in this draft are summarized in <xref target="changes.since.04" />.</t>
208    </note>
209  </front>
210  <middle>
211    <section anchor="caching" title="Introduction">
212      <t>HTTP is typically used for distributed information systems, where performance can be
213        improved by the use of response caches. This document defines aspects of HTTP/1.1 related to
214        caching and reusing response messages.</t>
215
216      <section anchor="intro.purpose" title="Purpose">
217        <iref item="cache" />
218        <t>An HTTP <x:dfn>cache</x:dfn> is a local store of response messages and the subsystem that
219          controls its message storage, retrieval, and deletion. A cache stores cacheable responses
220          in order to reduce the response time and network bandwidth consumption on future,
221          equivalent requests. Any client or server may include a cache, though a cache cannot be
222          used by a server that is acting as a tunnel.</t>
223        <t>Caching would be useless if it did not significantly improve performance. The goal of
224          caching in HTTP/1.1 is to reuse a prior response message to satisfy a current request. In
225          some cases, a stored response can be reused without the need for a network request,
226          reducing latency and network round-trips; a "freshness" mechanism is used for this purpose
227          (see <xref target="expiration.model" />). Even when a new request is required, it is often
228          possible to reuse all or parts of the payload of a prior response to satisfy the request,
229          thereby reducing network bandwidth usage; a "validation" mechanism is used for this
230          purpose (see <xref target="validation.model" />).</t>
231      </section>
232
233      <section anchor="intro.terminology" title="Terminology">
234        <t>This specification uses a number of terms to refer to the roles played by participants
235          in, and objects of, HTTP caching.</t>
236        <t>
237          <iref item="cacheable" />
238          <x:dfn>cacheable</x:dfn>
239          <list>
240            <t>A response is cacheable if a cache is allowed to store a copy of the response message
241              for use in answering subsequent requests. Even when a response is cacheable, there may
242              be additional constraints on whether a cache can use the cached copy to satisfy a
243              particular request.</t>
244          </list>
245        </t>
246        <t>
247          <iref item="explicit expiration time" />
248          <x:dfn>explicit expiration time</x:dfn>
249          <list>
250            <t>The time at which the origin server intends that an entity should no longer be
251              returned by a cache without further validation.</t>
252          </list>
253        </t>
254        <t>
255          <iref item="heuristic expiration time" />
256          <x:dfn>heuristic expiration time</x:dfn>
257          <list>
258            <t>An expiration time assigned by a cache when no explicit expiration time is
259            available.</t>
260          </list>
261        </t>
262        <t>
263          <iref item="age" />
264          <x:dfn>age</x:dfn>
265          <list>
266            <t>The age of a response is the time since it was sent by, or successfully validated
267              with, the origin server.</t>
268          </list>
269        </t>
270        <t>
271          <iref item="first-hand" />
272          <x:dfn>first-hand</x:dfn>
273          <list>
274            <t>A response is first-hand if the freshness model is not in use; i.e., its age is
275            0.</t>
276          </list>
277        </t>
278        <t>
279          <iref item="freshness lifetime" />
280          <x:dfn>freshness lifetime</x:dfn>
281          <list>
282            <t>The length of time between the generation of a response and its expiration time. </t>
283          </list>
284        </t>
285        <t>
286          <iref item="fresh" />
287          <x:dfn>fresh</x:dfn>
288          <list>
289            <t>A response is fresh if its age has not yet exceeded its freshness lifetime.</t>
290          </list>
291        </t>
292        <t>
293          <iref item="stale" />
294          <x:dfn>stale</x:dfn>
295          <list>
296            <t>A response is stale if its age has passed its freshness lifetime (either explicit or heuristic).</t>
297          </list>
298        </t>
299        <t>
300          <iref item="validator" />
301          <x:dfn>validator</x:dfn>
302          <list>
303            <t>A protocol element (e.g., an entity tag or a Last-Modified time) that is used to find
304              out whether a stored response is an equivalent copy of an entity.</t>
305          </list>
306        </t>
307        <t>
308          <iref item="validator" />
309          <x:dfn>shared cache</x:dfn>
310          <list>
311            <t>A cache that is accessible to more than one user. A non-shared cache is
312              dedicated to a single user.</t>
313          </list>
314        </t>
315      </section>
316
317
318      <section anchor="intro.requirements" title="Requirements">
319        <t>The key words "MUST", "MUST NOT", "REQUIRED", "SHALL", "SHALL NOT", "SHOULD", "SHOULD
320          NOT", "RECOMMENDED", "MAY", and "OPTIONAL" in this document are to be interpreted as
321          described in <xref target="RFC2119" />.</t>
322        <t>An implementation is not compliant if it fails to satisfy one or more of the &MUST;
323          or &REQUIRED; level requirements for the protocols it implements. An implementation
324          that satisfies all the &MUST; or &REQUIRED; level and all the &SHOULD; level
325          requirements for its protocols is said to be "unconditionally compliant"; one that
326          satisfies all the &MUST; level requirements but not all the &SHOULD; level
327          requirements for its protocols is said to be "conditionally compliant."</t>
328      </section>
329
330
331<section title="Syntax Notation" anchor="notation">
332  <x:anchor-alias value="ALPHA"/>
333  <x:anchor-alias value="CR"/>
334  <x:anchor-alias value="DIGIT"/>
335  <x:anchor-alias value="DQUOTE"/>
336  <x:anchor-alias value="LF"/>
337  <x:anchor-alias value="OCTET"/>
338  <x:anchor-alias value="SP"/>
339  <x:anchor-alias value="VCHAR"/>
340  <x:anchor-alias value="WSP"/>
341<t>
342  This specification uses the ABNF syntax defined in &notation;.
343  The following core rules are included by
344  reference, as defined in <xref target="RFC5234" x:fmt="," x:sec="B.1"/>:
345  ALPHA (letters), CR (carriage return), CRLF (CR LF), CTL (controls),
346  DIGIT (decimal 0-9), DQUOTE (double quote),
347  HEXDIG (hexadecimal 0-9/A-F/a-f), LF (line feed),
348  OCTET (any 8-bit sequence of data), SP (space),
349  VCHAR (any visible USASCII character),
350  and WSP (whitespace).
351</t>
352
353<section title="Core Rules" anchor="core.rules">
354  <x:anchor-alias value="quoted-string"/>
355  <x:anchor-alias value="token"/>
356  <x:anchor-alias value="OWS"/>
357<t>
358  The core rules below are defined in &basic-rules;:
359</t>
360<figure><artwork type="abnf2616">
361  <x:ref>quoted-string</x:ref> = &lt;quoted-string, defined in &basic-rules;&gt;
362  <x:ref>token</x:ref>         = &lt;token, defined in &basic-rules;&gt;
363  <x:ref>OWS</x:ref>           = &lt;OWS, defined in &basic-rules;&gt;
364</artwork></figure>
365</section>
366
367<section title="ABNF Rules defined in other Parts of the Specification" anchor="abnf.dependencies">
368  <x:anchor-alias value="field-name"/>
369  <x:anchor-alias value="HTTP-date"/>
370  <x:anchor-alias value="port"/>
371  <x:anchor-alias value="pseudonym"/>
372  <x:anchor-alias value="uri-host"/>
373<t>
374  The ABNF rules below are defined in other parts:
375</t>
376<figure><!--Part1--><artwork type="abnf2616">
377  <x:ref>field-name</x:ref>    = &lt;field-name, defined in &message-headers;&gt;
378  <x:ref>HTTP-date</x:ref>     = &lt;HTTP-date, defined in &full-date;&gt;
379  <x:ref>port</x:ref>          = &lt;port, defined in &uri;&gt;
380  <x:ref>pseudonym</x:ref>     = &lt;pseudonym, defined in &header-via;&gt; 
381  <x:ref>uri-host</x:ref>      = &lt;uri-host, defined in &uri;&gt;
382</artwork></figure>
383</section>
384
385</section>
386</section>
387
388    <section anchor="caching.overview" title="Cache Operation">
389
390      <section anchor="response.cacheability" title="Response Cacheability">
391        <t>A cache &MAY; store a response to any request, provided that: <list style="symbols">
392                <t>The request method is defined as being cacheable, and</t>
393            <t>the "no-store" cache directive (see <xref target="header.cache-control" />) does not
394              appear in request or response headers, and</t>
395            <t>the cache understands partial responses, if the response is partial or incomplete
396              (see <xref target="errors.or.incomplete.response.cache.behavior" />).</t>
397          </list>
398        </t>
399        <t>Note that in normal operation, most caches will not store a response that has neither a
400          cache validator nor an explicit expiration time, as such responses are not usually
401          useful to store. However, caches are not prohibited from storing such responses.</t>
402
403                <t>
404                        <cref>DISCUSS: A strict reading of 2616 is that a shared cache can store a private response,
405                        but never use it. I suspect that this may just be sloppiness in use of terminology, not intent;
406                        should this be disallowed? --mnot</cref>
407                </t>
408
409        <section anchor="errors.or.incomplete.response.cache.behavior"
410          title="Storing Incomplete Responses">
411          <t>A cache that receives an incomplete response (for example, with fewer bytes of data
412            than specified in a Content-Length header) &MAY; store the response. However, the
413            cache &MUST; treat this as a partial response &partial;. Partial responses
414            &MAY; be combined as described in &combining-byte-ranges;; the result might be a
415            full response or might still be partial. A cache &MUST-NOT; return a partial
416            response to a client without explicitly marking it as such using the 206 (Partial
417            Content) status code.</t>
418          <t>A cache that does not support the Range and Content-Range headers &MUST-NOT; store
419            incomplete or partial responses.</t>
420        </section>
421
422      </section>
423
424      <section anchor="constructing.responses.from.caches"
425        title="Constructing Responses from Caches">
426        <t>For a given request, a non-shared cache &MAY; return a stored response, provided
427          that: <list style="symbols">
428            <t>the presented target-URI and that of the stored response match (see
429              <cref>TBD</cref>), and</t>
430            <t>the request method associated with the stored response allows it to be
431              used for the presented request, and</t>
432            <t>selecting request-headers nominated by the stored response (if any) match those presented (see <xref
433                target="caching.negotiated.responses" />), and</t>
434            <t>the stored response is either:
435            <list style="symbols">
436                <t>fresh (see <xref target="expiration.model" />), or</t>
437                <t>allowed to be served stale (see <xref target="serving.stale.responses" />), or</t>
438                <t>successfully validated (see <xref target="validation.model" />).</t>
439            </list>, and</t>
440            <t>the presented request and stored response are free from directives that would prevent
441              its use (see <xref target="header.cache-control" /> and <xref target="header.pragma"
442             />).</t>
443          </list>
444        </t>
445        <t>A shared cache &MAY; return a stored response, provided that: <list style="symbols">
446            <t>the criteria for non-shared caches above are met (taking into account directives specific to shared
447              caches; see <xref target="header.cache-control" />), and</t>
448            <t>the stored response was not associated with an authenticated request (see
449              &header-authorization;), unless explicitly allowed (see <xref
450                target="header.cache-control" />).</t>
451          </list>
452        </t>
453        <t>All responses satisfied from cache include an appropriate Age header field; see
454            <xref target="header.age" />. <cref>DISCUSS: this currently includes successfully validated responses.</cref></t>
455        <t>All request methods other than GET and HEAD &MUST; be written through the cache to
456          the origin server. Note that such requests might invalidate already stored responses; see
457            <xref target="invalidation.after.updates.or.deletions" />.</t>
458        <t>Caches &SHOULD; use the most recent response (as determined by the Date header) when
459          more than one applicable response is stored. They &MAY; also send a request with
460          "Cache-Control: max-age=0" or "Cache-Control: no-cache" to disambiguate which response to
461          use.</t>
462        <t>
463          <cref>TODO: end-to-end and hop-by-hop headers, non-modifiable headers removed; re-spec in
464            p1</cref>
465        </t>
466      </section>
467
468
469
470
471      <section anchor="expiration.model" title="Freshness Model">
472
473        <t>When a response is "fresh" in the cache, it can be used to satisfy subsequent
474          requests without contacting the origin server, thereby improving efficiency.</t>
475        <t>This mechanism applies only to responses taken from a cache and not to first-hand responses.
476          It cannot be used to force a user agent to refresh its display or reload a resource; its
477          semantics apply only to caches. See <xref target="history.lists" /> for an explanation of
478          the difference between caches and history mechanisms.</t>
479        <t>The primary mechanism for avoiding requests is for an origin server to provide an
480          explicit expiration time in the future, using either the Expires header (<xref
481            target="header.expires" />) or the max-age response cache directive (<xref
482            target="cache-response-directive" />). Generally, origin servers will assign future
483          explicit expiration times to responses in the belief that the entity is not likely to
484          change in a semantically significant way before the expiration time is reached.</t>
485        <t>If an origin server wishes to force a cache to validate every request, it &MAY;
486          assign an explicit expiration time in the past. This means that the response is always
487          stale, so that caches should validate it before using it for subsequent requests. <cref>This wording may cause confusion, because the response may still be served stale.</cref></t>
488        <t>Since origin servers do not always provide explicit expiration times, HTTP caches may
489          assign heuristic expiration times when they are not specified, employing algorithms that
490          use other header values (such as the Last-Modified time) to estimate a plausible
491          expiration time. The HTTP/1.1 specification does not provide specific algorithms, but does
492          impose worst-case constraints on their results.</t>
493        <t>The calculation to determine if a response has expired is:</t>
494        <figure>
495          <artwork type="code">
496   response_is_fresh = (freshness_lifetime &gt; current_age)
497</artwork>
498        </figure>
499
500        <t>The freshness_lifetime is defined in <xref target="calculating.freshness.lifetime" />;
501          the current_age is defined in <xref target="age.calculations" />.</t>
502        <t>Additionally, clients may need to influence freshness calculation. They can do this using
503          several request cache directives, with the effect of either increasing or loosening
504          constraints on freshness. See <xref target="cache-request-directive" />.</t>
505        <t>
506          <cref>ISSUE: there are not requirements directly applying to cache-request-directives and
507            freshness.</cref>
508        </t>
509
510        <section anchor="calculating.freshness.lifetime" title="Calculating Freshness Lifetime">
511          <t>A cache can calculate the freshness lifetime (denoted as freshness_lifetime) of a
512            response by using the first match of: <list style="symbols">
513              <t>If the cache is shared and the s-maxage response cache directive (<xref
514                  target="cache-response-directive" />) is present, use its value, or</t>
515              <t>If the max-age response cache directive (<xref target="cache-response-directive"
516                 />) is present, use its value, or</t>
517              <t>If the Expires response header (<xref target="header.expires" />) is present, use
518                its value minus the value of the Date response header, or</t>
519              <t>Otherwise, no explicit expiration time is present in the response, but a heuristic
520                may be used; see <xref target="heuristic.freshness" />.</t>
521            </list>
522          </t>
523          <t>Note that this calculation is not vulnerable to clock skew, since all of the
524            information comes from the origin server.</t>
525
526          <section anchor="heuristic.freshness" title="Using Heuristic Freshness">
527            <t>If no explicit expiration time is present in a stored response that has a status code
528              of 200, 203, 206, 300, 301 or 410, a heuristic expiration time &MAY; be
529              calculated. Heuristics &MUST-NOT; be used for other response status codes. </t>
530            <t> When a heuristic is used to calculate freshness lifetime, the cache &SHOULD;
531              attach a Warning header with a 113 warn-code to the response if its current_age is
532              more than 24 hours and such a warning is not already present.</t>
533            <t>Also, if the response has a Last-Modified header (&header-last-modified;), the
534              heuristic expiration value &SHOULD; be no more than some fraction of the interval
535              since that time. A typical setting of this fraction might be 10%.</t>
536            <t>
537              <cref>REVIEW: took away HTTP/1.0 query string heuristic uncacheability.</cref>
538            </t>
539          </section>
540        </section>
541
542        <section anchor="age.calculations" title="Calculating Age">
543          <t>HTTP/1.1 uses the Age response-header to convey the estimated age of the response
544            message when obtained from a cache. The Age field value is the cache's estimate of the
545            amount of time since the response was generated or validated by the origin server. In
546            essence, the Age value is the sum of the time that the response has been resident in
547            each of the caches along the path from the origin server, plus the amount of time it has
548            been in transit along network paths.</t>
549          <t>When a stored response is used to satisfy a request, the cache &MUST; include a
550            single Age header field in the response with a value equal to the stored response's
551            current_age, calculated using the algorithm described in this section.</t>
552          <t>The term "age_value" denotes the value of the Age header, in a form appropriate for
553            arithmetic operations.</t>
554          <t>HTTP/1.1 requires origin servers to send a Date header, if possible, with every
555            response, giving the time at which the response was generated (see &header-date;).
556            The term "date_value" denotes the value of the Date header, in a form appropriate for
557            arithmetic operations.</t>
558          <t>The term "now" means "the current value of the clock at the host performing the
559            calculation." Hosts that use HTTP, but especially hosts running origin servers and
560            caches, &SHOULD; use NTP <xref target="RFC1305" /> or some similar protocol to
561            synchronize their clocks to a globally accurate time standard.</t>
562          <t>A response's age can be calculated in two entirely independent ways: <list
563              style="numbers">
564              <t>now minus date_value, if the local clock is reasonably well synchronized to the
565                origin server's clock. If the result is negative, the result is replaced by zero.</t>
566
567              <t>age_value, if all of the caches along the response path implement HTTP/1.1.</t>
568            </list>
569          </t>
570          <t>These are combined as</t>
571          <figure>
572            <artwork type="code">
573    corrected_received_age = max(now - date_value, age_value)
574</artwork>
575          </figure>
576          <t>When an Age value is received, it &MUST; be interpreted relative to the time the
577            request was initiated, not the time that the response was received.</t>
578          <figure>
579            <artwork type="code">
580   corrected_initial_age = corrected_received_age
581                         + (now - request_time)
582</artwork>
583          </figure>
584          <t>where "request_time" is the time (according to the local clock) when the request that
585            elicited this response was sent.</t>
586          <t>The current_age of a stored response can then be calculated by adding the amount of
587            time (in seconds) since the stored response was last validated by the origin server to
588            the corrected_initial_age.</t>
589          <t>In summary:</t>
590          <figure>
591            <artwork type="code">
592   /*
593    * age_value
594    *      is the value of Age: header received by the cache with
595    *              this response.
596    * date_value
597    *      is the value of the origin server's Date: header
598    * request_time
599    *      is the (local) time when the cache made the request
600    *              that resulted in this stored response
601    * response_time
602    *      is the (local) time when the cache received the
603    *              response
604    * now
605    *      is the current (local) time
606    */
607
608   apparent_age = max(0, response_time - date_value);
609   corrected_received_age = max(apparent_age, age_value);
610   response_delay = response_time - request_time;
611   corrected_initial_age = corrected_received_age + response_delay;
612   resident_time = now - response_time;
613   current_age   = corrected_initial_age + resident_time;
614</artwork>
615          </figure>
616        </section>
617
618        <section anchor="serving.stale.responses" title="Serving Stale Responses">
619          <t>A "stale" response is one that either has explicit expiry information, or is allowed to
620            have heuristic expiry calculated, but is not fresh according to the calculations in
621              <xref target="expiration.model" />.</t>
622          <t>Caches &MUST-NOT; return a stale response if it is prohibited by an explicit
623            in-protocol directive (e.g., by a "no-store" or "no-cache" cache directive, a
624            "must-revalidate" cache-response-directive, or an applicable "s-maxage" or
625            "proxy-revalidate" cache-response-directive; see <xref target="cache-response-directive"
626             />). </t>
627          <t>Caches &MAY; return a stale response if disconnected or explicitly allowed (e.g.,
628            the max-stale request directive; see <xref target="cache-request-directive" />).</t>
629          <t>Otherwise, caches &SHOULD-NOT; return stale responses.</t>
630          <t>Stale responses &SHOULD; have a Warning header with the 110 warn-code (see <xref
631              target="header.warning" />).</t>
632          <t>If a cache receives a first-hand response (either an entire response, or a 304 (Not
633            Modified) response) that it would normally forward to the requesting client, and the
634            received response is no longer fresh, the cache &SHOULD; forward it to the
635            requesting client without adding a new Warning (but without removing any existing
636            Warning headers). A cache &SHOULD-NOT; attempt to validate a response simply because
637            that response became stale in transit.</t>
638        </section>
639      </section>
640
641
642      <section anchor="validation.model" title="Validation Model">
643        <t>When a cache has a stale response that it would like to use, it &SHOULD; first check
644          with the origin server (or possibly an intermediate cache) to see if
645          it is still usable. This is called "validating" or "revalidating" the stored response.</t>
646        <t>HTTP's conditional request mechanism, defined in &conditional;, is used to avoid
647          retransmitting the response payload when the stored response is valid. When a stored
648          response includes one or more "cache validators", such as the field values of an ETag or
649          Last-Modified header field, then a validating GET request &SHOULD; be made conditional
650          to those field values; a 304 (Not Modified) response status code indicates that the stored
651          response can be updated and reused; see <xref target="combining.headers"/>.
652        <t>If the cache receives a full response (i.e., one with payload), it is used to satisfy the
653        request and replace the stored response.</t>
654        <t>If a cache receives a 5xx response while attempting to validate a response, it &MAY;
655          either forward this response to the requesting client, or act as if the server failed to
656          respond. In the latter case, it &MAY; return a previously stored response unless the
657          stored response includes the "must-revalidate" cache directive (see <xref
658            target="cache-response-directive" />).</t>
659      </section>
660
661      <section anchor="invalidation.after.updates.or.deletions"
662        title="Request Methods that Invalidate">
663        <t>Because unsafe methods &safe-methods; have the potential for changing state on the
664          origin server, intervening caches can use them to keep their contents
665          up-to-date.</t>
666        <t>The following HTTP methods &MUST; cause a cache to invalidate the Request-URI as well
667          as the Location and Content-Location headers (if present): <list style="symbols">
668            <t>PUT</t>
669            <t>DELETE</t>
670            <t>POST</t>
671          </list>
672        </t>
673        <t>An invalidation based on the URI in a Location or Content-Location header &MUST-NOT;
674          be performed if the host part of that URI differs from the host part in the Request-URI.
675          This helps prevent denial of service attacks.</t>
676        <t>
677          <cref>TODO: "host part" needs to be specified better.</cref>
678        </t>
679        <t>A cache that passes through requests for methods it does not understand &SHOULD;
680          invalidate the Request-URI.</t>
681        <t>Here, "invalidate" means that the cache will either remove all stored responses related
682          to the Request-URI, or will mark these as "invalid" and in need of a mandatory validation
683          before they can be returned in response to a subsequent request.</t>
684        <t>Note that this does not guarantee that all appropriate responses are invalidated. For
685          example, the request that caused the change at the origin server might not have gone
686          through the cache where a response is stored.</t>
687        <t>
688          <cref>TODO: specify that only successful (2xx, 3xx?) responses invalidate.</cref>
689        </t>
690      </section>
691
692
693
694
695
696      <section anchor="caching.negotiated.responses" title="Caching Negotiated Responses">
697        <t>Use of server-driven content negotiation (&server-driven-negotiation;), as indicated
698          by the presence of a Vary header field (<xref target="header.vary" />) in a response, alters
699          the conditions and procedure by which a cache can use the response for subsequent
700          requests.</t>
701        <t>When the cache receives a subsequent request which may be satisfied by a stored responses
702          that include a Vary header field, it &MUST-NOT; use it to satisfy the request unless
703          all of the selecting request-headers present in the new request match the corresponding
704          stored request-headers from the original request.</t>
705        <t>The selecting request-headers from two requests are defined to match if and only if the
706          selecting request-headers in the first request can be transformed to the selecting
707          request-headers in the second request by adding or removing linear white space
708          <cref>[ref]</cref> at places where this is allowed by the corresponding ABNF, and/or
709          combining multiple message-header fields with the same field name following the rules
710          about message headers in &message-headers;.</t>
711        <t>A Vary header field-value of "*" always fails to match, and subsequent requests on that
712          resource can only be properly interpreted by the origin server.</t>
713        <t>If the selecting request-headers for the stored response do not match the selecting
714          request header fields of the new request, then the cache &MUST-NOT; use the stored
715          response to satisfy the request unless it first relays the new request to the origin
716          server in a conditional request and the server responds with 304 (Not Modified), including
717          an entity tag or Content-Location that indicates the entity to be used.</t>
718        <t>If one or more applicable stored response has an entity tag, the forwarded request
719          &SHOULD; be conditional and include all of these entity tags in an If-None-Match
720          header field. This conveys to the server the set of entities currently stored by the
721          cache, so that if any one of these entities matches the requested entity, the server can
722          use the ETag header field in its 304 (Not Modified) response to tell the cache which
723          stored response is appropriate. If the entity-tag of the new response matches that of an
724          existing stored resopnse, the new response &SHOULD; be used to update its header
725          fields, and the result &MUST; be returned to the client.</t>
726        <t>If any of the existing stored responses contains only partial content for the associated
727          entity, its entity-tag &SHOULD-NOT; be included in the If-None-Match header field
728          unless the request is for a range that would be fully satisfied by that stored response.</t>
729        <t>If a cache receives a successful response whose Content-Location field matches that of an
730          existing stored response for the same Request-URI, whose entity-tag differs from that of
731          the existing stored response, and whose Date is more recent than that of the existing
732          response, the existing response &SHOULD-NOT; be returned in response to future
733          requests and &SHOULD; be deleted from the cache.</t>
734        <t>
735          <cref>TODO: this still needs work.</cref>
736        </t>
737      </section>
738
739
740      <section anchor="combining.headers" title="Combining Responses">
741        <t>When a cache receives a 304 (Not Modified) response or a 206 (Partial Content) response,
742          it needs to update the stored response with the new one, so that the updated response can
743          be sent to the client.</t>
744        <t>If the status code is 304 (Not Modified), the cache &SHOULD; use the stored entity-body as
745          the updated entity-body. If the status code is 206 (Partial Content) and the ETag or
746          Last-Modified headers match exactly, the cache &MAY; combine the stored entity-body in
747          the stored response with the updated entity-body received in the response and use the
748          result as the updated entity-body (see &combining-byte-ranges;).</t>
749        <t>The stored response headers are used for the updated response, except that <list
750            style="symbols">
751            <t>any stored Warning headers with warn-code 1xx (see <xref target="header.warning" />)
752              &MUST; be deleted from the stored response and the forwarded response.</t>
753            <t>any stored Warning headers with warn-code 2xx &MUST; be retained in the stored
754              response and the forwarded response.</t>
755            <t>any headers provided in the 304 or 206 response &MUST; replace the corresponding
756              headers from the stored response.</t>
757          </list>
758        </t>
759        <t>A cache &MUST; also replace stored headers with corresponding headers received in the
760          incoming response, except for Warning headers as described immediately above. If a header
761          field-name in the incoming response matches more than one header in the stored response,
762          all such old headers &MUST; be replaced. it &MAY; store the combined
763        entity-body.</t>
764        <t><cref>ISSUE: discuss how to handle HEAD updates</cref></t>
765      </section>
766
767    </section>
768
769
770
771
772    <section anchor="header.fields" title="Header Field Definitions">
773      <t>This section defines the syntax and semantics of HTTP/1.1 header fields related to caching.</t>
774      <t>For entity-header fields, both sender and recipient refer to either the client or the
775        server, depending on who sends and who receives the entity.</t>
776
777      <section anchor="header.age" title="Age">
778        <iref item="Age header" primary="true" x:for-anchor="" />
779        <iref item="Headers" primary="true" subitem="Age" x:for-anchor="" />
780        <x:anchor-alias value="Age"/>
781        <x:anchor-alias value="Age-v"/>
782        <x:anchor-alias value="age-value"/>
783        <t>      The response-header field "Age" conveys the sender's estimate of the amount of time since
784          the response (or its validation) was generated at the origin server. Age values are
785          calculated as specified in <xref target="age.calculations" />.</t>
786<figure><artwork type="abnf2616"><iref primary="true" item="Grammar" subitem="Age"/><iref primary="true" item="Grammar" subitem="Age-v"/>
787  <x:ref>Age</x:ref>   = "Age" ":" <x:ref>OWS</x:ref> <x:ref>Age-v</x:ref>
788  <x:ref>Age-v</x:ref> = <x:ref>delta-seconds</x:ref>
789</artwork></figure>
790        <t anchor="rule.delta-seconds">
791          <x:anchor-alias value="delta-seconds" /> Age field-values are non-negative decimal
792          integers, representing time in seconds.</t>
793        <figure>
794          <artwork type="abnf2616"><iref item="Grammar" primary="true" subitem="delta-seconds" />
795  <x:ref>delta-seconds</x:ref>  = 1*<x:ref>DIGIT</x:ref>
796</artwork>
797        </figure>
798        <t>If a cache receives a value larger than the largest positive integer it can represent, or
799          if any of its age calculations overflows, it &MUST; transmit an Age header with a
800          field-value of 2147483648 (2<x:sup>31</x:sup>). Caches &SHOULD; use an arithmetic type
801          of at least 31 bits of range.</t>
802        <t>The presence of an Age header field in a response implies that a response is not
803          first-hand. However, the converse is not true, since HTTP/1.0 caches may not implement the
804          Age header field.</t>
805      </section>
806
807      <section anchor="header.cache-control" title="Cache-Control">
808        <iref item="Cache-Control header" primary="true" x:for-anchor="" />
809        <iref item="Headers" primary="true" subitem="Cache-Control" x:for-anchor="" />
810        <x:anchor-alias value="Cache-Control"/>
811        <x:anchor-alias value="Cache-Control-v"/>
812        <x:anchor-alias value="cache-directive"/>
813        <x:anchor-alias value="cache-extension"/>
814        <x:anchor-alias value="cache-request-directive"/>
815        <x:anchor-alias value="cache-response-directive"/>
816        <t>The general-header field "Cache-Control" is used to specify directives that &MUST; be
817          obeyed by all caches along the request/response chain. The directives specify behavior
818          intended to prevent caches from adversely interfering with the request or response. Cache
819          directives are unidirectional in that the presence of a directive in a request does not
820          imply that the same directive is to be given in the response. <list>
821            <t>Note that HTTP/1.0 caches might not implement Cache-Control and might only implement
822              Pragma: no-cache (see <xref target="header.pragma" />).</t>
823          </list>
824        </t>
825        <t>Cache directives &MUST; be passed through by a proxy or gateway application,
826          regardless of their significance to that application, since the directives might be
827          applicable to all recipients along the request/response chain. It is not possible to
828          target a directive to a specific cache.</t>
829<figure><artwork type="abnf2616"><iref primary="true" item="Grammar" subitem="Cache-Control"/><iref primary="true" item="Grammar" subitem="Cache-Control-v"/><iref primary="true" item="Grammar" subitem="cache-extension"/>
830  <x:ref>Cache-Control</x:ref>   = "Cache-Control" ":" <x:ref>OWS</x:ref> <x:ref>Cache-Control-v</x:ref>
831  <x:ref>Cache-Control-v</x:ref> = 1#<x:ref>cache-directive</x:ref>
832
833  <x:ref>cache-directive</x:ref> = <x:ref>cache-request-directive</x:ref>
834     / <x:ref>cache-response-directive</x:ref>
835
836  <x:ref>cache-extension</x:ref> = <x:ref>token</x:ref> [ "=" ( <x:ref>token</x:ref> / <x:ref>quoted-string</x:ref> ) ]
837</artwork></figure>
838
839        <section anchor="cache-request-directive" title="Request Cache-Control Directives">
840          <x:anchor-alias value="cache-request-directive" />
841
842          <figure>
843            <artwork type="abnf2616"><iref item="Grammar" primary="true" subitem="cache-request-directive" />
844  <x:ref>cache-request-directive</x:ref> =
845       "no-cache"
846     / "no-store"
847     / "max-age" "=" <x:ref>delta-seconds</x:ref>
848     / "max-stale" [ "=" <x:ref>delta-seconds</x:ref> ]
849     / "min-fresh" "=" <x:ref>delta-seconds</x:ref>
850     / "no-transform"
851     / "only-if-cached"
852     / <x:ref>cache-extension</x:ref>
853</artwork>
854          </figure>
855
856
857          <t>
858            <iref item="Cache Directives" primary="true" subitem="no-cache" />
859            <iref item="no-cache" primary="true" subitem="Cache Directive" /> no-cache <list>
860              <t>The no-cache request directive indicates that a stored response &MUST-NOT; be
861                used to satisfy the request without successful validation on the origin server. </t>
862            </list>
863          </t>
864          <t>
865            <iref item="Cache Directives" primary="true" subitem="no-store" />
866            <iref item="no-store" primary="true" subitem="Cache Directive" /> no-store <list>
867              <t>The no-store request directive indicates that a cache &MUST-NOT; store any part
868                of either this request or any response to it. This directive applies to both
869                non-shared and shared caches. "&MUST-NOT; store" in this context means that the
870                cache &MUST-NOT; intentionally store the information in non-volatile storage,
871                and &MUST; make a best-effort attempt to remove the information from volatile
872                storage as promptly as possible after forwarding it.</t>
873              <t>This directive is NOT a reliable or sufficient mechanism for ensuring privacy. In
874                particular, malicious or compromised caches might not recognize or obey this
875                directive, and communications networks may be vulnerable to eavesdropping.</t>
876            </list>
877          </t>
878          <t>
879            <iref item="Cache Directives" primary="true" subitem="max-age" />
880            <iref item="max-age" primary="true" subitem="Cache Directive" /> max-age <list>
881              <t>The max-age request directive indicates that the client is willing to accept a
882                response whose age is no greater than the specified time in seconds. Unless
883                max-stale directive is also included, the client is not willing to accept a stale
884                response.</t>
885            </list>
886          </t>
887          <t>
888            <iref item="Cache Directives" primary="true" subitem="max-stale" />
889            <iref item="max-stale" primary="true" subitem="Cache Directive" /> max-stale <list>
890              <t>The max-stale request directive indicates that the client is willing to accept a
891                response that has exceeded its expiration time. If max-stale is assigned a value,
892                then the client is willing to accept a response that has exceeded its expiration
893                time by no more than the specified number of seconds. If no value is assigned to
894                max-stale, then the client is willing to accept a stale response of any age.</t>
895            </list>
896          </t>
897          <t>
898            <iref item="Cache Directives" primary="true" subitem="min-fresh" />
899            <iref item="min-fresh" primary="true" subitem="Cache Directive" /> min-fresh <list>
900              <t>The min-fresh request directive indicates that the client is willing to accept a
901                response whose freshness lifetime is no less than its current age plus the specified
902                time in seconds. That is, the client wants a response that will still be fresh for
903                at least the specified number of seconds.</t>
904            </list>
905          </t>
906          <t>
907            <iref item="Cache Directives" primary="true" subitem="no-transform" />
908            <iref item="no-transform" primary="true" subitem="Cache Directive" /> no-transform <list>
909              <t>The no-transform request directive indicates that an intermediate cache or proxy
910                &MUST-NOT; change the Content-Encoding, Content-Range or Content-Type request
911                headers, nor the request entity-body.</t>
912            </list>
913          </t>
914
915          <t>
916            <iref item="Cache Directives" primary="true" subitem="only-if-cached" />
917            <iref item="only-if-cached" primary="true" subitem="Cache Directive" /> only-if-cached <list>
918              <t>The only-if-cached request directive indicates that the client only wishes to
919                return a stored response. If it receives this directive, a cache &SHOULD; either
920                respond using a stored response that is consistent with the other constraints of the
921                request, or respond with a 504 (Gateway Timeout) status. If a group of caches is
922                being operated as a unified system with good internal connectivity, such a request
923                &MAY; be forwarded within that group of caches.</t>
924            </list>
925          </t>
926        </section>
927
928        <section anchor="cache-response-directive" title="Response Cache-Control Directives">
929          <x:anchor-alias value="cache-response-directive" />
930
931          <figure>
932            <artwork type="abnf2616"><iref item="Grammar" primary="true" subitem="cache-response-directive" />
933  <x:ref>cache-response-directive</x:ref> =
934       "public"
935     / "private" [ "=" <x:ref>DQUOTE</x:ref> 1#<x:ref>field-name</x:ref> <x:ref>DQUOTE</x:ref> ]
936     / "no-cache" [ "=" <x:ref>DQUOTE</x:ref> 1#<x:ref>field-name</x:ref> <x:ref>DQUOTE</x:ref> ]
937     / "no-store"
938     / "no-transform"
939     / "must-revalidate"
940     / "proxy-revalidate"
941     / "max-age" "=" <x:ref>delta-seconds</x:ref>
942     / "s-maxage" "=" <x:ref>delta-seconds</x:ref>
943     / <x:ref>cache-extension</x:ref>
944</artwork>
945          </figure>
946
947          <t>
948            <iref item="Cache Directives" primary="true" subitem="public" />
949            <iref item="public" primary="true" subitem="Cache Directive" /> public <list>
950              <t>The public response directive indicates that the response &MAY; be cached, even
951                if it would normally be non-cacheable or cacheable only within a non-shared cache.
952                (See also Authorization, &header-authorization;, for additional details.) </t>
953            </list>
954          </t>
955
956          <t>
957            <iref item="Cache Directives" primary="true" subitem="private" />
958            <iref item="private" primary="true" subitem="Cache Directive" /> private <list>
959              <t>The private response directive indicates that the response message is intended for
960                a single user and &MUST-NOT; be stored by a shared cache. A private (non-shared)
961                cache &MAY; store the response.</t>
962              <t>If the private response directive specifies one or more field-names, this
963                requirement is limited to the field-values associated with the listed response
964                headers. That is, the specified field-names(s) &MUST-NOT; be stored by a shared
965                cache, whereas the remainder of the response message &MAY; be.</t>
966              <t>
967                <x:h>Note:</x:h> This usage of the word private only controls where the response may
968                be stored, and cannot ensure the privacy of the message content.</t>
969            </list>
970          </t>
971          <t>
972            <iref item="Cache Directives" primary="true" subitem="no-cache" />
973            <iref item="no-cache" primary="true" subitem="Cache Directive" /> no-cache <list>
974              <t>The no-cache response directive indicates that a response &MUST-NOT; be used to
975                satisfy a subsequent request without successful validation on the origin server.
976                This allows an origin server to prevent caching even by caches that have been
977                configured to return stale responses.</t>
978              <t>If the no-cache response directive specifies one or more field-names, this
979                requirement is limited to the field-values assosicated with the listed response
980                headers. That is, the specified field-name(s) &MUST-NOT; be sent in the response
981                to a subsequent request without successful validation on the origin server. This
982                allows an origin server to prevent the re-use of certain header fields in a
983                response, while still allowing caching of the rest of the response.</t>
984              <t>
985                <x:h>Note:</x:h> Most HTTP/1.0 caches will not recognize or obey this directive.
986              </t>
987            </list>
988          </t>
989
990          <t>
991            <iref item="Cache Directives" primary="true" subitem="no-store" />
992            <iref item="no-store" primary="true" subitem="Cache Directive" /> no-store <list>
993              <t>The no-store response directive indicates that a cache &MUST-NOT; store any
994                part of either the immediate request or response. This directive applies to both
995                non-shared and shared caches. "&MUST-NOT; store" in this context means that the
996                cache &MUST-NOT; intentionally store the information in non-volatile storage,
997                and &MUST; make a best-effort attempt to remove the information from volatile
998                storage as promptly as possible after forwarding it.</t>
999              <t>This directive is NOT a reliable or sufficient mechanism for ensuring privacy. In
1000                particular, malicious or compromised caches might not recognize or obey this
1001                directive, and communications networks may be vulnerable to eavesdropping.</t>
1002            </list>
1003          </t>
1004          <t>
1005            <iref item="Cache Directives" primary="true" subitem="must-revalidate" />
1006            <iref item="must-revalidate" primary="true" subitem="Cache Directive" /> must-revalidate <list>
1007              <t>The must-revalidate response directive indicates that validation is required before
1008                the response is used by a cache to satisfy any request.</t>
1009              <t>When the present, caches &MUST-NOT; use a stored after it becomes stale to
1010                respond to a subsequent request without first validating it with the origin server.</t>
1011              <t>The must-revalidate directive is necessary to support reliable operation for
1012                certain protocol features. In all circumstances an HTTP/1.1 cache &MUST; obey
1013                the must-revalidate directive; in particular, if the cache cannot reach the origin
1014                server for any reason, it &MUST; generate a 504 (Gateway Timeout) response.</t>
1015              <t>Servers &SHOULD; send the must-revalidate directive if and only if failure to
1016                validate a request on the entity could result in incorrect operation, such as a
1017                silently unexecuted financial transaction.</t>
1018            </list>
1019          </t>
1020          <t>
1021            <iref item="Cache Directives" primary="true" subitem="proxy-revalidate" />
1022            <iref item="proxy-revalidate" primary="true" subitem="Cache Directive" />
1023            proxy-revalidate <list>
1024              <t>The proxy-revalidate response directive has the same meaning as the must-revalidate
1025                response directive, except that it does not apply to non-shared caches.</t>
1026            </list>
1027          </t>
1028          <t>
1029            <iref item="Cache Directives" primary="true" subitem="max-age" />
1030            <iref item="max-age" primary="true" subitem="Cache Directive" /> max-age <list>
1031              <t>The max-age response directive indicates that response is to be considered stale
1032                after its age is greater than the specified number of seconds.</t>
1033            </list>
1034          </t>
1035          <t>
1036            <iref item="Cache Directives" primary="true" subitem="s-maxage" />
1037            <iref item="s-maxage" primary="true" subitem="Cache Directive" /> s-maxage <list>
1038              <t>The s-maxage response directive indicates that, in shared caches, the maximum age
1039                specified by this directive overrides the maximum age specified by either the
1040                max-age directive or the Expires header. The s-maxage directive also implies the
1041                semantics of the proxy-revalidate response directive.</t>
1042            </list>
1043          </t>
1044          <t>
1045            <iref item="Cache Directives" primary="true" subitem="no-transform" />
1046            <iref item="no-transform" primary="true" subitem="Cache Directive" /> no-transform <list>
1047              <t>The no-transform response directive indicates that an intermediate cache or proxy
1048                &MUST-NOT; change the Content-Encoding, Content-Range or Content-Type response
1049                headers, nor the response entity-body.</t>
1050            </list>
1051          </t>
1052
1053        </section>
1054
1055        <section anchor="cache.control.extensions" title="Cache Control Extensions">
1056          <t>The Cache-Control header field can be extended through the use of one or more
1057            cache-extension tokens, each with an optional value. Informational extensions (those
1058            which do not require a change in cache behavior) &MAY; be added without changing the
1059            semantics of other directives. Behavioral extensions are designed to work by acting as
1060            modifiers to the existing base of cache directives. Both the new directive and the
1061            standard directive are supplied, such that applications which do not understand the new
1062            directive will default to the behavior specified by the standard directive, and those
1063            that understand the new directive will recognize it as modifying the requirements
1064            associated with the standard directive. In this way, extensions to the cache-control
1065            directives can be made without requiring changes to the base protocol.</t>
1066          <t>This extension mechanism depends on an HTTP cache obeying all of the cache-control
1067            directives defined for its native HTTP-version, obeying certain extensions, and ignoring
1068            all directives that it does not understand.</t>
1069          <t>For example, consider a hypothetical new response directive called "community" which
1070            acts as a modifier to the private directive. We define this new directive to mean that,
1071            in addition to any non-shared cache, any cache which is shared only by members of the
1072            community named within its value may cache the response. An origin server wishing to
1073            allow the UCI community to use an otherwise private response in their shared cache(s)
1074            could do so by including</t>
1075          <figure>
1076            <artwork type="example">
1077  Cache-Control: private, community="UCI"
1078</artwork>
1079          </figure>
1080          <t>A cache seeing this header field will act correctly even if the cache does not
1081            understand the community cache-extension, since it will also see and understand the
1082            private directive and thus default to the safe behavior.</t>
1083          <t>Unrecognized cache directives &MUST; be ignored; it is assumed that any cache
1084            directive likely to be unrecognized by an HTTP/1.1 cache will be combined with standard
1085            directives (or the response's default cacheability) such that the cache behavior will
1086            remain minimally correct even if the cache does not understand the extension(s).</t>
1087        </section>
1088
1089      </section>
1090
1091      <section anchor="header.expires" title="Expires">
1092        <iref item="Expires header" primary="true" x:for-anchor="" />
1093        <iref item="Headers" primary="true" subitem="Expires" x:for-anchor="" />
1094        <x:anchor-alias value="Expires"/>
1095        <x:anchor-alias value="Expires-v"/>
1096        <t>The entity-header field "Expires" gives the date/time after which the response is
1097          considered stale. See <xref target="expiration.model" /> for further discussion of the
1098          expiration model.</t>
1099        <t>The presence of an Expires field does not imply that the original resource will change or
1100          cease to exist at, before, or after that time.</t>
1101        <t>The field-value is an absolute date and time as defined by HTTP-date in &full-date;;
1102          it &MUST; be sent in rfc1123-date format.</t>
1103<figure><artwork type="abnf2616"><iref primary="true" item="Grammar" subitem="Expires"/><iref primary="true" item="Grammar" subitem="Expires-v"/>
1104  <x:ref>Expires</x:ref>   = "Expires" ":" <x:ref>OWS</x:ref> <x:ref>Expires-v</x:ref>
1105  <x:ref>Expires-v</x:ref> = <x:ref>HTTP-date</x:ref>
1106</artwork></figure>
1107        <t>For example</t>
1108        <figure>
1109          <artwork type="example">
1110  Expires: Thu, 01 Dec 1994 16:00:00 GMT
1111</artwork>
1112        </figure>
1113        <t>
1114          <list>
1115            <t>
1116              <x:h>Note:</x:h> if a response includes a Cache-Control field with the max-age
1117              directive (see <xref target="cache-response-directive" />), that directive overrides
1118              the Expires field.</t>
1119          </list>
1120        </t>
1121        <t>HTTP/1.1 servers &SHOULD-NOT; send Expires dates more than one year in the future.</t>
1122        <t>HTTP/1.1 clients and caches &MUST; treat other invalid date formats, especially
1123          including the value "0", as in the past (i.e., "already expired").</t>
1124      </section>
1125
1126      <section anchor="header.pragma" title="Pragma">
1127        <iref item="Pragma header" primary="true" x:for-anchor="" />
1128        <iref item="Headers" primary="true" subitem="Pragma" x:for-anchor="" />
1129        <x:anchor-alias value="extension-pragma"/>
1130        <x:anchor-alias value="Pragma"/>
1131        <x:anchor-alias value="Pragma-v"/>
1132        <x:anchor-alias value="pragma-directive"/>
1133        <t>The general-header field "Pragma" is used to include implementation-specific directives
1134          that might apply to any recipient along the request/response chain. All pragma directives
1135          specify optional behavior from the viewpoint of the protocol; however, some systems
1136          &MAY; require that behavior be consistent with the directives.</t>
1137<figure><artwork type="abnf2616"><iref primary="true" item="Grammar" subitem="Pragma"/><iref primary="true" item="Grammar" subitem="Pragma-v"/><iref primary="true" item="Grammar" subitem="pragma-directive"/><iref primary="true" item="Grammar" subitem="extension-pragma"/>
1138  <x:ref>Pragma</x:ref>            = "Pragma" ":" <x:ref>OWS</x:ref> <x:ref>Pragma-v</x:ref>
1139  <x:ref>Pragma-v</x:ref>          = 1#<x:ref>pragma-directive</x:ref>
1140  <x:ref>pragma-directive</x:ref>  = "no-cache" / <x:ref>extension-pragma</x:ref>
1141  <x:ref>extension-pragma</x:ref>  = <x:ref>token</x:ref> [ "=" ( <x:ref>token</x:ref> / <x:ref>quoted-string</x:ref> ) ]
1142</artwork></figure>
1143        <t>When the no-cache directive is present in a request message, an application &SHOULD;
1144          forward the request toward the origin server even if it has a cached copy of what is being
1145          requested. This pragma directive has the same semantics as the no-cache response directive
1146          (see <xref target="cache-response-directive" />) and is defined here for backward
1147          compatibility with HTTP/1.0. Clients &SHOULD; include both header fields when a
1148          no-cache request is sent to a server not known to be HTTP/1.1 compliant. HTTP/1.1 caches
1149          &SHOULD; treat "Pragma: no-cache" as if the client had sent "Cache-Control: no-cache".</t>
1150        <t>
1151          <list>
1152            <t>
1153              <x:h>Note:</x:h> because the meaning of "Pragma: no-cache" as a response-header field
1154              is not actually specified, it does not provide a reliable replacement for
1155              "Cache-Control: no-cache" in a response.</t>
1156          </list>
1157        </t>
1158        <t>This mechanism is deprecated; no new Pragma directives will be defined in HTTP.</t>
1159      </section>
1160
1161      <section anchor="header.vary" title="Vary">
1162        <iref item="Vary header" primary="true" x:for-anchor="" />
1163        <iref item="Headers" primary="true" subitem="Vary" x:for-anchor="" />
1164        <x:anchor-alias value="Vary"/>
1165        <x:anchor-alias value="Vary-v"/>
1166        <t>The "Vary" response-header field's value indicates the set of request-header fields that
1167          fully determines, while the response is fresh, whether a cache is permitted to use the
1168          response to reply to a subsequent request without validation. For uncacheable or stale
1169          responses, the Vary field value advises the user agent about the criteria that were used
1170          to select the representation. A Vary field value of "*" implies that a cache cannot
1171          determine from the request headers of a subsequent request whether this response is the
1172          appropriate representation. See <xref target="caching.negotiated.responses" /> for use of
1173          the Vary header field by caches.</t>
1174<figure><artwork type="abnf2616"><iref primary="true" item="Grammar" subitem="Vary"/><iref primary="true" item="Grammar" subitem="Vary-v"/>
1175  <x:ref>Vary</x:ref>   = "Vary" ":" <x:ref>OWS</x:ref> <x:ref>Vary-v</x:ref>
1176  <x:ref>Vary-v</x:ref> = "*" / 1#<x:ref>field-name</x:ref>
1177</artwork></figure>
1178        <t>The set of header fields named by the Vary field value is known as the "selecting"
1179          request-headers.</t>
1180        <t>Servers &SHOULD; include a Vary header field with any cacheable response that is
1181          subject to server-driven negotiation. Doing so allows a cache to properly interpret future
1182          requests on that resource and informs the user agent about the presence of negotiation on
1183          that resource. A server &MAY; include a Vary header field with a non-cacheable
1184          response that is subject to server-driven negotiation, since this might provide the user
1185          agent with useful information about the dimensions over which the response varies at the
1186          time of the response.</t>
1187        <t>A Vary field value of "*" signals that unspecified parameters not limited to the
1188          request-headers (e.g., the network address of the client), play a role in the selection of
1189          the response representation. The "*" value &MUST-NOT; be generated by a proxy server;
1190          it may only be generated by an origin server.</t>
1191        <t>The field-names given are not limited to the set of standard request-header fields
1192          defined by this specification. Field names are case-insensitive.</t>
1193      </section>
1194
1195      <section anchor="header.warning" title="Warning">
1196        <iref item="Warning header" primary="true" x:for-anchor="" />
1197        <iref item="Headers" primary="true" subitem="Warning" x:for-anchor="" />
1198        <x:anchor-alias value="Warning"/>
1199        <x:anchor-alias value="Warning-v"/>
1200        <x:anchor-alias value="warning-value"/>
1201        <x:anchor-alias value="warn-agent"/>
1202        <x:anchor-alias value="warn-code"/>
1203        <x:anchor-alias value="warn-date"/>
1204        <x:anchor-alias value="warn-text"/>
1205        <t>The general-header field "Warning" is used to carry additional information about the status
1206          or transformation of a message which might not be reflected in the message. This
1207          information is typically used to warn about possible incorrectness introduced by caching
1208          operations or transformations applied to the entity body of the message.</t>
1209        <t>Warnings can be used for other purposes, both cache-related and otherwise. The use of a
1210          warning, rather than an error status code, distinguish these responses from true failures.</t>
1211
1212        <t>Warning headers can in general be applied to any message, however some warn-codes are
1213          specific to caches and can only be applied to response messages.</t>
1214
1215<figure><artwork type="abnf2616"><iref primary="true" item="Grammar" subitem="Warning"/><iref primary="true" item="Grammar" subitem="Warning-v"/><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"/>
1216  <x:ref>Warning</x:ref>    = "Warning" ":" <x:ref>OWS</x:ref> <x:ref>Warning-v</x:ref>
1217  <x:ref>Warning-v</x:ref>  = 1#<x:ref>warning-value</x:ref>
1218 
1219  <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>
1220                                        [<x:ref>SP</x:ref> <x:ref>warn-date</x:ref>]
1221 
1222  <x:ref>warn-code</x:ref>  = 3<x:ref>DIGIT</x:ref>
1223  <x:ref>warn-agent</x:ref> = ( <x:ref>uri-host</x:ref> [ ":" <x:ref>port</x:ref> ] ) / <x:ref>pseudonym</x:ref>
1224                  ; the name or pseudonym of the server adding
1225                  ; the Warning header, for use in debugging
1226  <x:ref>warn-text</x:ref>  = <x:ref>quoted-string</x:ref>
1227  <x:ref>warn-date</x:ref>  = <x:ref>DQUOTE</x:ref> <x:ref>HTTP-date</x:ref> <x:ref>DQUOTE</x:ref>
1228</artwork></figure>
1229
1230        <t>Multiple warnings &MAY; be attached to a response (either by the origin server or by
1231          a cache), including multiple warnings with the same code number. For example, a server
1232          might provide the same warning with texts in both English and Basque.</t>
1233        <t>When this occurs, the user agent &SHOULD; inform the user of as many of them as
1234          possible, in the order that they appear in the response. If it is not possible to inform
1235          the user of all of the warnings, the user agent &SHOULD; follow these heuristics:
1236            <list style="symbols">
1237            <t>Warnings that appear early in the response take priority over those appearing later
1238              in the response.</t>
1239
1240            <t>Warnings in the user's preferred character set take priority over warnings in other
1241              character sets but with identical warn-codes and warn-agents.</t>
1242          </list>
1243        </t>
1244        <t>Systems that generate multiple Warning headers &SHOULD; order them with this user
1245          agent behavior in mind. New Warning headers &SHOULD; be added after any existing
1246          Warning headers.</t>
1247        <t>Warnings are assigned three digit warn-codes. The first digit indicates whether the
1248          Warning is required to be deleted from a stored response after validation: <list
1249            style="symbols">
1250            <t>1xx Warnings that describe the freshness or validation status of the response, and so
1251              &MUST; be deleted by caches after validation. They &MUST-NOT; be generated by a cache
1252              except when validating a cached entry, and &MUST-NOT; be generated by clients.</t>
1253            <t>2xx Warnings that describe some aspect of the entity body or entity headers that is
1254              not rectified by a validation (for example, a lossy compression of the entity bodies)
1255              and which &MUST-NOT; be deleted by caches after validation, unless a full response is
1256              returned, in which case they &MUST; be.</t>
1257          </list>
1258        </t>
1259        <t>The warn-text &SHOULD; be in a natural language and character set that is most likely
1260          to be intelligible to the human user receiving the response. This decision can be based on
1261          any available knowledge, such as the location of the cache or user, the Accept-Language
1262          field in a request, the Content-Language field in a response, etc. The default language is
1263          English and the default character set is ISO-8859-1 (<xref target="ISO-8859-1" />).</t>
1264        <t>If a character set other than ISO-8859-1 is used, it &MUST; be encoded in the
1265          warn-text using the method described in <xref target="RFC2047" />.</t>
1266        <t>If an implementation sends a message with one or more Warning headers to a receiver whose
1267          version is HTTP/1.0 or lower, then the sender &MUST; include in each warning-value a
1268          warn-date that matches the Date header in the message.</t>
1269        <t>If an implementation receives a message with a warning-value that includes a warn-date,
1270          and that warn-date is different from the Date value in the response, then that
1271          warning-value &MUST; be deleted from the message before storing, forwarding, or using
1272          it. (preventing the consequences of naive caching of Warning header fields.) If all of the
1273          warning-values are deleted for this reason, the Warning header &MUST; be deleted as
1274          well.</t>
1275        <t>The following warn-codes are defined by this specification, each with a recommended
1276          warn-text in English, and a description of its meaning.</t>
1277        <t>110 Response is stale <list>
1278            <t>&SHOULD; be included whenever the returned response is stale.</t>
1279          </list>
1280        </t>
1281        <t>111 Revalidation failed <list>
1282            <t>&SHOULD; be included if a cache returns a stale response because an attempt to
1283              validate the response failed, due to an inability to reach the server.</t>
1284          </list>
1285        </t>
1286        <t>112 Disconnected operation <list>
1287            <t>&SHOULD; be included if the cache is intentionally disconnected from the rest of
1288              the network for a period of time.</t>
1289          </list>
1290        </t>
1291        <t>113 Heuristic expiration <list>
1292            <t>&SHOULD; be included if the cache heuristically chose a freshness lifetime
1293              greater than 24 hours and the response's age is greater than 24 hours.</t>
1294          </list>
1295        </t>
1296        <t>199 Miscellaneous warning <list>
1297            <t>The warning text &MAY; include arbitrary information to be presented to a human
1298              user, or logged. A system receiving this warning &MUST-NOT; take any automated
1299              action, besides presenting the warning to the user.</t>
1300          </list>
1301        </t>
1302        <t>214 Transformation applied <list>
1303            <t>&MUST; be added by an intermediate cache or proxy if it applies any
1304              transformation changing the content-coding (as specified in the Content-Encoding
1305              header) or media-type (as specified in the Content-Type header) of the response, or
1306              the entity-body of the response, unless this Warning code already appears in the
1307              response.</t>
1308          </list>
1309        </t>
1310        <t>299 Miscellaneous persistent warning <list>
1311            <t>The warning text &MAY; include arbitrary information to be presented to a human
1312              user, or logged. A system receiving this warning &MUST-NOT; take any automated
1313              action.</t>
1314          </list>
1315        </t>
1316      </section>
1317
1318    </section>
1319
1320
1321    <section anchor="history.lists" title="History Lists">
1322      <t>User agents often have history mechanisms, such as "Back" buttons and history lists, which
1323        can be used to redisplay an entity retrieved earlier in a session.</t>
1324      <t>History mechanisms and caches are different. In particular history mechanisms
1325        &SHOULD-NOT; try to show a correct view of the current state of a resource. Rather, a
1326        history mechanism is meant to show exactly what the user saw at the time when the resource
1327        was retrieved.</t>
1328      <t>By default, an expiration time does not apply to history mechanisms. If the entity is still
1329        in storage, a history mechanism &SHOULD; display it even if the entity has expired,
1330        unless the user has specifically configured the agent to refresh expired history documents.</t>
1331      <t>This is not to be construed to prohibit the history mechanism from telling the user that a
1332        view might be stale. <list>
1333          <t>
1334            <x:h>Note:</x:h> if history list mechanisms unnecessarily prevent users from viewing
1335            stale resources, this will tend to force service authors to avoid using HTTP expiration
1336            controls and cache controls when they would otherwise like to. Service authors may
1337            consider it important that users not be presented with error messages or warning
1338            messages when they use navigation controls (such as BACK) to view previously fetched
1339            resources. Even though sometimes such resources ought not be cached, or ought to expire
1340            quickly, user interface considerations may force service authors to resort to other
1341            means of preventing caching (e.g. "once-only" URLs) in order not to suffer the effects
1342            of improperly functioning history mechanisms.</t>
1343        </list>
1344      </t>
1345    </section>
1346
1347
1348    <section anchor="IANA.considerations" title="IANA Considerations">
1349      <section anchor="message.header.registration" title="Message Header Registration">
1350        <t>The Message Header Registry located at <eref
1351            target="http://www.iana.org/assignments/message-headers/message-header-index.html" />
1352          should be updated with the permanent registrations below (see <xref target="RFC3864" />):</t>
1353        <!--AUTOGENERATED FROM extract-header-defs.xslt, do not edit manually-->
1354        <texttable align="left" anchor="iana.header.registration.table" suppress-title="true">
1355          <ttcol>Header Field Name</ttcol>
1356          <ttcol>Protocol</ttcol>
1357          <ttcol>Status</ttcol>
1358          <ttcol>Reference</ttcol>
1359
1360          <c>Age</c>
1361          <c>http</c>
1362          <c>standard</c>
1363          <c>
1364            <xref target="header.age" />
1365          </c>
1366          <c>Cache-Control</c>
1367          <c>http</c>
1368          <c>standard</c>
1369          <c>
1370            <xref target="header.cache-control" />
1371          </c>
1372          <c>Expires</c>
1373          <c>http</c>
1374          <c>standard</c>
1375          <c>
1376            <xref target="header.expires" />
1377          </c>
1378          <c>Pragma</c>
1379          <c>http</c>
1380          <c>standard</c>
1381          <c>
1382            <xref target="header.pragma" />
1383          </c>
1384          <c>Vary</c>
1385          <c>http</c>
1386          <c>standard</c>
1387          <c>
1388            <xref target="header.vary" />
1389          </c>
1390          <c>Warning</c>
1391          <c>http</c>
1392          <c>standard</c>
1393          <c>
1394            <xref target="header.warning" />
1395          </c>
1396        </texttable>
1397        <!--(END)-->
1398        <t>The change controller is: "IETF (iesg@ietf.org) - Internet Engineering Task Force".</t>
1399      </section>
1400    </section>
1401
1402    <section anchor="security.considerations" title="Security Considerations">
1403      <t>Caches expose additional potential vulnerabilities, since the contents of the cache
1404        represent an attractive target for malicious exploitation. Because cache contents persist
1405        after an HTTP request is complete, an attack on the cache can reveal information long after
1406        a user believes that the information has been removed from the network. Therefore, cache
1407        contents should be protected as sensitive information.</t>
1408    </section>
1409
1410    <section anchor="ack" title="Acknowledgments">
1411      <t>Much of the content and presentation of the caching design is due to suggestions and
1412        comments from individuals including: Shel Kaphan, Paul Leach, Koen Holtman, David Morris,
1413        and Larry Masinter.</t>
1414    </section>
1415  </middle>
1416
1417  <back>
1418    <references title="Normative References">
1419
1420      <reference anchor="ISO-8859-1">
1421        <front>
1422          <title> Information technology -- 8-bit single-byte coded graphic character sets -- Part
1423            1: Latin alphabet No. 1 </title>
1424          <author>
1425            <organization>International Organization for Standardization</organization>
1426          </author>
1427          <date year="1998" />
1428        </front>
1429        <seriesInfo name="ISO/IEC" value="8859-1:1998" />
1430      </reference>
1431
1432      <reference anchor="Part1">
1433        <front>
1434          <title abbrev="HTTP/1.1">HTTP/1.1, part 1: URIs, Connections, and Message Parsing</title>
1435          <author fullname="Roy T. Fielding" initials="R." role="editor" surname="Fielding">
1436            <organization abbrev="Day Software">Day Software</organization>
1437            <address><email>fielding@gbiv.com</email></address>
1438          </author>
1439          <author fullname="Jim Gettys" initials="J." surname="Gettys">
1440            <organization>One Laptop per Child</organization>
1441            <address><email>jg@laptop.org</email></address>
1442          </author>
1443          <author fullname="Jeffrey C. Mogul" initials="J." surname="Mogul">
1444            <organization abbrev="HP">Hewlett-Packard Company</organization>
1445            <address><email>JeffMogul@acm.org</email></address>
1446          </author>
1447          <author fullname="Henrik Frystyk Nielsen" initials="H." surname="Frystyk">
1448            <organization abbrev="Microsoft">Microsoft Corporation</organization>
1449            <address><email>henrikn@microsoft.com</email></address>
1450          </author>
1451          <author fullname="Larry Masinter" initials="L." surname="Masinter">
1452            <organization abbrev="Adobe Systems">Adobe Systems, Incorporated</organization>
1453            <address><email>LMM@acm.org</email></address>
1454          </author>
1455          <author fullname="Paul J. Leach" initials="P." surname="Leach">
1456            <organization abbrev="Microsoft">Microsoft Corporation</organization>
1457            <address><email>paulle@microsoft.com</email></address>
1458          </author>
1459          <author fullname="Tim Berners-Lee" initials="T." surname="Berners-Lee">
1460            <organization abbrev="W3C/MIT">World Wide Web Consortium</organization>
1461            <address><email>timbl@w3.org</email></address>
1462          </author>
1463          <author fullname="Yves Lafon" initials="Y." role="editor" surname="Lafon">
1464            <organization abbrev="W3C">World Wide Web Consortium</organization>
1465            <address><email>ylafon@w3.org</email></address>
1466          </author>
1467          <author fullname="Julian F. Reschke" initials="J. F." role="editor" surname="Reschke">
1468            <organization abbrev="greenbytes">greenbytes GmbH</organization>
1469            <address><email>julian.reschke@greenbytes.de</email></address>
1470          </author>
1471          <date month="&ID-MONTH;" year="&ID-YEAR;" />
1472        </front>
1473        <seriesInfo name="Internet-Draft" value="draft-ietf-httpbis-p1-messaging-&ID-VERSION;" />
1474        <x:source basename="p1-messaging" href="p1-messaging.xml" />
1475      </reference>
1476
1477      <reference anchor="Part2">
1478        <front>
1479          <title abbrev="HTTP/1.1">HTTP/1.1, part 2: Message Semantics</title>
1480          <author fullname="Roy T. Fielding" initials="R." role="editor" surname="Fielding">
1481            <organization abbrev="Day Software">Day Software</organization>
1482            <address><email>fielding@gbiv.com</email></address>
1483          </author>
1484          <author fullname="Jim Gettys" initials="J." surname="Gettys">
1485            <organization>One Laptop per Child</organization>
1486            <address><email>jg@laptop.org</email></address>
1487          </author>
1488          <author fullname="Jeffrey C. Mogul" initials="J." surname="Mogul">
1489            <organization abbrev="HP">Hewlett-Packard Company</organization>
1490            <address><email>JeffMogul@acm.org</email></address>
1491          </author>
1492          <author fullname="Henrik Frystyk Nielsen" initials="H." surname="Frystyk">
1493            <organization abbrev="Microsoft">Microsoft Corporation</organization>
1494            <address><email>henrikn@microsoft.com</email></address>
1495          </author>
1496          <author fullname="Larry Masinter" initials="L." surname="Masinter">
1497            <organization abbrev="Adobe Systems">Adobe Systems, Incorporated</organization>
1498            <address><email>LMM@acm.org</email></address>
1499          </author>
1500          <author fullname="Paul J. Leach" initials="P." surname="Leach">
1501            <organization abbrev="Microsoft">Microsoft Corporation</organization>
1502            <address><email>paulle@microsoft.com</email></address>
1503          </author>
1504          <author fullname="Tim Berners-Lee" initials="T." surname="Berners-Lee">
1505            <organization abbrev="W3C/MIT">World Wide Web Consortium</organization>
1506            <address><email>timbl@w3.org</email></address>
1507          </author>
1508          <author fullname="Yves Lafon" initials="Y." role="editor" surname="Lafon">
1509            <organization abbrev="W3C">World Wide Web Consortium</organization>
1510            <address><email>ylafon@w3.org</email></address>
1511          </author>
1512          <author fullname="Julian F. Reschke" initials="J. F." role="editor" surname="Reschke">
1513            <organization abbrev="greenbytes">greenbytes GmbH</organization>
1514            <address><email>julian.reschke@greenbytes.de</email></address>
1515          </author>
1516          <date month="&ID-MONTH;" year="&ID-YEAR;" />
1517        </front>
1518        <seriesInfo name="Internet-Draft" value="draft-ietf-httpbis-p2-semantics-&ID-VERSION;" />
1519        <x:source basename="p2-semantics" href="p2-semantics.xml" />
1520      </reference>
1521
1522      <reference anchor="Part3">
1523        <front>
1524          <title abbrev="HTTP/1.1">HTTP/1.1, part 3: Message Payload and Content Negotiation</title>
1525          <author fullname="Roy T. Fielding" initials="R." role="editor" surname="Fielding">
1526            <organization abbrev="Day Software">Day Software</organization>
1527            <address><email>fielding@gbiv.com</email></address>
1528          </author>
1529          <author fullname="Jim Gettys" initials="J." surname="Gettys">
1530            <organization>One Laptop per Child</organization>
1531            <address><email>jg@laptop.org</email></address>
1532          </author>
1533          <author fullname="Jeffrey C. Mogul" initials="J." surname="Mogul">
1534            <organization abbrev="HP">Hewlett-Packard Company</organization>
1535            <address><email>JeffMogul@acm.org</email></address>
1536          </author>
1537          <author fullname="Henrik Frystyk Nielsen" initials="H." surname="Frystyk">
1538            <organization abbrev="Microsoft">Microsoft Corporation</organization>
1539            <address><email>henrikn@microsoft.com</email></address>
1540          </author>
1541          <author fullname="Larry Masinter" initials="L." surname="Masinter">
1542            <organization abbrev="Adobe Systems">Adobe Systems, Incorporated</organization>
1543            <address><email>LMM@acm.org</email></address>
1544          </author>
1545          <author fullname="Paul J. Leach" initials="P." surname="Leach">
1546            <organization abbrev="Microsoft">Microsoft Corporation</organization>
1547            <address><email>paulle@microsoft.com</email></address>
1548          </author>
1549          <author fullname="Tim Berners-Lee" initials="T." surname="Berners-Lee">
1550            <organization abbrev="W3C/MIT">World Wide Web Consortium</organization>
1551            <address><email>timbl@w3.org</email></address>
1552          </author>
1553          <author fullname="Yves Lafon" initials="Y." role="editor" surname="Lafon">
1554            <organization abbrev="W3C">World Wide Web Consortium</organization>
1555            <address><email>ylafon@w3.org</email></address>
1556          </author>
1557          <author fullname="Julian F. Reschke" initials="J. F." role="editor" surname="Reschke">
1558            <organization abbrev="greenbytes">greenbytes GmbH</organization>
1559            <address><email>julian.reschke@greenbytes.de</email></address>
1560          </author>
1561          <date month="&ID-MONTH;" year="&ID-YEAR;" />
1562        </front>
1563        <seriesInfo name="Internet-Draft" value="draft-ietf-httpbis-p3-payload-&ID-VERSION;" />
1564        <x:source basename="p3-payload" href="p3-payload.xml" />
1565      </reference>
1566
1567      <reference anchor="Part4">
1568        <front>
1569          <title abbrev="HTTP/1.1">HTTP/1.1, part 4: Conditional Requests</title>
1570          <author fullname="Roy T. Fielding" initials="R." role="editor" surname="Fielding">
1571            <organization abbrev="Day Software">Day Software</organization>
1572            <address><email>fielding@gbiv.com</email></address>
1573          </author>
1574          <author fullname="Jim Gettys" initials="J." surname="Gettys">
1575            <organization>One Laptop per Child</organization>
1576            <address><email>jg@laptop.org</email></address>
1577          </author>
1578          <author fullname="Jeffrey C. Mogul" initials="J." surname="Mogul">
1579            <organization abbrev="HP">Hewlett-Packard Company</organization>
1580            <address><email>JeffMogul@acm.org</email></address>
1581          </author>
1582          <author fullname="Henrik Frystyk Nielsen" initials="H." surname="Frystyk">
1583            <organization abbrev="Microsoft">Microsoft Corporation</organization>
1584            <address><email>henrikn@microsoft.com</email></address>
1585          </author>
1586          <author fullname="Larry Masinter" initials="L." surname="Masinter">
1587            <organization abbrev="Adobe Systems">Adobe Systems, Incorporated</organization>
1588            <address><email>LMM@acm.org</email></address>
1589          </author>
1590          <author fullname="Paul J. Leach" initials="P." surname="Leach">
1591            <organization abbrev="Microsoft">Microsoft Corporation</organization>
1592            <address><email>paulle@microsoft.com</email></address>
1593          </author>
1594          <author fullname="Tim Berners-Lee" initials="T." surname="Berners-Lee">
1595            <organization abbrev="W3C/MIT">World Wide Web Consortium</organization>
1596            <address><email>timbl@w3.org</email></address>
1597          </author>
1598          <author fullname="Yves Lafon" initials="Y." role="editor" surname="Lafon">
1599            <organization abbrev="W3C">World Wide Web Consortium</organization>
1600            <address><email>ylafon@w3.org</email></address>
1601          </author>
1602          <author fullname="Julian F. Reschke" initials="J. F." role="editor" surname="Reschke">
1603            <organization abbrev="greenbytes">greenbytes GmbH</organization>
1604            <address><email>julian.reschke@greenbytes.de</email></address>
1605          </author>
1606          <date month="&ID-MONTH;" year="&ID-YEAR;" />
1607        </front>
1608        <seriesInfo name="Internet-Draft" value="draft-ietf-httpbis-p4-conditional-&ID-VERSION;" />
1609        <x:source basename="p4-conditional" href="p4-conditional.xml" />
1610      </reference>
1611
1612      <reference anchor="Part5">
1613        <front>
1614          <title abbrev="HTTP/1.1">HTTP/1.1, part 5: Range Requests and Partial Responses</title>
1615          <author fullname="Roy T. Fielding" initials="R." role="editor" surname="Fielding">
1616            <organization abbrev="Day Software">Day Software</organization>
1617            <address><email>fielding@gbiv.com</email></address>
1618          </author>
1619          <author fullname="Jim Gettys" initials="J." surname="Gettys">
1620            <organization>One Laptop per Child</organization>
1621            <address><email>jg@laptop.org</email></address>
1622          </author>
1623          <author fullname="Jeffrey C. Mogul" initials="J." surname="Mogul">
1624            <organization abbrev="HP">Hewlett-Packard Company</organization>
1625            <address><email>JeffMogul@acm.org</email></address>
1626          </author>
1627          <author fullname="Henrik Frystyk Nielsen" initials="H." surname="Frystyk">
1628            <organization abbrev="Microsoft">Microsoft Corporation</organization>
1629            <address><email>henrikn@microsoft.com</email></address>
1630          </author>
1631          <author fullname="Larry Masinter" initials="L." surname="Masinter">
1632            <organization abbrev="Adobe Systems">Adobe Systems, Incorporated</organization>
1633            <address><email>LMM@acm.org</email></address>
1634          </author>
1635          <author fullname="Paul J. Leach" initials="P." surname="Leach">
1636            <organization abbrev="Microsoft">Microsoft Corporation</organization>
1637            <address><email>paulle@microsoft.com</email></address>
1638          </author>
1639          <author fullname="Tim Berners-Lee" initials="T." surname="Berners-Lee">
1640            <organization abbrev="W3C/MIT">World Wide Web Consortium</organization>
1641            <address><email>timbl@w3.org</email></address>
1642          </author>
1643          <author fullname="Yves Lafon" initials="Y." role="editor" surname="Lafon">
1644            <organization abbrev="W3C">World Wide Web Consortium</organization>
1645            <address><email>ylafon@w3.org</email></address>
1646          </author>
1647          <author fullname="Julian F. Reschke" initials="J. F." role="editor" surname="Reschke">
1648            <organization abbrev="greenbytes">greenbytes GmbH</organization>
1649            <address><email>julian.reschke@greenbytes.de</email></address>
1650          </author>
1651          <date month="&ID-MONTH;" year="&ID-YEAR;" />
1652        </front>
1653        <seriesInfo name="Internet-Draft" value="draft-ietf-httpbis-p5-range-&ID-VERSION;" />
1654        <x:source basename="p5-range" href="p5-range.xml" />
1655      </reference>
1656
1657      <reference anchor="Part7">
1658        <front>
1659          <title abbrev="HTTP/1.1">HTTP/1.1, part 7: Authentication</title>
1660          <author fullname="Roy T. Fielding" initials="R." role="editor" surname="Fielding">
1661            <organization abbrev="Day Software">Day Software</organization>
1662            <address><email>fielding@gbiv.com</email></address>
1663          </author>
1664          <author fullname="Jim Gettys" initials="J." surname="Gettys">
1665            <organization>One Laptop per Child</organization>
1666            <address><email>jg@laptop.org</email></address>
1667          </author>
1668          <author fullname="Jeffrey C. Mogul" initials="J." surname="Mogul">
1669            <organization abbrev="HP">Hewlett-Packard Company</organization>
1670            <address><email>JeffMogul@acm.org</email></address>
1671          </author>
1672          <author fullname="Henrik Frystyk Nielsen" initials="H." surname="Frystyk">
1673            <organization abbrev="Microsoft">Microsoft Corporation</organization>
1674            <address><email>henrikn@microsoft.com</email></address>
1675          </author>
1676          <author fullname="Larry Masinter" initials="L." surname="Masinter">
1677            <organization abbrev="Adobe Systems">Adobe Systems, Incorporated</organization>
1678            <address><email>LMM@acm.org</email></address>
1679          </author>
1680          <author fullname="Paul J. Leach" initials="P." surname="Leach">
1681            <organization abbrev="Microsoft">Microsoft Corporation</organization>
1682            <address><email>paulle@microsoft.com</email></address>
1683          </author>
1684          <author fullname="Tim Berners-Lee" initials="T." surname="Berners-Lee">
1685            <organization abbrev="W3C/MIT">World Wide Web Consortium</organization>
1686            <address><email>timbl@w3.org</email></address>
1687          </author>
1688          <author fullname="Yves Lafon" initials="Y." role="editor" surname="Lafon">
1689            <organization abbrev="W3C">World Wide Web Consortium</organization>
1690            <address><email>ylafon@w3.org</email></address>
1691          </author>
1692          <author fullname="Julian F. Reschke" initials="J. F." role="editor" surname="Reschke">
1693            <organization abbrev="greenbytes">greenbytes GmbH</organization>
1694            <address><email>julian.reschke@greenbytes.de</email></address>
1695          </author>
1696          <date month="&ID-MONTH;" year="&ID-YEAR;" />
1697        </front>
1698        <seriesInfo name="Internet-Draft" value="draft-ietf-httpbis-p7-auth-&ID-VERSION;" />
1699        <x:source basename="p7-auth" href="p7-auth.xml" />
1700      </reference>
1701
1702      <reference anchor="RFC2047">
1703        <front>
1704          <title abbrev="Message Header Extensions">MIME (Multipurpose Internet Mail Extensions)
1705            Part Three: Message Header Extensions for Non-ASCII Text</title>
1706          <author fullname="Keith Moore" initials="K." surname="Moore">
1707            <organization>University of Tennessee</organization>
1708            <address><email>moore@cs.utk.edu</email></address>
1709          </author>
1710          <date month="November" year="1996" />
1711        </front>
1712        <seriesInfo name="RFC" value="2047" />
1713      </reference>
1714
1715      <reference anchor="RFC2119">
1716        <front>
1717          <title>Key words for use in RFCs to Indicate Requirement Levels</title>
1718          <author fullname="Scott Bradner" initials="S." surname="Bradner">
1719            <organization>Harvard University</organization>
1720            <address><email>sob@harvard.edu</email></address>
1721          </author>
1722          <date month="March" year="1997" />
1723        </front>
1724        <seriesInfo name="BCP" value="14" />
1725        <seriesInfo name="RFC" value="2119" />
1726      </reference>
1727
1728      <reference anchor="RFC5234">
1729        <front>
1730          <title abbrev="ABNF for Syntax Specifications">Augmented BNF for Syntax Specifications: ABNF</title>
1731          <author initials="D." surname="Crocker" fullname="Dave Crocker" role="editor">
1732            <organization>Brandenburg InternetWorking</organization>
1733            <address>
1734            <postal>
1735            <street>675 Spruce Dr.</street>
1736            <city>Sunnyvale</city>
1737            <region>CA</region>
1738            <code>94086</code>
1739            <country>US</country></postal>
1740            <phone>+1.408.246.8253</phone>
1741            <email>dcrocker@bbiw.net</email></address> 
1742          </author>
1743          <author initials="P." surname="Overell" fullname="Paul Overell">
1744            <organization>THUS plc.</organization>
1745            <address>
1746            <postal>
1747            <street>1/2 Berkeley Square</street>
1748            <street>99 Berkely Street</street>
1749            <city>Glasgow</city>
1750            <code>G3 7HR</code>
1751            <country>UK</country></postal>
1752            <email>paul.overell@thus.net</email></address>
1753          </author>
1754          <date month="January" year="2008"/>
1755        </front>
1756        <seriesInfo name="STD" value="68"/>
1757        <seriesInfo name="RFC" value="5234"/>
1758      </reference>
1759     
1760    </references>
1761
1762    <references title="Informative References">
1763
1764      <reference anchor="RFC1305">
1765        <front>
1766          <title>Network Time Protocol (Version 3) Specification, Implementation</title>
1767          <author fullname="David L. Mills" initials="D." surname="Mills">
1768            <organization>University of Delaware, Electrical Engineering Department</organization>
1769            <address><email>mills@udel.edu</email></address>
1770          </author>
1771          <date month="March" year="1992" />
1772        </front>
1773        <seriesInfo name="RFC" value="1305" />
1774      </reference>
1775
1776      <reference anchor="RFC2616">
1777        <front>
1778          <title>Hypertext Transfer Protocol -- HTTP/1.1</title>
1779          <author fullname="R. Fielding" initials="R." surname="Fielding">
1780            <organization>University of California, Irvine</organization>
1781            <address><email>fielding@ics.uci.edu</email></address>
1782          </author>
1783          <author fullname="J. Gettys" initials="J." surname="Gettys">
1784            <organization>W3C</organization>
1785            <address><email>jg@w3.org</email></address>
1786          </author>
1787          <author fullname="J. Mogul" initials="J." surname="Mogul">
1788            <organization>Compaq Computer Corporation</organization>
1789            <address><email>mogul@wrl.dec.com</email></address>
1790          </author>
1791          <author fullname="H. Frystyk" initials="H." surname="Frystyk">
1792            <organization>MIT Laboratory for Computer Science</organization>
1793            <address><email>frystyk@w3.org</email></address>
1794          </author>
1795          <author fullname="L. Masinter" initials="L." surname="Masinter">
1796            <organization>Xerox Corporation</organization>
1797            <address><email>masinter@parc.xerox.com</email></address>
1798          </author>
1799          <author fullname="P. Leach" initials="P." surname="Leach">
1800            <organization>Microsoft Corporation</organization>
1801            <address><email>paulle@microsoft.com</email></address>
1802          </author>
1803          <author fullname="T. Berners-Lee" initials="T." surname="Berners-Lee">
1804            <organization>W3C</organization>
1805            <address><email>timbl@w3.org</email></address>
1806          </author>
1807          <date month="June" year="1999" />
1808        </front>
1809        <seriesInfo name="RFC" value="2616" />
1810      </reference>
1811
1812      <reference anchor="RFC3864">
1813        <front>
1814          <title>Registration Procedures for Message Header Fields</title>
1815          <author fullname="G. Klyne" initials="G." surname="Klyne">
1816            <organization>Nine by Nine</organization>
1817            <address><email>GK-IETF@ninebynine.org</email></address>
1818          </author>
1819          <author fullname="M. Nottingham" initials="M." surname="Nottingham">
1820            <organization>BEA Systems</organization>
1821            <address><email>mnot@pobox.com</email></address>
1822          </author>
1823          <author fullname="J. Mogul" initials="J." surname="Mogul">
1824            <organization>HP Labs</organization>
1825            <address><email>JeffMogul@acm.org</email></address>
1826          </author>
1827          <date month="September" year="2004" />
1828        </front>
1829        <seriesInfo name="BCP" value="90" />
1830        <seriesInfo name="RFC" value="3864" />
1831      </reference>
1832
1833    </references>
1834
1835    <section anchor="compatibility" title="Compatibility with Previous Versions">
1836
1837      <section anchor="changes.from.rfc.2068" title="Changes from RFC 2068">
1838        <t>A case was missed in the Cache-Control model of HTTP/1.1; s-maxage was introduced to add
1839          this missing case. (Sections <xref format="counter" target="response.cacheability" />,
1840            <xref format="counter" target="header.cache-control" />).</t>
1841        <t>Transfer-coding and message lengths all interact in ways that required fixing exactly
1842          when chunked encoding is used (to allow for transfer encoding that may not be self
1843          delimiting); it was important to straighten out exactly how message lengths are computed.
1844          (see also <xref target="Part1" />, <xref target="Part3" /> and <xref target="Part5" />)</t>
1845        <t>Proxies should be able to add Content-Length when appropriate.</t>
1846        <t>Range request responses would become very verbose if all meta-data were always returned;
1847          by allowing the server to only send needed headers in a 206 response, this problem can be
1848          avoided. (<xref target="combining.headers" />)</t>
1849        <t>The Cache-Control: max-age directive was not properly defined for responses.</t>
1850        <t>Warnings could be cached incorrectly, or not updated appropriately. <xref
1851            format="counter" target="expiration.model" />, <xref format="counter"
1852            target="combining.headers" />, <xref format="counter" target="header.cache-control" />,
1853          and <xref format="counter" target="header.warning" />) Warning also needed to be a general
1854          header, as PUT or other methods may have need for it in requests.</t>
1855      </section>
1856
1857      <section anchor="changes.from.rfc.2616" title="Changes from RFC 2616">
1858        <t>Clarify denial of service attack avoidance requirement. (<xref
1859            target="invalidation.after.updates.or.deletions" />)</t>
1860      </section>
1861
1862    </section>
1863
1864<section xmlns:x="http://purl.org/net/xml2rfc/ext" title="Collected ABNF" anchor="collected.abnf">
1865<figure>
1866<artwork type="abnf" name="p6-cache.parsed-abnf">
1867<x:ref>Age</x:ref> = "Age:" OWS Age-v
1868<x:ref>Age-v</x:ref> = delta-seconds
1869
1870<x:ref>Cache-Control</x:ref> = "Cache-Control:" OWS Cache-Control-v
1871<x:ref>Cache-Control-v</x:ref> = *( "," OWS ) cache-directive *( OWS "," [ OWS
1872 cache-directive ] )
1873
1874<x:ref>Expires</x:ref> = "Expires:" OWS Expires-v
1875<x:ref>Expires-v</x:ref> = HTTP-date
1876
1877<x:ref>HTTP-date</x:ref> = &lt;HTTP-date, defined in [Part1], Section 3.2.1&gt;
1878
1879<x:ref>OWS</x:ref> = &lt;OWS, defined in [Part1], Section 1.2.2&gt;
1880
1881<x:ref>Pragma</x:ref> = "Pragma:" OWS Pragma-v
1882<x:ref>Pragma-v</x:ref> = *( "," OWS ) pragma-directive *( OWS "," [ OWS
1883 pragma-directive ] )
1884
1885<x:ref>Vary</x:ref> = "Vary:" OWS Vary-v
1886<x:ref>Vary-v</x:ref> = "*" / ( *( "," OWS ) field-name *( OWS "," [ OWS field-name
1887 ] ) )
1888
1889<x:ref>Warning</x:ref> = "Warning:" OWS Warning-v
1890<x:ref>Warning-v</x:ref> = *( "," OWS ) warning-value *( OWS "," [ OWS warning-value
1891 ] )
1892
1893<x:ref>cache-directive</x:ref> = cache-request-directive / cache-response-directive
1894<x:ref>cache-extension</x:ref> = token [ "=" ( token / quoted-string ) ]
1895<x:ref>cache-request-directive</x:ref> = "no-cache" / "no-store" / ( "max-age="
1896 delta-seconds ) / ( "max-stale" [ "=" delta-seconds ] ) / (
1897 "min-fresh=" delta-seconds ) / "no-transform" / "only-if-cached" /
1898 cache-extension
1899<x:ref>cache-response-directive</x:ref> = "public" / ( "private" [ "=" DQUOTE *( ","
1900 OWS ) field-name *( OWS "," [ OWS field-name ] ) DQUOTE ] ) / (
1901 "no-cache" [ "=" DQUOTE *( "," OWS ) field-name *( OWS "," [ OWS
1902 field-name ] ) DQUOTE ] ) / "no-store" / "no-transform" /
1903 "must-revalidate" / "proxy-revalidate" / ( "max-age=" delta-seconds
1904 ) / ( "s-maxage=" delta-seconds ) / cache-extension
1905
1906<x:ref>delta-seconds</x:ref> = 1*DIGIT
1907
1908<x:ref>extension-pragma</x:ref> = token [ "=" ( token / quoted-string ) ]
1909
1910<x:ref>field-name</x:ref> = &lt;field-name, defined in [Part1], Section 4.2&gt;
1911
1912<x:ref>port</x:ref> = &lt;port, defined in [Part1], Section 2.1&gt;
1913<x:ref>pragma-directive</x:ref> = "no-cache" / extension-pragma
1914<x:ref>pseudonym</x:ref> = &lt;pseudonym, defined in [Part1], Section 8.9&gt;
1915
1916<x:ref>quoted-string</x:ref> = &lt;quoted-string, defined in [Part1], Section 1.2.2&gt;
1917
1918<x:ref>token</x:ref> = &lt;token, defined in [Part1], Section 1.2.2&gt;
1919
1920<x:ref>uri-host</x:ref> = &lt;uri-host, defined in [Part1], Section 2.1&gt;
1921
1922<x:ref>warn-agent</x:ref> = ( uri-host [ ":" port ] ) / pseudonym
1923<x:ref>warn-code</x:ref> = 3DIGIT
1924<x:ref>warn-date</x:ref> = DQUOTE HTTP-date DQUOTE
1925<x:ref>warn-text</x:ref> = quoted-string
1926<x:ref>warning-value</x:ref> = warn-code SP warn-agent SP warn-text [ SP warn-date
1927 ]
1928
1929
1930</artwork>
1931</figure>
1932<figure><preamble>ABNF diagnostics:</preamble><artwork type="inline">; Age defined but not used
1933; Cache-Control defined but not used
1934; Expires defined but not used
1935; Pragma defined but not used
1936; Vary defined but not used
1937; Warning defined but not used
1938</artwork></figure></section>
1939
1940    <section anchor="change.log" title="Change Log (to be removed by RFC Editor before publication)">
1941
1942      <section title="Since RFC2616">
1943        <t>Extracted relevant partitions from <xref target="RFC2616" />.</t>
1944      </section>
1945
1946      <section title="Since draft-ietf-httpbis-p6-cache-00">
1947        <t>Closed issues: <list style="symbols">
1948            <t>
1949              <eref target="http://www3.tools.ietf.org/wg/httpbis/trac/ticket/9" />: "Trailer"
1950                (<eref target="http://purl.org/NET/http-errata#trailer-hop" />)</t>
1951            <t>
1952              <eref target="http://www3.tools.ietf.org/wg/httpbis/trac/ticket/12" />: "Invalidation
1953              after Update or Delete" (<eref target="http://purl.org/NET/http-errata#invalidupd" />)</t>
1954            <t>
1955              <eref target="http://www3.tools.ietf.org/wg/httpbis/trac/ticket/35" />: "Normative and
1956              Informative references"</t>
1957            <t>
1958              <eref target="http://www3.tools.ietf.org/wg/httpbis/trac/ticket/48" />: "Date
1959              reference typo"</t>
1960            <t>
1961              <eref target="http://www3.tools.ietf.org/wg/httpbis/trac/ticket/49" />: "Connection
1962              header text"</t>
1963            <t>
1964              <eref target="http://www3.tools.ietf.org/wg/httpbis/trac/ticket/65" />: "Informative
1965              references"</t>
1966            <t>
1967              <eref target="http://www3.tools.ietf.org/wg/httpbis/trac/ticket/66" />: "ISO-8859-1
1968              Reference"</t>
1969            <t>
1970              <eref target="http://www3.tools.ietf.org/wg/httpbis/trac/ticket/86" />: "Normative
1971              up-to-date references"</t>
1972            <t>
1973              <eref target="http://www3.tools.ietf.org/wg/httpbis/trac/ticket/87" />: "typo in
1974              13.2.2"</t>
1975          </list>
1976        </t>
1977        <t>Other changes: <list style="symbols">
1978            <t>Use names of RFC4234 core rules DQUOTE and HTAB (work in progress on <eref
1979                target="http://www3.tools.ietf.org/wg/httpbis/trac/ticket/36" />)</t>
1980          </list>
1981        </t>
1982      </section>
1983
1984      <section title="Since draft-ietf-httpbis-p6-cache-01">
1985        <t>Closed issues: <list style="symbols">
1986            <t>
1987              <eref target="http://www3.tools.ietf.org/wg/httpbis/trac/ticket/82" />: "rel_path not
1988              used"</t>
1989          </list>
1990        </t>
1991        <t>Other changes: <list style="symbols">
1992            <t>Get rid of duplicate BNF rule names ("host" -&gt; "uri-host") (work in progress
1993              on <eref target="http://www3.tools.ietf.org/wg/httpbis/trac/ticket/36" />)</t>
1994            <t>Add explicit references to BNF syntax and rules imported from other parts of the
1995              specification.</t>
1996          </list>
1997        </t>
1998      </section>
1999
2000      <section anchor="changes.since.02" title="Since draft-ietf-httpbis-p6-cache-02">
2001        <t>Ongoing work on IANA Message Header Registration (<eref
2002            target="http://www3.tools.ietf.org/wg/httpbis/trac/ticket/40" />): <list style="symbols">
2003            <t>Reference RFC 3984, and update header registrations for headers defined in this
2004              document.</t>
2005          </list>
2006        </t>
2007      </section>
2008
2009      <section anchor="changes.since.03" title="Since draft-ietf-httpbis-p6-cache-03">
2010        <t>Closed issues: <list style="symbols">
2011            <t>
2012              <eref target="http://www3.tools.ietf.org/wg/httpbis/trac/ticket/106" />: "Vary header
2013              classification"</t>
2014          </list>
2015        </t>
2016      </section>
2017
2018      <section anchor="changes.since.04" title="Since draft-ietf-httpbis-p6-cache-04">
2019      <t>
2020      </t>
2021      </section>
2022
2023      <section anchor="changes.since.05" title="Since draft-ietf-httpbis-p6-cache-05">
2024      <t>
2025        This is a total rewrite.
2026      </t>
2027      </section>
2028
2029    </section>
2030  </back>
2031</rfc>
Note: See TracBrowser for help on using the repository browser.