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

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

re-generate HTML, P6: fix a few formatting issues, add a few crefs

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