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

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

elaborate on 'disconnected'

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