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

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

Move 'freshening responses' under 'validation model'

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