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

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

clarify authorized request cacheability logic

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