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

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

Setting Expires in the past doesn't guarantee that caches will always validate.

  • Property svn:eol-style set to native
  • Property svn:mime-type set to text/html;charset=utf-8
File size: 165.2 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 http://dublincore.org/documents/2008/08/04/dc-html/">
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
42ul.empty {
43  list-style-type: none;
44}
45ul.empty li {
46  margin-top: .5em;
47}
48dl p {
49  margin-left: 0em;
50}
51dt {
52  margin-top: .5em;
53}
54h1 {
55  font-size: 14pt;
56  line-height: 21pt;
57  page-break-after: avoid;
58}
59h1.np {
60  page-break-before: always;
61}
62h1 a {
63  color: #333333;
64}
65h2 {
66  font-size: 12pt;
67  line-height: 15pt;
68  page-break-after: avoid;
69}
70h3, h4, h5, h6 {
71  font-size: 10pt;
72  page-break-after: avoid;
73}
74h2 a, h3 a, h4 a, h5 a, h6 a {
75  color: black;
76}
77img {
78  margin-left: 3em;
79}
80li {
81  margin-left: 2em;
82  margin-right: 2em;
83}
84ol {
85  margin-left: 2em;
86  margin-right: 2em;
87}
88ol p {
89  margin-left: 0em;
90}
91p {
92  margin-left: 2em;
93  margin-right: 2em;
94}
95pre {
96  margin-left: 3em;
97  background-color: lightyellow;
98  padding: .25em;
99}
100pre.text2 {
101  border-style: dotted;
102  border-width: 1px;
103  background-color: #f0f0f0;
104  width: 69em;
105}
106pre.inline {
107  background-color: white;
108  padding: 0em;
109}
110pre.text {
111  border-style: dotted;
112  border-width: 1px;
113  background-color: #f8f8f8;
114  width: 69em;
115}
116pre.drawing {
117  border-style: solid;
118  border-width: 1px;
119  background-color: #f8f8f8;
120  padding: 2em;
121}
122sup {
123  font-size: 60%;
124}
125table {
126  margin-left: 2em;
127}
128table.tt {
129  vertical-align: top;
130}
131table.full {
132  border-style: outset;
133  border-width: 1px;
134}
135table.headers {
136  border-style: outset;
137  border-width: 1px;
138}
139table.tt td {
140  vertical-align: top;
141}
142table.full td {
143  border-style: inset;
144  border-width: 1px;
145}
146table.tt th {
147  vertical-align: top;
148}
149table.full th {
150  border-style: inset;
151  border-width: 1px;
152}
153table.headers th {
154  border-style: none none inset none;
155  border-width: 1px;
156}
157table.left {
158  margin-right: auto;
159}
160table.right {
161  margin-left: auto;
162}
163table.center {
164  margin-left: auto;
165  margin-right: auto;
166}
167caption {
168  caption-side: bottom;
169  font-weight: bold;
170  font-size: 9pt;
171  margin-top: .5em;
172}
173
174table.header {
175  border-spacing: 1px;
176  width: 95%;
177  font-size: 10pt;
178  color: white;
179}
180td.top {
181  vertical-align: top;
182}
183td.topnowrap {
184  vertical-align: top;
185  white-space: nowrap; 
186}
187table.header td {
188  background-color: gray;
189  width: 50%;
190}
191table.header a {
192  color: white;
193}
194td.reference {
195  vertical-align: top;
196  white-space: nowrap;
197  padding-right: 1em;
198}
199thead {
200  display:table-header-group;
201}
202ul.toc, ul.toc ul {
203  list-style: none;
204  margin-left: 1.5em;
205  margin-right: 0em;
206  padding-left: 0em;
207}
208ul.toc li {
209  line-height: 150%;
210  font-weight: bold;
211  font-size: 10pt;
212  margin-left: 0em;
213  margin-right: 0em;
214}
215ul.toc li li {
216  line-height: normal;
217  font-weight: normal;
218  font-size: 9pt;
219  margin-left: 0em;
220  margin-right: 0em;
221}
222li.excluded {
223  font-size: 0pt;
224}
225ul p {
226  margin-left: 0em;
227}
228ul.ind, ul.ind ul {
229  list-style: none;
230  margin-left: 1.5em;
231  margin-right: 0em;
232  padding-left: 0em;
233  page-break-before: avoid;
234}
235ul.ind li {
236  font-weight: bold;
237  line-height: 200%;
238  margin-left: 0em;
239  margin-right: 0em;
240}
241ul.ind li li {
242  font-weight: normal;
243  line-height: 150%;
244  margin-left: 0em;
245  margin-right: 0em;
246}
247.avoidbreak {
248  page-break-inside: avoid;
249}
250.bcp14 {
251  font-style: normal;
252  text-transform: lowercase;
253  font-variant: small-caps;
254}
255.comment {
256  background-color: yellow;
257}
258.center {
259  text-align: center;
260}
261.error {
262  color: red;
263  font-style: italic;
264  font-weight: bold;
265}
266.figure {
267  font-weight: bold;
268  text-align: center;
269  font-size: 9pt;
270}
271.filename {
272  color: #333333;
273  font-weight: bold;
274  font-size: 12pt;
275  line-height: 21pt;
276  text-align: center;
277}
278.fn {
279  font-weight: bold;
280}
281.hidden {
282  display: none;
283}
284.left {
285  text-align: left;
286}
287.right {
288  text-align: right;
289}
290.title {
291  color: #990000;
292  font-size: 18pt;
293  line-height: 18pt;
294  font-weight: bold;
295  text-align: center;
296  margin-top: 36pt;
297}
298.vcardline {
299  display: block;
300}
301.warning {
302  font-size: 14pt;
303  background-color: yellow;
304}
305
306
307@media print {
308  .noprint {
309    display: none;
310  }
311 
312  a {
313    color: black;
314    text-decoration: none;
315  }
316
317  table.header {
318    width: 90%;
319  }
320
321  td.header {
322    width: 50%;
323    color: black;
324    background-color: white;
325    vertical-align: top;
326    font-size: 12pt;
327  }
328
329  ul.toc a::after {
330    content: leader('.') target-counter(attr(href), page);
331  }
332 
333  ul.ind li li a {
334    content: target-counter(attr(href), page);
335  }
336 
337  .print2col {
338    column-count: 2;
339    -moz-column-count: 2;
340    column-fill: auto;
341  }
342}
343
344@page {
345  @top-left {
346       content: "Internet-Draft"; 
347  } 
348  @top-right {
349       content: "February 2011"; 
350  } 
351  @top-center {
352       content: "HTTP/1.1, Part 6"; 
353  } 
354  @bottom-left {
355       content: "Fielding, et al."; 
356  } 
357  @bottom-center {
358       content: "Expires August 14, 2011"; 
359  } 
360  @bottom-right {
361       content: "[Page " counter(page) "]"; 
362  } 
363}
364
365@page:first { 
366    @top-left {
367      content: normal;
368    }
369    @top-right {
370      content: normal;
371    }
372    @top-center {
373      content: normal;
374    }
375}
376</style><link rel="Contents" href="#rfc.toc">
377      <link rel="Author" href="#rfc.authors">
378      <link rel="Copyright" href="#rfc.copyrightnotice">
379      <link rel="Index" href="#rfc.index">
380      <link rel="Chapter" title="1 Introduction" href="#rfc.section.1">
381      <link rel="Chapter" title="2 Cache Operation" href="#rfc.section.2">
382      <link rel="Chapter" title="3 Header Field Definitions" href="#rfc.section.3">
383      <link rel="Chapter" title="4 History Lists" href="#rfc.section.4">
384      <link rel="Chapter" title="5 IANA Considerations" href="#rfc.section.5">
385      <link rel="Chapter" title="6 Security Considerations" href="#rfc.section.6">
386      <link rel="Chapter" title="7 Acknowledgments" href="#rfc.section.7">
387      <link rel="Chapter" href="#rfc.section.8" title="8 References">
388      <link rel="Appendix" title="A Changes from RFC 2616" href="#rfc.section.A">
389      <link rel="Appendix" title="B Collected ABNF" href="#rfc.section.B">
390      <link rel="Appendix" title="C Change Log (to be removed by RFC Editor before publication)" href="#rfc.section.C">
391      <meta name="generator" content="http://greenbytes.de/tech/webdav/rfc2629.xslt, Revision 1.540, 2011-01-10 09:27:20, XSLT vendor: SAXON 8.9 from Saxonica http://www.saxonica.com/">
392      <link rel="schema.dct" href="http://purl.org/dc/terms/">
393      <meta name="dct.creator" content="Fielding, R.">
394      <meta name="dct.creator" content="Gettys, J.">
395      <meta name="dct.creator" content="Mogul, J.">
396      <meta name="dct.creator" content="Frystyk, H.">
397      <meta name="dct.creator" content="Masinter, L.">
398      <meta name="dct.creator" content="Leach, P.">
399      <meta name="dct.creator" content="Berners-Lee, T.">
400      <meta name="dct.creator" content="Lafon, Y.">
401      <meta name="dct.creator" content="Nottingham, M.">
402      <meta name="dct.creator" content="Reschke, J. F.">
403      <meta name="dct.identifier" content="urn:ietf:id:draft-ietf-httpbis-p6-cache-latest">
404      <meta name="dct.issued" scheme="ISO8601" content="2011-02-10">
405      <meta name="dct.replaces" content="urn:ietf:rfc:2616">
406      <meta name="dct.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.">
407      <meta name="description" 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.">
408   </head>
409   <body>
410      <table class="header">
411         <tbody>
412            <tr>
413               <td class="left">HTTPbis Working Group</td>
414               <td class="right">R. Fielding, Editor</td>
415            </tr>
416            <tr>
417               <td class="left">Internet-Draft</td>
418               <td class="right">Adobe</td>
419            </tr>
420            <tr>
421               <td class="left">Obsoletes: <a href="http://tools.ietf.org/html/rfc2616">2616</a> (if approved)
422               </td>
423               <td class="right">J. Gettys</td>
424            </tr>
425            <tr>
426               <td class="left">Intended status: Standards Track</td>
427               <td class="right">Alcatel-Lucent</td>
428            </tr>
429            <tr>
430               <td class="left">Expires: August 14, 2011</td>
431               <td class="right">J. Mogul</td>
432            </tr>
433            <tr>
434               <td class="left"></td>
435               <td class="right">HP</td>
436            </tr>
437            <tr>
438               <td class="left"></td>
439               <td class="right">H. Frystyk</td>
440            </tr>
441            <tr>
442               <td class="left"></td>
443               <td class="right">Microsoft</td>
444            </tr>
445            <tr>
446               <td class="left"></td>
447               <td class="right">L. Masinter</td>
448            </tr>
449            <tr>
450               <td class="left"></td>
451               <td class="right">Adobe</td>
452            </tr>
453            <tr>
454               <td class="left"></td>
455               <td class="right">P. Leach</td>
456            </tr>
457            <tr>
458               <td class="left"></td>
459               <td class="right">Microsoft</td>
460            </tr>
461            <tr>
462               <td class="left"></td>
463               <td class="right">T. Berners-Lee</td>
464            </tr>
465            <tr>
466               <td class="left"></td>
467               <td class="right">W3C/MIT</td>
468            </tr>
469            <tr>
470               <td class="left"></td>
471               <td class="right">Y. Lafon, Editor</td>
472            </tr>
473            <tr>
474               <td class="left"></td>
475               <td class="right">W3C</td>
476            </tr>
477            <tr>
478               <td class="left"></td>
479               <td class="right">M. Nottingham, Editor</td>
480            </tr>
481            <tr>
482               <td class="left"></td>
483               <td class="right">J. Reschke, Editor</td>
484            </tr>
485            <tr>
486               <td class="left"></td>
487               <td class="right">greenbytes</td>
488            </tr>
489            <tr>
490               <td class="left"></td>
491               <td class="right">February 10, 2011</td>
492            </tr>
493         </tbody>
494      </table>
495      <p class="title">HTTP/1.1, part 6: Caching<br><span class="filename">draft-ietf-httpbis-p6-cache-latest</span></p>
496      <h1 id="rfc.abstract"><a href="#rfc.abstract">Abstract</a></h1> 
497      <p>The Hypertext Transfer Protocol (HTTP) is an application-level protocol for distributed, collaborative, hypermedia information
498         systems. This document is Part 6 of the seven-part specification that defines the protocol referred to as "HTTP/1.1" and,
499         taken together, obsoletes RFC 2616. Part 6 defines requirements on HTTP caches and the associated header fields that control
500         cache behavior or indicate cacheable response messages.
501      </p> 
502      <h1 id="rfc.note.1"><a href="#rfc.note.1">Editorial Note (To be removed by RFC Editor)</a></h1> 
503      <p>Discussion of this draft should take place on the HTTPBIS working group mailing list (ietf-http-wg@w3.org). The current issues
504         list is at &lt;<a href="http://tools.ietf.org/wg/httpbis/trac/report/3">http://tools.ietf.org/wg/httpbis/trac/report/3</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;.
505      </p> 
506      <p>The changes in this draft are summarized in <a href="#changes.since.12" title="Since draft-ietf-httpbis-p6-cache-12">Appendix&nbsp;C.14</a>.
507      </p> 
508      <h1><a id="rfc.status" href="#rfc.status">Status of This Memo</a></h1>
509      <p>This Internet-Draft is submitted in full conformance with the provisions of BCP 78 and BCP 79.</p>
510      <p>Internet-Drafts are working documents of the Internet Engineering Task Force (IETF). Note that other groups may also distribute
511         working documents as Internet-Drafts. The list of current Internet-Drafts is at <a href="http://datatracker.ietf.org/drafts/current/">http://datatracker.ietf.org/drafts/current/</a>.
512      </p>
513      <p>Internet-Drafts are draft documents valid for a maximum of six months and may be updated, replaced, or obsoleted by other
514         documents at any time. It is inappropriate to use Internet-Drafts as reference material or to cite them other than as “work
515         in progress”.
516      </p>
517      <p>This Internet-Draft will expire on August 14, 2011.</p>
518      <h1><a id="rfc.copyrightnotice" href="#rfc.copyrightnotice">Copyright Notice</a></h1>
519      <p>Copyright © 2011 IETF Trust and the persons identified as the document authors. All rights reserved.</p>
520      <p>This document is subject to BCP 78 and the IETF Trust's Legal Provisions Relating to IETF Documents (<a href="http://trustee.ietf.org/license-info">http://trustee.ietf.org/license-info</a>) in effect on the date of publication of this document. Please review these documents carefully, as they describe your rights
521         and restrictions with respect to this document. Code Components extracted from this document must include Simplified BSD License
522         text as described in Section 4.e of the Trust Legal Provisions and are provided without warranty as described in the Simplified
523         BSD License.
524      </p>
525      <p>This document may contain material from IETF Documents or IETF Contributions published or made publicly available before November
526         10, 2008. The person(s) controlling the copyright in some of this material may not have granted the IETF Trust the right to
527         allow modifications of such material outside the IETF Standards Process. Without obtaining an adequate license from the person(s)
528         controlling the copyright in such materials, this document may not be modified outside the IETF Standards Process, and derivative
529         works of it may not be created outside the IETF Standards Process, except to format it for publication as an RFC or to translate
530         it into languages other than English.
531      </p>
532      <hr class="noprint">
533      <h1 class="np" id="rfc.toc"><a href="#rfc.toc">Table of Contents</a></h1>
534      <ul class="toc">
535         <li>1.&nbsp;&nbsp;&nbsp;<a href="#caching">Introduction</a><ul>
536               <li>1.1&nbsp;&nbsp;&nbsp;<a href="#intro.purpose">Purpose</a></li>
537               <li>1.2&nbsp;&nbsp;&nbsp;<a href="#intro.terminology">Terminology</a></li>
538               <li>1.3&nbsp;&nbsp;&nbsp;<a href="#intro.requirements">Requirements</a></li>
539               <li>1.4&nbsp;&nbsp;&nbsp;<a href="#notation">Syntax Notation</a><ul>
540                     <li>1.4.1&nbsp;&nbsp;&nbsp;<a href="#core.rules">Core Rules</a></li>
541                     <li>1.4.2&nbsp;&nbsp;&nbsp;<a href="#abnf.dependencies">ABNF Rules defined in other Parts of the Specification</a></li>
542                  </ul>
543               </li>
544            </ul>
545         </li>
546         <li>2.&nbsp;&nbsp;&nbsp;<a href="#caching.overview">Cache Operation</a><ul>
547               <li>2.1&nbsp;&nbsp;&nbsp;<a href="#response.cacheability">Response Cacheability</a><ul>
548                     <li>2.1.1&nbsp;&nbsp;&nbsp;<a href="#errors.or.incomplete.response.cache.behavior">Storing Partial and Incomplete Responses</a></li>
549                  </ul>
550               </li>
551               <li>2.2&nbsp;&nbsp;&nbsp;<a href="#constructing.responses.from.caches">Constructing Responses from Caches</a></li>
552               <li>2.3&nbsp;&nbsp;&nbsp;<a href="#expiration.model">Freshness Model</a><ul>
553                     <li>2.3.1&nbsp;&nbsp;&nbsp;<a href="#calculating.freshness.lifetime">Calculating Freshness Lifetime</a><ul>
554                           <li>2.3.1.1&nbsp;&nbsp;&nbsp;<a href="#heuristic.freshness">Calculating Heuristic Freshness</a></li>
555                        </ul>
556                     </li>
557                     <li>2.3.2&nbsp;&nbsp;&nbsp;<a href="#age.calculations">Calculating Age</a></li>
558                     <li>2.3.3&nbsp;&nbsp;&nbsp;<a href="#serving.stale.responses">Serving Stale Responses</a></li>
559                  </ul>
560               </li>
561               <li>2.4&nbsp;&nbsp;&nbsp;<a href="#validation.model">Validation Model</a></li>
562               <li>2.5&nbsp;&nbsp;&nbsp;<a href="#invalidation.after.updates.or.deletions">Request Methods that Invalidate</a></li>
563               <li>2.6&nbsp;&nbsp;&nbsp;<a href="#caching.authenticated.responses">Shared Caching of Authenticated Responses</a></li>
564               <li>2.7&nbsp;&nbsp;&nbsp;<a href="#caching.negotiated.responses">Caching Negotiated Responses</a></li>
565               <li>2.8&nbsp;&nbsp;&nbsp;<a href="#combining.responses">Combining Responses</a></li>
566            </ul>
567         </li>
568         <li>3.&nbsp;&nbsp;&nbsp;<a href="#header.fields">Header Field Definitions</a><ul>
569               <li>3.1&nbsp;&nbsp;&nbsp;<a href="#header.age">Age</a></li>
570               <li>3.2&nbsp;&nbsp;&nbsp;<a href="#header.cache-control">Cache-Control</a><ul>
571                     <li>3.2.1&nbsp;&nbsp;&nbsp;<a href="#cache-request-directive">Request Cache-Control Directives</a></li>
572                     <li>3.2.2&nbsp;&nbsp;&nbsp;<a href="#cache-response-directive">Response Cache-Control Directives</a></li>
573                     <li>3.2.3&nbsp;&nbsp;&nbsp;<a href="#cache.control.extensions">Cache Control Extensions</a></li>
574                  </ul>
575               </li>
576               <li>3.3&nbsp;&nbsp;&nbsp;<a href="#header.expires">Expires</a></li>
577               <li>3.4&nbsp;&nbsp;&nbsp;<a href="#header.pragma">Pragma</a></li>
578               <li>3.5&nbsp;&nbsp;&nbsp;<a href="#header.vary">Vary</a></li>
579               <li>3.6&nbsp;&nbsp;&nbsp;<a href="#header.warning">Warning</a></li>
580            </ul>
581         </li>
582         <li>4.&nbsp;&nbsp;&nbsp;<a href="#history.lists">History Lists</a></li>
583         <li>5.&nbsp;&nbsp;&nbsp;<a href="#IANA.considerations">IANA Considerations</a><ul>
584               <li>5.1&nbsp;&nbsp;&nbsp;<a href="#cache.directive.registration">Cache Directive Registry</a></li>
585               <li>5.2&nbsp;&nbsp;&nbsp;<a href="#header.field.registration">Header Field Registration</a></li>
586            </ul>
587         </li>
588         <li>6.&nbsp;&nbsp;&nbsp;<a href="#security.considerations">Security Considerations</a></li>
589         <li>7.&nbsp;&nbsp;&nbsp;<a href="#ack">Acknowledgments</a></li>
590         <li>8.&nbsp;&nbsp;&nbsp;<a href="#rfc.references">References</a><ul>
591               <li>8.1&nbsp;&nbsp;&nbsp;<a href="#rfc.references.1">Normative References</a></li>
592               <li>8.2&nbsp;&nbsp;&nbsp;<a href="#rfc.references.2">Informative References</a></li>
593            </ul>
594         </li>
595         <li><a href="#rfc.authors">Authors' Addresses</a></li>
596         <li>A.&nbsp;&nbsp;&nbsp;<a href="#changes.from.rfc.2616">Changes from RFC 2616</a></li>
597         <li>B.&nbsp;&nbsp;&nbsp;<a href="#collected.abnf">Collected ABNF</a></li>
598         <li>C.&nbsp;&nbsp;&nbsp;<a href="#change.log">Change Log (to be removed by RFC Editor before publication)</a><ul>
599               <li>C.1&nbsp;&nbsp;&nbsp;<a href="#rfc.section.C.1">Since RFC 2616</a></li>
600               <li>C.2&nbsp;&nbsp;&nbsp;<a href="#rfc.section.C.2">Since draft-ietf-httpbis-p6-cache-00</a></li>
601               <li>C.3&nbsp;&nbsp;&nbsp;<a href="#rfc.section.C.3">Since draft-ietf-httpbis-p6-cache-01</a></li>
602               <li>C.4&nbsp;&nbsp;&nbsp;<a href="#changes.since.02">Since draft-ietf-httpbis-p6-cache-02</a></li>
603               <li>C.5&nbsp;&nbsp;&nbsp;<a href="#changes.since.03">Since draft-ietf-httpbis-p6-cache-03</a></li>
604               <li>C.6&nbsp;&nbsp;&nbsp;<a href="#changes.since.04">Since draft-ietf-httpbis-p6-cache-04</a></li>
605               <li>C.7&nbsp;&nbsp;&nbsp;<a href="#changes.since.05">Since draft-ietf-httpbis-p6-cache-05</a></li>
606               <li>C.8&nbsp;&nbsp;&nbsp;<a href="#changes.since.06">Since draft-ietf-httpbis-p6-cache-06</a></li>
607               <li>C.9&nbsp;&nbsp;&nbsp;<a href="#changes.since.07">Since draft-ietf-httpbis-p6-cache-07</a></li>
608               <li>C.10&nbsp;&nbsp;&nbsp;<a href="#changes.since.08">Since draft-ietf-httpbis-p6-cache-08</a></li>
609               <li>C.11&nbsp;&nbsp;&nbsp;<a href="#changes.since.09">Since draft-ietf-httpbis-p6-cache-09</a></li>
610               <li>C.12&nbsp;&nbsp;&nbsp;<a href="#changes.since.10">Since draft-ietf-httpbis-p6-cache-10</a></li>
611               <li>C.13&nbsp;&nbsp;&nbsp;<a href="#changes.since.11">Since draft-ietf-httpbis-p6-cache-11</a></li>
612               <li>C.14&nbsp;&nbsp;&nbsp;<a href="#changes.since.12">Since draft-ietf-httpbis-p6-cache-12</a></li>
613            </ul>
614         </li>
615         <li><a href="#rfc.index">Index</a></li>
616      </ul>
617      <h1 id="rfc.section.1" class="np"><a href="#rfc.section.1">1.</a>&nbsp;<a id="caching" href="#caching">Introduction</a></h1>
618      <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.
619         This document defines aspects of HTTP/1.1 related to caching and reusing response messages.
620      </p>
621      <div id="rfc.iref.c.1"></div>
622      <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>
623      <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
624         stores cacheable responses in order to reduce the response time and network bandwidth consumption on future, equivalent requests.
625         Any client or server <em class="bcp14">MAY</em> employ a cache, though a cache cannot be used by a server that is acting as a tunnel.
626      </p>
627      <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
628         response message to satisfy a current request. In some cases, a stored response can be reused without the need for a network
629         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
630         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>).
631      </p>
632      <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>
633      <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>
634      <p id="rfc.section.1.2.p.2"> <span id="rfc.iref.c.2"></span>  <dfn>cache</dfn> 
635      </p>
636      <ul class="empty">
637         <li>A conformant implementation of a HTTP cache. Note that this implies an HTTP/1.1 cache; this specification does not define
638            conformance for HTTP/1.0 caches.
639         </li>
640      </ul>
641      <div id="shared.and.non-shared.caches">
642         <p id="rfc.section.1.2.p.3"> <span id="rfc.iref.s.1"></span>  <dfn>shared cache</dfn> 
643         </p>
644         <ul class="empty">
645            <li>A cache that is accessible to more than one user; usually (but not always) deployed as part of an intermediary.</li>
646         </ul>
647      </div>
648      <p id="rfc.section.1.2.p.4"> <span id="rfc.iref.p.1"></span>  <dfn>private cache</dfn> 
649      </p>
650      <ul class="empty">
651         <li>A cache that is dedicated to a single user.</li>
652      </ul>
653      <p id="rfc.section.1.2.p.5"> <span id="rfc.iref.c.3"></span>  <dfn>cacheable</dfn> 
654      </p>
655      <ul class="empty">
656         <li>A response is cacheable if a cache is allowed to store a copy of the response message for use in answering subsequent requests.
657            Even when a response is cacheable, there might be additional constraints on whether a cache can use the stored copy to satisfy
658            a particular request.
659         </li>
660      </ul>
661      <p id="rfc.section.1.2.p.6"> <span id="rfc.iref.e.1"></span>  <dfn>explicit expiration time</dfn> 
662      </p>
663      <ul class="empty">
664         <li>The time at which the origin server intends that a representation no longer be returned by a cache without further validation.</li>
665      </ul>
666      <p id="rfc.section.1.2.p.7"> <span id="rfc.iref.h.1"></span>  <dfn>heuristic expiration time</dfn> 
667      </p>
668      <ul class="empty">
669         <li>An expiration time assigned by a cache when no explicit expiration time is available.</li>
670      </ul>
671      <p id="rfc.section.1.2.p.8"> <span id="rfc.iref.a.1"></span>  <dfn>age</dfn> 
672      </p>
673      <ul class="empty">
674         <li>The age of a response is the time since it was sent by, or successfully validated with, the origin server.</li>
675      </ul>
676      <p id="rfc.section.1.2.p.9"> <span id="rfc.iref.f.1"></span>  <dfn>first-hand</dfn> 
677      </p>
678      <ul class="empty">
679         <li>A response is first-hand if the freshness model is not in use; i.e., its age is 0.</li>
680      </ul>
681      <p id="rfc.section.1.2.p.10"> <span id="rfc.iref.f.2"></span>  <dfn>freshness lifetime</dfn> 
682      </p>
683      <ul class="empty">
684         <li>The length of time between the generation of a response and its expiration time.</li>
685      </ul>
686      <p id="rfc.section.1.2.p.11"> <span id="rfc.iref.f.3"></span>  <dfn>fresh</dfn> 
687      </p>
688      <ul class="empty">
689         <li>A response is fresh if its age has not yet exceeded its freshness lifetime.</li>
690      </ul>
691      <p id="rfc.section.1.2.p.12"> <span id="rfc.iref.s.2"></span>  <dfn>stale</dfn> 
692      </p>
693      <ul class="empty">
694         <li>A response is stale if its age has passed its freshness lifetime (either explicit or heuristic).</li>
695      </ul>
696      <p id="rfc.section.1.2.p.13"> <span id="rfc.iref.v.1"></span>  <dfn>validator</dfn> 
697      </p>
698      <ul class="empty">
699         <li>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
700            equivalent copy of a representation.
701         </li>
702      </ul>
703      <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>
704      <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"
705         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>.
706      </p>
707      <p id="rfc.section.1.3.p.2">An implementation is not compliant if it fails to satisfy one or more of the "MUST" or "REQUIRED" level requirements for the
708         protocols it implements. An implementation that satisfies all the "MUST" or "REQUIRED" level and all the "SHOULD" level requirements
709         for its protocols is said to be "unconditionally compliant"; one that satisfies all the "MUST" level requirements but not
710         all the "SHOULD" level requirements for its protocols is said to be "conditionally compliant".
711      </p>
712      <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>
713      <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.
714      </p>
715      <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
716         (hexadecimal 0-9/A-F/a-f), LF (line feed), OCTET (any 8-bit sequence of data), SP (space), VCHAR (any visible USASCII character),
717         and WSP (whitespace).
718      </p>
719      <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>
720      <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>:
721      </p>
722      <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;
723  <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;
724  <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;
725</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>
726      <p id="rfc.section.1.4.2.p.1">The ABNF rules below are defined in other parts:</p>
727      <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#header.fields" title="Header Fields">Section 3.2</a>&gt;
728  <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#date.time.formats.full.date" title="Date/Time Formats: Full Date">Section 6.1</a>&gt;
729  <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.6</a>&gt;
730  <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 9.9</a>&gt; 
731  <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.6</a>&gt;
732</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>
733      <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>
734      <p id="rfc.section.2.1.p.1">A cache <em class="bcp14">MUST NOT</em> store a response to any request, unless:
735      </p>
736      <ul>
737         <li>The request method is understood by the cache and defined as being cacheable, and</li>
738         <li>the response status code is understood by the cache, and</li>
739         <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 header fields, and
740         </li>
741         <li>the "private" cache response directive (see <a href="#cache-response-directive" title="Response Cache-Control Directives">Section&nbsp;3.2.2</a> does not appear in the response, if the cache is shared, and
742         </li>
743         <li>the "Authorization" header field (see <a href="p7-auth.html#header.authorization" title="Authorization">Section 4.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 response explicitly allows it (see <a href="#caching.authenticated.responses" title="Shared Caching of Authenticated Responses">Section&nbsp;2.6</a>), and
744         </li>
745         <li>the response either:
746            <ul>
747               <li>contains an Expires header field (see <a href="#header.expires" id="rfc.xref.header.expires.1" title="Expires">Section&nbsp;3.3</a>), or
748               </li>
749               <li>contains a max-age response cache directive (see <a href="#cache-response-directive" title="Response Cache-Control Directives">Section&nbsp;3.2.2</a>), or
750               </li>
751               <li>contains a s-maxage response cache directive and the cache is shared, or</li>
752               <li>contains a Cache Control Extension (see <a href="#cache.control.extensions" title="Cache Control Extensions">Section&nbsp;3.2.3</a>) that allows it to be cached, or
753               </li>
754               <li>has a status code that can be served with heuristic freshness (see <a href="#heuristic.freshness" title="Calculating Heuristic Freshness">Section&nbsp;2.3.1.1</a>).
755               </li>
756            </ul> 
757         </li>
758      </ul>
759      <p id="rfc.section.2.1.p.2">In this context, a cache has "understood" a request method or a response status code if it recognises it and implements any
760         cache-specific behaviour. In particular, 206 Partial Content responses cannot be cached by an implementation that does not
761         handle partial content (see <a href="#errors.or.incomplete.response.cache.behavior" title="Storing Partial and Incomplete Responses">Section&nbsp;2.1.1</a>).
762      </p>
763      <p id="rfc.section.2.1.p.3">Note that in normal operation, most caches will not store a response that has neither a cache validator nor an explicit expiration
764         time, as such responses are not usually useful to store. However, caches are not prohibited from storing such responses.
765      </p>
766      <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>
767      <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
768         field) 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.
769      </p>
770      <p id="rfc.section.2.1.1.p.2">A cache that does not support the Range and Content-Range header fields <em class="bcp14">MUST NOT</em> store incomplete or partial responses.
771      </p>
772      <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>
773      <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:
774      </p>
775      <ul>
776         <li>The presented effective request URI (<a href="p1-messaging.html#effective.request.uri" title="Effective Request URI">Section 4.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>) and that of the stored response match, and
777         </li>
778         <li>the request method associated with the stored response allows it to be used for the presented request, and</li>
779         <li>selecting request-header fields nominated by the stored response (if any) match those presented (see <a href="#caching.negotiated.responses" title="Caching Negotiated Responses">Section&nbsp;2.7</a>), and
780         </li>
781         <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.2" 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
782         </li>
783         <li>the stored response is either:
784            <ul>
785               <li>fresh (see <a href="#expiration.model" title="Freshness Model">Section&nbsp;2.3</a>), or
786               </li>
787               <li>allowed to be served stale (see <a href="#serving.stale.responses" title="Serving Stale Responses">Section&nbsp;2.3.3</a>), or
788               </li>
789               <li>successfully validated (see <a href="#validation.model" title="Validation Model">Section&nbsp;2.4</a>).
790               </li>
791            </ul> 
792         </li>
793      </ul>
794      <p id="rfc.section.2.2.p.2">When a stored response is used to satisfy a request without validation, a cache <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>.
795      </p>
796      <p id="rfc.section.2.2.p.3">A cache <em class="bcp14">MUST</em> write through 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>) to the origin server; i.e., a cache must not generate a reply to such a request before having forwarded the request and
797         having received a corresponding response.
798      </p>
799      <p id="rfc.section.2.2.p.4">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>.
800      </p>
801      <p id="rfc.section.2.2.p.5">A cache <em class="bcp14">MUST</em> use the most recent response (as determined by the Date header field) when more than one suitable response is stored. It can
802         also forward a request with "Cache-Control: max-age=0" or "Cache-Control: no-cache" to disambiguate which response to use.
803      </p>
804      <p id="rfc.section.2.2.p.6">A cache that does not have a clock available <em class="bcp14">MUST NOT</em> used stored responses without revalidating them on every use. A cache, especially a shared cache, <em class="bcp14">SHOULD</em> use a mechanism, such as NTP <a href="#RFC1305" id="rfc.xref.RFC1305.1"><cite title="Network Time Protocol (Version 3) Specification, Implementation">[RFC1305]</cite></a>, to synchronize its clock with a reliable external standard.
805      </p>
806      <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>
807      <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,
808         thereby improving efficiency.
809      </p>
810      <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,
811         using either the Expires header field (<a href="#header.expires" id="rfc.xref.header.expires.2" 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 representation
812         is not likely to change in a semantically significant way before the expiration time is reached.
813      </p>
814      <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
815         to indicate that the response is already stale. Compliant caches will normally validate the cached response before reusing
816         it for subsequent requests (see <a href="#serving.stale.responses" title="Serving Stale Responses">Section&nbsp;2.3.3</a>).
817      </p>
818      <p id="rfc.section.2.3.p.4">Since origin servers do not always provide explicit expiration times, a cache <em class="bcp14">MAY</em> assign a heuristic expiration time when an explicit time is not specified, employing algorithms that use other header field
819         values (such as the Last-Modified time) to estimate a plausible expiration time. This specification does not provide specific
820         algorithms, but does impose worst-case constraints on their results.
821      </p>
822      <div id="rfc.figure.u.3"></div> 
823      <p>The calculation to determine if a response is fresh is:</p>  <pre class="text">   response_is_fresh = (freshness_lifetime &gt; current_age)
824</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>.
825      </p>
826      <p id="rfc.section.2.3.p.7">Additionally, clients might need to influence freshness calculation. They can do this using several request cache directives,
827         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>.
828      </p>
829      <p id="rfc.section.2.3.p.8"> <span class="comment" id="ISSUE-no-req-for-directives">[<a href="#ISSUE-no-req-for-directives" class="smpl">ISSUE-no-req-for-directives</a>: there are not requirements directly applying to cache-request-directives and freshness.]</span> 
830      </p>
831      <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
832         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.
833      </p>
834      <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>
835      <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>
836      <ul>
837         <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
838         </li>
839         <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
840         </li>
841         <li>If the Expires response header field (<a href="#header.expires" id="rfc.xref.header.expires.3" title="Expires">Section&nbsp;3.3</a>) is present, use its value minus the value of the Date response header field, or
842         </li>
843         <li>Otherwise, no explicit expiration time is present in the response. A heuristic freshness lifetime might be applicable; see <a href="#heuristic.freshness" title="Calculating Heuristic Freshness">Section&nbsp;2.3.1.1</a>.
844         </li>
845      </ul>
846      <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>
847      <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>
848      <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 whose definition allows heuristic freshness
849         to be used (including the following in <a href="p2-semantics.html#status.codes" title="Status Code Definitions">Section 8</a> of <a href="#Part2" id="rfc.xref.Part2.2"><cite title="HTTP/1.1, part 2: Message Semantics">[Part2]</cite></a>: 200, 203, 206, 300, 301 and 410), a cache <em class="bcp14">MAY</em> calculate a heuristic expiration time. A cache <em class="bcp14">MUST NOT</em> use heuristics to determine freshness for responses with status codes that do not explicitly allow it.
850      </p>
851      <p id="rfc.section.2.3.1.1.p.2">When a heuristic is used to calculate freshness lifetime, a cache <em class="bcp14">SHOULD</em> attach a Warning header field with a 113 warn-code to the response if its current_age is more than 24 hours and such a warning
852         is not already present.
853      </p>
854      <p id="rfc.section.2.3.1.1.p.3">Also, if the response has a Last-Modified header field (<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>), a cache <em class="bcp14">SHOULD NOT</em> use a heuristic expiration value that is more than some fraction of the interval since that time. A typical setting of this
855         fraction might be 10%.
856      </p>
857      <div class="note" id="rfc.section.2.3.1.1.p.4"> 
858         <p> <b>Note:</b> RFC 2616 (<a href="#RFC2616" id="rfc.xref.RFC2616.1"><cite title="Hypertext Transfer Protocol -- HTTP/1.1">[RFC2616]</cite></a>, <a href="http://tools.ietf.org/html/rfc2616#section-13.9">Section 13.9</a>) required that caches do not calculate heuristic freshness for URLs with query components (i.e., those containing '?'). In
859            practice, this has not been widely implemented. Therefore, servers are encouraged to send explicit directives (e.g., Cache-Control:
860            no-cache) if they wish to preclude caching.
861         </p> 
862      </div>
863      <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>
864      <p id="rfc.section.2.3.2.p.1">HTTP/1.1 uses the Age response-header field to convey the estimated age of the response message when obtained from a cache.
865         The Age field value is the cache's estimate of the amount of time since the response was generated or validated by the origin
866         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
867         path from the origin server, plus the amount of time it has been in transit along network paths.
868      </p>
869      <p id="rfc.section.2.3.2.p.2">The following data is used for the age calculation:</p>
870      <p id="rfc.section.2.3.2.p.3"> <dfn>age_value</dfn> 
871      </p>
872      <ul class="empty">
873         <li>The term "age_value" denotes the value of the Age header field (<a href="#header.age" id="rfc.xref.header.age.2" title="Age">Section&nbsp;3.1</a>), in a form appropriate for arithmetic operation; or 0, if not available.
874         </li>
875      </ul>
876      <p id="rfc.section.2.3.2.p.4"> <dfn>date_value</dfn> 
877      </p>
878      <ul class="empty">
879         <li>HTTP/1.1 requires origin servers to send a Date header field, if possible, with every response, giving the time at which the
880            response was generated. The term "date_value" denotes the value of the Date header field, in a form appropriate for arithmetic
881            operations. See <a href="p1-messaging.html#header.date" title="Date">Section 9.3</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> for the definition of the Date header field, and for requirements regarding responses without it.
882         </li>
883      </ul>
884      <p id="rfc.section.2.3.2.p.5"> <dfn>now</dfn> 
885      </p>
886      <ul class="empty">
887         <li>The term "now" means "the current value of the clock at the host performing the calculation". A cache <em class="bcp14">SHOULD</em> use NTP (<a href="#RFC1305" id="rfc.xref.RFC1305.2"><cite title="Network Time Protocol (Version 3) Specification, Implementation">[RFC1305]</cite></a>) or some similar protocol to synchronize its clocks to a globally accurate time standard.
888         </li>
889      </ul>
890      <p id="rfc.section.2.3.2.p.6"> <dfn>request_time</dfn> 
891      </p>
892      <ul class="empty">
893         <li>The current value of the clock at the host at the time the request resulting in the stored response was made.</li>
894      </ul>
895      <p id="rfc.section.2.3.2.p.7"> <dfn>response_time</dfn> 
896      </p>
897      <ul class="empty">
898         <li>The current value of the clock at the host at the time the response was received.</li>
899      </ul>
900      <p id="rfc.section.2.3.2.p.8">A response's age can be calculated in two entirely independent ways: </p>
901      <ol>
902         <li>the "apparent_age": response_time minus date_value, if the local clock is reasonably well synchronized to the origin server's
903            clock. If the result is negative, the result is replaced by zero.
904         </li>
905         <li>the "corrected_age_value", if all of the caches along the response path implement HTTP/1.1. A cache <em class="bcp14">MUST</em> interpret this value relative to the time the request was initiated, not the time that the response was received.
906         </li>
907      </ol>
908      <div id="rfc.figure.u.4"></div> <pre class="text">  apparent_age = max(0, response_time - date_value);
909
910  response_delay = response_time - request_time;
911  corrected_age_value = age_value + response_delay; 
912</pre> <div id="rfc.figure.u.5"></div> 
913      <p>These are combined as</p>  <pre class="text">  corrected_initial_age = max(apparent_age, corrected_age_value);
914</pre><p id="rfc.section.2.3.2.p.11">The current_age of a stored response can then be calculated by adding the amount of time (in seconds) since the stored response
915         was last validated by the origin server to the corrected_initial_age.
916      </p>
917      <div id="rfc.figure.u.6"></div><pre class="text">  resident_time = now - response_time;
918  current_age = corrected_initial_age + resident_time;
919</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>
920      <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, but
921         is not fresh according to the calculations in <a href="#expiration.model" title="Freshness Model">Section&nbsp;2.3</a>.
922      </p>
923      <p id="rfc.section.2.3.3.p.2">A cache <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
924         directive, a "must-revalidate" cache-response-directive, or an applicable "s-maxage" or "proxy-revalidate" cache-response-directive;
925         see <a href="#cache-response-directive" title="Response Cache-Control Directives">Section&nbsp;3.2.2</a>).
926      </p>
927      <p id="rfc.section.2.3.3.p.3">A cache <em class="bcp14">SHOULD NOT</em> return stale responses unless it is disconnected (i.e., it cannot contact the origin server or otherwise find a forward path)
928         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>).
929      </p>
930      <p id="rfc.section.2.3.3.p.4">A cache <em class="bcp14">SHOULD</em> append a Warning header field with the 110 warn-code (see <a href="#header.warning" id="rfc.xref.header.warning.1" title="Warning">Section&nbsp;3.6</a>) to stale responses. Likewise, a cache <em class="bcp14">SHOULD</em> add the 112 warn-code to stale responses if the cache is disconnected.
931      </p>
932      <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
933         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 header fields).
934         A cache <em class="bcp14">SHOULD NOT</em> attempt to validate a response simply because that response became stale in transit.
935      </p>
936      <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>
937      <p id="rfc.section.2.4.p.1">When a cache has one or more stored responses for a requested URI, but cannot serve any of them (e.g., because they are not
938         fresh, or one cannot be selected; see <a href="#caching.negotiated.responses" title="Caching Negotiated Responses">Section&nbsp;2.7</a>), it can use the conditional request mechanism <a href="#Part4" id="rfc.xref.Part4.2"><cite title="HTTP/1.1, part 4: Conditional Requests">[Part4]</cite></a> in the forwarded request to give the origin server an opportunity to both select a valid stored response to be used, and to
939         update it. This process is known as "validating" or "revalidating" the stored response.
940      </p>
941      <p id="rfc.section.2.4.p.2">When sending such a conditional request, a cache <em class="bcp14">SHOULD</em> add an If-Modified-Since header field whose value is that of the Last-Modified header field from the selected (see <a href="#caching.negotiated.responses" title="Caching Negotiated Responses">Section&nbsp;2.7</a>) stored response, if available.
942      </p>
943      <p id="rfc.section.2.4.p.3">Additionally, a cache <em class="bcp14">SHOULD</em> add an If-None-Match header field whose value is that of the ETag header field(s) from all responses stored for the requested
944         URI, if present. However, if any of the stored responses contains only partial content, the cache <em class="bcp14">SHOULD NOT</em> include its entity-tag in the If-None-Match header field unless the request is for a range that would be fully satisfied by
945         that stored response.
946      </p>
947      <p id="rfc.section.2.4.p.4">A 304 (Not Modified) response status code indicates that the stored response can be updated and reused; see <a href="#combining.responses" title="Combining Responses">Section&nbsp;2.8</a>.
948      </p>
949      <p id="rfc.section.2.4.p.5">A full response (i.e., one with a response body) indicates that none of the stored responses nominated in the conditional
950         request is suitable. Instead, a cache <em class="bcp14">SHOULD</em> use the full response to satisfy the request and <em class="bcp14">MAY</em> replace the stored response.
951      </p>
952      <p id="rfc.section.2.4.p.6">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 (see <a href="#serving.stale.responses" title="Serving Stale Responses">Section&nbsp;2.3.3</a>).
953      </p>
954      <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>
955      <p id="rfc.section.2.5.p.1">Because unsafe request methods (<a href="p2-semantics.html#safe.methods" title="Safe Methods">Section 7.1.1</a> of <a href="#Part2" id="rfc.xref.Part2.3"><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.
956      </p>
957      <p id="rfc.section.2.5.p.2">A cache <em class="bcp14">MUST</em> invalidate the effective Request URI (<a href="p1-messaging.html#effective.request.uri" title="Effective Request URI">Section 4.3</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>) as well as the URI(s) in the Location and Content-Location header fields (if present) when the following request methods
958         are received:
959      </p>
960      <ul>
961         <li>PUT</li>
962         <li>DELETE</li>
963         <li>POST</li>
964      </ul>
965      <p id="rfc.section.2.5.p.3">However, a cache <em class="bcp14">MUST NOT</em> invalidate a URI from a Location or Content-Location header field if the host part of that URI differs from the host part
966         in the effective request URI (<a href="p1-messaging.html#effective.request.uri" title="Effective Request URI">Section 4.3</a> of <a href="#Part1" id="rfc.xref.Part1.14"><cite title="HTTP/1.1, part 1: URIs, Connections, and Message Parsing">[Part1]</cite></a>). This helps prevent denial of service attacks.
967      </p>
968      <p id="rfc.section.2.5.p.4">A cache that passes through requests with methods it does not understand <em class="bcp14">SHOULD</em> invalidate the effective request URI (<a href="p1-messaging.html#effective.request.uri" title="Effective Request URI">Section 4.3</a> of <a href="#Part1" id="rfc.xref.Part1.15"><cite title="HTTP/1.1, part 1: URIs, Connections, and Message Parsing">[Part1]</cite></a>).
969      </p>
970      <p id="rfc.section.2.5.p.5">Here, "invalidate" means that the cache will either remove all stored responses related to the effective request URI, or will
971         mark these as "invalid" and in need of a mandatory validation before they can be returned in response to a subsequent request.
972      </p>
973      <p id="rfc.section.2.5.p.6">Note that this does not guarantee that all appropriate responses are invalidated. For example, the request that caused the
974         change at the origin server might not have gone through the cache where a response is stored.
975      </p>
976      <h2 id="rfc.section.2.6"><a href="#rfc.section.2.6">2.6</a>&nbsp;<a id="caching.authenticated.responses" href="#caching.authenticated.responses">Shared Caching of Authenticated Responses</a></h2>
977      <p id="rfc.section.2.6.p.1">A shared cache <em class="bcp14">MUST NOT</em> use a cached response to a request with an Authorization header field (<a href="p7-auth.html#header.authorization" title="Authorization">Section 4.1</a> of <a href="#Part7" id="rfc.xref.Part7.2"><cite title="HTTP/1.1, part 7: Authentication">[Part7]</cite></a>) to satisfy any subsequent request unless a cache directive that allows such responses to be stored is present in the response.
978      </p>
979      <p id="rfc.section.2.6.p.2">In this specification, the following Cache-Control response directives (<a href="#cache-response-directive" title="Response Cache-Control Directives">Section&nbsp;3.2.2</a>) have such an effect: must-revalidate, public, s-maxage.
980      </p>
981      <p id="rfc.section.2.6.p.3">Note that cached responses that contain the "must-revalidate" and/or "s-maxage" response directives are not allowed to be
982         served stale (<a href="#serving.stale.responses" title="Serving Stale Responses">Section&nbsp;2.3.3</a>) by shared caches. In particular, a response with either "max-age=0, must-revalidate" or "s-maxage=0" cannot be used to satisfy
983         a subsequent request without revalidating it on the origin server.
984      </p>
985      <h2 id="rfc.section.2.7"><a href="#rfc.section.2.7">2.7</a>&nbsp;<a id="caching.negotiated.responses" href="#caching.negotiated.responses">Caching Negotiated Responses</a></h2>
986      <p id="rfc.section.2.7.p.1">When a cache receives a request that can be satisfied by a stored response that has 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-header fields nominated by the Vary header field match in both the original
987         request (i.e., that associated with the stored response), and the presented request.
988      </p>
989      <p id="rfc.section.2.7.p.2">The selecting request-header fields from two requests are defined to match if and only if those in the first request can be
990         transformed to those in the second request by applying any of the following:
991      </p>
992      <ul>
993         <li>adding or removing whitespace, where allowed in the header field's syntax</li>
994         <li>combining multiple message-header fields with the same field name (see <a href="p1-messaging.html#header.fields" title="Header Fields">Section 3.2</a> of <a href="#Part1" id="rfc.xref.Part1.16"><cite title="HTTP/1.1, part 1: URIs, Connections, and Message Parsing">[Part1]</cite></a>)
995         </li>
996         <li>normalizing both header field values in a way that is known to have identical semantics, according to the header field's specification
997            (e.g., re-ordering field values when order is not significant; case-normalization, where values are defined to be case-insensitive)
998         </li>
999      </ul>
1000      <p id="rfc.section.2.7.p.3">If (after any normalization that might take place) a header field is absent from a request, it can only match another request
1001         if it is also absent there.
1002      </p>
1003      <p id="rfc.section.2.7.p.4">A Vary header field-value of "*" always fails to match, and subsequent requests to that resource can only be properly interpreted
1004         by the origin server.
1005      </p>
1006      <p id="rfc.section.2.7.p.5">The stored response with matching selecting request-header fields is known as the selected response.</p>
1007      <p id="rfc.section.2.7.p.6">If no selected response is available, the cache <em class="bcp14">MAY</em> forward the presented request to the origin server in a conditional request; see <a href="#validation.model" title="Validation Model">Section&nbsp;2.4</a>.
1008      </p>
1009      <h2 id="rfc.section.2.8"><a href="#rfc.section.2.8">2.8</a>&nbsp;<a id="combining.responses" href="#combining.responses">Combining Responses</a></h2>
1010      <p id="rfc.section.2.8.p.1">When a cache receives a 304 (Not Modified) response or a 206 (Partial Content) response (in this section, the "new" response"),
1011         it needs to create an updated response by combining the stored response with the new one, so that the updated response can
1012         be used to satisfy the request, and potentially update the cached response.
1013      </p>
1014      <p id="rfc.section.2.8.p.2">If the new response contains an ETag, it identifies the stored response to use. <span class="comment" id="TODO-mention-CL">[<a href="#TODO-mention-CL" class="smpl">TODO-mention-CL</a>: might need language about Content-Location here]</span><span class="comment" id="TODO-select-for-combine">[<a href="#TODO-select-for-combine" class="smpl">TODO-select-for-combine</a>: Shouldn't this be the selected response?]</span> 
1015      </p>
1016      <p id="rfc.section.2.8.p.3">When the new response's status code is 206 (partial content), a cache <em class="bcp14">MUST NOT</em> combine it with the old response if either response does not have a validator, and <em class="bcp14">MUST NOT</em> combine it with the old response when those validators do not match with the strong comparison function (see <a href="p4-conditional.html#weak.and.strong.validators" title="Weak and Strong Validators">Section 4</a> of <a href="#Part4" id="rfc.xref.Part4.3"><cite title="HTTP/1.1, part 4: Conditional Requests">[Part4]</cite></a>).
1017      </p>
1018      <p id="rfc.section.2.8.p.4">The stored response header fields are used as those of the updated response, except that </p>
1019      <ul>
1020         <li>a cache <em class="bcp14">MUST</em> delete any stored Warning header fields with warn-code 1xx (see <a href="#header.warning" id="rfc.xref.header.warning.2" title="Warning">Section&nbsp;3.6</a>).
1021         </li>
1022         <li>a cache <em class="bcp14">MUST</em> retain any stored Warning header fields with warn-code 2xx.
1023         </li>
1024         <li>a cache <em class="bcp14">MUST</em> use other header fields provided in the new response to replace all instances of the corresponding header fields from the
1025            stored response.
1026         </li>
1027      </ul>
1028      <p id="rfc.section.2.8.p.5">A cache <em class="bcp14">MUST</em> use the updated response header fields to replace those of the stored response (unless the stored response is removed). In
1029         the case of a 206 response, a cache <em class="bcp14">MAY</em> store the combined representation.
1030      </p>
1031      <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>
1032      <p id="rfc.section.3.p.1">This section defines the syntax and semantics of HTTP/1.1 header fields related to caching.</p>
1033      <div id="rfc.iref.a.2"></div>
1034      <div id="rfc.iref.h.2"></div>
1035      <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>
1036      <p id="rfc.section.3.1.p.1">The "Age" response-header field conveys the sender's estimate of the amount of time since the response was generated or successfully
1037         validated at the origin server. Age values are calculated as specified in <a href="#age.calculations" title="Calculating Age">Section&nbsp;2.3.2</a>.
1038      </p>
1039      <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>
1040  <a href="#header.age" class="smpl">Age-v</a> = <a href="#rule.delta-seconds" class="smpl">delta-seconds</a>
1041</pre><div id="rule.delta-seconds">
1042         <p id="rfc.section.3.1.p.3">  Age field-values are non-negative integers, representing time in seconds.</p>
1043      </div>
1044      <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>
1045</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,
1046         it <em class="bcp14">MUST</em> transmit an Age header field with a field-value of 2147483648 (2<sup>31</sup>). Recipients parsing the Age header field-value <em class="bcp14">SHOULD</em> use an arithmetic type of at least 31 bits of range.
1047      </p>
1048      <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
1049         true, since HTTP/1.0 caches might not implement the Age header field.
1050      </p>
1051      <div id="rfc.iref.c.4"></div>
1052      <div id="rfc.iref.h.3"></div>
1053      <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>
1054      <p id="rfc.section.3.2.p.1">The "Cache-Control" general-header field is used to specify directives for caches along the request/response chain. Such cache
1055         directives are unidirectional in that the presence of a directive in a request does not imply that the same directive is to
1056         be given in the response.
1057      </p>
1058      <p id="rfc.section.3.2.p.2">A cache <em class="bcp14">MUST</em> obey the requirements of the Cache-Control directives defined in this section. See <a href="#cache.control.extensions" title="Cache Control Extensions">Section&nbsp;3.2.3</a> for information about how Cache-Control directives defined elsewhere are handled.
1059      </p>
1060      <div class="note" id="rfc.section.3.2.p.3"> 
1061         <p> <b>Note:</b> 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>).
1062         </p> 
1063      </div>
1064      <p id="rfc.section.3.2.p.4">An intermediary (i.e., a proxy or gateway, whether or not it implements a cache) <em class="bcp14">MUST</em> pass cache directives through, regardless of their significance to that application, since the directives might be applicable
1065         to all recipients along the request/response chain. It is not possible to target a directive to a specific cache.
1066      </p>
1067      <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>
1068  <a href="#header.cache-control" class="smpl">Cache-Control-v</a> = 1#<a href="#header.cache-control" class="smpl">cache-directive</a>
1069
1070  <a href="#header.cache-control" class="smpl">cache-directive</a> = <a href="#header.cache-control" class="smpl">cache-request-directive</a>
1071     / <a href="#header.cache-control" class="smpl">cache-response-directive</a>
1072
1073  <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> ) ]
1074</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>
1075      <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> =
1076       "no-cache"
1077     / "no-store"
1078     / "max-age" "=" <a href="#rule.delta-seconds" class="smpl">delta-seconds</a>
1079     / "max-stale" [ "=" <a href="#rule.delta-seconds" class="smpl">delta-seconds</a> ]
1080     / "min-fresh" "=" <a href="#rule.delta-seconds" class="smpl">delta-seconds</a>
1081     / "no-transform"
1082     / "only-if-cached"
1083     / <a href="#header.cache-control" class="smpl">cache-extension</a>
1084</pre><p id="rfc.section.3.2.1.p.2"> <dfn>no-cache</dfn>  <span id="rfc.iref.c.5"></span>  <span id="rfc.iref.n.1"></span> 
1085      </p>
1086      <ul class="empty">
1087         <li>The no-cache request directive indicates that a cache <em class="bcp14">MUST NOT</em> use a stored response to satisfy the request without successful validation on the origin server.
1088         </li>
1089      </ul>
1090      <p id="rfc.section.3.2.1.p.3"> <dfn>no-store</dfn>  <span id="rfc.iref.c.6"></span>  <span id="rfc.iref.n.2"></span> 
1091      </p>
1092      <ul class="empty">
1093         <li>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 private 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.
1094         </li>
1095         <li>This directive is NOT a reliable or sufficient mechanism for ensuring privacy. In particular, malicious or compromised caches
1096            might not recognize or obey this directive, and communications networks might be vulnerable to eavesdropping.
1097         </li>
1098         <li>Note that if a request containing this directive is satisfied from a cache, the no-store request directive does not apply
1099            to the already stored response.
1100         </li>
1101      </ul>
1102      <p id="rfc.section.3.2.1.p.4"> <dfn>max-age</dfn>  <span id="rfc.iref.c.7"></span>  <span id="rfc.iref.m.1"></span> 
1103      </p>
1104      <ul class="empty">
1105         <li>The max-age request directive indicates that the client is willing to accept a response whose age is no greater than the specified
1106            time in seconds. Unless the max-stale request directive is also present, the client is not willing to accept a stale response.
1107         </li>
1108      </ul>
1109      <p id="rfc.section.3.2.1.p.5"> <dfn>max-stale</dfn>  <span id="rfc.iref.c.8"></span>  <span id="rfc.iref.m.2"></span> 
1110      </p>
1111      <ul class="empty">
1112         <li>The max-stale request directive indicates that the client is willing to accept a response that has exceeded its expiration
1113            time. If max-stale is assigned a value, then the client is willing to accept a response that has exceeded its expiration time
1114            by no more than the specified number of seconds. If no value is assigned to max-stale, then the client is willing to accept
1115            a stale response of any age.
1116         </li>
1117      </ul>
1118      <p id="rfc.section.3.2.1.p.6"> <dfn>min-fresh</dfn>  <span id="rfc.iref.c.9"></span>  <span id="rfc.iref.m.3"></span> 
1119      </p>
1120      <ul class="empty">
1121         <li>The min-fresh request directive indicates that the client is willing to accept a response whose freshness lifetime is no less
1122            than its current age plus the specified time in seconds. That is, the client wants a response that will still be fresh for
1123            at least the specified number of seconds.
1124         </li>
1125      </ul>
1126      <p id="rfc.section.3.2.1.p.7"> <dfn>no-transform</dfn>  <span id="rfc.iref.c.10"></span>  <span id="rfc.iref.n.3"></span> 
1127      </p>
1128      <ul class="empty">
1129         <li>The no-transform request directive indicates that an intermediary (whether or not it implements a cache) <em class="bcp14">MUST NOT</em> change the Content-Encoding, Content-Range or Content-Type request header fields, nor the request representation.
1130         </li>
1131      </ul>
1132      <p id="rfc.section.3.2.1.p.8"> <dfn>only-if-cached</dfn>  <span id="rfc.iref.c.11"></span>  <span id="rfc.iref.o.1"></span> 
1133      </p>
1134      <ul class="empty">
1135         <li>The only-if-cached request directive indicates that the client only wishes to return a stored response. If it receives this
1136            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
1137            (Gateway Timeout) status code. If a group of caches is being operated as a unified system with good internal connectivity,
1138            a member cache <em class="bcp14">MAY</em> forward such a request within that group of caches.
1139         </li>
1140      </ul>
1141      <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>
1142      <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> =
1143       "public"
1144     / "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> ]
1145     / "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> ]
1146     / "no-store"
1147     / "no-transform"
1148     / "must-revalidate"
1149     / "proxy-revalidate"
1150     / "max-age" "=" <a href="#rule.delta-seconds" class="smpl">delta-seconds</a>
1151     / "s-maxage" "=" <a href="#rule.delta-seconds" class="smpl">delta-seconds</a>
1152     / <a href="#header.cache-control" class="smpl">cache-extension</a>
1153</pre><p id="rfc.section.3.2.2.p.2"> <dfn>public</dfn>  <span id="rfc.iref.c.12"></span>  <span id="rfc.iref.p.2"></span> 
1154      </p>
1155      <ul class="empty">
1156         <li>The public response directive indicates that a cache <em class="bcp14">MAY</em> store the response, even if it would normally be non-cacheable or cacheable only within a private cache. (See also Authorization, <a href="p7-auth.html#header.authorization" title="Authorization">Section 4.1</a> of <a href="#Part7" id="rfc.xref.Part7.3"><cite title="HTTP/1.1, part 7: Authentication">[Part7]</cite></a>, for additional details.)
1157         </li>
1158      </ul>
1159      <p id="rfc.section.3.2.2.p.3"> <dfn>private</dfn>  <span id="rfc.iref.c.13"></span>  <span id="rfc.iref.p.3"></span> 
1160      </p>
1161      <ul class="empty">
1162         <li>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 cache <em class="bcp14">MAY</em> store the response.
1163         </li>
1164         <li>If the private response directive specifies one or more field-names, this requirement is limited to the field-values associated
1165            with the listed response header fields. That is, a shared cache <em class="bcp14">MUST NOT</em> store the specified field-names(s), whereas it <em class="bcp14">MAY</em> store the remainder of the response message.
1166         </li>
1167         <li> <b>Note:</b> This usage of the word private only controls where the response can be stored; it cannot ensure the privacy of the message
1168            content. Also, private response directives with field-names are often handled by implementations as if an unqualified private
1169            directive was received; i.e., the special handling for the qualified form is not widely implemented.
1170         </li>
1171      </ul>
1172      <p id="rfc.section.3.2.2.p.4"> <dfn>no-cache</dfn>  <span id="rfc.iref.c.14"></span>  <span id="rfc.iref.n.4"></span> 
1173      </p>
1174      <ul class="empty">
1175         <li>The no-cache response directive indicates that the response MUST NOT be used to satisfy a subsequent request without successful
1176            validation on the origin server. This allows an origin server to prevent a cache from using it to satisfy a request without
1177            contacting it, even by caches that have been configured to return stale responses.
1178         </li>
1179         <li>If the no-cache response directive specifies one or more field-names, this requirement is limited to the field-values associated
1180            with the listed response header fields. That is, a cache <em class="bcp14">MUST NOT</em> send the specified field-name(s) in the response to a subsequent request without successful validation on the origin server.
1181            This allows an origin server to prevent the re-use of certain header fields in a response, while still allowing caching of
1182            the rest of the response.
1183         </li>
1184         <li> <b>Note:</b> Most HTTP/1.0 caches will not recognize or obey this directive. Also, no-cache response directives with field-names are often
1185            handled by implementations as if an unqualified no-cache directive was received; i.e., the special handling for the qualified
1186            form is not widely implemented.
1187         </li>
1188      </ul>
1189      <p id="rfc.section.3.2.2.p.5"> <dfn>no-store</dfn>  <span id="rfc.iref.c.15"></span>  <span id="rfc.iref.n.5"></span> 
1190      </p>
1191      <ul class="empty">
1192         <li>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 private 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.
1193         </li>
1194         <li>This directive is NOT a reliable or sufficient mechanism for ensuring privacy. In particular, malicious or compromised caches
1195            might not recognize or obey this directive, and communications networks might be vulnerable to eavesdropping.
1196         </li>
1197      </ul>
1198      <p id="rfc.section.3.2.2.p.6"> <dfn>must-revalidate</dfn>  <span id="rfc.iref.c.16"></span>  <span id="rfc.iref.m.4"></span> 
1199      </p>
1200      <ul class="empty">
1201         <li>The must-revalidate response directive indicates that once it has become stale, a cache <em class="bcp14">MUST NOT</em> use the response to satisfy subsequent requests without successful validation on the origin server.
1202         </li>
1203         <li>The must-revalidate directive is necessary to support reliable operation for certain protocol features. In all circumstances
1204            a cache <em class="bcp14">MUST</em> obey the must-revalidate directive; in particular, if a cache cannot reach the origin server for any reason, it <em class="bcp14">MUST</em> generate a 504 (Gateway Timeout) response.
1205         </li>
1206         <li>A server <em class="bcp14">SHOULD</em> send the must-revalidate directive if and only if failure to validate a request on the representation could result in incorrect
1207            operation, such as a silently unexecuted financial transaction.
1208         </li>
1209      </ul>
1210      <p id="rfc.section.3.2.2.p.7"> <dfn>proxy-revalidate</dfn>  <span id="rfc.iref.c.17"></span>  <span id="rfc.iref.p.4"></span> 
1211      </p>
1212      <ul class="empty">
1213         <li>The proxy-revalidate response directive has the same meaning as the must-revalidate response directive, except that it does
1214            not apply to private caches.
1215         </li>
1216      </ul>
1217      <p id="rfc.section.3.2.2.p.8"> <dfn>max-age</dfn>  <span id="rfc.iref.c.18"></span>  <span id="rfc.iref.m.5"></span> 
1218      </p>
1219      <ul class="empty">
1220         <li>The max-age response directive indicates that response is to be considered stale after its age is greater than the specified
1221            number of seconds.
1222         </li>
1223      </ul>
1224      <p id="rfc.section.3.2.2.p.9"> <dfn>s-maxage</dfn>  <span id="rfc.iref.c.19"></span>  <span id="rfc.iref.s.3"></span> 
1225      </p>
1226      <ul class="empty">
1227         <li>The s-maxage response directive indicates that, in shared caches, the maximum age specified by this directive overrides the
1228            maximum age specified by either the max-age directive or the Expires header field. The s-maxage directive also implies the
1229            semantics of the proxy-revalidate response directive.
1230         </li>
1231      </ul>
1232      <p id="rfc.section.3.2.2.p.10"> <dfn>no-transform</dfn>  <span id="rfc.iref.c.20"></span>  <span id="rfc.iref.n.6"></span> 
1233      </p>
1234      <ul class="empty">
1235         <li>The no-transform response directive indicates that an intermediary (regardless of whether it implements a cache) <em class="bcp14">MUST NOT</em> change the Content-Encoding, Content-Range or Content-Type response header fields, nor the response representation.
1236         </li>
1237      </ul>
1238      <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>
1239      <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
1240         value. Informational extensions (those that do not require a change in cache behavior) can be added without changing the semantics
1241         of other directives. Behavioral extensions are designed to work by acting as modifiers to the existing base of cache directives.
1242         Both the new directive and the standard directive are supplied, such that applications that do not understand the new directive
1243         will default to the behavior specified by the standard directive, and those that understand the new directive will recognize
1244         it as modifying the requirements associated with the standard directive. In this way, extensions to the cache-control directives
1245         can be made without requiring changes to the base protocol.
1246      </p>
1247      <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,
1248         obeying certain extensions, and ignoring all directives that it does not understand.
1249      </p>
1250      <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.
1251         We define this new directive to mean that, in addition to any private cache, any cache that is shared only by members of the
1252         community named within its value may cache the response. An origin server wishing to allow the UCI community to use an otherwise
1253         private response in their shared cache(s) could do so by including
1254      </p>
1255      <div id="rfc.figure.u.12"></div><pre class="text">  Cache-Control: private, community="UCI"
1256</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
1257         it will also see and understand the private directive and thus default to the safe behavior.
1258      </p>
1259      <p id="rfc.section.3.2.3.p.6">A cache <em class="bcp14">MUST</em> be ignore unrecognized cache directives; it is assumed that any cache directive likely to be unrecognized by an HTTP/1.1 cache
1260         will be combined with standard directives (or the response's default cacheability) such that the cache behavior will remain
1261         minimally correct even if the cache does not understand the extension(s).
1262      </p>
1263      <p id="rfc.section.3.2.3.p.7">The HTTP Cache Directive Registry defines the name space for the cache directives.</p>
1264      <p id="rfc.section.3.2.3.p.8">A registration <em class="bcp14">MUST</em> include the following fields:
1265      </p>
1266      <ul>
1267         <li>Cache Directive Name</li>
1268         <li>Pointer to specification text</li>
1269      </ul>
1270      <p id="rfc.section.3.2.3.p.9">Values to be added to this name space are subject to IETF review (<a href="#RFC5226" id="rfc.xref.RFC5226.1"><cite title="Guidelines for Writing an IANA Considerations Section in RFCs">[RFC5226]</cite></a>, <a href="http://tools.ietf.org/html/rfc5226#section-4.1">Section 4.1</a>).
1271      </p>
1272      <p id="rfc.section.3.2.3.p.10">The registry itself is maintained at &lt;<a href="http://www.iana.org/assignments/http-cache-directives">http://www.iana.org/assignments/http-cache-directives</a>&gt;.
1273      </p>
1274      <div id="rfc.iref.e.2"></div>
1275      <div id="rfc.iref.h.4"></div>
1276      <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>
1277      <p id="rfc.section.3.3.p.1">The "Expires" header field 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.
1278      </p>
1279      <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
1280         that time.
1281      </p>
1282      <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#date.time.formats.full.date" title="Date/Time Formats: Full Date">Section 6.1</a> of <a href="#Part1" id="rfc.xref.Part1.17"><cite title="HTTP/1.1, part 1: URIs, Connections, and Message Parsing">[Part1]</cite></a>; a sender <em class="bcp14">MUST</em> use the rfc1123-date format.
1283      </p>
1284      <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>
1285  <a href="#header.expires" class="smpl">Expires-v</a> = <a href="#abnf.dependencies" class="smpl">HTTP-date</a>
1286</pre><div id="rfc.figure.u.14"></div> 
1287      <p>For example</p>  <pre class="text">  Expires: Thu, 01 Dec 1994 16:00:00 GMT
1288</pre><div class="note" id="rfc.section.3.3.p.6"> 
1289         <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.
1290         </p> 
1291      </div>
1292      <p id="rfc.section.3.3.p.7">A server <em class="bcp14">SHOULD NOT</em> send Expires dates more than one year in the future.
1293      </p>
1294      <p id="rfc.section.3.3.p.8">A cache <em class="bcp14">MUST</em> treat other invalid date formats, especially including the value "0", as in the past (i.e., "already expired").
1295      </p>
1296      <div id="rfc.iref.p.5"></div>
1297      <div id="rfc.iref.h.5"></div>
1298      <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>
1299      <p id="rfc.section.3.4.p.1">The "Pragma" general-header field is used to include implementation-specific directives that might apply to any recipient
1300         along the request/response chain. All pragma directives specify optional behavior from the viewpoint of the protocol; however,
1301         some systems <em class="bcp14">MAY</em> require that behavior be consistent with the directives.
1302      </p>
1303      <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>
1304  <a href="#header.pragma" class="smpl">Pragma-v</a>          = 1#<a href="#header.pragma" class="smpl">pragma-directive</a>
1305  <a href="#header.pragma" class="smpl">pragma-directive</a>  = "no-cache" / <a href="#header.pragma" class="smpl">extension-pragma</a>
1306  <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> ) ]
1307</pre><p id="rfc.section.3.4.p.3">When the no-cache directive is present in a request message, a cache <em class="bcp14">SHOULD</em> forward the request toward the origin server even if it has a stored copy of what is being requested. This pragma directive
1308         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. A client <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. A cache <em class="bcp14">SHOULD</em> treat "Pragma: no-cache" as if the client had sent "Cache-Control: no-cache".
1309      </p>
1310      <div class="note" id="rfc.section.3.4.p.4"> 
1311         <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
1312            replacement for "Cache-Control: no-cache" in a response.
1313         </p> 
1314      </div>
1315      <p id="rfc.section.3.4.p.5">This mechanism is deprecated; no new Pragma directives will be defined in HTTP.</p>
1316      <div id="rfc.iref.v.2"></div>
1317      <div id="rfc.iref.h.6"></div>
1318      <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>
1319      <p id="rfc.section.3.5.p.1">The "Vary" response-header field conveys the set of request-header fields that were used to select the representation.</p>
1320      <p id="rfc.section.3.5.p.2">Caches use this information, in part, to determine whether a stored response can be used to satisfy a given request; see <a href="#caching.negotiated.responses" title="Caching Negotiated Responses">Section&nbsp;2.7</a>. determines, while the response is fresh, whether a cache is permitted to use the response to reply to a subsequent request
1321         without validation; see <a href="#caching.negotiated.responses" title="Caching Negotiated Responses">Section&nbsp;2.7</a>.
1322      </p>
1323      <p id="rfc.section.3.5.p.3">In uncacheable or stale responses, the Vary field value advises the user agent about the criteria that were used to select
1324         the representation.
1325      </p>
1326      <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>
1327  <a href="#header.vary" class="smpl">Vary-v</a> = "*" / 1#<a href="#abnf.dependencies" class="smpl">field-name</a>
1328</pre><p id="rfc.section.3.5.p.5">The set of header fields named by the Vary field value is known as the selecting request-header fields.</p>
1329      <p id="rfc.section.3.5.p.6">A server <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
1330         to properly interpret future requests on that resource and informs the user agent about the presence of negotiation on that
1331         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
1332         the user agent with useful information about the dimensions over which the response varies at the time of the response.
1333      </p>
1334      <p id="rfc.section.3.5.p.7">A Vary field value of "*" signals that unspecified parameters not limited to the request-header fields (e.g., the network
1335         address of the client), play a role in the selection of the response representation; therefore, a cache cannot determine whether
1336         this response is appropriate. A proxy <em class="bcp14">MUST NOT</em> generate the "*" value.
1337      </p>
1338      <p id="rfc.section.3.5.p.8">The field-names given are not limited to the set of standard request-header fields defined by this specification. Field names
1339         are case-insensitive.
1340      </p>
1341      <div id="rfc.iref.w.1"></div>
1342      <div id="rfc.iref.h.7"></div>
1343      <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>
1344      <p id="rfc.section.3.6.p.1">The "Warning" general-header field is used to carry additional information about the status or transformation of a message
1345         that might not be reflected in the message. This information is typically used to warn about possible incorrectness introduced
1346         by caching operations or transformations applied to the payload of the message.
1347      </p>
1348      <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
1349         code, distinguishes these responses from true failures.
1350      </p>
1351      <p id="rfc.section.3.6.p.3">Warning header fields can in general be applied to any message, however some warn-codes are specific to caches and can only
1352         be applied to response messages.
1353      </p>
1354      <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>
1355  <a href="#header.warning" class="smpl">Warning-v</a>  = 1#<a href="#header.warning" class="smpl">warning-value</a>
1356 
1357  <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>
1358                                        [<a href="#notation" class="smpl">SP</a> <a href="#header.warning" class="smpl">warn-date</a>]
1359 
1360  <a href="#header.warning" class="smpl">warn-code</a>  = 3<a href="#notation" class="smpl">DIGIT</a>
1361  <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>
1362                  ; the name or pseudonym of the server adding
1363                  ; the Warning header field, for use in debugging
1364  <a href="#header.warning" class="smpl">warn-text</a>  = <a href="#core.rules" class="smpl">quoted-string</a>
1365  <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>
1366</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
1367         the same code number, only differing in warn-text.
1368      </p>
1369      <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.
1370      </p>
1371      <p id="rfc.section.3.6.p.7">Systems that generate multiple Warning header fields <em class="bcp14">SHOULD</em> order them with this user agent behavior in mind. New Warning header fields <em class="bcp14">SHOULD</em> be added after any existing Warning headers fields.
1372      </p>
1373      <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
1374         a stored response after validation:
1375      </p>
1376      <ul>
1377         <li>1xx Warnings describe the freshness or validation status of the response, and so <em class="bcp14">MUST</em> be deleted by a cache after validation. They can only be generated by a cache when validating a cached entry, and <em class="bcp14">MUST NOT</em> be generated in any other situation.
1378         </li>
1379         <li>2xx Warnings describe some aspect of the representation that is not rectified by a validation (for example, a lossy compression
1380            of the representation) and <em class="bcp14">MUST NOT</em> be deleted by a cache after validation, unless a full response is returned, in which case they <em class="bcp14">MUST</em> be.
1381         </li>
1382      </ul>
1383      <p id="rfc.section.3.6.p.9">If an implementation sends a message with one or more Warning header fields to a receiver whose version is HTTP/1.0 or lower,
1384         then the sender <em class="bcp14">MUST</em> include in each warning-value a warn-date that matches the Date header field in the message.
1385      </p>
1386      <p id="rfc.section.3.6.p.10">If a system receives a message with a warning-value that includes a warn-date, and that warn-date is different from the Date
1387         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
1388         header fields.) If all of the warning-values are deleted for this reason, the Warning header field <em class="bcp14">MUST</em> be deleted as well.
1389      </p>
1390      <p id="rfc.section.3.6.p.11">The following warn-codes are defined by this specification, each with a recommended warn-text in English, and a description
1391         of its meaning.
1392      </p>
1393      <p id="rfc.section.3.6.p.12"> 110 Response is stale </p>
1394      <ul class="empty">
1395         <li>A cache <em class="bcp14">SHOULD</em> include this whenever the returned response is stale.
1396         </li>
1397      </ul>
1398      <p id="rfc.section.3.6.p.13"> 111 Revalidation failed </p>
1399      <ul class="empty">
1400         <li>A cache <em class="bcp14">SHOULD</em> include this when returning a stale response because an attempt to validate the response failed, due to an inability to reach
1401            the server.
1402         </li>
1403      </ul>
1404      <p id="rfc.section.3.6.p.14"> 112 Disconnected operation </p>
1405      <ul class="empty">
1406         <li>A cache <em class="bcp14">SHOULD</em> b include this if it is intentionally disconnected from the rest of the network for a period of time.
1407         </li>
1408      </ul>
1409      <p id="rfc.section.3.6.p.15"> 113 Heuristic expiration </p>
1410      <ul class="empty">
1411         <li>A cache <em class="bcp14">SHOULD</em> include this if it heuristically chose a freshness lifetime greater than 24 hours and the response's age is greater than 24
1412            hours.
1413         </li>
1414      </ul>
1415      <p id="rfc.section.3.6.p.16"> 199 Miscellaneous warning </p>
1416      <ul class="empty">
1417         <li>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.
1418         </li>
1419      </ul>
1420      <p id="rfc.section.3.6.p.17"> 214 Transformation applied </p>
1421      <ul class="empty">
1422         <li><em class="bcp14">MUST</em> be added by a proxy if it applies any transformation to the representation, such as changing the content-coding, media-type,
1423            or modifying the representation data, unless this Warning code already appears in the response.
1424         </li>
1425      </ul>
1426      <p id="rfc.section.3.6.p.18"> 299 Miscellaneous persistent warning </p>
1427      <ul class="empty">
1428         <li>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.
1429         </li>
1430      </ul>
1431      <h1 id="rfc.section.4"><a href="#rfc.section.4">4.</a>&nbsp;<a id="history.lists" href="#history.lists">History Lists</a></h1>
1432      <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 a representation
1433         retrieved earlier in a session.
1434      </p>
1435      <p id="rfc.section.4.p.2">The freshness model (<a href="#expiration.model" title="Freshness Model">Section&nbsp;2.3</a>) does not necessarily apply to history mechanisms. I.e., a history mechanism can display a previous representation even if
1436         it has expired.
1437      </p>
1438      <p id="rfc.section.4.p.3">This does not prohibit the history mechanism from telling the user that a view might be stale, or from honoring cache directives
1439         (e.g., Cache-Control: no-store).
1440      </p>
1441      <h1 id="rfc.section.5"><a href="#rfc.section.5">5.</a>&nbsp;<a id="IANA.considerations" href="#IANA.considerations">IANA Considerations</a></h1>
1442      <h2 id="rfc.section.5.1"><a href="#rfc.section.5.1">5.1</a>&nbsp;<a id="cache.directive.registration" href="#cache.directive.registration">Cache Directive Registry</a></h2>
1443      <p id="rfc.section.5.1.p.1">The registration procedure for HTTP Cache Directives is defined by <a href="#cache.control.extensions" title="Cache Control Extensions">Section&nbsp;3.2.3</a> of this document.
1444      </p>
1445      <p id="rfc.section.5.1.p.2">The HTTP Cache Directive Registry shall be created at &lt;<a href="http://www.iana.org/assignments/http-cache-directives">http://www.iana.org/assignments/http-cache-directives</a>&gt; and be populated with the registrations below:
1446      </p>
1447      <div id="rfc.table.1">
1448         <div id="iana.cache.directive.registration.table"></div>
1449         <table class="tt full left" cellpadding="3" cellspacing="0">
1450            <thead>
1451               <tr>
1452                  <th>Cache Directive</th>
1453                  <th>Reference</th>
1454               </tr>
1455            </thead>
1456            <tbody>
1457               <tr>
1458                  <td class="left">max-age</td>
1459                  <td class="left"> <a href="#cache-request-directive" title="Request Cache-Control Directives">Section&nbsp;3.2.1</a>, <a href="#cache-response-directive" title="Response Cache-Control Directives">Section&nbsp;3.2.2</a> 
1460                  </td>
1461               </tr>
1462               <tr>
1463                  <td class="left">max-stale</td>
1464                  <td class="left"> <a href="#cache-request-directive" title="Request Cache-Control Directives">Section&nbsp;3.2.1</a> 
1465                  </td>
1466               </tr>
1467               <tr>
1468                  <td class="left">min-fresh</td>
1469                  <td class="left"> <a href="#cache-request-directive" title="Request Cache-Control Directives">Section&nbsp;3.2.1</a> 
1470                  </td>
1471               </tr>
1472               <tr>
1473                  <td class="left">must-revalidate</td>
1474                  <td class="left"> <a href="#cache-response-directive" title="Response Cache-Control Directives">Section&nbsp;3.2.2</a> 
1475                  </td>
1476               </tr>
1477               <tr>
1478                  <td class="left">no-cache</td>
1479                  <td class="left"> <a href="#cache-request-directive" title="Request Cache-Control Directives">Section&nbsp;3.2.1</a>, <a href="#cache-response-directive" title="Response Cache-Control Directives">Section&nbsp;3.2.2</a> 
1480                  </td>
1481               </tr>
1482               <tr>
1483                  <td class="left">no-store</td>
1484                  <td class="left"> <a href="#cache-request-directive" title="Request Cache-Control Directives">Section&nbsp;3.2.1</a>, <a href="#cache-response-directive" title="Response Cache-Control Directives">Section&nbsp;3.2.2</a> 
1485                  </td>
1486               </tr>
1487               <tr>
1488                  <td class="left">no-transform</td>
1489                  <td class="left"> <a href="#cache-request-directive" title="Request Cache-Control Directives">Section&nbsp;3.2.1</a>, <a href="#cache-response-directive" title="Response Cache-Control Directives">Section&nbsp;3.2.2</a> 
1490                  </td>
1491               </tr>
1492               <tr>
1493                  <td class="left">only-if-cached</td>
1494                  <td class="left"> <a href="#cache-request-directive" title="Request Cache-Control Directives">Section&nbsp;3.2.1</a> 
1495                  </td>
1496               </tr>
1497               <tr>
1498                  <td class="left">private</td>
1499                  <td class="left"> <a href="#cache-response-directive" title="Response Cache-Control Directives">Section&nbsp;3.2.2</a> 
1500                  </td>
1501               </tr>
1502               <tr>
1503                  <td class="left">proxy-revalidate</td>
1504                  <td class="left"> <a href="#cache-response-directive" title="Response Cache-Control Directives">Section&nbsp;3.2.2</a> 
1505                  </td>
1506               </tr>
1507               <tr>
1508                  <td class="left">public</td>
1509                  <td class="left"> <a href="#cache-response-directive" title="Response Cache-Control Directives">Section&nbsp;3.2.2</a> 
1510                  </td>
1511               </tr>
1512               <tr>
1513                  <td class="left">s-maxage</td>
1514                  <td class="left"> <a href="#cache-response-directive" title="Response Cache-Control Directives">Section&nbsp;3.2.2</a> 
1515                  </td>
1516               </tr>
1517               <tr>
1518                  <td class="left">stale-if-error</td>
1519                  <td class="left"> <a href="#RFC5861" id="rfc.xref.RFC5861.1"><cite title="HTTP Cache-Control Extensions for Stale Content">[RFC5861]</cite></a>, <a href="http://tools.ietf.org/html/rfc5861#section-4">Section 4</a> 
1520                  </td>
1521               </tr>
1522               <tr>
1523                  <td class="left">stale-while-revalidate</td>
1524                  <td class="left"> <a href="#RFC5861" id="rfc.xref.RFC5861.2"><cite title="HTTP Cache-Control Extensions for Stale Content">[RFC5861]</cite></a>, <a href="http://tools.ietf.org/html/rfc5861#section-3">Section 3</a> 
1525                  </td>
1526               </tr>
1527            </tbody>
1528         </table>
1529      </div>
1530      <h2 id="rfc.section.5.2"><a href="#rfc.section.5.2">5.2</a>&nbsp;<a id="header.field.registration" href="#header.field.registration">Header Field Registration</a></h2>
1531      <p id="rfc.section.5.2.p.1">The Message Header Field 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; shall 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>):
1532      </p>
1533      <div id="rfc.table.2">
1534         <div id="iana.header.registration.table"></div>
1535         <table class="tt full left" cellpadding="3" cellspacing="0">
1536            <thead>
1537               <tr>
1538                  <th>Header Field Name</th>
1539                  <th>Protocol</th>
1540                  <th>Status</th>
1541                  <th>Reference</th>
1542               </tr>
1543            </thead>
1544            <tbody>
1545               <tr>
1546                  <td class="left">Age</td>
1547                  <td class="left">http</td>
1548                  <td class="left">standard</td>
1549                  <td class="left"> <a href="#header.age" id="rfc.xref.header.age.3" title="Age">Section&nbsp;3.1</a> 
1550                  </td>
1551               </tr>
1552               <tr>
1553                  <td class="left">Cache-Control</td>
1554                  <td class="left">http</td>
1555                  <td class="left">standard</td>
1556                  <td class="left"> <a href="#header.cache-control" id="rfc.xref.header.cache-control.3" title="Cache-Control">Section&nbsp;3.2</a> 
1557                  </td>
1558               </tr>
1559               <tr>
1560                  <td class="left">Expires</td>
1561                  <td class="left">http</td>
1562                  <td class="left">standard</td>
1563                  <td class="left"> <a href="#header.expires" id="rfc.xref.header.expires.4" title="Expires">Section&nbsp;3.3</a> 
1564                  </td>
1565               </tr>
1566               <tr>
1567                  <td class="left">Pragma</td>
1568                  <td class="left">http</td>
1569                  <td class="left">standard</td>
1570                  <td class="left"> <a href="#header.pragma" id="rfc.xref.header.pragma.3" title="Pragma">Section&nbsp;3.4</a> 
1571                  </td>
1572               </tr>
1573               <tr>
1574                  <td class="left">Vary</td>
1575                  <td class="left">http</td>
1576                  <td class="left">standard</td>
1577                  <td class="left"> <a href="#header.vary" id="rfc.xref.header.vary.2" title="Vary">Section&nbsp;3.5</a> 
1578                  </td>
1579               </tr>
1580               <tr>
1581                  <td class="left">Warning</td>
1582                  <td class="left">http</td>
1583                  <td class="left">standard</td>
1584                  <td class="left"> <a href="#header.warning" id="rfc.xref.header.warning.3" title="Warning">Section&nbsp;3.6</a> 
1585                  </td>
1586               </tr>
1587            </tbody>
1588         </table>
1589      </div>
1590      <p id="rfc.section.5.2.p.2">The change controller is: "IETF (iesg@ietf.org) - Internet Engineering Task Force".</p>
1591      <h1 id="rfc.section.6"><a href="#rfc.section.6">6.</a>&nbsp;<a id="security.considerations" href="#security.considerations">Security Considerations</a></h1>
1592      <p id="rfc.section.6.p.1">Caches expose additional potential vulnerabilities, since the contents of the cache represent an attractive target for malicious
1593         exploitation. Because cache contents persist after an HTTP request is complete, an attack on the cache can reveal information
1594         long after a user believes that the information has been removed from the network. Therefore, cache contents need to be protected
1595         as sensitive information.
1596      </p>
1597      <h1 id="rfc.section.7"><a href="#rfc.section.7">7.</a>&nbsp;<a id="ack" href="#ack">Acknowledgments</a></h1>
1598      <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:
1599         Shel Kaphan, Paul Leach, Koen Holtman, David Morris, and Larry Masinter.
1600      </p>
1601      <h1 id="rfc.references"><a id="rfc.section.8" href="#rfc.section.8">8.</a> References
1602      </h1>
1603      <h2 id="rfc.references.1"><a href="#rfc.section.8.1" id="rfc.section.8.1">8.1</a> Normative References
1604      </h2>
1605      <table>             
1606         <tr>
1607            <td class="reference"><b id="Part1">[Part1]</b></td>
1608            <td class="top"><a href="mailto:fielding@gbiv.com" title="Adobe Systems Incorporated">Fielding, R., Ed.</a>, <a href="mailto:jg@freedesktop.org" title="Alcatel-Lucent Bell Labs">Gettys, J.</a>, <a href="mailto:JeffMogul@acm.org" title="Hewlett-Packard Company">Mogul, J.</a>, <a href="mailto:henrikn@microsoft.com" title="Microsoft Corporation">Frystyk, H.</a>, <a href="mailto:LMM@acm.org" title="Adobe Systems Incorporated">Masinter, L.</a>, <a href="mailto:paulle@microsoft.com" title="Microsoft Corporation">Leach, P.</a>, <a href="mailto:timbl@w3.org" title="World Wide Web Consortium">Berners-Lee, T.</a>, <a href="mailto:ylafon@w3.org" title="World Wide Web Consortium">Lafon, Y., Ed.</a>, and <a href="mailto:julian.reschke@greenbytes.de" title="greenbytes GmbH">J. 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), February&nbsp;2011.
1609            </td>
1610         </tr>
1611         <tr>
1612            <td class="reference"><b id="Part2">[Part2]</b></td>
1613            <td class="top"><a href="mailto:fielding@gbiv.com" title="Adobe Systems Incorporated">Fielding, R., Ed.</a>, <a href="mailto:jg@freedesktop.org" title="Alcatel-Lucent Bell Labs">Gettys, J.</a>, <a href="mailto:JeffMogul@acm.org" title="Hewlett-Packard Company">Mogul, J.</a>, <a href="mailto:henrikn@microsoft.com" title="Microsoft Corporation">Frystyk, H.</a>, <a href="mailto:LMM@acm.org" title="Adobe Systems Incorporated">Masinter, L.</a>, <a href="mailto:paulle@microsoft.com" title="Microsoft Corporation">Leach, P.</a>, <a href="mailto:timbl@w3.org" title="World Wide Web Consortium">Berners-Lee, T.</a>, <a href="mailto:ylafon@w3.org" title="World Wide Web Consortium">Lafon, Y., Ed.</a>, and <a href="mailto:julian.reschke@greenbytes.de" title="greenbytes GmbH">J. 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), February&nbsp;2011.
1614            </td>
1615         </tr>
1616         <tr>
1617            <td class="reference"><b id="Part4">[Part4]</b></td>
1618            <td class="top"><a href="mailto:fielding@gbiv.com" title="Adobe Systems Incorporated">Fielding, R., Ed.</a>, <a href="mailto:jg@freedesktop.org" title="Alcatel-Lucent Bell Labs">Gettys, J.</a>, <a href="mailto:JeffMogul@acm.org" title="Hewlett-Packard Company">Mogul, J.</a>, <a href="mailto:henrikn@microsoft.com" title="Microsoft Corporation">Frystyk, H.</a>, <a href="mailto:LMM@acm.org" title="Adobe Systems Incorporated">Masinter, L.</a>, <a href="mailto:paulle@microsoft.com" title="Microsoft Corporation">Leach, P.</a>, <a href="mailto:timbl@w3.org" title="World Wide Web Consortium">Berners-Lee, T.</a>, <a href="mailto:ylafon@w3.org" title="World Wide Web Consortium">Lafon, Y., Ed.</a>, and <a href="mailto:julian.reschke@greenbytes.de" title="greenbytes GmbH">J. 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), February&nbsp;2011.
1619            </td>
1620         </tr>
1621         <tr>
1622            <td class="reference"><b id="Part5">[Part5]</b></td>
1623            <td class="top"><a href="mailto:fielding@gbiv.com" title="Adobe Systems Incorporated">Fielding, R., Ed.</a>, <a href="mailto:jg@freedesktop.org" title="Alcatel-Lucent Bell Labs">Gettys, J.</a>, <a href="mailto:JeffMogul@acm.org" title="Hewlett-Packard Company">Mogul, J.</a>, <a href="mailto:henrikn@microsoft.com" title="Microsoft Corporation">Frystyk, H.</a>, <a href="mailto:LMM@acm.org" title="Adobe Systems Incorporated">Masinter, L.</a>, <a href="mailto:paulle@microsoft.com" title="Microsoft Corporation">Leach, P.</a>, <a href="mailto:timbl@w3.org" title="World Wide Web Consortium">Berners-Lee, T.</a>, <a href="mailto:ylafon@w3.org" title="World Wide Web Consortium">Lafon, Y., Ed.</a>, and <a href="mailto:julian.reschke@greenbytes.de" title="greenbytes GmbH">J. 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), February&nbsp;2011.
1624            </td>
1625         </tr>
1626         <tr>
1627            <td class="reference"><b id="Part7">[Part7]</b></td>
1628            <td class="top"><a href="mailto:fielding@gbiv.com" title="Adobe Systems Incorporated">Fielding, R., Ed.</a>, <a href="mailto:jg@freedesktop.org" title="Alcatel-Lucent Bell Labs">Gettys, J.</a>, <a href="mailto:JeffMogul@acm.org" title="Hewlett-Packard Company">Mogul, J.</a>, <a href="mailto:henrikn@microsoft.com" title="Microsoft Corporation">Frystyk, H.</a>, <a href="mailto:LMM@acm.org" title="Adobe Systems Incorporated">Masinter, L.</a>, <a href="mailto:paulle@microsoft.com" title="Microsoft Corporation">Leach, P.</a>, <a href="mailto:timbl@w3.org" title="World Wide Web Consortium">Berners-Lee, T.</a>, <a href="mailto:ylafon@w3.org" title="World Wide Web Consortium">Lafon, Y., Ed.</a>, and <a href="mailto:julian.reschke@greenbytes.de" title="greenbytes GmbH">J. 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), February&nbsp;2011.
1629            </td>
1630         </tr>
1631         <tr>
1632            <td class="reference"><b id="RFC2119">[RFC2119]</b></td>
1633            <td class="top"><a href="mailto:sob@harvard.edu" 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.
1634            </td>
1635         </tr>
1636         <tr>
1637            <td class="reference"><b id="RFC5234">[RFC5234]</b></td>
1638            <td class="top"><a href="mailto:dcrocker@bbiw.net" title="Brandenburg InternetWorking">Crocker, D., Ed.</a> and <a href="mailto:paul.overell@thus.net" 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.
1639            </td>
1640         </tr>
1641      </table>
1642      <h2 id="rfc.references.2"><a href="#rfc.section.8.2" id="rfc.section.8.2">8.2</a> Informative References
1643      </h2>
1644      <table>         
1645         <tr>
1646            <td class="reference"><b id="RFC1305">[RFC1305]</b></td>
1647            <td class="top"><a href="mailto:mills@udel.edu" 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.
1648            </td>
1649         </tr>
1650         <tr>
1651            <td class="reference"><b id="RFC2616">[RFC2616]</b></td>
1652            <td class="top"><a href="mailto:fielding@ics.uci.edu" title="University of California, Irvine">Fielding, R.</a>, <a href="mailto:jg@w3.org" title="W3C">Gettys, J.</a>, <a href="mailto:mogul@wrl.dec.com" title="Compaq Computer Corporation">Mogul, J.</a>, <a href="mailto:frystyk@w3.org" title="MIT Laboratory for Computer Science">Frystyk, H.</a>, <a href="mailto:masinter@parc.xerox.com" title="Xerox Corporation">Masinter, L.</a>, <a href="mailto:paulle@microsoft.com" title="Microsoft Corporation">Leach, P.</a>, and <a href="mailto:timbl@w3.org" 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.
1653            </td>
1654         </tr>
1655         <tr>
1656            <td class="reference"><b id="RFC3864">[RFC3864]</b></td>
1657            <td class="top"><a href="mailto:GK-IETF@ninebynine.org" title="Nine by Nine">Klyne, G.</a>, <a href="mailto:mnot@pobox.com" title="BEA Systems">Nottingham, M.</a>, and <a href="mailto:JeffMogul@acm.org" 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.
1658            </td>
1659         </tr>
1660         <tr>
1661            <td class="reference"><b id="RFC5226">[RFC5226]</b></td>
1662            <td class="top"><a href="mailto:narten@us.ibm.com" title="IBM">Narten, T.</a> and <a href="mailto:Harald@Alvestrand.no" title="Google">H. Alvestrand</a>, “<a href="http://tools.ietf.org/html/rfc5226">Guidelines for Writing an IANA Considerations Section in RFCs</a>”, BCP&nbsp;26, RFC&nbsp;5226, May&nbsp;2008.
1663            </td>
1664         </tr>
1665         <tr>
1666            <td class="reference"><b id="RFC5861">[RFC5861]</b></td>
1667            <td class="top"><a href="mailto:mnot@yahoo-inc.com" title="Yahoo! Inc.">Nottingham, M.</a>, “<a href="http://tools.ietf.org/html/rfc5861">HTTP Cache-Control Extensions for Stale Content</a>”, RFC&nbsp;5861, April&nbsp;2010.
1668            </td>
1669         </tr>
1670      </table>
1671      <div class="avoidbreak">
1672         <h1 id="rfc.authors"><a href="#rfc.authors">Authors' Addresses</a></h1>
1673         <address class="vcard"><span class="vcardline"><span class="fn">Roy T. Fielding</span>
1674               (editor)
1675               <span class="n hidden"><span class="family-name">Fielding</span><span class="given-name">Roy T.</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 href="mailto:fielding@gbiv.com"><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>
1676         <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">Alcatel-Lucent Bell Labs</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 href="mailto:jg@freedesktop.org"><span class="email">jg@freedesktop.org</span></a></span><span class="vcardline">URI: <a href="http://gettys.wordpress.com/" class="url">http://gettys.wordpress.com/</a></span></address>
1677         <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 href="mailto:JeffMogul@acm.org"><span class="email">JeffMogul@acm.org</span></a></span></address>
1678         <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 href="mailto:henrikn@microsoft.com"><span class="email">henrikn@microsoft.com</span></a></span></address>
1679         <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 href="mailto:LMM@acm.org"><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>
1680         <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 href="mailto:paulle@microsoft.com"><span class="email">paulle@microsoft.com</span></a></span></address>
1681         <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 href="mailto:timbl@w3.org"><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>
1682         <address class="vcard"><span class="vcardline"><span class="fn">Yves Lafon</span>
1683               (editor)
1684               <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 href="mailto:ylafon@w3.org"><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>
1685         <address class="vcard"><span class="vcardline"><span class="fn">Mark Nottingham</span>
1686               (editor)
1687               <span class="n hidden"><span class="family-name">Nottingham</span><span class="given-name">Mark</span></span></span><span class="vcardline">Email: <a href="mailto:mnot@mnot.net"><span class="email">mnot@mnot.net</span></a></span><span class="vcardline">URI: <a href="http://www.mnot.net/" class="url">http://www.mnot.net/</a></span></address>
1688         <address class="vcard"><span class="vcardline"><span class="fn">Julian F. Reschke</span>
1689               (editor)
1690               <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 href="mailto:julian.reschke@greenbytes.de"><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>
1691      </div>
1692      <h1 id="rfc.section.A" class="np"><a href="#rfc.section.A">A.</a>&nbsp;<a id="changes.from.rfc.2616" href="#changes.from.rfc.2616">Changes from RFC 2616</a></h1>
1693      <p id="rfc.section.A.p.1">Make the specified age calculation algorithm less conservative. (<a href="#age.calculations" title="Calculating Age">Section&nbsp;2.3.2</a>)
1694      </p>
1695      <p id="rfc.section.A.p.2">Remove requirement to consider Content-Location in successful responses in order to determine the appropriate response to
1696         use. (<a href="#validation.model" title="Validation Model">Section&nbsp;2.4</a>)
1697      </p>
1698      <p id="rfc.section.A.p.3">Clarify denial of service attack avoidance requirement. (<a href="#invalidation.after.updates.or.deletions" title="Request Methods that Invalidate">Section&nbsp;2.5</a>)
1699      </p>
1700      <p id="rfc.section.A.p.4">Do not mention RFC 2047 encoding and multiple languages in Warning header fields anymore, as these aspects never were implemented.
1701         (<a href="#header.warning" id="rfc.xref.header.warning.4" title="Warning">Section&nbsp;3.6</a>)
1702      </p>
1703      <h1 id="rfc.section.B"><a href="#rfc.section.B">B.</a>&nbsp;<a id="collected.abnf" href="#collected.abnf">Collected ABNF</a></h1>
1704      <div id="rfc.figure.u.18"></div> <pre class="inline"><a href="#header.age" class="smpl">Age</a> = "Age:" OWS Age-v
1705<a href="#header.age" class="smpl">Age-v</a> = delta-seconds
1706
1707<a href="#header.cache-control" class="smpl">Cache-Control</a> = "Cache-Control:" OWS Cache-Control-v
1708<a href="#header.cache-control" class="smpl">Cache-Control-v</a> = *( "," OWS ) cache-directive *( OWS "," [ OWS
1709 cache-directive ] )
1710
1711<a href="#header.expires" class="smpl">Expires</a> = "Expires:" OWS Expires-v
1712<a href="#header.expires" class="smpl">Expires-v</a> = HTTP-date
1713
1714<a href="#abnf.dependencies" class="smpl">HTTP-date</a> = &lt;HTTP-date, defined in [Part1], Section 6.1&gt;
1715
1716<a href="#core.rules" class="smpl">OWS</a> = &lt;OWS, defined in [Part1], Section 1.2.2&gt;
1717
1718<a href="#header.pragma" class="smpl">Pragma</a> = "Pragma:" OWS Pragma-v
1719<a href="#header.pragma" class="smpl">Pragma-v</a> = *( "," OWS ) pragma-directive *( OWS "," [ OWS
1720 pragma-directive ] )
1721
1722<a href="#header.vary" class="smpl">Vary</a> = "Vary:" OWS Vary-v
1723<a href="#header.vary" class="smpl">Vary-v</a> = "*" / ( *( "," OWS ) field-name *( OWS "," [ OWS field-name
1724 ] ) )
1725
1726<a href="#header.warning" class="smpl">Warning</a> = "Warning:" OWS Warning-v
1727<a href="#header.warning" class="smpl">Warning-v</a> = *( "," OWS ) warning-value *( OWS "," [ OWS warning-value
1728 ] )
1729
1730<a href="#header.cache-control" class="smpl">cache-directive</a> = cache-request-directive / cache-response-directive
1731<a href="#header.cache-control" class="smpl">cache-extension</a> = token [ "=" ( token / quoted-string ) ]
1732<a href="#header.cache-control" class="smpl">cache-request-directive</a> = "no-cache" / "no-store" / ( "max-age="
1733 delta-seconds ) / ( "max-stale" [ "=" delta-seconds ] ) / (
1734 "min-fresh=" delta-seconds ) / "no-transform" / "only-if-cached" /
1735 cache-extension
1736<a href="#header.cache-control" class="smpl">cache-response-directive</a> = "public" / ( "private" [ "=" DQUOTE *( ","
1737 OWS ) field-name *( OWS "," [ OWS field-name ] ) DQUOTE ] ) / (
1738 "no-cache" [ "=" DQUOTE *( "," OWS ) field-name *( OWS "," [ OWS
1739 field-name ] ) DQUOTE ] ) / "no-store" / "no-transform" /
1740 "must-revalidate" / "proxy-revalidate" / ( "max-age=" delta-seconds
1741 ) / ( "s-maxage=" delta-seconds ) / cache-extension
1742
1743<a href="#rule.delta-seconds" class="smpl">delta-seconds</a> = 1*DIGIT
1744
1745<a href="#header.pragma" class="smpl">extension-pragma</a> = token [ "=" ( token / quoted-string ) ]
1746
1747<a href="#abnf.dependencies" class="smpl">field-name</a> = &lt;field-name, defined in [Part1], Section 3.2&gt;
1748
1749<a href="#abnf.dependencies" class="smpl">port</a> = &lt;port, defined in [Part1], Section 2.6&gt;
1750<a href="#header.pragma" class="smpl">pragma-directive</a> = "no-cache" / extension-pragma
1751<a href="#abnf.dependencies" class="smpl">pseudonym</a> = &lt;pseudonym, defined in [Part1], Section 9.9&gt;
1752
1753<a href="#core.rules" class="smpl">quoted-string</a> = &lt;quoted-string, defined in [Part1], Section 1.2.2&gt;
1754
1755<a href="#core.rules" class="smpl">token</a> = &lt;token, defined in [Part1], Section 1.2.2&gt;
1756
1757<a href="#abnf.dependencies" class="smpl">uri-host</a> = &lt;uri-host, defined in [Part1], Section 2.6&gt;
1758
1759<a href="#header.warning" class="smpl">warn-agent</a> = ( uri-host [ ":" port ] ) / pseudonym
1760<a href="#header.warning" class="smpl">warn-code</a> = 3DIGIT
1761<a href="#header.warning" class="smpl">warn-date</a> = DQUOTE HTTP-date DQUOTE
1762<a href="#header.warning" class="smpl">warn-text</a> = quoted-string
1763<a href="#header.warning" class="smpl">warning-value</a> = warn-code SP warn-agent SP warn-text [ SP warn-date
1764 ]
1765</pre> <div id="rfc.figure.u.19"></div>
1766      <p>ABNF diagnostics:</p><pre class="inline">; Age defined but not used
1767; Cache-Control defined but not used
1768; Expires defined but not used
1769; Pragma defined but not used
1770; Vary defined but not used
1771; Warning defined but not used
1772</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>
1773      <h2 id="rfc.section.C.1"><a href="#rfc.section.C.1">C.1</a>&nbsp;Since RFC 2616
1774      </h2>
1775      <p id="rfc.section.C.1.p.1">Extracted relevant partitions from <a href="#RFC2616" id="rfc.xref.RFC2616.2"><cite title="Hypertext Transfer Protocol -- HTTP/1.1">[RFC2616]</cite></a>.
1776      </p>
1777      <h2 id="rfc.section.C.2"><a href="#rfc.section.C.2">C.2</a>&nbsp;Since draft-ietf-httpbis-p6-cache-00
1778      </h2>
1779      <p id="rfc.section.C.2.p.1">Closed issues: </p>
1780      <ul>
1781         <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;)
1782         </li>
1783         <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;)
1784         </li>
1785         <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"
1786         </li>
1787         <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"
1788         </li>
1789         <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"
1790         </li>
1791         <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"
1792         </li>
1793         <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"
1794         </li>
1795         <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"
1796         </li>
1797         <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"
1798         </li>
1799      </ul>
1800      <p id="rfc.section.C.2.p.2">Other changes: </p>
1801      <ul>
1802         <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;)
1803         </li>
1804      </ul>
1805      <h2 id="rfc.section.C.3"><a href="#rfc.section.C.3">C.3</a>&nbsp;Since draft-ietf-httpbis-p6-cache-01
1806      </h2>
1807      <p id="rfc.section.C.3.p.1">Closed issues: </p>
1808      <ul>
1809         <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"
1810         </li>
1811      </ul>
1812      <p id="rfc.section.C.3.p.2">Other changes: </p>
1813      <ul>
1814         <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;)
1815         </li>
1816         <li>Add explicit references to BNF syntax and rules imported from other parts of the specification.</li>
1817      </ul>
1818      <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>
1819      <p id="rfc.section.C.4.p.1">Ongoing work on IANA Message Header Field Registration (&lt;<a href="http://tools.ietf.org/wg/httpbis/trac/ticket/40">http://tools.ietf.org/wg/httpbis/trac/ticket/40</a>&gt;):
1820      </p>
1821      <ul>
1822         <li>Reference RFC 3984, and update header field registrations for header fields defined in this document.</li>
1823      </ul>
1824      <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>
1825      <p id="rfc.section.C.5.p.1">Closed issues: </p>
1826      <ul>
1827         <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"
1828         </li>
1829      </ul>
1830      <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>
1831      <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;):
1832      </p>
1833      <ul>
1834         <li>Use "/" instead of "|" for alternatives.</li>
1835         <li>Introduce new ABNF rules for "bad" whitespace ("BWS"), optional whitespace ("OWS") and required whitespace ("RWS").</li>
1836         <li>Rewrite ABNFs to spell out whitespace rules, factor out header field value format definitions.</li>
1837      </ul>
1838      <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>
1839      <p id="rfc.section.C.7.p.1">This is a total rewrite of this part of the specification.</p>
1840      <p id="rfc.section.C.7.p.2">Affected issues: </p>
1841      <ul>
1842         <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"
1843         </li>
1844         <li> &lt;<a href="http://tools.ietf.org/wg/httpbis/trac/ticket/60">http://tools.ietf.org/wg/httpbis/trac/ticket/60</a>&gt;: "Placement of 13.5.1 and 13.5.2"
1845         </li>
1846         <li> &lt;<a href="http://tools.ietf.org/wg/httpbis/trac/ticket/138">http://tools.ietf.org/wg/httpbis/trac/ticket/138</a>&gt;: "The role of Warning and Semantic Transparency in Caching"
1847         </li>
1848         <li> &lt;<a href="http://tools.ietf.org/wg/httpbis/trac/ticket/139">http://tools.ietf.org/wg/httpbis/trac/ticket/139</a>&gt;: "Methods and Caching"
1849         </li>
1850      </ul>
1851      <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;):
1852      </p>
1853      <ul>
1854         <li>Add appendix containing collected and expanded ABNF, reorganize ABNF introduction.</li>
1855      </ul>
1856      <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>
1857      <p id="rfc.section.C.8.p.1">Closed issues: </p>
1858      <ul>
1859         <li> &lt;<a href="http://tools.ietf.org/wg/httpbis/trac/ticket/161">http://tools.ietf.org/wg/httpbis/trac/ticket/161</a>&gt;: "base for numeric protocol elements"
1860         </li>
1861      </ul>
1862      <p id="rfc.section.C.8.p.2">Affected issues: </p>
1863      <ul>
1864         <li> &lt;<a href="http://tools.ietf.org/wg/httpbis/trac/ticket/37">http://tools.ietf.org/wg/httpbis/trac/ticket/37</a>&gt;: WVary and non-existant headers"
1865         </li>
1866      </ul>
1867      <h2 id="rfc.section.C.9"><a href="#rfc.section.C.9">C.9</a>&nbsp;<a id="changes.since.07" href="#changes.since.07">Since draft-ietf-httpbis-p6-cache-07</a></h2>
1868      <p id="rfc.section.C.9.p.1">Closed issues: </p>
1869      <ul>
1870         <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"
1871         </li>
1872         <li> &lt;<a href="http://tools.ietf.org/wg/httpbis/trac/ticket/167">http://tools.ietf.org/wg/httpbis/trac/ticket/167</a>&gt;: "Content-Location on 304 responses"
1873         </li>
1874         <li> &lt;<a href="http://tools.ietf.org/wg/httpbis/trac/ticket/169">http://tools.ietf.org/wg/httpbis/trac/ticket/169</a>&gt;: "private and no-cache CC directives with headers"
1875         </li>
1876         <li> &lt;<a href="http://tools.ietf.org/wg/httpbis/trac/ticket/187">http://tools.ietf.org/wg/httpbis/trac/ticket/187</a>&gt;: "RFC2047 and warn-text"
1877         </li>
1878      </ul>
1879      <h2 id="rfc.section.C.10"><a href="#rfc.section.C.10">C.10</a>&nbsp;<a id="changes.since.08" href="#changes.since.08">Since draft-ietf-httpbis-p6-cache-08</a></h2>
1880      <p id="rfc.section.C.10.p.1">Closed issues: </p>
1881      <ul>
1882         <li> &lt;<a href="http://tools.ietf.org/wg/httpbis/trac/ticket/147">http://tools.ietf.org/wg/httpbis/trac/ticket/147</a>&gt;: "serving negotiated responses from cache: header-specific canonicalization"
1883         </li>
1884         <li> &lt;<a href="http://tools.ietf.org/wg/httpbis/trac/ticket/197">http://tools.ietf.org/wg/httpbis/trac/ticket/197</a>&gt;: "Effect of CC directives on history lists"
1885         </li>
1886      </ul>
1887      <p id="rfc.section.C.10.p.2">Affected issues: </p>
1888      <ul>
1889         <li> &lt;<a href="http://tools.ietf.org/wg/httpbis/trac/ticket/199">http://tools.ietf.org/wg/httpbis/trac/ticket/199</a>&gt;: Status codes and caching
1890         </li>
1891      </ul>
1892      <p id="rfc.section.C.10.p.3">Partly resolved issues: </p>
1893      <ul>
1894         <li> &lt;<a href="http://tools.ietf.org/wg/httpbis/trac/ticket/60">http://tools.ietf.org/wg/httpbis/trac/ticket/60</a>&gt;: "Placement of 13.5.1 and 13.5.2"
1895         </li>
1896      </ul>
1897      <h2 id="rfc.section.C.11"><a href="#rfc.section.C.11">C.11</a>&nbsp;<a id="changes.since.09" href="#changes.since.09">Since draft-ietf-httpbis-p6-cache-09</a></h2>
1898      <p id="rfc.section.C.11.p.1">Closed issues: </p>
1899      <ul>
1900         <li> &lt;<a href="http://tools.ietf.org/wg/httpbis/trac/ticket/29">http://tools.ietf.org/wg/httpbis/trac/ticket/29</a>&gt;: "Age calculation"
1901         </li>
1902         <li> &lt;<a href="http://tools.ietf.org/wg/httpbis/trac/ticket/168">http://tools.ietf.org/wg/httpbis/trac/ticket/168</a>&gt;: "Clarify differences between / requirements for request and response CC directives"
1903         </li>
1904         <li> &lt;<a href="http://tools.ietf.org/wg/httpbis/trac/ticket/174">http://tools.ietf.org/wg/httpbis/trac/ticket/174</a>&gt;: "Caching authenticated responses"
1905         </li>
1906         <li> &lt;<a href="http://tools.ietf.org/wg/httpbis/trac/ticket/208">http://tools.ietf.org/wg/httpbis/trac/ticket/208</a>&gt;: "IANA registry for cache-control directives"
1907         </li>
1908         <li> &lt;<a href="http://tools.ietf.org/wg/httpbis/trac/ticket/211">http://tools.ietf.org/wg/httpbis/trac/ticket/211</a>&gt;: "Heuristic caching of URLs with query components"
1909         </li>
1910      </ul>
1911      <p id="rfc.section.C.11.p.2">Partly resolved issues: </p>
1912      <ul>
1913         <li> &lt;<a href="http://tools.ietf.org/wg/httpbis/trac/ticket/196">http://tools.ietf.org/wg/httpbis/trac/ticket/196</a>&gt;: "Term for the requested resource's URI"
1914         </li>
1915      </ul>
1916      <h2 id="rfc.section.C.12"><a href="#rfc.section.C.12">C.12</a>&nbsp;<a id="changes.since.10" href="#changes.since.10">Since draft-ietf-httpbis-p6-cache-10</a></h2>
1917      <p id="rfc.section.C.12.p.1">Closed issues: </p>
1918      <ul>
1919         <li> &lt;<a href="http://tools.ietf.org/wg/httpbis/trac/ticket/109">http://tools.ietf.org/wg/httpbis/trac/ticket/109</a>&gt;: "Clarify entity / representation / variant terminology"
1920         </li>
1921         <li> &lt;<a href="http://tools.ietf.org/wg/httpbis/trac/ticket/220">http://tools.ietf.org/wg/httpbis/trac/ticket/220</a>&gt;: "consider removing the 'changes from 2068' sections"
1922         </li>
1923         <li> &lt;<a href="http://tools.ietf.org/wg/httpbis/trac/ticket/223">http://tools.ietf.org/wg/httpbis/trac/ticket/223</a>&gt;: "Allowing heuristic caching for new status codes"
1924         </li>
1925         <li> &lt;<a href="http://tools.ietf.org/wg/httpbis/trac/ticket/223">http://tools.ietf.org/wg/httpbis/trac/ticket/223</a>&gt;: "Allowing heuristic caching for new status codes"
1926         </li>
1927         <li>Clean up TODOs and prose in "Combining Responses."</li>
1928      </ul>
1929      <h2 id="rfc.section.C.13"><a href="#rfc.section.C.13">C.13</a>&nbsp;<a id="changes.since.11" href="#changes.since.11">Since draft-ietf-httpbis-p6-cache-11</a></h2>
1930      <p id="rfc.section.C.13.p.1">Closed issues: </p>
1931      <ul>
1932         <li> &lt;<a href="http://tools.ietf.org/wg/httpbis/trac/ticket/204">http://tools.ietf.org/wg/httpbis/trac/ticket/204</a>&gt;: "Text about clock requirement for caches belongs in p6"
1933         </li>
1934      </ul>
1935      <h2 id="rfc.section.C.14"><a href="#rfc.section.C.14">C.14</a>&nbsp;<a id="changes.since.12" href="#changes.since.12">Since draft-ietf-httpbis-p6-cache-12</a></h2>
1936      <p id="rfc.section.C.14.p.1">None yet.</p>
1937      <h1 id="rfc.index"><a href="#rfc.index">Index</a></h1>
1938      <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.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> 
1939      </p>
1940      <div class="print2col">
1941         <ul class="ind">
1942            <li><a id="rfc.index.A" href="#rfc.index.A"><b>A</b></a><ul>
1943                  <li>age&nbsp;&nbsp;<a href="#rfc.iref.a.1">1.2</a></li>
1944                  <li>Age header&nbsp;&nbsp;<a href="#rfc.xref.header.age.1">2.2</a>, <a href="#rfc.xref.header.age.2">2.3.2</a>, <a href="#rfc.iref.a.2"><b>3.1</b></a>, <a href="#rfc.xref.header.age.3">5.2</a></li>
1945               </ul>
1946            </li>
1947            <li><a id="rfc.index.C" href="#rfc.index.C"><b>C</b></a><ul>
1948                  <li>cache&nbsp;&nbsp;<a href="#rfc.iref.c.1">1.1</a>, <a href="#rfc.iref.c.2">1.2</a></li>
1949                  <li>Cache Directives&nbsp;&nbsp;
1950                     <ul>
1951                        <li>max-age&nbsp;&nbsp;<a href="#rfc.iref.c.7"><b>3.2.1</b></a>, <a href="#rfc.iref.c.18"><b>3.2.2</b></a></li>
1952                        <li>max-stale&nbsp;&nbsp;<a href="#rfc.iref.c.8"><b>3.2.1</b></a></li>
1953                        <li>min-fresh&nbsp;&nbsp;<a href="#rfc.iref.c.9"><b>3.2.1</b></a></li>
1954                        <li>must-revalidate&nbsp;&nbsp;<a href="#rfc.iref.c.16"><b>3.2.2</b></a></li>
1955                        <li>no-cache&nbsp;&nbsp;<a href="#rfc.iref.c.5"><b>3.2.1</b></a>, <a href="#rfc.iref.c.14"><b>3.2.2</b></a></li>
1956                        <li>no-store&nbsp;&nbsp;<a href="#rfc.iref.c.6"><b>3.2.1</b></a>, <a href="#rfc.iref.c.15"><b>3.2.2</b></a></li>
1957                        <li>no-transform&nbsp;&nbsp;<a href="#rfc.iref.c.10"><b>3.2.1</b></a>, <a href="#rfc.iref.c.20"><b>3.2.2</b></a></li>
1958                        <li>only-if-cached&nbsp;&nbsp;<a href="#rfc.iref.c.11"><b>3.2.1</b></a></li>
1959                        <li>private&nbsp;&nbsp;<a href="#rfc.iref.c.13"><b>3.2.2</b></a></li>
1960                        <li>proxy-revalidate&nbsp;&nbsp;<a href="#rfc.iref.c.17"><b>3.2.2</b></a></li>
1961                        <li>public&nbsp;&nbsp;<a href="#rfc.iref.c.12"><b>3.2.2</b></a></li>
1962                        <li>s-maxage&nbsp;&nbsp;<a href="#rfc.iref.c.19"><b>3.2.2</b></a></li>
1963                     </ul>
1964                  </li>
1965                  <li>Cache-Control header&nbsp;&nbsp;<a href="#rfc.xref.header.cache-control.1">2.1</a>, <a href="#rfc.xref.header.cache-control.2">2.2</a>, <a href="#rfc.iref.c.4"><b>3.2</b></a>, <a href="#rfc.xref.header.cache-control.3">5.2</a></li>
1966                  <li>cacheable&nbsp;&nbsp;<a href="#rfc.iref.c.3">1.2</a></li>
1967               </ul>
1968            </li>
1969            <li><a id="rfc.index.E" href="#rfc.index.E"><b>E</b></a><ul>
1970                  <li>Expires header&nbsp;&nbsp;<a href="#rfc.xref.header.expires.1">2.1</a>, <a href="#rfc.xref.header.expires.2">2.3</a>, <a href="#rfc.xref.header.expires.3">2.3.1</a>, <a href="#rfc.iref.e.2"><b>3.3</b></a>, <a href="#rfc.xref.header.expires.4">5.2</a></li>
1971                  <li>explicit expiration time&nbsp;&nbsp;<a href="#rfc.iref.e.1">1.2</a></li>
1972               </ul>
1973            </li>
1974            <li><a id="rfc.index.F" href="#rfc.index.F"><b>F</b></a><ul>
1975                  <li>first-hand&nbsp;&nbsp;<a href="#rfc.iref.f.1">1.2</a></li>
1976                  <li>fresh&nbsp;&nbsp;<a href="#rfc.iref.f.3">1.2</a></li>
1977                  <li>freshness lifetime&nbsp;&nbsp;<a href="#rfc.iref.f.2">1.2</a></li>
1978               </ul>
1979            </li>
1980            <li><a id="rfc.index.G" href="#rfc.index.G"><b>G</b></a><ul>
1981                  <li><tt>Grammar</tt>&nbsp;&nbsp;
1982                     <ul>
1983                        <li><tt>Age</tt>&nbsp;&nbsp;<a href="#rfc.iref.g.1"><b>3.1</b></a></li>
1984                        <li><tt>Age-v</tt>&nbsp;&nbsp;<a href="#rfc.iref.g.2"><b>3.1</b></a></li>
1985                        <li><tt>Cache-Control</tt>&nbsp;&nbsp;<a href="#rfc.iref.g.4"><b>3.2</b></a></li>
1986                        <li><tt>Cache-Control-v</tt>&nbsp;&nbsp;<a href="#rfc.iref.g.5"><b>3.2</b></a></li>
1987                        <li><tt>cache-extension</tt>&nbsp;&nbsp;<a href="#rfc.iref.g.6"><b>3.2</b></a></li>
1988                        <li><tt>cache-request-directive</tt>&nbsp;&nbsp;<a href="#rfc.iref.g.7"><b>3.2.1</b></a></li>
1989                        <li><tt>cache-response-directive</tt>&nbsp;&nbsp;<a href="#rfc.iref.g.8"><b>3.2.2</b></a></li>
1990                        <li><tt>delta-seconds</tt>&nbsp;&nbsp;<a href="#rfc.iref.g.3"><b>3.1</b></a></li>
1991                        <li><tt>Expires</tt>&nbsp;&nbsp;<a href="#rfc.iref.g.9"><b>3.3</b></a></li>
1992                        <li><tt>Expires-v</tt>&nbsp;&nbsp;<a href="#rfc.iref.g.10"><b>3.3</b></a></li>
1993                        <li><tt>extension-pragma</tt>&nbsp;&nbsp;<a href="#rfc.iref.g.14"><b>3.4</b></a></li>
1994                        <li><tt>Pragma</tt>&nbsp;&nbsp;<a href="#rfc.iref.g.11"><b>3.4</b></a></li>
1995                        <li><tt>pragma-directive</tt>&nbsp;&nbsp;<a href="#rfc.iref.g.13"><b>3.4</b></a></li>
1996                        <li><tt>Pragma-v</tt>&nbsp;&nbsp;<a href="#rfc.iref.g.12"><b>3.4</b></a></li>
1997                        <li><tt>Vary</tt>&nbsp;&nbsp;<a href="#rfc.iref.g.15"><b>3.5</b></a></li>
1998                        <li><tt>Vary-v</tt>&nbsp;&nbsp;<a href="#rfc.iref.g.16"><b>3.5</b></a></li>
1999                        <li><tt>warn-agent</tt>&nbsp;&nbsp;<a href="#rfc.iref.g.21"><b>3.6</b></a></li>
2000                        <li><tt>warn-code</tt>&nbsp;&nbsp;<a href="#rfc.iref.g.20"><b>3.6</b></a></li>
2001                        <li><tt>warn-date</tt>&nbsp;&nbsp;<a href="#rfc.iref.g.23"><b>3.6</b></a></li>
2002                        <li><tt>warn-text</tt>&nbsp;&nbsp;<a href="#rfc.iref.g.22"><b>3.6</b></a></li>
2003                        <li><tt>Warning</tt>&nbsp;&nbsp;<a href="#rfc.iref.g.17"><b>3.6</b></a></li>
2004                        <li><tt>Warning-v</tt>&nbsp;&nbsp;<a href="#rfc.iref.g.18"><b>3.6</b></a></li>
2005                        <li><tt>warning-value</tt>&nbsp;&nbsp;<a href="#rfc.iref.g.19"><b>3.6</b></a></li>
2006                     </ul>
2007                  </li>
2008               </ul>
2009            </li>
2010            <li><a id="rfc.index.H" href="#rfc.index.H"><b>H</b></a><ul>
2011                  <li>Headers&nbsp;&nbsp;
2012                     <ul>
2013                        <li>Age&nbsp;&nbsp;<a href="#rfc.xref.header.age.1">2.2</a>, <a href="#rfc.xref.header.age.2">2.3.2</a>, <a href="#rfc.iref.h.2"><b>3.1</b></a>, <a href="#rfc.xref.header.age.3">5.2</a></li>
2014                        <li>Cache-Control&nbsp;&nbsp;<a href="#rfc.xref.header.cache-control.1">2.1</a>, <a href="#rfc.xref.header.cache-control.2">2.2</a>, <a href="#rfc.iref.h.3"><b>3.2</b></a>, <a href="#rfc.xref.header.cache-control.3">5.2</a></li>
2015                        <li>Expires&nbsp;&nbsp;<a href="#rfc.xref.header.expires.1">2.1</a>, <a href="#rfc.xref.header.expires.2">2.3</a>, <a href="#rfc.xref.header.expires.3">2.3.1</a>, <a href="#rfc.iref.h.4"><b>3.3</b></a>, <a href="#rfc.xref.header.expires.4">5.2</a></li>
2016                        <li>Pragma&nbsp;&nbsp;<a href="#rfc.xref.header.pragma.1">2.2</a>, <a href="#rfc.xref.header.pragma.2">3.2</a>, <a href="#rfc.iref.h.5"><b>3.4</b></a>, <a href="#rfc.xref.header.pragma.3">5.2</a></li>
2017                        <li>Vary&nbsp;&nbsp;<a href="#rfc.xref.header.vary.1">2.7</a>, <a href="#rfc.iref.h.6"><b>3.5</b></a>, <a href="#rfc.xref.header.vary.2">5.2</a></li>
2018                        <li>Warning&nbsp;&nbsp;<a href="#rfc.xref.header.warning.1">2.3.3</a>, <a href="#rfc.xref.header.warning.2">2.8</a>, <a href="#rfc.iref.h.7"><b>3.6</b></a>, <a href="#rfc.xref.header.warning.3">5.2</a>, <a href="#rfc.xref.header.warning.4">A</a></li>
2019                     </ul>
2020                  </li>
2021                  <li>heuristic expiration time&nbsp;&nbsp;<a href="#rfc.iref.h.1">1.2</a></li>
2022               </ul>
2023            </li>
2024            <li><a id="rfc.index.M" href="#rfc.index.M"><b>M</b></a><ul>
2025                  <li>max-age&nbsp;&nbsp;
2026                     <ul>
2027                        <li>Cache Directive&nbsp;&nbsp;<a href="#rfc.iref.m.1"><b>3.2.1</b></a>, <a href="#rfc.iref.m.5"><b>3.2.2</b></a></li>
2028                     </ul>
2029                  </li>
2030                  <li>max-stale&nbsp;&nbsp;
2031                     <ul>
2032                        <li>Cache Directive&nbsp;&nbsp;<a href="#rfc.iref.m.2"><b>3.2.1</b></a></li>
2033                     </ul>
2034                  </li>
2035                  <li>min-fresh&nbsp;&nbsp;
2036                     <ul>
2037                        <li>Cache Directive&nbsp;&nbsp;<a href="#rfc.iref.m.3"><b>3.2.1</b></a></li>
2038                     </ul>
2039                  </li>
2040                  <li>must-revalidate&nbsp;&nbsp;
2041                     <ul>
2042                        <li>Cache Directive&nbsp;&nbsp;<a href="#rfc.iref.m.4"><b>3.2.2</b></a></li>
2043                     </ul>
2044                  </li>
2045               </ul>
2046            </li>
2047            <li><a id="rfc.index.N" href="#rfc.index.N"><b>N</b></a><ul>
2048                  <li>no-cache&nbsp;&nbsp;
2049                     <ul>
2050                        <li>Cache Directive&nbsp;&nbsp;<a href="#rfc.iref.n.1"><b>3.2.1</b></a>, <a href="#rfc.iref.n.4"><b>3.2.2</b></a></li>
2051                     </ul>
2052                  </li>
2053                  <li>no-store&nbsp;&nbsp;
2054                     <ul>
2055                        <li>Cache Directive&nbsp;&nbsp;<a href="#rfc.iref.n.2"><b>3.2.1</b></a>, <a href="#rfc.iref.n.5"><b>3.2.2</b></a></li>
2056                     </ul>
2057                  </li>
2058                  <li>no-transform&nbsp;&nbsp;
2059                     <ul>
2060                        <li>Cache Directive&nbsp;&nbsp;<a href="#rfc.iref.n.3"><b>3.2.1</b></a>, <a href="#rfc.iref.n.6"><b>3.2.2</b></a></li>
2061                     </ul>
2062                  </li>
2063               </ul>
2064            </li>
2065            <li><a id="rfc.index.O" href="#rfc.index.O"><b>O</b></a><ul>
2066                  <li>only-if-cached&nbsp;&nbsp;
2067                     <ul>
2068                        <li>Cache Directive&nbsp;&nbsp;<a href="#rfc.iref.o.1"><b>3.2.1</b></a></li>
2069                     </ul>
2070                  </li>
2071               </ul>
2072            </li>
2073            <li><a id="rfc.index.P" href="#rfc.index.P"><b>P</b></a><ul>
2074                  <li><em>Part1</em>&nbsp;&nbsp;<a href="#rfc.xref.Part1.1">1.4</a>, <a href="#rfc.xref.Part1.2">1.4.1</a>, <a href="#rfc.xref.Part1.3">1.4.1</a>, <a href="#rfc.xref.Part1.4">1.4.1</a>, <a href="#rfc.xref.Part1.5">1.4.1</a>, <a href="#rfc.xref.Part1.6">1.4.2</a>, <a href="#rfc.xref.Part1.7">1.4.2</a>, <a href="#rfc.xref.Part1.8">1.4.2</a>, <a href="#rfc.xref.Part1.9">1.4.2</a>, <a href="#rfc.xref.Part1.10">1.4.2</a>, <a href="#rfc.xref.Part1.11">2.2</a>, <a href="#rfc.xref.Part1.12">2.3.2</a>, <a href="#rfc.xref.Part1.13">2.5</a>, <a href="#rfc.xref.Part1.14">2.5</a>, <a href="#rfc.xref.Part1.15">2.5</a>, <a href="#rfc.xref.Part1.16">2.7</a>, <a href="#rfc.xref.Part1.17">3.3</a>, <a href="#Part1"><b>8.1</b></a><ul>
2075                        <li><em>Section 1.2</em>&nbsp;&nbsp;<a href="#rfc.xref.Part1.1">1.4</a></li>
2076                        <li><em>Section 1.2.2</em>&nbsp;&nbsp;<a href="#rfc.xref.Part1.2">1.4.1</a>, <a href="#rfc.xref.Part1.3">1.4.1</a>, <a href="#rfc.xref.Part1.4">1.4.1</a>, <a href="#rfc.xref.Part1.5">1.4.1</a></li>
2077                        <li><em>Section 2.6</em>&nbsp;&nbsp;<a href="#rfc.xref.Part1.8">1.4.2</a>, <a href="#rfc.xref.Part1.10">1.4.2</a></li>
2078                        <li><em>Section 3.2</em>&nbsp;&nbsp;<a href="#rfc.xref.Part1.6">1.4.2</a>, <a href="#rfc.xref.Part1.16">2.7</a></li>
2079                        <li><em>Section 4.3</em>&nbsp;&nbsp;<a href="#rfc.xref.Part1.11">2.2</a>, <a href="#rfc.xref.Part1.13">2.5</a>, <a href="#rfc.xref.Part1.14">2.5</a>, <a href="#rfc.xref.Part1.15">2.5</a></li>
2080                        <li><em>Section 6.1</em>&nbsp;&nbsp;<a href="#rfc.xref.Part1.7">1.4.2</a>, <a href="#rfc.xref.Part1.17">3.3</a></li>
2081                        <li><em>Section 9.3</em>&nbsp;&nbsp;<a href="#rfc.xref.Part1.12">2.3.2</a></li>
2082                        <li><em>Section 9.9</em>&nbsp;&nbsp;<a href="#rfc.xref.Part1.9">1.4.2</a></li>
2083                     </ul>
2084                  </li>
2085                  <li><em>Part2</em>&nbsp;&nbsp;<a href="#rfc.xref.Part2.1">2.2</a>, <a href="#rfc.xref.Part2.2">2.3.1.1</a>, <a href="#rfc.xref.Part2.3">2.5</a>, <a href="#Part2"><b>8.1</b></a><ul>
2086                        <li><em>Section 7.1.1</em>&nbsp;&nbsp;<a href="#rfc.xref.Part2.1">2.2</a>, <a href="#rfc.xref.Part2.3">2.5</a></li>
2087                        <li><em>Section 8</em>&nbsp;&nbsp;<a href="#rfc.xref.Part2.2">2.3.1.1</a></li>
2088                     </ul>
2089                  </li>
2090                  <li><em>Part4</em>&nbsp;&nbsp;<a href="#rfc.xref.Part4.1">2.3.1.1</a>, <a href="#rfc.xref.Part4.2">2.4</a>, <a href="#rfc.xref.Part4.3">2.8</a>, <a href="#Part4"><b>8.1</b></a><ul>
2091                        <li><em>Section 4</em>&nbsp;&nbsp;<a href="#rfc.xref.Part4.3">2.8</a></li>
2092                        <li><em>Section 6.6</em>&nbsp;&nbsp;<a href="#rfc.xref.Part4.1">2.3.1.1</a></li>
2093                     </ul>
2094                  </li>
2095                  <li><em>Part5</em>&nbsp;&nbsp;<a href="#rfc.xref.Part5.1">2.1.1</a>, <a href="#rfc.xref.Part5.2">2.1.1</a>, <a href="#Part5"><b>8.1</b></a><ul>
2096                        <li><em>Section 4</em>&nbsp;&nbsp;<a href="#rfc.xref.Part5.2">2.1.1</a></li>
2097                     </ul>
2098                  </li>
2099                  <li><em>Part7</em>&nbsp;&nbsp;<a href="#rfc.xref.Part7.1">2.1</a>, <a href="#rfc.xref.Part7.2">2.6</a>, <a href="#rfc.xref.Part7.3">3.2.2</a>, <a href="#Part7"><b>8.1</b></a><ul>
2100                        <li><em>Section 4.1</em>&nbsp;&nbsp;<a href="#rfc.xref.Part7.1">2.1</a>, <a href="#rfc.xref.Part7.2">2.6</a>, <a href="#rfc.xref.Part7.3">3.2.2</a></li>
2101                     </ul>
2102                  </li>
2103                  <li>Pragma header&nbsp;&nbsp;<a href="#rfc.xref.header.pragma.1">2.2</a>, <a href="#rfc.xref.header.pragma.2">3.2</a>, <a href="#rfc.iref.p.5"><b>3.4</b></a>, <a href="#rfc.xref.header.pragma.3">5.2</a></li>
2104                  <li>private&nbsp;&nbsp;
2105                     <ul>
2106                        <li>Cache Directive&nbsp;&nbsp;<a href="#rfc.iref.p.3"><b>3.2.2</b></a></li>
2107                     </ul>
2108                  </li>
2109                  <li>private cache&nbsp;&nbsp;<a href="#rfc.iref.p.1">1.2</a></li>
2110                  <li>proxy-revalidate&nbsp;&nbsp;
2111                     <ul>
2112                        <li>Cache Directive&nbsp;&nbsp;<a href="#rfc.iref.p.4"><b>3.2.2</b></a></li>
2113                     </ul>
2114                  </li>
2115                  <li>public&nbsp;&nbsp;
2116                     <ul>
2117                        <li>Cache Directive&nbsp;&nbsp;<a href="#rfc.iref.p.2"><b>3.2.2</b></a></li>
2118                     </ul>
2119                  </li>
2120               </ul>
2121            </li>
2122            <li><a id="rfc.index.R" href="#rfc.index.R"><b>R</b></a><ul>
2123                  <li><em>RFC1305</em>&nbsp;&nbsp;<a href="#rfc.xref.RFC1305.1">2.2</a>, <a href="#rfc.xref.RFC1305.2">2.3.2</a>, <a href="#RFC1305"><b>8.2</b></a></li>
2124                  <li><em>RFC2119</em>&nbsp;&nbsp;<a href="#rfc.xref.RFC2119.1">1.3</a>, <a href="#RFC2119"><b>8.1</b></a></li>
2125                  <li><em>RFC2616</em>&nbsp;&nbsp;<a href="#rfc.xref.RFC2616.1">2.3.1.1</a>, <a href="#RFC2616"><b>8.2</b></a>, <a href="#rfc.xref.RFC2616.2">C.1</a><ul>
2126                        <li><em>Section 13.9</em>&nbsp;&nbsp;<a href="#rfc.xref.RFC2616.1">2.3.1.1</a></li>
2127                     </ul>
2128                  </li>
2129                  <li><em>RFC3864</em>&nbsp;&nbsp;<a href="#rfc.xref.RFC3864.1">5.2</a>, <a href="#RFC3864"><b>8.2</b></a></li>
2130                  <li><em>RFC5226</em>&nbsp;&nbsp;<a href="#rfc.xref.RFC5226.1">3.2.3</a>, <a href="#RFC5226"><b>8.2</b></a><ul>
2131                        <li><em>Section 4.1</em>&nbsp;&nbsp;<a href="#rfc.xref.RFC5226.1">3.2.3</a></li>
2132                     </ul>
2133                  </li>
2134                  <li><em>RFC5234</em>&nbsp;&nbsp;<a href="#rfc.xref.RFC5234.1">1.4</a>, <a href="#rfc.xref.RFC5234.2">1.4</a>, <a href="#RFC5234"><b>8.1</b></a><ul>
2135                        <li><em>Appendix B.1</em>&nbsp;&nbsp;<a href="#rfc.xref.RFC5234.2">1.4</a></li>
2136                     </ul>
2137                  </li>
2138                  <li><em>RFC5861</em>&nbsp;&nbsp;<a href="#rfc.xref.RFC5861.1">5.1</a>, <a href="#rfc.xref.RFC5861.2">5.1</a>, <a href="#RFC5861"><b>8.2</b></a><ul>
2139                        <li><em>Section 3</em>&nbsp;&nbsp;<a href="#rfc.xref.RFC5861.2">5.1</a></li>
2140                        <li><em>Section 4</em>&nbsp;&nbsp;<a href="#rfc.xref.RFC5861.1">5.1</a></li>
2141                     </ul>
2142                  </li>
2143               </ul>
2144            </li>
2145            <li><a id="rfc.index.S" href="#rfc.index.S"><b>S</b></a><ul>
2146                  <li>s-maxage&nbsp;&nbsp;
2147                     <ul>
2148                        <li>Cache Directive&nbsp;&nbsp;<a href="#rfc.iref.s.3"><b>3.2.2</b></a></li>
2149                     </ul>
2150                  </li>
2151                  <li>shared cache&nbsp;&nbsp;<a href="#rfc.iref.s.1">1.2</a></li>
2152                  <li>stale&nbsp;&nbsp;<a href="#rfc.iref.s.2">1.2</a></li>
2153               </ul>
2154            </li>
2155            <li><a id="rfc.index.V" href="#rfc.index.V"><b>V</b></a><ul>
2156                  <li>validator&nbsp;&nbsp;<a href="#rfc.iref.v.1">1.2</a></li>
2157                  <li>Vary header&nbsp;&nbsp;<a href="#rfc.xref.header.vary.1">2.7</a>, <a href="#rfc.iref.v.2"><b>3.5</b></a>, <a href="#rfc.xref.header.vary.2">5.2</a></li>
2158               </ul>
2159            </li>
2160            <li><a id="rfc.index.W" href="#rfc.index.W"><b>W</b></a><ul>
2161                  <li>Warning header&nbsp;&nbsp;<a href="#rfc.xref.header.warning.1">2.3.3</a>, <a href="#rfc.xref.header.warning.2">2.8</a>, <a href="#rfc.iref.w.1"><b>3.6</b></a>, <a href="#rfc.xref.header.warning.3">5.2</a>, <a href="#rfc.xref.header.warning.4">A</a></li>
2162               </ul>
2163            </li>
2164         </ul>
2165      </div>
2166   </body>
2167</html>
Note: See TracBrowser for help on using the repository browser.