source: draft-ietf-httpbis/06/p6-cache.html

Last change on this file was 2726, checked in by julian.reschke@…, 8 years ago

update to latest version of rfc2629.xslt, regen all HTML

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