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

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

make IANA policy definitions consistent (see #346)

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