source: draft-ietf-httpbis/latest/p6-cache.html @ 562

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

add anchors to a few TODOs

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