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

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

Work-in-progress: hyperlink header field definitions(P4)

  • Property svn:eol-style set to native
  • Property svn:mime-type set to text/html;charset=utf-8
File size: 176.5 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><script>
7var buttonsAdded = false;
9function init() {
10  var fb = document.createElement("div");
11  fb.className = "feedback noprint";
12  fb.setAttribute("onclick", "feedback();");
13  fb.appendChild(document.createTextNode("feedback"));
15  var bodyl = document.getElementsByTagName("body");
16  bodyl.item(0).appendChild(fb);
19function feedback() {
20  toggleButtonsToElementsByName("h1");
21  toggleButtonsToElementsByName("h2");
22  toggleButtonsToElementsByName("h3");
23  toggleButtonsToElementsByName("h4");
25  buttonsAdded = !buttonsAdded;
28function toggleButtonsToElementsByName(name) {
29  var list = document.getElementsByTagName(name);
30  for (var i = 0; i < list.length; i++) {
31    toggleButton(list.item(i));
32  }
35function toggleButton(node) {
36  if (! buttonsAdded) {
38    // docname
39    var template = "{docname},%20%22{section}%22&body=<{ref}>:";
41    var id = node.getAttribute("id");
42    // better id available?
43    var titlelinks = node.getElementsByTagName("a");
44    for (var i = 0; i < titlelinks.length; i++) {
45      var tl = titlelinks.item(i);
46      if (tl.getAttribute("id")) {
47        id = tl.getAttribute("id");
48      }
49    }
51    // ref
52    var ref = window.location.toString();
53    var hash = ref.indexOf("#");
54    if (hash != -1) {
55      ref = ref.substring(0, hash);
56    }
57    if (id != "") {
58      ref += "#" + id;
59    }
61    // docname
62    var docname = "draft-ietf-httpbis-p6-cache-latest";
64    // section
65    var section = node.textContent;
66    section = section.replace("\u00a0", " ");
68    // build URI from template
69    var uri = template.replace("{docname}", encodeURIComponent(docname));
70    uri = uri.replace("{section}", encodeURIComponent(section));
71    uri = uri.replace("{ref}", encodeURIComponent(ref));
73    var button = document.createElement("a");
74    button.className = "fbbutton noprint";
75    button.setAttribute("href", uri);
76    button.appendChild(document.createTextNode("send feedback"));
77    node.appendChild(button);
78  }
79  else {
80    var buttons = node.getElementsByTagName("a");
81    for (var i = 0; i < buttons.length; i++) {
82      var b = buttons.item(i);
83      if (b.className == "fbbutton noprint") {
84        node.removeChild(b);
85      }
86    }
87  }
88}</script><style type="text/css" title="Xml2Rfc (sans serif)">
89a {
90  text-decoration: none;
92a.smpl {
93  color: black;
95a:hover {
96  text-decoration: underline;
98a:active {
99  text-decoration: underline;
101address {
102  margin-top: 1em;
103  margin-left: 2em;
104  font-style: normal;
106body {
107  color: black;
108  font-family: verdana, helvetica, arial, sans-serif;
109  font-size: 10pt;
110  margin-right: 2em;
112cite {
113  font-style: normal;
115div.note {
116  margin-left: 2em;
118dl {
119  margin-left: 2em;
121ul.empty {
122  list-style-type: none;
124ul.empty li {
125  margin-top: .5em;
127dl p {
128  margin-left: 0em;
130dt {
131  margin-top: .5em;
133h1 {
134  font-size: 14pt;
135  line-height: 21pt;
136  page-break-after: avoid;
137} {
139  page-break-before: always;
141h1 a {
142  color: #333333;
144h2 {
145  font-size: 12pt;
146  line-height: 15pt;
147  page-break-after: avoid;
149h3, h4, h5, h6 {
150  font-size: 10pt;
151  page-break-after: avoid;
153h2 a, h3 a, h4 a, h5 a, h6 a {
154  color: black;
156img {
157  margin-left: 3em;
159li {
160  margin-left: 2em;
162ol {
163  margin-left: 2em;
164} {
166  list-style-type: lower-alpha;
167} {
169  list-style-type: upper-alpha;
171ol p {
172  margin-left: 0em;
174p {
175  margin-left: 2em;
177pre {
178  margin-left: 3em;
179  background-color: lightyellow;
180  padding: .25em;
181  page-break-inside: avoid;
183pre.text2 {
184  border-style: dotted;
185  border-width: 1px;
186  background-color: #f0f0f0;
187  width: 69em;
189pre.inline {
190  background-color: white;
191  padding: 0em;
193pre.text {
194  border-style: dotted;
195  border-width: 1px;
196  background-color: #f8f8f8;
197  width: 69em;
199pre.drawing {
200  border-style: solid;
201  border-width: 1px;
202  background-color: #f8f8f8;
203  padding: 2em;
205sup {
206  font-size: 60%;
208table {
209  margin-left: 2em;
210} {
212  vertical-align: top;
214table.full {
215  border-style: outset;
216  border-width: 1px;
218table.headers {
219  border-style: outset;
220  border-width: 1px;
221} td {
223  vertical-align: top;
225table.full td {
226  border-style: inset;
227  border-width: 1px;
228} th {
230  vertical-align: top;
232table.full th {
233  border-style: inset;
234  border-width: 1px;
236table.headers th {
237  border-style: none none inset none;
238  border-width: 1px;
240table.left {
241  margin-right: auto;
243table.right {
244  margin-left: auto;
245} {
247  margin-left: auto;
248  margin-right: auto;
250caption {
251  caption-side: bottom;
252  font-weight: bold;
253  font-size: 9pt;
254  margin-top: .5em;
257table.header {
258  border-spacing: 1px;
259  width: 95%;
260  font-size: 10pt;
261  color: white;
262} {
264  vertical-align: top;
266td.topnowrap {
267  vertical-align: top;
268  white-space: nowrap;
270table.header td {
271  background-color: gray;
272  width: 50%;
274table.header a {
275  color: white;
277td.reference {
278  vertical-align: top;
279  white-space: nowrap;
280  padding-right: 1em;
282thead {
283  display:table-header-group;
285ul.toc, ul.toc ul {
286  list-style: none;
287  margin-left: 1.5em;
288  padding-left: 0em;
290ul.toc li {
291  line-height: 150%;
292  font-weight: bold;
293  font-size: 10pt;
294  margin-left: 0em;
296ul.toc li li {
297  line-height: normal;
298  font-weight: normal;
299  font-size: 9pt;
300  margin-left: 0em;
302li.excluded {
303  font-size: 0pt;
305ul p {
306  margin-left: 0em;
308ul.ind, ul.ind ul {
309  list-style: none;
310  margin-left: 1.5em;
311  padding-left: 0em;
312  page-break-before: avoid;
314ul.ind li {
315  font-weight: bold;
316  line-height: 200%;
317  margin-left: 0em;
319ul.ind li li {
320  font-weight: normal;
321  line-height: 150%;
322  margin-left: 0em;
324.avoidbreak {
325  page-break-inside: avoid;
327.bcp14 {
328  font-style: normal;
329  text-transform: lowercase;
330  font-variant: small-caps;
332.comment {
333  background-color: yellow;
334} {
336  text-align: center;
338.error {
339  color: red;
340  font-style: italic;
341  font-weight: bold;
343.figure {
344  font-weight: bold;
345  text-align: center;
346  font-size: 9pt;
348.filename {
349  color: #333333;
350  font-weight: bold;
351  font-size: 12pt;
352  line-height: 21pt;
353  text-align: center;
355.fn {
356  font-weight: bold;
358.hidden {
359  display: none;
361.left {
362  text-align: left;
364.right {
365  text-align: right;
367.title {
368  color: #990000;
369  font-size: 18pt;
370  line-height: 18pt;
371  font-weight: bold;
372  text-align: center;
373  margin-top: 36pt;
375.vcardline {
376  display: block;
378.warning {
379  font-size: 14pt;
380  background-color: yellow;
381} {
383  position: fixed;
384  bottom: 1%;
385  right: 1%;
386  padding: 3px 5px;
387  color: white;
388  border-radius: 5px;
389  background: #a00000;
390  border: 1px solid silver;
392.fbbutton {
393  margin-left: 1em;
394  color: #303030;
395  font-size: small;
396  font-weight: normal;
397  background: #d0d000;
398  padding: 1px 4px;
399  border: 1px solid silver;
400  border-radius: 5px;
403@media print {
404  .noprint {
405    display: none;
406  }
408  a {
409    color: black;
410    text-decoration: none;
411  }
413  table.header {
414    width: 90%;
415  }
417  td.header {
418    width: 50%;
419    color: black;
420    background-color: white;
421    vertical-align: top;
422    font-size: 12pt;
423  }
425  ul.toc a::after {
426    content: leader('.') target-counter(attr(href), page);
427  }
429  ul.ind li li a {
430    content: target-counter(attr(href), page);
431  }
433  .print2col {
434    column-count: 2;
435    -moz-column-count: 2;
436    column-fill: auto;
437  }
440@page {
441  @top-left {
442       content: "Internet-Draft";
443  }
444  @top-right {
445       content: "July 2012";
446  }
447  @top-center {
448       content: "HTTP/1.1, Part 6";
449  }
450  @bottom-left {
451       content: "Fielding, et al.";
452  }
453  @bottom-center {
454       content: "Expires January 9, 2013";
455  }
456  @bottom-right {
457       content: "[Page " counter(page) "]";
458  }
461@page:first {
462    @top-left {
463      content: normal;
464    }
465    @top-right {
466      content: normal;
467    }
468    @top-center {
469      content: normal;
470    }
472</style><link rel="Contents" href="#rfc.toc">
473      <link rel="Author" href="#rfc.authors">
474      <link rel="Copyright" href="#rfc.copyrightnotice">
475      <link rel="Index" href="#rfc.index">
476      <link rel="Chapter" title="1 Introduction" href="#rfc.section.1">
477      <link rel="Chapter" title="2 Cache Operation" href="#rfc.section.2">
478      <link rel="Chapter" title="3 Header Field Definitions" href="#rfc.section.3">
479      <link rel="Chapter" title="4 History Lists" href="#rfc.section.4">
480      <link rel="Chapter" title="5 IANA Considerations" href="#rfc.section.5">
481      <link rel="Chapter" title="6 Security Considerations" href="#rfc.section.6">
482      <link rel="Chapter" title="7 Acknowledgments" href="#rfc.section.7">
483      <link rel="Chapter" href="#rfc.section.8" title="8 References">
484      <link rel="Appendix" title="A Changes from RFC 2616" href="#rfc.section.A">
485      <link rel="Appendix" title="B Collected ABNF" href="#rfc.section.B">
486      <link rel="Appendix" title="C Change Log (to be removed by RFC Editor before publication)" href="#rfc.section.C">
487      <link href="p5-range.html" rel="prev">
488      <link href="p7-auth.html" rel="next">
489      <meta name="generator" content=", Revision 1.584, 2012-06-24 15:59:38, XSLT vendor: SAXON 8.9 from Saxonica">
490      <link rel="schema.dct" href="">
491      <meta name="dct.creator" content="Fielding, R.">
492      <meta name="dct.creator" content="Lafon, Y.">
493      <meta name="dct.creator" content="Nottingham, M.">
494      <meta name="dct.creator" content="Reschke, J. F.">
495      <meta name="dct.identifier" content="urn:ietf:id:draft-ietf-httpbis-p6-cache-latest">
496      <meta name="dct.issued" scheme="ISO8601" content="2012-07-08">
497      <meta name="dct.replaces" content="urn:ietf:rfc:2616">
498      <meta name="dct.abstract" content="The Hypertext Transfer Protocol (HTTP) is an application-level protocol for distributed, collaborative, hypertext information systems. HTTP has been in use by the World Wide Web global information initiative since 1990. 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.">
499      <meta name="description" content="The Hypertext Transfer Protocol (HTTP) is an application-level protocol for distributed, collaborative, hypertext information systems. HTTP has been in use by the World Wide Web global information initiative since 1990. 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.">
500   </head>
501   <body onload="init();">
502      <table class="header">
503         <tbody>
504            <tr>
505               <td class="left">HTTPbis Working Group</td>
506               <td class="right">R. Fielding, Editor</td>
507            </tr>
508            <tr>
509               <td class="left">Internet-Draft</td>
510               <td class="right">Adobe</td>
511            </tr>
512            <tr>
513               <td class="left">Obsoletes: <a href="">2616</a> (if approved)
514               </td>
515               <td class="right">Y. Lafon, Editor</td>
516            </tr>
517            <tr>
518               <td class="left">Intended status: Standards Track</td>
519               <td class="right">W3C</td>
520            </tr>
521            <tr>
522               <td class="left">Expires: January 9, 2013</td>
523               <td class="right">M. Nottingham, Editor</td>
524            </tr>
525            <tr>
526               <td class="left"></td>
527               <td class="right">Rackspace</td>
528            </tr>
529            <tr>
530               <td class="left"></td>
531               <td class="right">J. Reschke, Editor</td>
532            </tr>
533            <tr>
534               <td class="left"></td>
535               <td class="right">greenbytes</td>
536            </tr>
537            <tr>
538               <td class="left"></td>
539               <td class="right">July 8, 2012</td>
540            </tr>
541         </tbody>
542      </table>
543      <p class="title">HTTP/1.1, part 6: Caching<br><span class="filename">draft-ietf-httpbis-p6-cache-latest</span></p>
544      <h1 id="rfc.abstract"><a href="#rfc.abstract">Abstract</a></h1>
545      <p>The Hypertext Transfer Protocol (HTTP) is an application-level protocol for distributed, collaborative, hypertext information
546         systems. HTTP has been in use by the World Wide Web global information initiative since 1990. This document is Part 6 of the
547         seven-part specification that defines the protocol referred to as "HTTP/1.1" and, taken together, obsoletes RFC 2616.
548      </p> 
549      <p>Part 6 defines requirements on HTTP caches and the associated header fields that control cache behavior or indicate cacheable
550         response messages.
551      </p>
552      <h1 id="rfc.note.1"><a href="#rfc.note.1">Editorial Note (To be removed by RFC Editor)</a></h1>
553      <p>Discussion of this draft ought to take place on the HTTPBIS working group mailing list (, which is archived
554         at &lt;<a href=""></a>&gt;.
555      </p> 
556      <p>The current issues list is at &lt;<a href=""></a>&gt; and related documents (including fancy diffs) can be found at &lt;<a href=""></a>&gt;.
557      </p> 
558      <p>The changes in this draft are summarized in <a href="#changes.since.19" title="Since draft-ietf-httpbis-p6-cache-19">Appendix&nbsp;C.1</a>.
559      </p>
560      <h1><a id="rfc.status" href="#rfc.status">Status of This Memo</a></h1>
561      <p>This Internet-Draft is submitted in full conformance with the provisions of BCP 78 and BCP 79.</p>
562      <p>Internet-Drafts are working documents of the Internet Engineering Task Force (IETF). Note that other groups may also distribute
563         working documents as Internet-Drafts. The list of current Internet-Drafts is at <a href=""></a>.
564      </p>
565      <p>Internet-Drafts are draft documents valid for a maximum of six months and may be updated, replaced, or obsoleted by other
566         documents at any time. It is inappropriate to use Internet-Drafts as reference material or to cite them other than as “work
567         in progress”.
568      </p>
569      <p>This Internet-Draft will expire on January 9, 2013.</p>
570      <h1><a id="rfc.copyrightnotice" href="#rfc.copyrightnotice">Copyright Notice</a></h1>
571      <p>Copyright © 2012 IETF Trust and the persons identified as the document authors. All rights reserved.</p>
572      <p>This document is subject to BCP 78 and the IETF Trust's Legal Provisions Relating to IETF Documents (<a href=""></a>) in effect on the date of publication of this document. Please review these documents carefully, as they describe your rights
573         and restrictions with respect to this document. Code Components extracted from this document must include Simplified BSD License
574         text as described in Section 4.e of the Trust Legal Provisions and are provided without warranty as described in the Simplified
575         BSD License.
576      </p>
577      <p>This document may contain material from IETF Documents or IETF Contributions published or made publicly available before November
578         10, 2008. The person(s) controlling the copyright in some of this material may not have granted the IETF Trust the right to
579         allow modifications of such material outside the IETF Standards Process. Without obtaining an adequate license from the person(s)
580         controlling the copyright in such materials, this document may not be modified outside the IETF Standards Process, and derivative
581         works of it may not be created outside the IETF Standards Process, except to format it for publication as an RFC or to translate
582         it into languages other than English.
583      </p>
584      <hr class="noprint">
585      <h1 class="np" id="rfc.toc"><a href="#rfc.toc">Table of Contents</a></h1>
586      <ul class="toc">
587         <li>1.&nbsp;&nbsp;&nbsp;<a href="#caching">Introduction</a><ul>
588               <li>1.1&nbsp;&nbsp;&nbsp;<a href="#intro.purpose">Purpose</a></li>
589               <li>1.2&nbsp;&nbsp;&nbsp;<a href="#intro.terminology">Terminology</a></li>
590               <li>1.3&nbsp;&nbsp;&nbsp;<a href="#intro.conformance.and.error.handling">Conformance and Error Handling</a></li>
591               <li>1.4&nbsp;&nbsp;&nbsp;<a href="#notation">Syntax Notation</a><ul>
592                     <li>1.4.1&nbsp;&nbsp;&nbsp;<a href="#core.rules">Core Rules</a></li>
593                     <li>1.4.2&nbsp;&nbsp;&nbsp;<a href="#abnf.dependencies">ABNF Rules defined in other Parts of the Specification</a></li>
594                  </ul>
595               </li>
596               <li>1.5&nbsp;&nbsp;&nbsp;<a href="#delta-seconds">Delta Seconds</a></li>
597            </ul>
598         </li>
599         <li>2.&nbsp;&nbsp;&nbsp;<a href="#caching.overview">Cache Operation</a><ul>
600               <li>2.1&nbsp;&nbsp;&nbsp;<a href="#response.cacheability">Response Cacheability</a></li>
601               <li>2.2&nbsp;&nbsp;&nbsp;<a href="#constructing.responses.from.caches">Constructing Responses from Caches</a></li>
602               <li>2.3&nbsp;&nbsp;&nbsp;<a href="#expiration.model">Freshness Model</a><ul>
603                     <li>2.3.1&nbsp;&nbsp;&nbsp;<a href="#calculating.freshness.lifetime">Calculating Freshness Lifetime</a><ul>
604                           <li>;&nbsp;&nbsp;<a href="#heuristic.freshness">Calculating Heuristic Freshness</a></li>
605                        </ul>
606                     </li>
607                     <li>2.3.2&nbsp;&nbsp;&nbsp;<a href="#age.calculations">Calculating Age</a></li>
608                     <li>2.3.3&nbsp;&nbsp;&nbsp;<a href="#serving.stale.responses">Serving Stale Responses</a></li>
609                  </ul>
610               </li>
611               <li>2.4&nbsp;&nbsp;&nbsp;<a href="#validation.model">Validation Model</a><ul>
612                     <li>2.4.1&nbsp;&nbsp;&nbsp;<a href="#freshening.responses">Freshening Responses with 304 Not Modified</a></li>
613                  </ul>
614               </li>
615               <li>2.5&nbsp;&nbsp;&nbsp;<a href="#head.effects">Updating Caches with HEAD Responses</a></li>
616               <li>2.6&nbsp;&nbsp;&nbsp;<a href="#invalidation.after.updates.or.deletions">Request Methods that Invalidate</a></li>
617               <li>2.7&nbsp;&nbsp;&nbsp;<a href="#caching.authenticated.responses">Shared Caching of Authenticated Responses</a></li>
618               <li>2.8&nbsp;&nbsp;&nbsp;<a href="#caching.negotiated.responses">Caching Negotiated Responses</a></li>
619               <li>2.9&nbsp;&nbsp;&nbsp;<a href="#combining.responses">Combining Partial Content</a></li>
620            </ul>
621         </li>
622         <li>3.&nbsp;&nbsp;&nbsp;<a href="#header.field.definitions">Header Field Definitions</a><ul>
623               <li>3.1&nbsp;&nbsp;&nbsp;<a href="#header.age">Age</a></li>
624               <li>3.2&nbsp;&nbsp;&nbsp;<a href="#header.cache-control">Cache-Control</a><ul>
625                     <li>3.2.1&nbsp;&nbsp;&nbsp;<a href="#cache-request-directive">Request Cache-Control Directives</a><ul>
626                           <li>;&nbsp;&nbsp;<a href="">no-cache</a></li>
627                           <li>;&nbsp;&nbsp;<a href="">no-store</a></li>
628                           <li>;&nbsp;&nbsp;<a href="#cache-request-directive.max-age">max-age</a></li>
629                           <li>;&nbsp;&nbsp;<a href="#cache-request-directive.max-stale">max-stale</a></li>
630                           <li>;&nbsp;&nbsp;<a href="#cache-request-directive.min-fresh">min-fresh</a></li>
631                           <li>;&nbsp;&nbsp;<a href="">no-transform</a></li>
632                           <li>;&nbsp;&nbsp;<a href="#cache-request-directive.only-if-cached">only-if-cached</a></li>
633                        </ul>
634                     </li>
635                     <li>3.2.2&nbsp;&nbsp;&nbsp;<a href="#cache-response-directive">Response Cache-Control Directives</a><ul>
636                           <li>;&nbsp;&nbsp;<a href="#cache-response-directive.only-if-cached">public</a></li>
637                           <li>;&nbsp;&nbsp;<a href="#cache-response-directive.private">private</a></li>
638                           <li>;&nbsp;&nbsp;<a href="">no-cache</a></li>
639                           <li>;&nbsp;&nbsp;<a href="">no-store</a></li>
640                           <li>;&nbsp;&nbsp;<a href="#cache-response-directive.must-revalidate">must-revalidate</a></li>
641                           <li>;&nbsp;&nbsp;<a href="#cache-response-directive.proxy-revalidate">proxy-revalidate</a></li>
642                           <li>;&nbsp;&nbsp;<a href="#cache-response-directive.max-age">max-age</a></li>
643                           <li>;&nbsp;&nbsp;<a href="#cache-response-directive.s-maxage">s-maxage</a></li>
644                           <li>;&nbsp;&nbsp;<a href="">no-transform</a></li>
645                        </ul>
646                     </li>
647                     <li>3.2.3&nbsp;&nbsp;&nbsp;<a href="#cache.control.extensions">Cache Control Extensions</a></li>
648                  </ul>
649               </li>
650               <li>3.3&nbsp;&nbsp;&nbsp;<a href="#header.expires">Expires</a></li>
651               <li>3.4&nbsp;&nbsp;&nbsp;<a href="#header.pragma">Pragma</a></li>
652               <li>3.5&nbsp;&nbsp;&nbsp;<a href="#header.vary">Vary</a></li>
653               <li>3.6&nbsp;&nbsp;&nbsp;<a href="#header.warning">Warning</a><ul>
654                     <li>3.6.1&nbsp;&nbsp;&nbsp;<a href="#warn.110">110 Response is Stale</a></li>
655                     <li>3.6.2&nbsp;&nbsp;&nbsp;<a href="#warn.111">111 Revalidation Failed</a></li>
656                     <li>3.6.3&nbsp;&nbsp;&nbsp;<a href="#warn.112">112 Disconnected Operation</a></li>
657                     <li>3.6.4&nbsp;&nbsp;&nbsp;<a href="#warn.113">113 Heuristic Expiration</a></li>
658                     <li>3.6.5&nbsp;&nbsp;&nbsp;<a href="#warn.199">199 Miscellaneous Warning</a></li>
659                     <li>3.6.6&nbsp;&nbsp;&nbsp;<a href="#warn.214">214 Transformation Applied</a></li>
660                     <li>3.6.7&nbsp;&nbsp;&nbsp;<a href="#warn.299">299 Miscellaneous Persistent Warning</a></li>
661                     <li>3.6.8&nbsp;&nbsp;&nbsp;<a href="#warn.code.extensions">Warn Code Extensions</a></li>
662                  </ul>
663               </li>
664            </ul>
665         </li>
666         <li>4.&nbsp;&nbsp;&nbsp;<a href="#history.lists">History Lists</a></li>
667         <li>5.&nbsp;&nbsp;&nbsp;<a href="#IANA.considerations">IANA Considerations</a><ul>
668               <li>5.1&nbsp;&nbsp;&nbsp;<a href="#cache.directive.registration">Cache Directive Registry</a></li>
669               <li>5.2&nbsp;&nbsp;&nbsp;<a href="#warn.code.registration">Warn Code Registry</a></li>
670               <li>5.3&nbsp;&nbsp;&nbsp;<a href="#header.field.registration">Header Field Registration</a></li>
671            </ul>
672         </li>
673         <li>6.&nbsp;&nbsp;&nbsp;<a href="#security.considerations">Security Considerations</a></li>
674         <li>7.&nbsp;&nbsp;&nbsp;<a href="#acks">Acknowledgments</a></li>
675         <li>8.&nbsp;&nbsp;&nbsp;<a href="#rfc.references">References</a><ul>
676               <li>8.1&nbsp;&nbsp;&nbsp;<a href="#rfc.references.1">Normative References</a></li>
677               <li>8.2&nbsp;&nbsp;&nbsp;<a href="#rfc.references.2">Informative References</a></li>
678            </ul>
679         </li>
680         <li><a href="#rfc.authors">Authors' Addresses</a></li>
681         <li>A.&nbsp;&nbsp;&nbsp;<a href="#changes.from.rfc.2616">Changes from RFC 2616</a></li>
682         <li>B.&nbsp;&nbsp;&nbsp;<a href="#collected.abnf">Collected ABNF</a></li>
683         <li>C.&nbsp;&nbsp;&nbsp;<a href="#change.log">Change Log (to be removed by RFC Editor before publication)</a><ul>
684               <li>C.1&nbsp;&nbsp;&nbsp;<a href="#changes.since.19">Since draft-ietf-httpbis-p6-cache-19</a></li>
685            </ul>
686         </li>
687         <li><a href="#rfc.index">Index</a></li>
688      </ul>
689      <h1 id="rfc.section.1" class="np"><a href="#rfc.section.1">1.</a>&nbsp;<a id="caching" href="#caching">Introduction</a></h1>
690      <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.
691         This document defines aspects of HTTP/1.1 related to caching and reusing response messages.
692      </p>
693      <div id="rfc.iref.c.1"></div>
694      <h2 id="rfc.section.1.1"><a href="#rfc.section.1.1">1.1</a>&nbsp;<a id="intro.purpose" href="#intro.purpose">Purpose</a></h2>
695      <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
696         stores cacheable responses in order to reduce the response time and network bandwidth consumption on future, equivalent requests.
697         Any client or server <em class="bcp14">MAY</em> employ a cache, though a cache cannot be used by a server that is acting as a tunnel.
698      </p>
699      <p id="rfc.section.1.1.p.2">The goal of caching in HTTP/1.1 is to significantly improve performance by reusing a prior response message to satisfy a current
700         request. A stored response is considered "fresh", as defined in <a href="#expiration.model" title="Freshness Model">Section&nbsp;2.3</a>, if the response can be reused without "validation" (checking with the origin server to see if the cached response remains
701         valid for this request). A fresh cache response can therefore reduce both latency and network transfers each time it is reused.
702         When a cached response is not fresh, it might still be reusable if it can be freshened by validation (<a href="#validation.model" title="Validation Model">Section&nbsp;2.4</a>) or if the origin is unavailable.
703      </p>
704      <h2 id="rfc.section.1.2"><a href="#rfc.section.1.2">1.2</a>&nbsp;<a id="intro.terminology" href="#intro.terminology">Terminology</a></h2>
705      <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>
706      <p id="rfc.section.1.2.p.2"> <span id="rfc.iref.c.2"></span>  <dfn>cache</dfn> 
707      </p>
708      <ul class="empty">
709         <li>A conformant implementation of a HTTP cache. Note that this implies an HTTP/1.1 cache; this specification does not define
710            conformance for HTTP/1.0 caches.
711         </li>
712      </ul>
713      <div id="shared.and.non-shared.caches">
714         <p id="rfc.section.1.2.p.3"> <span id="rfc.iref.s.1"></span>  <dfn>shared cache</dfn> 
715         </p>
716         <ul class="empty">
717            <li>A cache that stores responses to be reused by more than one user; usually (but not always) deployed as part of an intermediary.</li>
718         </ul>
719      </div>
720      <p id="rfc.section.1.2.p.4"> <span id="rfc.iref.p.1"></span>  <dfn>private cache</dfn> 
721      </p>
722      <ul class="empty">
723         <li>A cache that is dedicated to a single user.</li>
724      </ul>
725      <p id="rfc.section.1.2.p.5"> <span id="rfc.iref.c.3"></span>  <dfn>cacheable</dfn> 
726      </p>
727      <ul class="empty">
728         <li>A response is cacheable if a cache is allowed to store a copy of the response message for use in answering subsequent requests.
729            Even when a response is cacheable, there might be additional constraints on whether a cache can use the stored copy to satisfy
730            a particular request.
731         </li>
732      </ul>
733      <p id="rfc.section.1.2.p.6"> <span id="rfc.iref.e.1"></span>  <dfn>explicit expiration time</dfn> 
734      </p>
735      <ul class="empty">
736         <li>The time at which the origin server intends that a representation no longer be returned by a cache without further validation.</li>
737      </ul>
738      <p id="rfc.section.1.2.p.7"> <span id="rfc.iref.h.1"></span>  <dfn>heuristic expiration time</dfn> 
739      </p>
740      <ul class="empty">
741         <li>An expiration time assigned by a cache when no explicit expiration time is available.</li>
742      </ul>
743      <p id="rfc.section.1.2.p.8"> <span id="rfc.iref.a.1"></span>  <dfn>age</dfn> 
744      </p>
745      <ul class="empty">
746         <li>The age of a response is the time since it was sent by, or successfully validated with, the origin server.</li>
747      </ul>
748      <p id="rfc.section.1.2.p.9"> <span id="rfc.iref.f.1"></span>  <dfn>first-hand</dfn> 
749      </p>
750      <ul class="empty">
751         <li>A response is first-hand if the freshness model is not in use; i.e., its age is 0.</li>
752      </ul>
753      <p id="rfc.section.1.2.p.10"> <span id="rfc.iref.f.2"></span>  <dfn>freshness lifetime</dfn> 
754      </p>
755      <ul class="empty">
756         <li>The length of time between the generation of a response and its expiration time.</li>
757      </ul>
758      <p id="rfc.section.1.2.p.11"> <span id="rfc.iref.f.3"></span>  <dfn>fresh</dfn> 
759      </p>
760      <ul class="empty">
761         <li>A response is fresh if its age has not yet exceeded its freshness lifetime.</li>
762      </ul>
763      <p id="rfc.section.1.2.p.12"> <span id="rfc.iref.s.2"></span>  <dfn>stale</dfn> 
764      </p>
765      <ul class="empty">
766         <li>A response is stale if its age has passed its freshness lifetime (either explicit or heuristic).</li>
767      </ul>
768      <p id="rfc.section.1.2.p.13"> <span id="rfc.iref.v.1"></span>  <dfn>validator</dfn> 
769      </p>
770      <ul class="empty">
771         <li>A protocol element (e.g., an entity-tag or a <a href="p4-conditional.html#header.last-modified" class="smpl">Last-Modified</a> time) that is used to find out whether a stored response is an equivalent copy of a representation. See <a href="p4-conditional.html#weak.and.strong.validators" title="Weak versus Strong">Section 2.1</a> of <a href="#Part4" id="rfc.xref.Part4.1"><cite title="HTTP/1.1, part 4: Conditional Requests">[Part4]</cite></a>.
772         </li>
773      </ul>
774      <p id="rfc.section.1.2.p.14"> <span id="rfc.iref.s.3"></span>  <span id="rfc.iref.v.2"></span>  <dfn>strong validator</dfn> 
775      </p>
776      <ul class="empty">
777         <li>A validator that is defined by the origin server such that its current value will change if the representation body changes;
778            i.e., an entity-tag that is not marked as weak (<a href="p4-conditional.html#header.etag" title="ETag">Section 2.3</a> of <a href="#Part4" id="rfc.xref.Part4.2"><cite title="HTTP/1.1, part 4: Conditional Requests">[Part4]</cite></a>) or, if no entity-tag is provided, a <a href="p4-conditional.html#header.last-modified" class="smpl">Last-Modified</a> value that is strong in the sense defined by <a href="p4-conditional.html#lastmod.comparison" title="Comparison">Section 2.2.2</a> of <a href="#Part4" id="rfc.xref.Part4.3"><cite title="HTTP/1.1, part 4: Conditional Requests">[Part4]</cite></a>.
779         </li>
780      </ul>
781      <h2 id="rfc.section.1.3"><a href="#rfc.section.1.3">1.3</a>&nbsp;<a id="intro.conformance.and.error.handling" href="#intro.conformance.and.error.handling">Conformance and Error Handling</a></h2>
782      <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"
783         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>.
784      </p>
785      <p id="rfc.section.1.3.p.2">This document defines conformance criteria for several roles in HTTP communication, including Senders, Recipients, Clients,
786         Servers, User-Agents, Origin Servers, Intermediaries, Proxies and Gateways. See <a href="p1-messaging.html#architecture" title="Architecture">Section 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> for definitions of these terms.
787      </p>
788      <p id="rfc.section.1.3.p.3">An implementation is considered conformant if it complies with all of the requirements associated with its role(s). Note that
789         SHOULD-level requirements are relevant here, unless one of the documented exceptions is applicable.
790      </p>
791      <p id="rfc.section.1.3.p.4">This document also uses ABNF to define valid protocol elements (<a href="#notation" title="Syntax Notation">Section&nbsp;1.4</a>). In addition to the prose requirements placed upon them, Senders <em class="bcp14">MUST NOT</em> generate protocol elements that are invalid.
792      </p>
793      <p id="rfc.section.1.3.p.5">Unless noted otherwise, Recipients <em class="bcp14">MUST</em> be able to parse all protocol elements matching the ABNF rules defined for them and <em class="bcp14">MAY</em> take steps to recover a usable protocol element from an invalid construct. However, HTTP does not define specific error handling
794         mechanisms, except in cases where it has direct impact on security. This is because different uses of the protocol require
795         different error handling strategies; for example, a Web browser might wish to transparently recover from a response where
796         the Location header field doesn't parse according to the ABNF, whereby in a systems control protocol using HTTP, this type
797         of error recovery could lead to dangerous consequences.
798      </p>
799      <h2 id="rfc.section.1.4"><a href="#rfc.section.1.4">1.4</a>&nbsp;<a id="notation" href="#notation">Syntax Notation</a></h2>
800      <p id="rfc.section.1.4.p.1">This specification uses the Augmented Backus-Naur Form (ABNF) notation of <a href="#RFC5234" id="rfc.xref.RFC5234.1"><cite title="Augmented BNF for Syntax Specifications: ABNF">[RFC5234]</cite></a> with the list rule extension defined in <a href="p1-messaging.html#notation" title="Syntax Notation">Section 1.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>. <a href="#collected.abnf" title="Collected ABNF">Appendix&nbsp;B</a> shows the collected ABNF with the list rule expanded.
801      </p>
802      <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
803         (hexadecimal 0-9/A-F/a-f), LF (line feed), OCTET (any 8-bit sequence of data), SP (space), and VCHAR (any visible US-ASCII
804         character).
805      </p>
806      <h3 id="rfc.section.1.4.1"><a href="#rfc.section.1.4.1">1.4.1</a>&nbsp;<a id="core.rules" href="#core.rules">Core Rules</a></h3>
807      <p id="rfc.section.1.4.1.p.1">The core rules below are 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>:
808      </p>
809      <div id="rfc.figure.u.1"></div><pre class="inline">  <a href="#core.rules" class="smpl">OWS</a>           = &lt;OWS, 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#whitespace" title="Whitespace">Section 3.2.1</a>&gt;
810  <a href="#core.rules" class="smpl">quoted-string</a> = &lt;quoted-string, 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#field.components" title="Field value components">Section 3.2.4</a>&gt;
811  <a href="#core.rules" class="smpl">token</a>         = &lt;token, 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#field.components" title="Field value components">Section 3.2.4</a>&gt;
812</pre><h3 id="rfc.section.1.4.2"><a href="#rfc.section.1.4.2">1.4.2</a>&nbsp;<a id="abnf.dependencies" href="#abnf.dependencies">ABNF Rules defined in other Parts of the Specification</a></h3>
813      <p id="rfc.section.1.4.2.p.1">The ABNF rules below are defined in other parts:</p>
814      <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.7"><cite title="HTTP/1.1, part 1: URIs, Connections, and Message Parsing">[Part1]</cite></a>, <a href="p1-messaging.html#header.fields" title="Header Fields">Section 3.2</a>&gt;
815  <a href="#abnf.dependencies" class="smpl">HTTP-date</a>     = &lt;HTTP-date, defined in <a href="#Part2" id="rfc.xref.Part2.1"><cite title="HTTP/1.1, part 2: Message Semantics, Payload and Content Negotiation">[Part2]</cite></a>, <a href="" title="Date/Time Formats">Section 5.1</a>&gt;
816  <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.7</a>&gt;
817  <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 6.2</a>&gt;
818  <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.7</a>&gt;
819</pre><h2 id="rfc.section.1.5"><a href="#rfc.section.1.5">1.5</a>&nbsp;<a id="delta-seconds" href="#delta-seconds">Delta Seconds</a></h2>
820      <p id="rfc.section.1.5.p.1">The delta-seconds rule specifies a non-negative integer, representing time in seconds.</p>
821      <div id="rfc.figure.u.3"></div><pre class="inline"><span id="rfc.iref.g.1"></span>  <a href="#delta-seconds" class="smpl">delta-seconds</a>  = 1*<a href="#notation" class="smpl">DIGIT</a>
822</pre><p id="rfc.section.1.5.p.3">If an implementation receives a delta-seconds value larger than the largest positive integer it can represent, or if any of
823         its subsequent calculations overflows, it <em class="bcp14">MUST</em> consider the value to be 2147483648 (2<sup>31</sup>). Recipients parsing a delta-seconds value <em class="bcp14">MUST</em> use an arithmetic type of at least 31 bits of range, and senders <em class="bcp14">MUST NOT</em> send delta-seconds with a value greater than 2147483648.
824      </p>
825      <div id="rfc.iref.c.4"></div>
826      <div id="rfc.iref.c.5"></div>
827      <h1 id="rfc.section.2"><a href="#rfc.section.2">2.</a>&nbsp;<a id="caching.overview" href="#caching.overview">Cache Operation</a></h1>
828      <p id="rfc.section.2.p.1">Proper cache operation preserves the semantics of HTTP transfers (<a href="#Part2" id="rfc.xref.Part2.2"><cite title="HTTP/1.1, part 2: Message Semantics, Payload and Content Negotiation">[Part2]</cite></a>) while eliminating the transfer of information already held in the cache. Although caching is an entirely <em class="bcp14">OPTIONAL</em> feature of HTTP, we assume that reusing the cached response is desirable and that such reuse is the default behavior when
829         no requirement or locally-desired configuration prevents it. Therefore, HTTP cache requirements are focused on preventing
830         a cache from either storing a non-reusable response or reusing a stored response inappropriately.
831      </p>
832      <p id="rfc.section.2.p.2">Each <dfn>cache entry</dfn> consists of a cache key and one or more HTTP responses corresponding to prior requests that used the same key. The most common
833         form of cache entry is a successful result of a retrieval request: i.e., a <a href="p2-semantics.html#status.200" class="smpl">200 (OK)</a> response containing a representation of the resource identified by the request target. However, it is also possible to cache
834         negative results (e.g., <a href="p2-semantics.html#status.404" class="smpl">404 (Not Found)</a>, incomplete results (e.g., <a href="p5-range.html#status.206" class="smpl">206 (Partial Content)</a>), and responses to safe methods other than GET if the method's definition allows such caching and defines something suitable
835         for use as a cache key.
836      </p>
837      <p id="rfc.section.2.p.3">The default <dfn>cache key</dfn> consists of the request method and target URI. However, since HTTP caches in common use today are typically limited to caching
838         responses to GET, most implementations simply decline other methods and use only the URI as the key.
839      </p>
840      <p id="rfc.section.2.p.4">If a request target is subject to content negotiation, its cache entry might consist of multiple stored responses, each differentiated
841         by a secondary key for the values of the original request's selecting header fields (<a href="#caching.negotiated.responses" title="Caching Negotiated Responses">Section&nbsp;2.8</a>).
842      </p>
843      <h2 id="rfc.section.2.1"><a href="#rfc.section.2.1">2.1</a>&nbsp;<a id="response.cacheability" href="#response.cacheability">Response Cacheability</a></h2>
844      <p id="rfc.section.2.1.p.1">A cache <em class="bcp14">MUST NOT</em> store a response to any request, unless:
845      </p>
846      <ul>
847         <li>The request method is understood by the cache and defined as being cacheable, and</li>
848         <li>the response status code is understood by the cache, and</li>
849         <li>the "no-store" cache directive (see <a href="#header.cache-control" id="rfc.xref.header.cache-control.1" title="Cache-Control">Section&nbsp;3.2</a>) does not appear in request or response header fields, and
850         </li>
851         <li>the "private" cache response directive (see <a href="#cache-response-directive" title="Response Cache-Control Directives">Section&nbsp;3.2.2</a>) does not appear in the response, if the cache is shared, and
852         </li>
853         <li>the <a href="p7-auth.html#header.authorization" class="smpl">Authorization</a> header field (see <a href="p7-auth.html#header.authorization" title="Authorization">Section 4.1</a> of <a href="#Part7" id="rfc.xref.Part7.1"><cite title="HTTP/1.1, part 7: Authentication">[Part7]</cite></a>) does not appear in the request, if the cache is shared, unless the response explicitly allows it (see <a href="#caching.authenticated.responses" title="Shared Caching of Authenticated Responses">Section&nbsp;2.7</a>), and
854         </li>
855         <li>the response either:
856            <ul>
857               <li>contains an <a href="#header.expires" class="smpl">Expires</a> header field (see <a href="#header.expires" id="rfc.xref.header.expires.1" title="Expires">Section&nbsp;3.3</a>), or
858               </li>
859               <li>contains a max-age response cache directive (see <a href="#cache-response-directive" title="Response Cache-Control Directives">Section&nbsp;3.2.2</a>), or
860               </li>
861               <li>contains a s-maxage response cache directive and the cache is shared, or</li>
862               <li>contains a Cache Control Extension (see <a href="#cache.control.extensions" title="Cache Control Extensions">Section&nbsp;3.2.3</a>) that allows it to be cached, or
863               </li>
864               <li>has a status code that can be served with heuristic freshness (see <a href="#heuristic.freshness" title="Calculating Heuristic Freshness">Section&nbsp;</a>).
865               </li>
866            </ul>
867         </li>
868      </ul>
869      <p id="rfc.section.2.1.p.2">Note that any of the requirements listed above can be overridden by a cache-control extension; see <a href="#cache.control.extensions" title="Cache Control Extensions">Section&nbsp;3.2.3</a>.
870      </p>
871      <p id="rfc.section.2.1.p.3">In this context, a cache has "understood" a request method or a response status code if it recognizes it and implements any
872         cache-specific behavior.
873      </p>
874      <p id="rfc.section.2.1.p.4">Note that, in normal operation, most caches will not store a response that has neither a cache validator nor an explicit expiration
875         time, as such responses are not usually useful to store. However, caches are not prohibited from storing such responses.
876      </p>
877      <p id="rfc.section.2.1.p.5">A response message is considered complete when all of the octets indicated by the message framing (<a href="#Part1" id="rfc.xref.Part1.11"><cite title="HTTP/1.1, part 1: URIs, Connections, and Message Parsing">[Part1]</cite></a>) are received prior to the connection being closed. If the request is GET, the response status is <a href="p2-semantics.html#status.200" class="smpl">200 (OK)</a>, and the entire response header block has been received, a cache <em class="bcp14">MAY</em> store an incomplete response message body if the cache entry is recorded as incomplete. Likewise, a <a href="p5-range.html#status.206" class="smpl">206 (Partial Content)</a> response <em class="bcp14">MAY</em> be stored as if it were an incomplete <a href="p2-semantics.html#status.200" class="smpl">200 (OK)</a> cache entry. However, a cache <em class="bcp14">MUST NOT</em> store incomplete or partial content responses if it does not support the <a href="p5-range.html#range.retrieval.requests" class="smpl">Range</a> and <a href="p5-range.html#header.content-range" class="smpl">Content-Range</a> header fields or if it does not understand the range units used in those fields.
878      </p>
879      <p id="rfc.section.2.1.p.6">A cache <em class="bcp14">MAY</em> complete a stored incomplete response by making a subsequent range request (<a href="#Part5" id="rfc.xref.Part5.1"><cite title="HTTP/1.1, part 5: Range Requests and Partial Responses">[Part5]</cite></a>) and combining the successful response with the stored entry, as defined in <a href="#combining.responses" title="Combining Partial Content">Section&nbsp;2.9</a>. A cache <em class="bcp14">MUST NOT</em> use an incomplete response to answer requests unless the response has been made complete or the request is partial and specifies
880         a range that is wholly within the incomplete response. A cache <em class="bcp14">MUST NOT</em> send a partial response to a client without explicitly marking it as such using the <a href="p5-range.html#status.206" class="smpl">206 (Partial Content)</a> status code.
881      </p>
882      <h2 id="rfc.section.2.2"><a href="#rfc.section.2.2">2.2</a>&nbsp;<a id="constructing.responses.from.caches" href="#constructing.responses.from.caches">Constructing Responses from Caches</a></h2>
883      <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:
884      </p>
885      <ul>
886         <li>The presented effective request URI (<a href="p1-messaging.html#effective.request.uri" title="Effective Request URI">Section 5.5</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>) and that of the stored response match, and
887         </li>
888         <li>the request method associated with the stored response allows it to be used for the presented request, and</li>
889         <li>selecting header fields nominated by the stored response (if any) match those presented (see <a href="#caching.negotiated.responses" title="Caching Negotiated Responses">Section&nbsp;2.8</a>), and
890         </li>
891         <li>the presented request does not contain the no-cache pragma (<a href="#header.pragma" id="rfc.xref.header.pragma.1" title="Pragma">Section&nbsp;3.4</a>), nor the no-cache cache directive (<a href="#cache-request-directive" title="Request Cache-Control Directives">Section&nbsp;3.2.1</a>), unless the stored response is successfully validated (<a href="#validation.model" title="Validation Model">Section&nbsp;2.4</a>), and
892         </li>
893         <li>the stored response does not contain the no-cache cache directive (<a href="#cache-response-directive" title="Response Cache-Control Directives">Section&nbsp;3.2.2</a>), unless it is successfully validated (<a href="#validation.model" title="Validation Model">Section&nbsp;2.4</a>), and
894         </li>
895         <li>the stored response is either:
896            <ul>
897               <li>fresh (see <a href="#expiration.model" title="Freshness Model">Section&nbsp;2.3</a>), or
898               </li>
899               <li>allowed to be served stale (see <a href="#serving.stale.responses" title="Serving Stale Responses">Section&nbsp;2.3.3</a>), or
900               </li>
901               <li>successfully validated (see <a href="#validation.model" title="Validation Model">Section&nbsp;2.4</a>).
902               </li>
903            </ul>
904         </li>
905      </ul>
906      <p id="rfc.section.2.2.p.2">Note that any of the requirements listed above can be overridden by a cache-control extension; see <a href="#cache.control.extensions" title="Cache Control Extensions">Section&nbsp;3.2.3</a>.
907      </p>
908      <p id="rfc.section.2.2.p.3">When a stored response is used to satisfy a request without validation, a cache <em class="bcp14">MUST</em> include a single <a href="#header.age" class="smpl">Age</a> 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>.
909      </p>
910      <p id="rfc.section.2.2.p.4">A cache <em class="bcp14">MUST</em> write through requests with methods that are unsafe (<a href="p2-semantics.html#safe.methods" title="Safe Methods">Section 2.1.1</a> of <a href="#Part2" id="rfc.xref.Part2.3"><cite title="HTTP/1.1, part 2: Message Semantics, Payload and Content Negotiation">[Part2]</cite></a>) to the origin server; i.e., a cache is not allowed to generate a reply to such a request before having forwarded the request
911         and having received a corresponding response.
912      </p>
913      <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.6</a>.
914      </p>
915      <p id="rfc.section.2.2.p.6">When more than one suitable response is stored, a cache <em class="bcp14">MUST</em> use the most recent response (as determined by the Date header field). It can also forward a request with "Cache-Control:
916         max-age=0" or "Cache-Control: no-cache" to disambiguate which response to use.
917      </p>
918      <p id="rfc.section.2.2.p.7">A cache that does not have a clock available <em class="bcp14">MUST NOT</em> use stored responses without revalidating them on every use. A cache, especially a shared cache, <em class="bcp14">SHOULD</em> use a mechanism, such as NTP <a href="#RFC1305" id="rfc.xref.RFC1305.1"><cite title="Network Time Protocol (Version 3) Specification, Implementation">[RFC1305]</cite></a>, to synchronize its clock with a reliable external standard.
919      </p>
920      <h2 id="rfc.section.2.3"><a href="#rfc.section.2.3">2.3</a>&nbsp;<a id="expiration.model" href="#expiration.model">Freshness Model</a></h2>
921      <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,
922         thereby improving efficiency.
923      </p>
924      <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,
925         using either the <a href="#header.expires" class="smpl">Expires</a> header field (<a href="#header.expires" id="rfc.xref.header.expires.2" title="Expires">Section&nbsp;3.3</a>) or the max-age response cache directive (<a href="#cache-response-directive" title="Response Cache-Control Directives">Section&nbsp;3.2.2</a>). Generally, origin servers will assign future explicit expiration times to responses in the belief that the representation
926         is not likely to change in a semantically significant way before the expiration time is reached.
927      </p>
928      <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
929         to indicate that the response is already stale. Compliant caches will normally validate the cached response before reusing
930         it for subsequent requests (see <a href="#serving.stale.responses" title="Serving Stale Responses">Section&nbsp;2.3.3</a>).
931      </p>
932      <p id="rfc.section.2.3.p.4">Since origin servers do not always provide explicit expiration times, a cache <em class="bcp14">MAY</em> assign a heuristic expiration time when an explicit time is not specified, employing algorithms that use other header field
933         values (such as the <a href="p4-conditional.html#header.last-modified" class="smpl">Last-Modified</a> time) to estimate a plausible expiration time. This specification does not provide specific algorithms, but does impose worst-case
934         constraints on their results.
935      </p>
936      <div id="rfc.figure.u.4"></div>
937      <p>The calculation to determine if a response is fresh is:</p>  <pre class="text">   response_is_fresh = (freshness_lifetime &gt; current_age)
938</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>.
939      </p>
940      <p id="rfc.section.2.3.p.7">Additionally, clients can influence freshness calculation — either constraining it relaxing it — by using the max-age and
941         min-fresh request cache directives. See <a href="#cache-request-directive" title="Request Cache-Control Directives">Section&nbsp;3.2.1</a> for details.
942      </p>
943      <p id="rfc.section.2.3.p.8">Note that freshness applies only to cache operation; it cannot be used to force a user agent to refresh its display or reload
944         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.
945      </p>
946      <h3 id="rfc.section.2.3.1"><a href="#rfc.section.2.3.1">2.3.1</a>&nbsp;<a id="calculating.freshness.lifetime" href="#calculating.freshness.lifetime">Calculating Freshness Lifetime</a></h3>
947      <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>
948      <ul>
949         <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
950         </li>
951         <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
952         </li>
953         <li>If the <a href="#header.expires" class="smpl">Expires</a> response header field (<a href="#header.expires" id="rfc.xref.header.expires.3" title="Expires">Section&nbsp;3.3</a>) is present, use its value minus the value of the Date response header field, or
954         </li>
955         <li>Otherwise, no explicit expiration time is present in the response. A heuristic freshness lifetime might be applicable; see <a href="#heuristic.freshness" title="Calculating Heuristic Freshness">Section&nbsp;</a>.
956         </li>
957      </ul>
958      <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>
959      <p id="rfc.section.2.3.1.p.3">When there is more than one value present for a given directive (e.g., two <a href="#header.expires" class="smpl">Expires</a> header fields, multiple Cache-Control: max-age directives), it is considered invalid. Caches are encouraged to consider responses
960         that have invalid freshness information to be stale.
961      </p>
962      <h4 id="rfc.section."><a href="#rfc.section."></a>&nbsp;<a id="heuristic.freshness" href="#heuristic.freshness">Calculating Heuristic Freshness</a></h4>
963      <p id="rfc.section.">If no explicit expiration time is present in a stored response that has a status code whose definition allows heuristic freshness
964         to be used (including the following in <a href="" title="Status Codes">Section 4</a> of <a href="#Part2" id="rfc.xref.Part2.4"><cite title="HTTP/1.1, part 2: Message Semantics, Payload and Content Negotiation">[Part2]</cite></a>: <a href="p2-semantics.html#status.200" class="smpl">200 (OK)</a>, <a href="p2-semantics.html#status.203" class="smpl">203
965            (Non-Authoritative Information)</a>, <a href="p5-range.html#status.206" class="smpl">206 (Partial Content)</a>, <a href="p2-semantics.html#status.300" class="smpl">300 (Multiple Choices)</a>, <a href="p2-semantics.html#status.301" class="smpl">301 (Moved Permanently)</a> and <a href="p2-semantics.html#status.410" class="smpl">410 (Gone)</a>), a cache <em class="bcp14">MAY</em> calculate a heuristic expiration time. A cache <em class="bcp14">MUST NOT</em> use heuristics to determine freshness for responses with status codes that do not explicitly allow it.
966      </p>
967      <p id="rfc.section.">When a heuristic is used to calculate freshness lifetime, a cache <em class="bcp14">SHOULD</em> attach a <a href="#header.warning" class="smpl">Warning</a> header field with a 113 warn-code to the response if its current_age is more than 24 hours and such a warning is not already
968         present.
969      </p>
970      <p id="rfc.section.">Also, if the response has a <a href="p4-conditional.html#header.last-modified" class="smpl">Last-Modified</a> header field (<a href="p4-conditional.html#header.last-modified" title="Last-Modified">Section 2.2</a> of <a href="#Part4" id="rfc.xref.Part4.4"><cite title="HTTP/1.1, part 4: Conditional Requests">[Part4]</cite></a>), caches are encouraged to use a heuristic expiration value that is no more than some fraction of the interval since that
971         time. A typical setting of this fraction might be 10%.
972      </p>
973      <div class="note" id="rfc.section.">
974         <p> <b>Note:</b> RFC 2616 (<a href="#RFC2616" id="rfc.xref.RFC2616.1"><cite title="Hypertext Transfer Protocol -- HTTP/1.1">[RFC2616]</cite></a>, <a href="">Section 13.9</a>) required that caches do not calculate heuristic freshness for URIs with query components (i.e., those containing '?'). In
975            practice, this has not been widely implemented. Therefore, servers are encouraged to send explicit directives (e.g., Cache-Control:
976            no-cache) if they wish to preclude caching.
977         </p>
978      </div>
979      <h3 id="rfc.section.2.3.2"><a href="#rfc.section.2.3.2">2.3.2</a>&nbsp;<a id="age.calculations" href="#age.calculations">Calculating Age</a></h3>
980      <p id="rfc.section.2.3.2.p.1">HTTP/1.1 uses the <a href="#header.age" class="smpl">Age</a> header field to convey the estimated age of the response message when obtained from a cache. The Age field value is the cache's
981         estimate of the amount of time since the response was generated or validated by the origin server. In essence, the Age value
982         is the sum of the time that the response has been resident in each of the caches along the path from the origin server, plus
983         the amount of time it has been in transit along network paths.
984      </p>
985      <p id="rfc.section.2.3.2.p.2">The following data is used for the age calculation:</p>
986      <p id="rfc.section.2.3.2.p.3"> <dfn>age_value</dfn> 
987      </p>
988      <ul class="empty">
989         <li>The term "age_value" denotes the value of the <a href="#header.age" class="smpl">Age</a> header field (<a href="#header.age" id="rfc.xref.header.age.2" title="Age">Section&nbsp;3.1</a>), in a form appropriate for arithmetic operation; or 0, if not available.
990         </li>
991      </ul>
992      <p id="rfc.section.2.3.2.p.4"> <dfn>date_value</dfn> 
993      </p>
994      <ul class="empty">
995         <li>HTTP/1.1 requires origin servers to send a Date header field, if possible, with every response, giving the time at which the
996            response was generated. The term "date_value" denotes the value of the Date header field, in a form appropriate for arithmetic
997            operations. See <a href="" title="Date">Section 9.10</a> of <a href="#Part2" id="rfc.xref.Part2.5"><cite title="HTTP/1.1, part 2: Message Semantics, Payload and Content Negotiation">[Part2]</cite></a> for the definition of the Date header field, and for requirements regarding responses without it.
998         </li>
999      </ul>
1000      <p id="rfc.section.2.3.2.p.5"> <dfn>now</dfn> 
1001      </p>
1002      <ul class="empty">
1003         <li>The term "now" means "the current value of the clock at the host performing the calculation". A cache <em class="bcp14">SHOULD</em> use NTP (<a href="#RFC1305" id="rfc.xref.RFC1305.2"><cite title="Network Time Protocol (Version 3) Specification, Implementation">[RFC1305]</cite></a>) or some similar protocol to synchronize its clocks to a globally accurate time standard.
1004         </li>
1005      </ul>
1006      <p id="rfc.section.2.3.2.p.6"> <dfn>request_time</dfn> 
1007      </p>
1008      <ul class="empty">
1009         <li>The current value of the clock at the host at the time the request resulting in the stored response was made.</li>
1010      </ul>
1011      <p id="rfc.section.2.3.2.p.7"> <dfn>response_time</dfn> 
1012      </p>
1013      <ul class="empty">
1014         <li>The current value of the clock at the host at the time the response was received.</li>
1015      </ul>
1016      <p id="rfc.section.2.3.2.p.8">A response's age can be calculated in two entirely independent ways: </p>
1017      <ol>
1018         <li>the "apparent_age": response_time minus date_value, if the local clock is reasonably well synchronized to the origin server's
1019            clock. If the result is negative, the result is replaced by zero.
1020         </li>
1021         <li>the "corrected_age_value", if all of the caches along the response path implement HTTP/1.1. A cache <em class="bcp14">MUST</em> interpret this value relative to the time the request was initiated, not the time that the response was received.
1022         </li>
1023      </ol>
1024      <div id="rfc.figure.u.5"></div> <pre class="text">  apparent_age = max(0, response_time - date_value);
1026  response_delay = response_time - request_time;
1027  corrected_age_value = age_value + response_delay; 
1028</pre> <div id="rfc.figure.u.6"></div>
1029      <p>These <em class="bcp14">SHOULD</em> be combined as
1030      </p>  <pre class="text">  corrected_initial_age = max(apparent_age, corrected_age_value);
1031</pre><p id="rfc.section.2.3.2.p.11">unless the cache is confident in the value of the <a href="#header.age" class="smpl">Age</a> header field (e.g., because there are no HTTP/1.0 hops in the Via header field), in which case the corrected_age_value <em class="bcp14">MAY</em> be used as the corrected_initial_age.
1032      </p>
1033      <p id="rfc.section.2.3.2.p.12">The current_age of a stored response can then be calculated by adding the amount of time (in seconds) since the stored response
1034         was last validated by the origin server to the corrected_initial_age.
1035      </p>
1036      <div id="rfc.figure.u.7"></div><pre class="text">  resident_time = now - response_time;
1037  current_age = corrected_initial_age + resident_time;
1038</pre><p id="rfc.section.2.3.2.p.14">Additionally, to avoid common problems in date parsing:</p>
1039      <p id="rfc.section.2.3.2.p.15"> </p>
1040      <ul>
1041         <li>HTTP/1.1 clients and caches <em class="bcp14">SHOULD</em> assume that an RFC-850 date which appears to be more than 50 years in the future is in fact in the past (this helps solve
1042            the "year 2000" problem).
1043         </li>
1044         <li>Although all date formats are specified to be case-sensitive, recipients <em class="bcp14">SHOULD</em> match day, week and timezone names case-insensitively.
1045         </li>
1046         <li>An HTTP/1.1 implementation <em class="bcp14">MAY</em> internally represent a parsed <a href="#header.expires" class="smpl">Expires</a> date as earlier than the proper value, but <em class="bcp14">MUST NOT</em> internally represent a parsed Expires date as later than the proper value.
1047         </li>
1048         <li>All expiration-related calculations <em class="bcp14">MUST</em> be done in GMT. The local time zone <em class="bcp14">MUST NOT</em> influence the calculation or comparison of an age or expiration time.
1049         </li>
1050         <li>If an HTTP header field incorrectly carries a date value with a time zone other than GMT, it <em class="bcp14">MUST</em> be converted into GMT using the most conservative possible conversion.
1051         </li>
1052      </ul>
1053      <h3 id="rfc.section.2.3.3"><a href="#rfc.section.2.3.3">2.3.3</a>&nbsp;<a id="serving.stale.responses" href="#serving.stale.responses">Serving Stale Responses</a></h3>
1054      <p id="rfc.section.2.3.3.p.1">A "stale" response is one that either has explicit expiry information or is allowed to have heuristic expiry calculated, but
1055         is not fresh according to the calculations in <a href="#expiration.model" title="Freshness Model">Section&nbsp;2.3</a>.
1056      </p>
1057      <p id="rfc.section.2.3.3.p.2">A cache <em class="bcp14">MUST NOT</em> return a stale response if it is prohibited by an explicit in-protocol directive (e.g., by a "no-store" or "no-cache" cache
1058         directive, a "must-revalidate" cache-response-directive, or an applicable "s-maxage" or "proxy-revalidate" cache-response-directive;
1059         see <a href="#cache-response-directive" title="Response Cache-Control Directives">Section&nbsp;3.2.2</a>).
1060      </p>
1061      <p id="rfc.section.2.3.3.p.3">A cache <em class="bcp14">MUST NOT</em> return stale responses unless it is disconnected (i.e., it cannot contact the origin server or otherwise find a forward path)
1062         or doing so is explicitly allowed (e.g., by the max-stale request directive; see <a href="#cache-request-directive" title="Request Cache-Control Directives">Section&nbsp;3.2.1</a>).
1063      </p>
1064      <p id="rfc.section.2.3.3.p.4">A cache <em class="bcp14">SHOULD</em> append a <a href="#header.warning" class="smpl">Warning</a> header field with the 110 warn-code (see <a href="#header.warning" id="rfc.xref.header.warning.1" title="Warning">Section&nbsp;3.6</a>) to stale responses. Likewise, a cache <em class="bcp14">SHOULD</em> add the 112 warn-code to stale responses if the cache is disconnected.
1065      </p>
1066      <p id="rfc.section.2.3.3.p.5">If a cache receives a first-hand response (either an entire response, or a <a href="p4-conditional.html#status.304" class="smpl">304 (Not Modified)</a> response) that it would normally forward to the requesting client, and the received response is no longer fresh, the cache
1067         can forward it to the requesting client without adding a new <a href="#header.warning" class="smpl">Warning</a> (but without removing any existing Warning header fields). A cache shouldn't attempt to validate a response simply because
1068         that response became stale in transit.
1069      </p>
1070      <h2 id="rfc.section.2.4"><a href="#rfc.section.2.4">2.4</a>&nbsp;<a id="validation.model" href="#validation.model">Validation Model</a></h2>
1071      <p id="rfc.section.2.4.p.1">When a cache has one or more stored responses for a requested URI, but cannot serve any of them (e.g., because they are not
1072         fresh, or one cannot be selected; see <a href="#caching.negotiated.responses" title="Caching Negotiated Responses">Section&nbsp;2.8</a>), it can use the conditional request mechanism <a href="#Part4" id="rfc.xref.Part4.5"><cite title="HTTP/1.1, part 4: Conditional Requests">[Part4]</cite></a> in the forwarded request to give the origin server an opportunity to both select a valid stored response to be used, and to
1073         update it. This process is known as "validating" or "revalidating" the stored response.
1074      </p>
1075      <p id="rfc.section.2.4.p.2">When sending such a conditional request, a cache adds an <a href="p4-conditional.html#header.if-modified-since" class="smpl">If-Modified-Since</a> header field whose value is that of the <a href="p4-conditional.html#header.last-modified" class="smpl">Last-Modified</a> header field from the selected (see <a href="#caching.negotiated.responses" title="Caching Negotiated Responses">Section&nbsp;2.8</a>) stored response, if available.
1076      </p>
1077      <p id="rfc.section.2.4.p.3">Additionally, a cache can add an <a href="p4-conditional.html#header.if-none-match" class="smpl">If-None-Match</a> header field whose value is that of the <a href="p4-conditional.html#header.etag" class="smpl">ETag</a> header field(s) from all responses stored for the requested URI, if present. However, if any of the stored responses contains
1078         only partial content, the cache shouldn't include its entity-tag in the If-None-Match header field unless the request is for
1079         a range that would be fully satisfied by that stored response.
1080      </p>
1081      <p id="rfc.section.2.4.p.4">Cache handling of a response to a conditional request is dependent upon its status code:</p>
1082      <p id="rfc.section.2.4.p.5"> </p>
1083      <ul>
1084         <li>A <a href="p4-conditional.html#status.304" class="smpl">304 (Not Modified)</a> response status code indicates that the stored response can be updated and reused; see <a href="#freshening.responses" title="Freshening Responses with 304 Not Modified">Section&nbsp;2.4.1</a>.
1085         </li>
1086         <li>A full response (i.e., one with a response body) indicates that none of the stored responses nominated in the conditional
1087            request is suitable. Instead, the cache can use the full response to satisfy the request and <em class="bcp14">MAY</em> replace the stored response(s).
1088         </li>
1089         <li>However, if a cache receives a <a href="p2-semantics.html#status.5xx" class="smpl">5xx (Server Error)</a> response while attempting to validate a response, it can either forward this response to the requesting client, or act as
1090            if the server failed to respond. In the latter case, it can return a previously stored response (see <a href="#serving.stale.responses" title="Serving Stale Responses">Section&nbsp;2.3.3</a>).
1091         </li>
1092      </ul>
1093      <h3 id="rfc.section.2.4.1"><a href="#rfc.section.2.4.1">2.4.1</a>&nbsp;<a id="freshening.responses" href="#freshening.responses">Freshening Responses with 304 Not Modified</a></h3>
1094      <p id="rfc.section.2.4.1.p.1">When a cache receives a <a href="p4-conditional.html#status.304" class="smpl">304 (Not Modified)</a> response and already has one or more stored <a href="p2-semantics.html#status.200" class="smpl">200 (OK)</a> responses for the same cache key, the cache needs to identify which of the stored responses are updated by this new response
1095         and then update the stored response(s) with the new information provided in the <a href="p4-conditional.html#status.304" class="smpl">304</a> response.
1096      </p>
1097      <ul>
1098         <li>If the new response contains a strong validator, then that strong validator identifies the selected representation. All of
1099            the stored responses with the same strong validator are selected. If none of the stored responses contain the same strong
1100            validator, then this new response corresponds to a new selected representation and <em class="bcp14">MUST NOT</em> update the existing stored responses.
1101         </li>
1102         <li>If the new response contains a weak validator and that validator corresponds to one of the cache's stored responses, then
1103            the most recent of those matching stored responses is selected.
1104         </li>
1105         <li>If the new response does not include any form of validator, there is only one stored response, and that stored response also
1106            lacks a validator, then that stored response is selected.
1107         </li>
1108      </ul>
1109      <p id="rfc.section.2.4.1.p.2">If a stored response is selected for update, the cache <em class="bcp14">MUST</em>:
1110      </p>
1111      <ul>
1112         <li>delete any <a href="#header.warning" class="smpl">Warning</a> header fields in the stored response with warn-code 1xx (see <a href="#header.warning" id="rfc.xref.header.warning.2" title="Warning">Section&nbsp;3.6</a>);
1113         </li>
1114         <li>retain any <a href="#header.warning" class="smpl">Warning</a> header fields in the stored response with warn-code 2xx; and,
1115         </li>
1116         <li>use other header fields provided in the <a href="p4-conditional.html#status.304" class="smpl">304 (Not Modified)</a> response to replace all instances of the corresponding header fields in the stored response.
1117         </li>
1118      </ul>
1119      <h2 id="rfc.section.2.5"><a href="#rfc.section.2.5">2.5</a>&nbsp;<a id="head.effects" href="#head.effects">Updating Caches with HEAD Responses</a></h2>
1120      <p id="rfc.section.2.5.p.1">A response to the HEAD method is identical to what an equivalent request made with a GET would have been, except it lacks
1121         a body. This property of HEAD responses is used to both invalidate and update cached GET responses.
1122      </p>
1123      <p id="rfc.section.2.5.p.2">If one or more stored GET responses can be selected (as per <a href="#caching.negotiated.responses" title="Caching Negotiated Responses">Section&nbsp;2.8</a>) for a HEAD request, and the Content-Length, <a href="p4-conditional.html#header.etag" class="smpl">ETag</a> or <a href="p4-conditional.html#header.last-modified" class="smpl">Last-Modified</a> value of a HEAD response differs from that in a selected GET response, the cache <em class="bcp14">MUST</em> consider that selected response to be stale.
1124      </p>
1125      <p id="rfc.section.2.5.p.3">If the Content-Length, <a href="p4-conditional.html#header.etag" class="smpl">ETag</a> and <a href="p4-conditional.html#header.last-modified" class="smpl">Last-Modified</a> values of a HEAD response (when present) are the same as that in a selected GET response (as per <a href="#caching.negotiated.responses" title="Caching Negotiated Responses">Section&nbsp;2.8</a>), the cache <em class="bcp14">SHOULD</em> update the remaining headers in the stored response using the following rules:
1126      </p>
1127      <ul>
1128         <li>delete any <a href="#header.warning" class="smpl">Warning</a> header fields in the stored response with warn-code 1xx (see <a href="#header.warning" id="rfc.xref.header.warning.3" title="Warning">Section&nbsp;3.6</a>);
1129         </li>
1130         <li>retain any <a href="#header.warning" class="smpl">Warning</a> header fields in the stored response with warn-code 2xx; and,
1131         </li>
1132         <li>use other header fields provided in the response to replace all instances of the corresponding header fields in the stored
1133            response.
1134         </li>
1135      </ul>
1136      <h2 id="rfc.section.2.6"><a href="#rfc.section.2.6">2.6</a>&nbsp;<a id="invalidation.after.updates.or.deletions" href="#invalidation.after.updates.or.deletions">Request Methods that Invalidate</a></h2>
1137      <p id="rfc.section.2.6.p.1">Because unsafe request methods (<a href="p2-semantics.html#safe.methods" title="Safe Methods">Section 2.1.1</a> of <a href="#Part2" id="rfc.xref.Part2.6"><cite title="HTTP/1.1, part 2: Message Semantics, Payload and Content Negotiation">[Part2]</cite></a>) such as PUT, POST or DELETE have the potential for changing state on the origin server, intervening caches can use them
1138         to keep their contents up-to-date.
1139      </p>
1140      <p id="rfc.section.2.6.p.2">A cache <em class="bcp14">MUST</em> invalidate the effective Request URI (<a href="p1-messaging.html#effective.request.uri" title="Effective Request URI">Section 5.5</a> of <a href="#Part1" id="rfc.xref.Part1.13"><cite title="HTTP/1.1, part 1: URIs, Connections, and Message Parsing">[Part1]</cite></a>) as well as the URI(s) in the Location and Content-Location response header fields (if present) when a non-error response
1141         to a request with an unsafe method is received.
1142      </p>
1143      <p id="rfc.section.2.6.p.3">However, a cache <em class="bcp14">MUST NOT</em> invalidate a URI from a Location or Content-Location response header field if the host part of that URI differs from the host
1144         part in the effective request URI (<a href="p1-messaging.html#effective.request.uri" title="Effective Request URI">Section 5.5</a> of <a href="#Part1" id="rfc.xref.Part1.14"><cite title="HTTP/1.1, part 1: URIs, Connections, and Message Parsing">[Part1]</cite></a>). This helps prevent denial of service attacks.
1145      </p>
1146      <p id="rfc.section.2.6.p.4">A cache <em class="bcp14">MUST</em> invalidate the effective request URI (<a href="p1-messaging.html#effective.request.uri" title="Effective Request URI">Section 5.5</a> of <a href="#Part1" id="rfc.xref.Part1.15"><cite title="HTTP/1.1, part 1: URIs, Connections, and Message Parsing">[Part1]</cite></a>) when it receives a non-error response to a request with a method whose safety is unknown.
1147      </p>
1148      <p id="rfc.section.2.6.p.5">Here, a "non-error response" is one with a <a href="p2-semantics.html#status.2xx" class="smpl">2xx (Successful)</a> or <a href="p2-semantics.html#status.3xx" class="smpl">3xx (Redirection)</a> status code. "Invalidate" means that the cache will either remove all stored responses related to the effective request URI,
1149         or will mark these as "invalid" and in need of a mandatory validation before they can be returned in response to a subsequent
1150         request.
1151      </p>
1152      <p id="rfc.section.2.6.p.6">Note that this does not guarantee that all appropriate responses are invalidated. For example, the request that caused the
1153         change at the origin server might not have gone through the cache where a response is stored.
1154      </p>
1155      <h2 id="rfc.section.2.7"><a href="#rfc.section.2.7">2.7</a>&nbsp;<a id="caching.authenticated.responses" href="#caching.authenticated.responses">Shared Caching of Authenticated Responses</a></h2>
1156      <p id="rfc.section.2.7.p.1">A shared cache <em class="bcp14">MUST NOT</em> use a cached response to a request with an <a href="p7-auth.html#header.authorization" class="smpl">Authorization</a> header field (<a href="p7-auth.html#header.authorization" title="Authorization">Section 4.1</a> of <a href="#Part7" id="rfc.xref.Part7.2"><cite title="HTTP/1.1, part 7: Authentication">[Part7]</cite></a>) to satisfy any subsequent request unless a cache directive that allows such responses to be stored is present in the response.
1157      </p>
1158      <p id="rfc.section.2.7.p.2">In this specification, the following <a href="#header.cache-control" class="smpl">Cache-Control</a> response directives (<a href="#cache-response-directive" title="Response Cache-Control Directives">Section&nbsp;3.2.2</a>) have such an effect: must-revalidate, public, s-maxage.
1159      </p>
1160      <p id="rfc.section.2.7.p.3">Note that cached responses that contain the "must-revalidate" and/or "s-maxage" response directives are not allowed to be
1161         served stale (<a href="#serving.stale.responses" title="Serving Stale Responses">Section&nbsp;2.3.3</a>) by shared caches. In particular, a response with either "max-age=0, must-revalidate" or "s-maxage=0" cannot be used to satisfy
1162         a subsequent request without revalidating it on the origin server.
1163      </p>
1164      <h2 id="rfc.section.2.8"><a href="#rfc.section.2.8">2.8</a>&nbsp;<a id="caching.negotiated.responses" href="#caching.negotiated.responses">Caching Negotiated Responses</a></h2>
1165      <p id="rfc.section.2.8.p.1">When a cache receives a request that can be satisfied by a stored response that has a <a href="#header.vary" class="smpl">Vary</a> 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 header fields nominated by the Vary header field match in both the original
1166         request (i.e., that associated with the stored response), and the presented request.
1167      </p>
1168      <p id="rfc.section.2.8.p.2">The selecting header fields from two requests are defined to match if and only if those in the first request can be transformed
1169         to those in the second request by applying any of the following:
1170      </p>
1171      <ul>
1172         <li>adding or removing whitespace, where allowed in the header field's syntax</li>
1173         <li>combining multiple header fields with the same field name (see <a href="p1-messaging.html#header.fields" title="Header Fields">Section 3.2</a> of <a href="#Part1" id="rfc.xref.Part1.16"><cite title="HTTP/1.1, part 1: URIs, Connections, and Message Parsing">[Part1]</cite></a>)
1174         </li>
1175         <li>normalizing both header field values in a way that is known to have identical semantics, according to the header field's specification
1176            (e.g., re-ordering field values when order is not significant; case-normalization, where values are defined to be case-insensitive)
1177         </li>
1178      </ul>
1179      <p id="rfc.section.2.8.p.3">If (after any normalization that might take place) a header field is absent from a request, it can only match another request
1180         if it is also absent there.
1181      </p>
1182      <p id="rfc.section.2.8.p.4">A <a href="#header.vary" class="smpl">Vary</a> header field-value of "*" always fails to match, and subsequent requests to that resource can only be properly interpreted
1183         by the origin server.
1184      </p>
1185      <p id="rfc.section.2.8.p.5">The stored response with matching selecting header fields is known as the selected response.</p>
1186      <p id="rfc.section.2.8.p.6">If multiple selected responses are available, the most recent response (as determined by the Date header field) is used; see <a href="#constructing.responses.from.caches" title="Constructing Responses from Caches">Section&nbsp;2.2</a>.
1187      </p>
1188      <p id="rfc.section.2.8.p.7">If no selected response is available, the cache can forward the presented request to the origin server in a conditional request;
1189         see <a href="#validation.model" title="Validation Model">Section&nbsp;2.4</a>.
1190      </p>
1191      <h2 id="rfc.section.2.9"><a href="#rfc.section.2.9">2.9</a>&nbsp;<a id="combining.responses" href="#combining.responses">Combining Partial Content</a></h2>
1192      <p id="rfc.section.2.9.p.1">A response might transfer only a partial representation if the connection closed prematurely or if the request used one or
1193         more Range specifiers (<a href="#Part5" id="rfc.xref.Part5.2"><cite title="HTTP/1.1, part 5: Range Requests and Partial Responses">[Part5]</cite></a>). After several such transfers, a cache might have received several ranges of the same representation. A cache <em class="bcp14">MAY</em> combine these ranges into a single stored response, and reuse that response to satisfy later requests, if they all share the
1194         same strong validator and the cache complies with the client requirements in <a href="p5-range.html#combining.byte.ranges" title="Combining Ranges">Section 4.2</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>.
1195      </p>
1196      <p id="rfc.section.2.9.p.2">When combining the new response with one or more stored responses, a cache <em class="bcp14">MUST</em>:
1197      </p>
1198      <ul>
1199         <li>delete any <a href="#header.warning" class="smpl">Warning</a> header fields in the stored response with warn-code 1xx (see <a href="#header.warning" id="rfc.xref.header.warning.4" title="Warning">Section&nbsp;3.6</a>);
1200         </li>
1201         <li>retain any <a href="#header.warning" class="smpl">Warning</a> header fields in the stored response with warn-code 2xx; and,
1202         </li>
1203         <li>use other header fields provided in the new response, aside from <a href="p5-range.html#header.content-range" class="smpl">Content-Range</a>, to replace all instances of the corresponding header fields in the stored response.
1204         </li>
1205      </ul>
1206      <h1 id="rfc.section.3"><a href="#rfc.section.3">3.</a>&nbsp;<a id="header.field.definitions" href="#header.field.definitions">Header Field Definitions</a></h1>
1207      <p id="rfc.section.3.p.1">This section defines the syntax and semantics of HTTP/1.1 header fields related to caching.</p>
1208      <div id="rfc.iref.a.2"></div>
1209      <div id="rfc.iref.h.2"></div>
1210      <h2 id="rfc.section.3.1"><a href="#rfc.section.3.1">3.1</a>&nbsp;<a id="header.age" href="#header.age">Age</a></h2>
1211      <p id="rfc.section.3.1.p.1">The "Age" header field conveys the sender's estimate of the amount of time since the response was generated or successfully
1212         validated at the origin server. Age values are calculated as specified in <a href="#age.calculations" title="Calculating Age">Section&nbsp;2.3.2</a>.
1213      </p>
1214      <div id="rfc.figure.u.8"></div><pre class="inline"><span id="rfc.iref.g.2"></span>  <a href="#header.age" class="smpl">Age</a> = <a href="#delta-seconds" class="smpl">delta-seconds</a>
1215</pre><p id="rfc.section.3.1.p.3">Age field-values are non-negative integers, representing time in seconds (see <a href="#delta-seconds" title="Delta Seconds">Section&nbsp;1.5</a>).
1216      </p>
1217      <p id="rfc.section.3.1.p.4">The presence of an Age header field in a response implies that a response is not first-hand. However, the converse is not
1218         true, since HTTP/1.0 caches might not implement the Age header field.
1219      </p>
1220      <div id="rfc.iref.c.6"></div>
1221      <div id="rfc.iref.h.3"></div>
1222      <h2 id="rfc.section.3.2"><a href="#rfc.section.3.2">3.2</a>&nbsp;<a id="header.cache-control" href="#header.cache-control">Cache-Control</a></h2>
1223      <p id="rfc.section.3.2.p.1">The "Cache-Control" header field is used to specify directives for caches along the request/response chain. Such cache directives
1224         are unidirectional in that the presence of a directive in a request does not imply that the same directive is to be given
1225         in the response.
1226      </p>
1227      <p id="rfc.section.3.2.p.2">A cache <em class="bcp14">MUST</em> obey the requirements of the Cache-Control directives defined in this section. See <a href="#cache.control.extensions" title="Cache Control Extensions">Section&nbsp;3.2.3</a> for information about how Cache-Control directives defined elsewhere are handled.
1228      </p>
1229      <div class="note" id="rfc.section.3.2.p.3">
1230         <p> <b>Note:</b> HTTP/1.0 caches might not implement Cache-Control and might only implement Pragma: no-cache (see <a href="#header.pragma" id="rfc.xref.header.pragma.2" title="Pragma">Section&nbsp;3.4</a>).
1231         </p>
1232      </div>
1233      <p id="rfc.section.3.2.p.4">A proxy, whether or not it implements a cache, <em class="bcp14">MUST</em> pass cache directives through in forwarded messages, regardless of their significance to that application, since the directives
1234         might be applicable to all recipients along the request/response chain. It is not possible to target a directive to a specific
1235         cache.
1236      </p>
1237      <p id="rfc.section.3.2.p.5">Cache directives are identified by a token, to be compared case-insensitively, and have an optional argument, that can use
1238         both token and quoted-string syntax. For the directives defined below that define arguments, recipients ought to accept both
1239         forms, even if one is documented to be preferred. For any directive not defined by this specification, recipients <em class="bcp14">MUST</em> accept both forms.
1240      </p>
1241      <div id="rfc.figure.u.9"></div><pre class="inline"><span id="rfc.iref.g.3"></span><span id="rfc.iref.g.4"></span>  <a href="#header.cache-control" class="smpl">Cache-Control</a>   = 1#<a href="#header.cache-control" class="smpl">cache-directive</a>
1243  <a href="#header.cache-control" class="smpl">cache-directive</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> ) ]
1244</pre><p id="rfc.section.3.2.p.7">For the cache directives defined below, no argument is defined (nor allowed) otherwise stated otherwise.</p>
1245      <h3 id="rfc.section.3.2.1"><a href="#rfc.section.3.2.1">3.2.1</a>&nbsp;<a id="cache-request-directive" href="#cache-request-directive">Request Cache-Control Directives</a></h3>
1246      <div id="rfc.iref.c.7"></div>
1247      <div id="rfc.iref.n.1"></div>
1248      <h4 id="rfc.section."><a href="#rfc.section."></a>&nbsp;<a id="" href="">no-cache</a></h4>
1249      <p id="rfc.section.">The no-cache request directive indicates that a cache <em class="bcp14">MUST NOT</em> use a stored response to satisfy the request without successful validation on the origin server.
1250      </p>
1251      <div id="rfc.iref.c.8"></div>
1252      <div id="rfc.iref.n.2"></div>
1253      <h4 id="rfc.section."><a href="#rfc.section."></a>&nbsp;<a id="" href="">no-store</a></h4>
1254      <p id="rfc.section.">The no-store request directive indicates that a cache <em class="bcp14">MUST NOT</em> store any part of either this request or any response to it. This directive applies to both private and shared caches. "<em class="bcp14">MUST NOT</em> store" in this context means that the cache <em class="bcp14">MUST NOT</em> intentionally store the information in non-volatile storage, and <em class="bcp14">MUST</em> make a best-effort attempt to remove the information from volatile storage as promptly as possible after forwarding it.
1255      </p>
1256      <p id="rfc.section.">This directive is NOT a reliable or sufficient mechanism for ensuring privacy. In particular, malicious or compromised caches
1257         might not recognize or obey this directive, and communications networks might be vulnerable to eavesdropping.
1258      </p>
1259      <p id="rfc.section.">Note that if a request containing this directive is satisfied from a cache, the no-store request directive does not apply
1260         to the already stored response.
1261      </p>
1262      <div id="rfc.iref.c.9"></div>
1263      <div id="rfc.iref.m.1"></div>
1264      <h4 id="rfc.section."><a href="#rfc.section."></a>&nbsp;<a id="cache-request-directive.max-age" href="#cache-request-directive.max-age">max-age</a></h4>
1265      <p id="rfc.section.">Argument syntax: </p>
1266      <ul class="empty">
1267         <li> <a href="#delta-seconds" class="smpl">delta-seconds</a> (see <a href="#delta-seconds" title="Delta Seconds">Section&nbsp;1.5</a>)
1268         </li>
1269      </ul>
1270      <p id="rfc.section.">The max-age request directive indicates that the client is unwilling to accept a response whose age is greater than the specified
1271         number of seconds. Unless the max-stale request directive is also present, the client is not willing to accept a stale response.
1272      </p>
1273      <p id="rfc.section."> <b>Note:</b> This directive uses the token form of the argument syntax; e.g., 'max-age=5', not 'max-age="5"'. Senders <em class="bcp14">SHOULD NOT</em> use the quoted-string form.
1274      </p>
1275      <div id="rfc.iref.c.10"></div>
1276      <div id="rfc.iref.m.2"></div>
1277      <h4 id="rfc.section."><a href="#rfc.section."></a>&nbsp;<a id="cache-request-directive.max-stale" href="#cache-request-directive.max-stale">max-stale</a></h4>
1278      <p id="rfc.section.">Argument syntax: </p>
1279      <ul class="empty">
1280         <li> <a href="#delta-seconds" class="smpl">delta-seconds</a> (see <a href="#delta-seconds" title="Delta Seconds">Section&nbsp;1.5</a>)
1281         </li>
1282      </ul>
1283      <p id="rfc.section.">The max-stale request directive indicates that the client is willing to accept a response that has exceeded its expiration
1284         time. If max-stale is assigned a value, then the client is willing to accept a response that has exceeded its expiration time
1285         by no more than the specified number of seconds. If no value is assigned to max-stale, then the client is willing to accept
1286         a stale response of any age.
1287      </p>
1288      <p id="rfc.section."> <b>Note:</b> This directive uses the token form of the argument syntax; e.g., 'max-stale=10', not 'max-stale="10"'. Senders <em class="bcp14">SHOULD NOT</em> use the quoted-string form.
1289      </p>
1290      <div id="rfc.iref.c.11"></div>
1291      <div id="rfc.iref.m.3"></div>
1292      <h4 id="rfc.section."><a href="#rfc.section."></a>&nbsp;<a id="cache-request-directive.min-fresh" href="#cache-request-directive.min-fresh">min-fresh</a></h4>
1293      <p id="rfc.section.">Argument syntax: </p>
1294      <ul class="empty">
1295         <li> <a href="#delta-seconds" class="smpl">delta-seconds</a> (see <a href="#delta-seconds" title="Delta Seconds">Section&nbsp;1.5</a>)
1296         </li>
1297      </ul>
1298      <p id="rfc.section.">The min-fresh request directive indicates that the client is willing to accept a response whose freshness lifetime is no less
1299         than its current age plus the specified time in seconds. That is, the client wants a response that will still be fresh for
1300         at least the specified number of seconds.
1301      </p>
1302      <p id="rfc.section."> <b>Note:</b> This directive uses the token form of the argument syntax; e.g., 'min-fresh=20', not 'min-fresh="20"'. Senders <em class="bcp14">SHOULD NOT</em> use the quoted-string form.
1303      </p>
1304      <div id="rfc.iref.c.12"></div>
1305      <div id="rfc.iref.n.3"></div>
1306      <h4 id="rfc.section."><a href="#rfc.section."></a>&nbsp;<a id="" href="">no-transform</a></h4>
1307      <p id="rfc.section.">The no-transform request directive indicates that an intermediary (whether or not it implements a cache) <em class="bcp14">MUST NOT</em> change the Content-Encoding, <a href="p5-range.html#header.content-range" class="smpl">Content-Range</a> or Content-Type request header fields, nor the request representation.
1308      </p>
1309      <div id="rfc.iref.c.13"></div>
1310      <div id="rfc.iref.o.1"></div>
1311      <h4 id="rfc.section."><a href="#rfc.section."></a>&nbsp;<a id="cache-request-directive.only-if-cached" href="#cache-request-directive.only-if-cached">only-if-cached</a></h4>
1312      <p id="rfc.section.">The only-if-cached request directive indicates that the client only wishes to obtain a stored response. If it receives 3ive,
1313         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 <a href="p2-semantics.html#status.504" class="smpl">504
1314            (Gateway Timeout)</a> status code. If a group of caches is being operated as a unified system with good internal connectivity, a member cache <em class="bcp14">MAY</em> forward such a request within that group of caches.
1315      </p>
1316      <h3 id="rfc.section.3.2.2"><a href="#rfc.section.3.2.2">3.2.2</a>&nbsp;<a id="cache-response-directive" href="#cache-response-directive">Response Cache-Control Directives</a></h3>
1317      <div id="rfc.iref.c.14"></div>
1318      <div id="rfc.iref.p.2"></div>
1319      <h4 id="rfc.section."><a href="#rfc.section."></a>&nbsp;<a id="cache-response-directive.only-if-cached" href="#cache-response-directive.only-if-cached">public</a></h4>
1320      <p id="rfc.section.">The public response directive indicates that a response whose associated request contains an 'Authentication' header <em class="bcp14">MAY</em> be stored (see <a href="#caching.authenticated.responses" title="Shared Caching of Authenticated Responses">Section&nbsp;2.7</a>).
1321      </p>
1322      <div id="rfc.iref.c.15"></div>
1323      <div id="rfc.iref.p.3"></div>
1324      <h4 id="rfc.section."><a href="#rfc.section."></a>&nbsp;<a id="cache-response-directive.private" href="#cache-response-directive.private">private</a></h4>
1325      <p id="rfc.section.">Argument syntax: </p>
1326      <ul class="empty">
1327         <li>#<a href="#abnf.dependencies" class="smpl">field-name</a>
1328         </li>
1329      </ul>
1330      <p id="rfc.section.">The private response directive indicates that the response message is intended for a single user and <em class="bcp14">MUST NOT</em> be stored by a shared cache. A private cache <em class="bcp14">MAY</em> store the response.
1331      </p>
1332      <p id="rfc.section.">If the private response directive specifies one or more field-names, this requirement is limited to the field-values associated
1333         with the listed response header fields. That is, a shared cache <em class="bcp14">MUST NOT</em> store the specified field-names(s), whereas it <em class="bcp14">MAY</em> store the remainder of the response message.
1334      </p>
1335      <p id="rfc.section.">The field-names given are not limited to the set of standard header fields defined by this specification. Field names are
1336         case-insensitive.
1337      </p>
1338      <p id="rfc.section."> <b>Note:</b> This usage of the word "private" only controls where the response can be stored; it cannot ensure the privacy of the message
1339         content. Also, private response directives with field-names are often handled by implementations as if an unqualified private
1340         directive was received; i.e., the special handling for the qualified form is not widely implemented.
1341      </p>
1342      <p id="rfc.section."> <b>Note:</b> This directive uses the quoted-string form of the argument syntax. Senders <em class="bcp14">SHOULD NOT</em> use the token form (even if quoting appears not to be needed for single-entry lists).
1343      </p>
1344      <div id="rfc.iref.c.16"></div>
1345      <div id="rfc.iref.n.4"></div>
1346      <h4 id="rfc.section."><a href="#rfc.section."></a>&nbsp;<a id="" href="">no-cache</a></h4>
1347      <p id="rfc.section.">Argument syntax: </p>
1348      <ul class="empty">
1349         <li>#<a href="#abnf.dependencies" class="smpl">field-name</a>
1350         </li>
1351      </ul>
1352      <p id="rfc.section.">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
1353         prevent a cache from using it to satisfy a request without contacting it, even by caches that have been configured to return
1354         stale responses.
1355      </p>
1356      <p id="rfc.section.">If the no-cache response directive specifies one or more field-names, then a cache <em class="bcp14">MAY</em> use the response to satisfy a subsequent request, subject to any other restrictions on caching. However, any header fields
1357         in the response that have the field-name(s) listed <em class="bcp14">MUST NOT</em> be sent in the response to a subsequent request without successful revalidation with the origin server. This allows an origin
1358         server to prevent the re-use of certain header fields in a response, while still allowing caching of the rest of the response.
1359      </p>
1360      <p id="rfc.section.">The field-names given are not limited to the set of standard header fields defined by this specification. Field names are
1361         case-insensitive.
1362      </p>
1363      <p id="rfc.section."> <b>Note:</b> Most HTTP/1.0 caches will not recognize or obey this directive. Also, no-cache response directives with field-names are often
1364         handled by implementations as if an unqualified no-cache directive was received; i.e., the special handling for the qualified
1365         form is not widely implemented.
1366      </p>
1367      <p id="rfc.section."> <b>Note:</b> This directive uses the quoted-string form of the argument syntax. Senders <em class="bcp14">SHOULD NOT</em> use the token form (even if quoting appears not to be needed for single-entry lists).
1368      </p>
1369      <div id="rfc.iref.c.17"></div>
1370      <div id="rfc.iref.n.5"></div>
1371      <h4 id="rfc.section."><a href="#rfc.section."></a>&nbsp;<a id="" href="">no-store</a></h4>
1372      <p id="rfc.section.">The no-store response directive indicates that a cache <em class="bcp14">MUST NOT</em> store any part of either the immediate request or response. This directive applies to both private and shared caches. "<em class="bcp14">MUST NOT</em> store" in this context means that the cache <em class="bcp14">MUST NOT</em> intentionally store the information in non-volatile storage, and <em class="bcp14">MUST</em> make a best-effort attempt to remove the information from volatile storage as promptly as possible after forwarding it.
1373      </p>
1374      <p id="rfc.section.">This directive is NOT a reliable or sufficient mechanism for ensuring privacy. In particular, malicious or compromised caches
1375         might not recognize or obey this directive, and communications networks might be vulnerable to eavesdropping.
1376      </p>
1377      <div id="rfc.iref.c.18"></div>
1378      <div id="rfc.iref.m.4"></div>
1379      <h4 id="rfc.section."><a href="#rfc.section."></a>&nbsp;<a id="cache-response-directive.must-revalidate" href="#cache-response-directive.must-revalidate">must-revalidate</a></h4>
1380      <p id="rfc.section.">The must-revalidate response directive indicates that once it has become stale, a cache <em class="bcp14">MUST NOT</em> use the response to satisfy subsequent requests without successful validation on the origin server.
1381      </p>
1382      <p id="rfc.section.">The must-revalidate directive is necessary to support reliable operation for certain protocol features. In all circumstances
1383         a cache <em class="bcp14">MUST</em> obey the must-revalidate directive; in particular, if a cache cannot reach the origin server for any reason, it <em class="bcp14">MUST</em> generate a <a href="p2-semantics.html#status.504" class="smpl">504 (Gateway Timeout)</a> response.
1384      </p>
1385      <p id="rfc.section.">The must-revalidate directive ought to be used by servers if and only if failure to validate a request on the representation
1386         could result in incorrect operation, such as a silently unexecuted financial transaction.
1387      </p>
1388      <div id="rfc.iref.c.19"></div>
1389      <div id="rfc.iref.p.4"></div>
1390      <h4 id="rfc.section."><a href="#rfc.section."></a>&nbsp;<a id="cache-response-directive.proxy-revalidate" href="#cache-response-directive.proxy-revalidate">proxy-revalidate</a></h4>
1391      <p id="rfc.section.">The proxy-revalidate response directive has the same meaning as the must-revalidate response directive, except that it does
1392         not apply to private caches.
1393      </p>
1394      <div id="rfc.iref.c.20"></div>
1395      <div id="rfc.iref.m.5"></div>
1396      <h4 id="rfc.section."><a href="#rfc.section."></a>&nbsp;<a id="cache-response-directive.max-age" href="#cache-response-directive.max-age">max-age</a></h4>
1397      <p id="rfc.section.">Argument syntax: </p>
1398      <ul class="empty">
1399         <li> <a href="#delta-seconds" class="smpl">delta-seconds</a> (see <a href="#delta-seconds" title="Delta Seconds">Section&nbsp;1.5</a>)
1400         </li>
1401      </ul>
1402      <p id="rfc.section.">The max-age response directive indicates that the response is to be considered stale after its age is greater than the specified
1403         number of seconds.
1404      </p>
1405      <p id="rfc.section."> <b>Note:</b> This directive uses the token form of the argument syntax; e.g., 'max-age=5', not 'max-age="5"'. Senders <em class="bcp14">SHOULD NOT</em> use the quoted-string form.
1406      </p>
1407      <div id="rfc.iref.c.21"></div>
1408      <div id="rfc.iref.s.4"></div>
1409      <h4 id="rfc.section."><a href="#rfc.section."></a>&nbsp;<a id="cache-response-directive.s-maxage" href="#cache-response-directive.s-maxage">s-maxage</a></h4>
1410      <p id="rfc.section.">Argument syntax: </p>
1411      <ul class="empty">
1412         <li> <a href="#delta-seconds" class="smpl">delta-seconds</a> (see <a href="#delta-seconds" title="Delta Seconds">Section&nbsp;1.5</a>)
1413         </li>
1414      </ul>
1415      <p id="rfc.section.">The s-maxage response directive indicates that, in shared caches, the maximum age specified by this directive overrides the
1416         maximum age specified by either the max-age directive or the <a href="#header.expires" class="smpl">Expires</a> header field. The s-maxage directive also implies the semantics of the proxy-revalidate response directive.
1417      </p>
1418      <p id="rfc.section."> <b>Note:</b> This directive uses the token form of the argument syntax; e.g., 's-maxage=10', not 's-maxage="10"'. Senders <em class="bcp14">SHOULD NOT</em> use the quoted-string form.
1419      </p>
1420      <div id="rfc.iref.c.22"></div>
1421      <div id="rfc.iref.n.6"></div>
1422      <h4 id="rfc.section."><a href="#rfc.section."></a>&nbsp;<a id="" href="">no-transform</a></h4>
1423      <p id="rfc.section.">The no-transform response directive indicates that an intermediary (regardless of whether it implements a cache) <em class="bcp14">MUST NOT</em> change the Content-Encoding, <a href="p5-range.html#header.content-range" class="smpl">Content-Range</a> or Content-Type response header fields, nor the response representation.
1424      </p>
1425      <h3 id="rfc.section.3.2.3"><a href="#rfc.section.3.2.3">3.2.3</a>&nbsp;<a id="cache.control.extensions" href="#cache.control.extensions">Cache Control Extensions</a></h3>
1426      <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
1427         value. Informational extensions (those that do not require a change in cache behavior) can be added without changing the semantics
1428         of other directives. Behavioral extensions are designed to work by acting as modifiers to the existing base of cache directives.
1429         Both the new directive and the standard directive are supplied, such that applications that do not understand the new directive
1430         will default to the behavior specified by the standard directive, and those that understand the new directive will recognize
1431         it as modifying the requirements associated with the standard directive. In this way, extensions to the cache-control directives
1432         can be made without requiring changes to the base protocol.
1433      </p>
1434      <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,
1435         obeying certain extensions, and ignoring all directives that it does not understand.
1436      </p>
1437      <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.
1438         We define this new directive to mean that, in addition to any private cache, any cache that is shared only by members of the
1439         community named within its value is allowed to cache the response. An origin server wishing to allow the UCI community to
1440         use an otherwise private response in their shared cache(s) could do so by including
1441      </p>
1442      <div id="rfc.figure.u.10"></div><pre class="text">  Cache-Control: private, community="UCI"
1443</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
1444         it will also see and understand the private directive and thus default to the safe behavior.
1445      </p>
1446      <p id="rfc.section.3.2.3.p.6">A cache <em class="bcp14">MUST</em> ignore unrecognized cache directives; it is assumed that any cache directive likely to be unrecognized by an HTTP/1.1 cache
1447         will be combined with standard directives (or the response's default cacheability) such that the cache behavior will remain
1448         minimally correct even if the cache does not understand the extension(s).
1449      </p>
1450      <p id="rfc.section.3.2.3.p.7">New extension directives ought to consider defining:</p>
1451      <p id="rfc.section.3.2.3.p.8"> </p>
1452      <ul>
1453         <li>What it means for a directive to be specified multiple times,</li>
1454         <li>When the directive does not take an argument, what it means when an argument is present,</li>
1455         <li>When the directive requires an argument, what it means when it is missing.</li>
1456      </ul>
1457      <p id="rfc.section.3.2.3.p.9">The HTTP Cache Directive Registry defines the name space for the cache directives.</p>
1458      <p id="rfc.section.3.2.3.p.10">A registration <em class="bcp14">MUST</em> include the following fields:
1459      </p>
1460      <ul>
1461         <li>Cache Directive Name</li>
1462         <li>Pointer to specification text</li>
1463      </ul>
1464      <p id="rfc.section.3.2.3.p.11">Values to be added to this name space require IETF Review (see <a href="#RFC5226" id="rfc.xref.RFC5226.1"><cite title="Guidelines for Writing an IANA Considerations Section in RFCs">[RFC5226]</cite></a>, <a href="">Section 4.1</a>).
1465      </p>
1466      <p id="rfc.section.3.2.3.p.12">The registry itself is maintained at &lt;<a href=""></a>&gt;.
1467      </p>
1468      <div id="rfc.iref.e.2"></div>
1469      <div id="rfc.iref.h.4"></div>
1470      <h2 id="rfc.section.3.3"><a href="#rfc.section.3.3">3.3</a>&nbsp;<a id="header.expires" href="#header.expires">Expires</a></h2>
1471      <p id="rfc.section.3.3.p.1">The "Expires" header field gives the date/time after which the response is considered stale. See <a href="#expiration.model" title="Freshness Model">Section&nbsp;2.3</a> for further discussion of the freshness model.
1472      </p>
1473      <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
1474         that time.
1475      </p>
1476      <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="Date/Time Formats">Section 5.1</a> of <a href="#Part2" id="rfc.xref.Part2.7"><cite title="HTTP/1.1, part 2: Message Semantics, Payload and Content Negotiation">[Part2]</cite></a>; a sender <em class="bcp14">MUST</em> use the rfc1123-date format.
1477      </p>
1478      <div id="rfc.figure.u.11"></div><pre class="inline"><span id="rfc.iref.g.5"></span>  <a href="#header.expires" class="smpl">Expires</a> = <a href="#abnf.dependencies" class="smpl">HTTP-date</a>
1479</pre><div id="rfc.figure.u.12"></div>
1480      <p>For example</p>  <pre class="text">  Expires: Thu, 01 Dec 1994 16:00:00 GMT
1481</pre><p id="rfc.section.3.3.p.6">A cache <em class="bcp14">MUST</em> treat other invalid date formats, especially including the value "0", as in the past (i.e., "already expired").
1482      </p>
1483      <div class="note" id="rfc.section.3.3.p.7">
1484         <p> <b>Note:</b> If a response includes a <a href="#header.cache-control" class="smpl">Cache-Control</a> 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.
1485         </p>
1486      </div>
1487      <p id="rfc.section.3.3.p.8">Historically, HTTP required the Expires field-value to be no more than a year in the future. While longer freshness lifetimes
1488         are no longer prohibited, extremely large values have been demonstrated to cause problems (e.g., clock overflows due to use
1489         of 32-bit integers for time values), and most caches will evict a response far sooner than that. Therefore, senders ought
1490         not produce them.
1491      </p>
1492      <p id="rfc.section.3.3.p.9">An origin server without a clock <em class="bcp14">MUST NOT</em> assign Expires values to a response unless these values were associated with the resource by a system or user with a reliable
1493         clock. It <em class="bcp14">MAY</em> assign an Expires value that is known, at or before server configuration time, to be in the past (this allows "pre-expiration"
1494         of responses without storing separate Expires values for each resource).
1495      </p>
1496      <div id="rfc.iref.p.5"></div>
1497      <div id="rfc.iref.h.5"></div>
1498      <h2 id="rfc.section.3.4"><a href="#rfc.section.3.4">3.4</a>&nbsp;<a id="header.pragma" href="#header.pragma">Pragma</a></h2>
1499      <p id="rfc.section.3.4.p.1">The "Pragma" header field allows backwards compatibility with HTTP/1.0 caches, so that clients can specify a "no-cache" request
1500         that they will understand (as <a href="#header.cache-control" class="smpl">Cache-Control</a> was not defined until HTTP/1.1). When the Cache-Control header field is also present and understood in a request, Pragma is
1501         ignored.
1502      </p>
1503      <p id="rfc.section.3.4.p.2">In HTTP/1.0, Pragma was defined as an extensible field for implementation-specified directives for recipients. This specification
1504         deprecates such extensions to improve interoperability.
1505      </p>
1506      <div id="rfc.figure.u.13"></div><pre class="inline"><span id="rfc.iref.g.6"></span><span id="rfc.iref.g.7"></span><span id="rfc.iref.g.8"></span>  <a href="#header.pragma" class="smpl">Pragma</a>           = 1#<a href="#header.pragma" class="smpl">pragma-directive</a>
1507  <a href="#header.pragma" class="smpl">pragma-directive</a> = "no-cache" / <a href="#header.pragma" class="smpl">extension-pragma</a>
1508  <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> ) ]
1509</pre><p id="rfc.section.3.4.p.4">When the <a href="#header.cache-control" class="smpl">Cache-Control</a> header field is not present in a request, the no-cache request pragma-directive <em class="bcp14">MUST</em> have the same effect on caches as if "Cache-Control: no-cache" were present (see <a href="#cache-request-directive" title="Request Cache-Control Directives">Section&nbsp;3.2.1</a>).
1510      </p>
1511      <p id="rfc.section.3.4.p.5">When sending a no-cache request, a client ought to include both the pragma and cache-control directives, unless Cache-Control:
1512         no-cache is purposefully omitted to target other <a href="#header.cache-control" class="smpl">Cache-Control</a> response directives at HTTP/1.1 caches. For example:
1513      </p>
1514      <div id="rfc.figure.u.14"></div> <pre class="text">GET / HTTP/1.1
1516Cache-Control: max-age=30
1517Pragma: no-cache
1519</pre> <p id="rfc.section.3.4.p.7">will constrain HTTP/1.1 caches to serve a response no older than 30 seconds, while precluding implementations that do not
1520         understand <a href="#header.cache-control" class="smpl">Cache-Control</a> from serving a cached response.
1521      </p>
1522      <div class="note" id="rfc.section.3.4.p.8">
1523         <p> <b>Note:</b> Because the meaning of "Pragma: no-cache" in responses is not specified, it does not provide a reliable replacement for "Cache-Control:
1524            no-cache" in them.
1525         </p>
1526      </div>
1527      <div id="rfc.iref.v.3"></div>
1528      <div id="rfc.iref.h.6"></div>
1529      <h2 id="rfc.section.3.5"><a href="#rfc.section.3.5">3.5</a>&nbsp;<a id="header.vary" href="#header.vary">Vary</a></h2>
1530      <p id="rfc.section.3.5.p.1">The "Vary" header field conveys the set of header fields that were used to select the representation.</p>
1531      <p id="rfc.section.3.5.p.2">Caches use this information, in part, to determine whether a stored response can be used to satisfy a given request; see <a href="#caching.negotiated.responses" title="Caching Negotiated Responses">Section&nbsp;2.8</a>. determines, while the response is fresh, whether a cache is permitted to use the response to reply to a subsequent request
1532         without validation; see <a href="#caching.negotiated.responses" title="Caching Negotiated Responses">Section&nbsp;2.8</a>.
1533      </p>
1534      <p id="rfc.section.3.5.p.3">In uncacheable or stale responses, the Vary field value advises the user agent about the criteria that were used to select
1535         the representation.
1536      </p>
1537      <div id="rfc.figure.u.15"></div><pre class="inline"><span id="rfc.iref.g.9"></span>  <a href="#header.vary" class="smpl">Vary</a> = "*" / 1#<a href="#abnf.dependencies" class="smpl">field-name</a>
1538</pre><p id="rfc.section.3.5.p.5">The set of header fields named by the Vary field value is known as the selecting header fields.</p>
1539      <p id="rfc.section.3.5.p.6">A server <em class="bcp14">SHOULD</em> include a Vary header field with any cacheable response that is subject to server-driven negotiation. Doing so allows a cache
1540         to properly interpret future requests on that resource and informs the user agent about the presence of negotiation on that
1541         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
1542         the user agent with useful information about the dimensions over which the response varies at the time of the response.
1543      </p>
1544      <p id="rfc.section.3.5.p.7">A Vary field value of "*" signals that unspecified parameters not limited to the header fields (e.g., the network address
1545         of the client), play a role in the selection of the response representation; therefore, a cache cannot determine whether this
1546         response is appropriate. A proxy <em class="bcp14">MUST NOT</em> generate the "*" value.
1547      </p>
1548      <p id="rfc.section.3.5.p.8">The field-names given are not limited to the set of standard header fields defined by this specification. Field names are
1549         case-insensitive.
1550      </p>
1551      <div id="rfc.iref.w.1"></div>
1552      <div id="rfc.iref.h.7"></div>
1553      <h2 id="rfc.section.3.6"><a href="#rfc.section.3.6">3.6</a>&nbsp;<a id="header.warning" href="#header.warning">Warning</a></h2>
1554      <p id="rfc.section.3.6.p.1">The "Warning" header field is used to carry additional information about the status or transformation of a message that might
1555         not be reflected in the message. This information is typically used to warn about possible incorrectness introduced by caching
1556         operations or transformations applied to the payload of the message.
1557      </p>
1558      <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
1559         code, distinguishes these responses from true failures.
1560      </p>
1561      <p id="rfc.section.3.6.p.3">Warning header fields can in general be applied to any message, however some warn-codes are specific to caches and can only
1562         be applied to response messages.
1563      </p>
1564      <div id="rfc.figure.u.16"></div><pre class="inline"><span id="rfc.iref.g.10"></span><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><span id="rfc.iref.g.15"></span>  <a href="#header.warning" class="smpl">Warning</a>       = 1#<a href="#header.warning" class="smpl">warning-value</a>
1566  <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>
1567                                        [<a href="#notation" class="smpl">SP</a> <a href="#header.warning" class="smpl">warn-date</a>]
1569  <a href="#header.warning" class="smpl">warn-code</a>  = 3<a href="#notation" class="smpl">DIGIT</a>
1570  <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>
1571                  ; the name or pseudonym of the server adding
1572                  ; the Warning header field, for use in debugging
1573  <a href="#header.warning" class="smpl">warn-text</a>  = <a href="#core.rules" class="smpl">quoted-string</a>
1574  <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>
1575</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
1576         the same code number, only differing in warn-text.
1577      </p>
1578      <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.
1579      </p>
1580      <p id="rfc.section.3.6.p.7">Systems that generate multiple Warning header fields are encouraged to order them with this user agent behavior in mind. New
1581         Warning header fields are added after any existing Warning headers fields.
1582      </p>
1583      <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
1584         a stored response after validation:
1585      </p>
1586      <ul>
1587         <li>1xx Warnings describe the freshness or validation status of the response, and so <em class="bcp14">MUST</em> be deleted by a cache after validation. They can only be generated by a cache when validating a cached entry, and <em class="bcp14">MUST NOT</em> be generated in any other situation.
1588         </li>
1589         <li>2xx Warnings describe some aspect of the representation that is not rectified by a validation (for example, a lossy compression
1590            of the representation) and <em class="bcp14">MUST NOT</em> be deleted by a cache after validation, unless a full response is returned, in which case they <em class="bcp14">MUST</em> be.
1591         </li>
1592      </ul>
1593      <p id="rfc.section.3.6.p.9">If an implementation sends a message with one or more Warning header fields to a receiver whose version is HTTP/1.0 or lower,
1594         then the sender <em class="bcp14">MUST</em> include in each warning-value a warn-date that matches the Date header field in the message.
1595      </p>
1596      <p id="rfc.section.3.6.p.10">If a system receives a message with a warning-value that includes a warn-date, and that warn-date is different from the Date
1597         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
1598         header fields.) If all of the warning-values are deleted for this reason, the Warning header field <em class="bcp14">MUST</em> be deleted as well.
1599      </p>
1600      <p id="rfc.section.3.6.p.11">The following warn-codes are defined by this specification, each with a recommended warn-text in English, and a description
1601         of its meaning.
1602      </p>
1603      <div id="rfc.iref.76"></div>
1604      <div id="rfc.iref.w.2"></div>
1605      <h3 id="rfc.section.3.6.1"><a href="#rfc.section.3.6.1">3.6.1</a>&nbsp;<a id="warn.110" href="#warn.110">110 Response is Stale</a></h3>
1606      <p id="rfc.section.3.6.1.p.1">A cache <em class="bcp14">SHOULD</em> include this whenever the returned response is stale.
1607      </p>
1608      <div id="rfc.iref.77"></div>
1609      <div id="rfc.iref.w.3"></div>
1610      <h3 id="rfc.section.3.6.2"><a href="#rfc.section.3.6.2">3.6.2</a>&nbsp;<a id="warn.111" href="#warn.111">111 Revalidation Failed</a></h3>
1611      <p id="rfc.section.3.6.2.p.1">A cache <em class="bcp14">SHOULD</em> include this when returning a stale response because an attempt to validate the response failed, due to an inability to reach
1612         the server.
1613      </p>
1614      <div id="rfc.iref.78"></div>
1615      <div id="rfc.iref.w.4"></div>
1616      <h3 id="rfc.section.3.6.3"><a href="#rfc.section.3.6.3">3.6.3</a>&nbsp;<a id="warn.112" href="#warn.112">112 Disconnected Operation</a></h3>
1617      <p id="rfc.section.3.6.3.p.1">A cache <em class="bcp14">SHOULD</em> include this if it is intentionally disconnected from the rest of the network for a period of time.
1618      </p>
1619      <div id="rfc.iref.79"></div>
1620      <div id="rfc.iref.w.5"></div>
1621      <h3 id="rfc.section.3.6.4"><a href="#rfc.section.3.6.4">3.6.4</a>&nbsp;<a id="warn.113" href="#warn.113">113 Heuristic Expiration</a></h3>
1622      <p id="rfc.section.3.6.4.p.1">A cache <em class="bcp14">SHOULD</em> include this if it heuristically chose a freshness lifetime greater than 24 hours and the response's age is greater than 24
1623         hours.
1624      </p>
1625      <div id="rfc.iref.80"></div>
1626      <div id="rfc.iref.w.6"></div>
1627      <h3 id="rfc.section.3.6.5"><a href="#rfc.section.3.6.5">3.6.5</a>&nbsp;<a id="warn.199" href="#warn.199">199 Miscellaneous Warning</a></h3>
1628      <p id="rfc.section.3.6.5.p.1">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.
1629      </p>
1630      <div id="rfc.iref.81"></div>
1631      <div id="rfc.iref.w.7"></div>
1632      <h3 id="rfc.section.3.6.6"><a href="#rfc.section.3.6.6">3.6.6</a>&nbsp;<a id="warn.214" href="#warn.214">214 Transformation Applied</a></h3>
1633      <p id="rfc.section.3.6.6.p.1"> <em class="bcp14">MUST</em> be added by a proxy if it applies any transformation to the representation, such as changing the content-coding, media-type,
1634         or modifying the representation data, unless this Warning code already appears in the response.
1635      </p>
1636      <div id="rfc.iref.82"></div>
1637      <div id="rfc.iref.w.8"></div>
1638      <h3 id="rfc.section.3.6.7"><a href="#rfc.section.3.6.7">3.6.7</a>&nbsp;<a id="warn.299" href="#warn.299">299 Miscellaneous Persistent Warning</a></h3>
1639      <p id="rfc.section.3.6.7.p.1">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.
1640      </p>
1641      <h3 id="rfc.section.3.6.8"><a href="#rfc.section.3.6.8">3.6.8</a>&nbsp;<a id="warn.code.extensions" href="#warn.code.extensions">Warn Code Extensions</a></h3>
1642      <p id="rfc.section.3.6.8.p.1">The HTTP Warn Code Registry defines the name space for warn codes.</p>
1643      <p id="rfc.section.3.6.8.p.2">A registration <em class="bcp14">MUST</em> include the following fields:
1644      </p>
1645      <ul>
1646         <li>Warn Code (3 digits)</li>
1647         <li>Short Description</li>
1648         <li>Pointer to specification text</li>
1649      </ul>
1650      <p id="rfc.section.3.6.8.p.3">Values to be added to this name space require IETF Review (see <a href="#RFC5226" id="rfc.xref.RFC5226.2"><cite title="Guidelines for Writing an IANA Considerations Section in RFCs">[RFC5226]</cite></a>, <a href="">Section 4.1</a>).
1651      </p>
1652      <p id="rfc.section.3.6.8.p.4">The registry itself is maintained at &lt;<a href=""></a>&gt;.
1653      </p>
1654      <h1 id="rfc.section.4"><a href="#rfc.section.4">4.</a>&nbsp;<a id="history.lists" href="#history.lists">History Lists</a></h1>
1655      <p id="rfc.section.4.p.1">User agents often have history mechanisms, such as "Back" buttons and history lists, that can be used to redisplay a representation
1656         retrieved earlier in a session.
1657      </p>
1658      <p id="rfc.section.4.p.2">The freshness model (<a href="#expiration.model" title="Freshness Model">Section&nbsp;2.3</a>) does not necessarily apply to history mechanisms. I.e., a history mechanism can display a previous representation even if
1659         it has expired.
1660      </p>
1661      <p id="rfc.section.4.p.3">This does not prohibit the history mechanism from telling the user that a view might be stale, or from honoring cache directives
1662         (e.g., Cache-Control: no-store).
1663      </p>
1664      <h1 id="rfc.section.5"><a href="#rfc.section.5">5.</a>&nbsp;<a id="IANA.considerations" href="#IANA.considerations">IANA Considerations</a></h1>
1665      <h2 id="rfc.section.5.1"><a href="#rfc.section.5.1">5.1</a>&nbsp;<a id="cache.directive.registration" href="#cache.directive.registration">Cache Directive Registry</a></h2>
1666      <p id="rfc.section.5.1.p.1">The registration procedure for HTTP Cache Directives is defined by <a href="#cache.control.extensions" title="Cache Control Extensions">Section&nbsp;3.2.3</a> of this document.
1667      </p>
1668      <p id="rfc.section.5.1.p.2">The HTTP Cache Directive Registry shall be created at &lt;<a href=""></a>&gt; and be populated with the registrations below:
1669      </p>
1670      <div id="rfc.table.1">
1671         <div id="iana.cache.directive.registration.table"></div>
1672         <table class="tt full left" cellpadding="3" cellspacing="0">
1673            <thead>
1674               <tr>
1675                  <th>Cache Directive</th>
1676                  <th>Reference</th>
1677               </tr>
1678            </thead>
1679            <tbody>
1680               <tr>
1681                  <td class="left">max-age</td>
1682                  <td class="left"> <a href="#cache-request-directive.max-age" title="max-age">Section&nbsp;</a>, <a href="#cache-response-directive.max-age" title="max-age">Section&nbsp;</a>
1683                  </td>
1684               </tr>
1685               <tr>
1686                  <td class="left">max-stale</td>
1687                  <td class="left"> <a href="#cache-request-directive.max-stale" title="max-stale">Section&nbsp;</a>
1688                  </td>
1689               </tr>
1690               <tr>
1691                  <td class="left">min-fresh</td>
1692                  <td class="left"> <a href="#cache-request-directive.min-fresh" title="min-fresh">Section&nbsp;</a>
1693                  </td>
1694               </tr>
1695               <tr>
1696                  <td class="left">must-revalidate</td>
1697                  <td class="left"> <a href="#cache-response-directive.must-revalidate" title="must-revalidate">Section&nbsp;</a>
1698                  </td>
1699               </tr>
1700               <tr>
1701                  <td class="left">no-cache</td>
1702                  <td class="left"> <a href="" title="no-cache">Section&nbsp;</a>, <a href="" title="no-cache">Section&nbsp;</a>
1703                  </td>
1704               </tr>
1705               <tr>
1706                  <td class="left">no-store</td>
1707                  <td class="left"> <a href="" title="no-store">Section&nbsp;</a>, <a href="" title="no-store">Section&nbsp;</a>
1708                  </td>
1709               </tr>
1710               <tr>
1711                  <td class="left">no-transform</td>
1712                  <td class="left"> <a href="" title="no-transform">Section&nbsp;</a>, <a href="" title="no-transform">Section&nbsp;</a>
1713                  </td>
1714               </tr>
1715               <tr>
1716                  <td class="left">only-if-cached</td>
1717                  <td class="left"> <a href="#cache-request-directive.only-if-cached" title="only-if-cached">Section&nbsp;</a>
1718                  </td>
1719               </tr>
1720               <tr>
1721                  <td class="left">private</td>
1722                  <td class="left"> <a href="#cache-response-directive.private" title="private">Section&nbsp;</a>
1723                  </td>
1724               </tr>
1725               <tr>
1726                  <td class="left">proxy-revalidate</td>
1727                  <td class="left"> <a href="#cache-response-directive.proxy-revalidate" title="proxy-revalidate">Section&nbsp;</a>
1728                  </td>
1729               </tr>
1730               <tr>
1731                  <td class="left">public</td>
1732                  <td class="left"> <a href="#cache-response-directive.only-if-cached" title="public">Section&nbsp;</a>
1733                  </td>
1734               </tr>
1735               <tr>
1736                  <td class="left">s-maxage</td>
1737                  <td class="left"> <a href="#cache-response-directive.s-maxage" title="s-maxage">Section&nbsp;</a>
1738                  </td>
1739               </tr>
1740               <tr>
1741                  <td class="left">stale-if-error</td>
1742                  <td class="left"> <a href="#RFC5861" id="rfc.xref.RFC5861.1"><cite title="HTTP Cache-Control Extensions for Stale Content">[RFC5861]</cite></a>, <a href="">Section 4</a>
1743                  </td>
1744               </tr>
1745               <tr>
1746                  <td class="left">stale-while-revalidate</td>
1747                  <td class="left"> <a href="#RFC5861" id="rfc.xref.RFC5861.2"><cite title="HTTP Cache-Control Extensions for Stale Content">[RFC5861]</cite></a>, <a href="">Section 3</a>
1748                  </td>
1749               </tr>
1750            </tbody>
1751         </table>
1752      </div>
1753      <h2 id="rfc.section.5.2"><a href="#rfc.section.5.2">5.2</a>&nbsp;<a id="warn.code.registration" href="#warn.code.registration">Warn Code Registry</a></h2>
1754      <p id="rfc.section.5.2.p.1">The registration procedure for HTTP Warn Codes is defined by <a href="#warn.code.extensions" title="Warn Code Extensions">Section&nbsp;3.6.8</a> of this document.
1755      </p>
1756      <p id="rfc.section.5.2.p.2">The HTTP Warn Code Registry shall be created at &lt;<a href=""></a>&gt; and be populated with the registrations below:
1757      </p>
1758      <div id="rfc.table.2">
1759         <div id="iana.warn.code.registration.table"></div>
1760         <table class="tt full left" cellpadding="3" cellspacing="0">
1761            <thead>
1762               <tr>
1763                  <th>Warn Code</th>
1764                  <th>Short Description</th>
1765                  <th>Reference</th>
1766               </tr>
1767            </thead>
1768            <tbody>
1769               <tr>
1770                  <td class="left">110</td>
1771                  <td class="left">Response is Stale</td>
1772                  <td class="left"> <a href="#warn.110" id="rfc.xref.warn.110.1" title="110 Response is Stale">Section&nbsp;3.6.1</a>
1773                  </td>
1774               </tr>
1775               <tr>
1776                  <td class="left">111</td>
1777                  <td class="left">Revalidation Failed</td>
1778                  <td class="left"> <a href="#warn.111" id="rfc.xref.warn.111.1" title="111 Revalidation Failed">Section&nbsp;3.6.2</a>
1779                  </td>
1780               </tr>
1781               <tr>
1782                  <td class="left">112</td>
1783                  <td class="left">Disconnected Operation</td>
1784                  <td class="left"> <a href="#warn.112" id="rfc.xref.warn.112.1" title="112 Disconnected Operation">Section&nbsp;3.6.3</a>
1785                  </td>
1786               </tr>
1787               <tr>
1788                  <td class="left">113</td>
1789                  <td class="left">Heuristic Expiration</td>
1790                  <td class="left"> <a href="#warn.113" id="rfc.xref.warn.113.1" title="113 Heuristic Expiration">Section&nbsp;3.6.4</a>
1791                  </td>
1792               </tr>
1793               <tr>
1794                  <td class="left">199</td>
1795                  <td class="left">Miscellaneous Warning</td>
1796                  <td class="left"> <a href="#warn.199" id="rfc.xref.warn.199.1" title="199 Miscellaneous Warning">Section&nbsp;3.6.5</a>
1797                  </td>
1798               </tr>
1799               <tr>
1800                  <td class="left">214</td>
1801                  <td class="left">Transformation Applied</td>
1802                  <td class="left"> <a href="#warn.214" id="rfc.xref.warn.214.1" title="214 Transformation Applied">Section&nbsp;3.6.6</a>
1803                  </td>
1804               </tr>
1805               <tr>
1806                  <td class="left">299</td>
1807                  <td class="left">Miscellaneous Persistent Warning</td>
1808                  <td class="left"> <a href="#warn.299" id="rfc.xref.warn.299.1" title="299 Miscellaneous Persistent Warning">Section&nbsp;3.6.7</a>
1809                  </td>
1810               </tr>
1811            </tbody>
1812         </table>
1813      </div>
1814      <h2 id="rfc.section.5.3"><a href="#rfc.section.5.3">5.3</a>&nbsp;<a id="header.field.registration" href="#header.field.registration">Header Field Registration</a></h2>
1815      <p id="rfc.section.5.3.p.1">The Message Header Field Registry located at &lt;<a href=""></a>&gt; shall be updated with the permanent registrations below (see <a href="#RFC3864" id="rfc.xref.RFC3864.1"><cite title="Registration Procedures for Message Header Fields">[RFC3864]</cite></a>):
1816      </p>
1817      <div id="rfc.table.3">
1818         <div id="iana.header.registration.table"></div>
1819         <table class="tt full left" cellpadding="3" cellspacing="0">
1820            <thead>
1821               <tr>
1822                  <th>Header Field Name</th>
1823                  <th>Protocol</th>
1824                  <th>Status</th>
1825                  <th>Reference</th>
1826               </tr>
1827            </thead>
1828            <tbody>
1829               <tr>
1830                  <td class="left">Age</td>
1831                  <td class="left">http</td>
1832                  <td class="left">standard</td>
1833                  <td class="left"> <a href="#header.age" id="rfc.xref.header.age.3" title="Age">Section&nbsp;3.1</a>
1834                  </td>
1835               </tr>
1836               <tr>
1837                  <td class="left">Cache-Control</td>
1838                  <td class="left">http</td>
1839                  <td class="left">standard</td>
1840                  <td class="left"> <a href="#header.cache-control" id="rfc.xref.header.cache-control.2" title="Cache-Control">Section&nbsp;3.2</a>
1841                  </td>
1842               </tr>
1843               <tr>
1844                  <td class="left">Expires</td>
1845                  <td class="left">http</td>
1846                  <td class="left">standard</td>
1847                  <td class="left"> <a href="#header.expires" id="rfc.xref.header.expires.4" title="Expires">Section&nbsp;3.3</a>
1848                  </td>
1849               </tr>
1850               <tr>
1851                  <td class="left">Pragma</td>
1852                  <td class="left">http</td>
1853                  <td class="left">standard</td>
1854                  <td class="left"> <a href="#header.pragma" id="rfc.xref.header.pragma.3" title="Pragma">Section&nbsp;3.4</a>
1855                  </td>
1856               </tr>
1857               <tr>
1858                  <td class="left">Vary</td>
1859                  <td class="left">http</td>
1860                  <td class="left">standard</td>
1861                  <td class="left"> <a href="#header.vary" id="rfc.xref.header.vary.2" title="Vary">Section&nbsp;3.5</a>
1862                  </td>
1863               </tr>
1864               <tr>
1865                  <td class="left">Warning</td>
1866                  <td class="left">http</td>
1867                  <td class="left">standard</td>
1868                  <td class="left"> <a href="#header.warning" id="rfc.xref.header.warning.5" title="Warning">Section&nbsp;3.6</a>
1869                  </td>
1870               </tr>
1871            </tbody>
1872         </table>
1873      </div>
1874      <p id="rfc.section.5.3.p.2">The change controller is: "IETF ( - Internet Engineering Task Force".</p>
1875      <h1 id="rfc.section.6"><a href="#rfc.section.6">6.</a>&nbsp;<a id="security.considerations" href="#security.considerations">Security Considerations</a></h1>
1876      <p id="rfc.section.6.p.1">Caches expose additional potential vulnerabilities, since the contents of the cache represent an attractive target for malicious
1877         exploitation. Because cache contents persist after an HTTP request is complete, an attack on the cache can reveal information
1878         long after a user believes that the information has been removed from the network. Therefore, cache contents need to be protected
1879         as sensitive information.
1880      </p>
1881      <h1 id="rfc.section.7"><a href="#rfc.section.7">7.</a>&nbsp;<a id="acks" href="#acks">Acknowledgments</a></h1>
1882      <p id="rfc.section.7.p.1">See <a href="p1-messaging.html#acks" title="Acknowledgments">Section 9</a> of <a href="#Part1" id="rfc.xref.Part1.17"><cite title="HTTP/1.1, part 1: URIs, Connections, and Message Parsing">[Part1]</cite></a>.
1883      </p>
1884      <h1 id="rfc.references"><a id="rfc.section.8" href="#rfc.section.8">8.</a> References
1885      </h1>
1886      <h2 id="rfc.references.1"><a href="#rfc.section.8.1" id="rfc.section.8.1">8.1</a> Normative References
1887      </h2>
1888      <table>             
1889         <tr>
1890            <td class="reference"><b id="Part1">[Part1]</b></td>
1891            <td class="top"><a href="" title="Adobe Systems Incorporated">Fielding, R., Ed.</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-latest (work in progress), July&nbsp;2012.
1892            </td>
1893         </tr>
1894         <tr>
1895            <td class="reference"><b id="Part2">[Part2]</b></td>
1896            <td class="top"><a href="" title="Adobe Systems Incorporated">Fielding, R., Ed.</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, Payload and Content Negotiation</a>”, Internet-Draft&nbsp;draft-ietf-httpbis-p2-semantics-latest (work in progress), July&nbsp;2012.
1897            </td>
1898         </tr>
1899         <tr>
1900            <td class="reference"><b id="Part4">[Part4]</b></td>
1901            <td class="top"><a href="" title="Adobe Systems Incorporated">Fielding, R., Ed.</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-latest (work in progress), July&nbsp;2012.
1902            </td>
1903         </tr>
1904         <tr>
1905            <td class="reference"><b id="Part5">[Part5]</b></td>
1906            <td class="top"><a href="" title="Adobe Systems Incorporated">Fielding, R., Ed.</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-latest (work in progress), July&nbsp;2012.
1907            </td>
1908         </tr>
1909         <tr>
1910            <td class="reference"><b id="Part7">[Part7]</b></td>
1911            <td class="top"><a href="" title="Adobe Systems Incorporated">Fielding, R., Ed.</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-latest (work in progress), July&nbsp;2012.
1912            </td>
1913         </tr>
1914         <tr>
1915            <td class="reference"><b id="RFC2119">[RFC2119]</b></td>
1916            <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.
1917            </td>
1918         </tr>
1919         <tr>
1920            <td class="reference"><b id="RFC5234">[RFC5234]</b></td>
1921            <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.
1922            </td>
1923         </tr>
1924      </table>
1925      <h2 id="rfc.references.2"><a href="#rfc.section.8.2" id="rfc.section.8.2">8.2</a> Informative References
1926      </h2>
1927      <table>         
1928         <tr>
1929            <td class="reference"><b id="RFC1305">[RFC1305]</b></td>
1930            <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.
1931            </td>
1932         </tr>
1933         <tr>
1934            <td class="reference"><b id="RFC2616">[RFC2616]</b></td>
1935            <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.
1936            </td>
1937         </tr>
1938         <tr>
1939            <td class="reference"><b id="RFC3864">[RFC3864]</b></td>
1940            <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.
1941            </td>
1942         </tr>
1943         <tr>
1944            <td class="reference"><b id="RFC5226">[RFC5226]</b></td>
1945            <td class="top"><a href="" title="IBM">Narten, T.</a> and <a href="" title="Google">H. Alvestrand</a>, “<a href="">Guidelines for Writing an IANA Considerations Section in RFCs</a>”, BCP&nbsp;26, RFC&nbsp;5226, May&nbsp;2008.
1946            </td>
1947         </tr>
1948         <tr>
1949            <td class="reference"><b id="RFC5861">[RFC5861]</b></td>
1950            <td class="top"><a href="" title="Yahoo! Inc.">Nottingham, M.</a>, “<a href="">HTTP Cache-Control Extensions for Stale Content</a>”, RFC&nbsp;5861, April&nbsp;2010.
1951            </td>
1952         </tr>
1953      </table>
1954      <div class="avoidbreak">
1955         <h1 id="rfc.authors"><a href="#rfc.authors">Authors' Addresses</a></h1>
1956         <address class="vcard"><span class="vcardline"><span class="fn">Roy T. Fielding</span>
1957               (editor)
1958               <span class="n hidden"><span class="family-name">Fielding</span><span class="given-name">Roy T.</span></span></span><span class="org vcardline">Adobe Systems Incorporated</span><span class="adr"><span class="street-address vcardline">345 Park Ave</span><span class="vcardline"><span class="locality">San Jose</span>, <span class="region">CA</span>&nbsp;<span class="postal-code">95110</span></span><span class="country-name vcardline">USA</span></span><span class="vcardline">Email: <a href=""><span class="email"></span></a></span><span class="vcardline">URI: <a href="" class="url"></a></span></address>
1959         <address class="vcard"><span class="vcardline"><span class="fn">Yves Lafon</span>
1960               (editor)
1961               <span class="n hidden"><span class="family-name">Lafon</span><span class="given-name">Yves</span></span></span><span class="org vcardline">World Wide Web Consortium</span><span class="adr"><span class="street-address vcardline">W3C / ERCIM</span><span class="street-address vcardline">2004, rte des Lucioles</span><span class="vcardline"><span class="locality">Sophia-Antipolis</span>, <span class="region">AM</span>&nbsp;<span class="postal-code">06902</span></span><span class="country-name vcardline">France</span></span><span class="vcardline">Email: <a href=""><span class="email"></span></a></span><span class="vcardline">URI: <a href="" class="url"></a></span></address>
1962         <address class="vcard"><span class="vcardline"><span class="fn">Mark Nottingham</span>
1963               (editor)
1964               <span class="n hidden"><span class="family-name">Nottingham</span><span class="given-name">Mark</span></span></span><span class="org vcardline">Rackspace</span><span class="vcardline">Email: <a href=""><span class="email"></span></a></span><span class="vcardline">URI: <a href="" class="url"></a></span></address>
1965         <address class="vcard"><span class="vcardline"><span class="fn">Julian F. Reschke</span>
1966               (editor)
1967               <span class="n hidden"><span class="family-name">Reschke</span><span class="given-name">Julian F.</span></span></span><span class="org vcardline">greenbytes GmbH</span><span class="adr"><span class="street-address vcardline">Hafenweg 16</span><span class="vcardline"><span class="locality">Muenster</span>, <span class="region">NW</span>&nbsp;<span class="postal-code">48155</span></span><span class="country-name vcardline">Germany</span></span><span class="vcardline">Email: <a href=""><span class="email"></span></a></span><span class="vcardline">URI: <a href="" class="url"></a></span></address>
1968      </div>
1969      <h1 id="rfc.section.A" class="np"><a href="#rfc.section.A">A.</a>&nbsp;<a id="changes.from.rfc.2616" href="#changes.from.rfc.2616">Changes from RFC 2616</a></h1>
1970      <p id="rfc.section.A.p.1">Make the specified age calculation algorithm less conservative. (<a href="#age.calculations" title="Calculating Age">Section&nbsp;2.3.2</a>)
1971      </p>
1972      <p id="rfc.section.A.p.2">Remove requirement to consider Content-Location in successful responses in order to determine the appropriate response to
1973         use. (<a href="#validation.model" title="Validation Model">Section&nbsp;2.4</a>)
1974      </p>
1975      <p id="rfc.section.A.p.3">Clarify denial of service attack avoidance requirement. (<a href="#invalidation.after.updates.or.deletions" title="Request Methods that Invalidate">Section&nbsp;2.6</a>)
1976      </p>
1977      <p id="rfc.section.A.p.4">Change ABNF productions for header fields to only define the field value. (<a href="#header.field.definitions" title="Header Field Definitions">Section&nbsp;3</a>)
1978      </p>
1979      <p id="rfc.section.A.p.5">Do not mention RFC 2047 encoding and multiple languages in <a href="#header.warning" class="smpl">Warning</a> header fields anymore, as these aspects never were implemented. (<a href="#header.warning" id="rfc.xref.header.warning.6" title="Warning">Section&nbsp;3.6</a>)
1980      </p>
1981      <h1 id="rfc.section.B"><a href="#rfc.section.B">B.</a>&nbsp;<a id="collected.abnf" href="#collected.abnf">Collected ABNF</a></h1>
1982      <div id="rfc.figure.u.17"></div> <pre class="inline"><a href="#header.age" class="smpl">Age</a> = delta-seconds
1984<a href="#header.cache-control" class="smpl">Cache-Control</a> = *( "," OWS ) cache-directive *( OWS "," [ OWS
1985 cache-directive ] )
1987<a href="#header.expires" class="smpl">Expires</a> = HTTP-date
1989<a href="#abnf.dependencies" class="smpl">HTTP-date</a> = &lt;HTTP-date, defined in [Part2], Section 5.1&gt;
1991<a href="#core.rules" class="smpl">OWS</a> = &lt;OWS, defined in [Part1], Section 3.2.1&gt;
1993<a href="#header.pragma" class="smpl">Pragma</a> = *( "," OWS ) pragma-directive *( OWS "," [ OWS
1994 pragma-directive ] )
1996<a href="#header.vary" class="smpl">Vary</a> = "*" / ( *( "," OWS ) field-name *( OWS "," [ OWS field-name ]
1997 ) )
1999<a href="#header.warning" class="smpl">Warning</a> = *( "," OWS ) warning-value *( OWS "," [ OWS warning-value ]
2000 )
2002<a href="#header.cache-control" class="smpl">cache-directive</a> = token [ "=" ( token / quoted-string ) ]
2004<a href="#delta-seconds" class="smpl">delta-seconds</a> = 1*DIGIT
2006<a href="#header.pragma" class="smpl">extension-pragma</a> = token [ "=" ( token / quoted-string ) ]
2008<a href="#abnf.dependencies" class="smpl">field-name</a> = &lt;field-name, defined in [Part1], Section 3.2&gt;
2010<a href="#abnf.dependencies" class="smpl">port</a> = &lt;port, defined in [Part1], Section 2.7&gt;
2011<a href="#header.pragma" class="smpl">pragma-directive</a> = "no-cache" / extension-pragma
2012<a href="#abnf.dependencies" class="smpl">pseudonym</a> = &lt;pseudonym, defined in [Part1], Section 6.2&gt;
2014<a href="#core.rules" class="smpl">quoted-string</a> = &lt;quoted-string, defined in [Part1], Section 3.2.4&gt;
2016<a href="#core.rules" class="smpl">token</a> = &lt;token, defined in [Part1], Section 3.2.4&gt;
2018<a href="#abnf.dependencies" class="smpl">uri-host</a> = &lt;uri-host, defined in [Part1], Section 2.7&gt;
2020<a href="#header.warning" class="smpl">warn-agent</a> = ( uri-host [ ":" port ] ) / pseudonym
2021<a href="#header.warning" class="smpl">warn-code</a> = 3DIGIT
2022<a href="#header.warning" class="smpl">warn-date</a> = DQUOTE HTTP-date DQUOTE
2023<a href="#header.warning" class="smpl">warn-text</a> = quoted-string
2024<a href="#header.warning" class="smpl">warning-value</a> = warn-code SP warn-agent SP warn-text [ SP warn-date
2025 ]
2026</pre> <div id="rfc.figure.u.18"></div>
2027      <p>ABNF diagnostics:</p><pre class="inline">; Age defined but not used
2028; Cache-Control defined but not used
2029; Expires defined but not used
2030; Pragma defined but not used
2031; Vary defined but not used
2032; Warning defined but not used
2033</pre><h1 id="rfc.section.C"><a href="#rfc.section.C">C.</a>&nbsp;<a id="change.log" href="#change.log">Change Log (to be removed by RFC Editor before publication)</a></h1>
2034      <p id="rfc.section.C.p.1">Changes up to the first Working Group Last Call draft are summarized in &lt;<a href=""></a>&gt;.
2035      </p>
2036      <h2 id="rfc.section.C.1"><a href="#rfc.section.C.1">C.1</a>&nbsp;<a id="changes.since.19" href="#changes.since.19">Since draft-ietf-httpbis-p6-cache-19</a></h2>
2037      <p id="rfc.section.C.1.p.1">Closed issues: </p>
2038      <ul>
2039         <li> &lt;<a href=""></a>&gt;: "untangle Cache-Control ABNF"
2040         </li>
2041         <li> &lt;<a href=""></a>&gt;: "Multiple values in Cache-Control headers"
2042         </li>
2043         <li> &lt;<a href=""></a>&gt;: "Case sensitivity of header fields in CC values"
2044         </li>
2045         <li> &lt;<a href=""></a>&gt;: "Spurious 'MAY's"
2046         </li>
2047         <li> &lt;<a href=""></a>&gt;: "enhance considerations for new cache control directives"
2048         </li>
2049         <li> &lt;<a href=""></a>&gt;: "ABNF requirements for recipients"
2050         </li>
2051      </ul>
2052      <h1 id="rfc.index"><a href="#rfc.index">Index</a></h1>
2053      <p class="noprint"><a href="#rfc.index.1">1</a> <a href="#rfc.index.2">2</a> <a href="#rfc.index.A">A</a> <a href="#rfc.index.C">C</a> <a href="#rfc.index.E">E</a> <a href="#rfc.index.F">F</a> <a href="#rfc.index.G">G</a> <a href="#rfc.index.H">H</a> <a href="#rfc.index.M">M</a> <a href="#rfc.index.N">N</a> <a href="#rfc.index.O">O</a> <a href="#rfc.index.P">P</a> <a href="#rfc.index.R">R</a> <a href="#rfc.index.S">S</a> <a href="#rfc.index.V">V</a> <a href="#rfc.index.W">W</a>
2054      </p>
2055      <div class="print2col">
2056         <ul class="ind">
2057            <li><a id="rfc.index.1" href="#rfc.index.1"><b>1</b></a><ul>
2058                  <li>110 Response is Stale (warn code)&nbsp;&nbsp;<a href="#rfc.iref.76"><b>3.6.1</b></a>, <a href="#rfc.xref.warn.110.1">5.2</a></li>
2059                  <li>111 Revalidation Failed (warn code)&nbsp;&nbsp;<a href="#rfc.iref.77"><b>3.6.2</b></a>, <a href="#rfc.xref.warn.111.1">5.2</a></li>
2060                  <li>112 Disconnected Operation (warn code)&nbsp;&nbsp;<a href="#rfc.iref.78"><b>3.6.3</b></a>, <a href="#rfc.xref.warn.112.1">5.2</a></li>
2061                  <li>113 Heuristic Expiration (warn code)&nbsp;&nbsp;<a href="#rfc.iref.79"><b>3.6.4</b></a>, <a href="#rfc.xref.warn.113.1">5.2</a></li>
2062                  <li>199 Miscellaneous Warning (warn code)&nbsp;&nbsp;<a href="#rfc.iref.80"><b>3.6.5</b></a>, <a href="#rfc.xref.warn.199.1">5.2</a></li>
2063               </ul>
2064            </li>
2065            <li><a id="rfc.index.2" href="#rfc.index.2"><b>2</b></a><ul>
2066                  <li>214 Transformation Applied (warn code)&nbsp;&nbsp;<a href="#rfc.iref.81"><b>3.6.6</b></a>, <a href="#rfc.xref.warn.214.1">5.2</a></li>
2067                  <li>299 Miscellaneous Persistent Warning (warn code)&nbsp;&nbsp;<a href="#rfc.iref.82"><b>3.6.7</b></a>, <a href="#rfc.xref.warn.299.1">5.2</a></li>
2068               </ul>
2069            </li>
2070            <li><a id="rfc.index.A" href="#rfc.index.A"><b>A</b></a><ul>
2071                  <li>age&nbsp;&nbsp;<a href="#rfc.iref.a.1">1.2</a></li>
2072                  <li>Age header field&nbsp;&nbsp;<a href="#rfc.xref.header.age.1">2.2</a>, <a href="#rfc.xref.header.age.2">2.3.2</a>, <a href="#rfc.iref.a.2"><b>3.1</b></a>, <a href="#rfc.xref.header.age.3">5.3</a></li>
2073               </ul>
2074            </li>
2075            <li><a id="rfc.index.C" href="#rfc.index.C"><b>C</b></a><ul>
2076                  <li>cache&nbsp;&nbsp;<a href="#rfc.iref.c.1">1.1</a>, <a href="#rfc.iref.c.2">1.2</a></li>
2077                  <li>Cache Directives&nbsp;&nbsp;
2078                     <ul>
2079                        <li>max-age&nbsp;&nbsp;<a href="#rfc.iref.c.9"><b></b></a>, <a href="#rfc.iref.c.20"><b></b></a></li>
2080                        <li>max-stale&nbsp;&nbsp;<a href="#rfc.iref.c.10"><b></b></a></li>
2081                        <li>min-fresh&nbsp;&nbsp;<a href="#rfc.iref.c.11"><b></b></a></li>
2082                        <li>must-revalidate&nbsp;&nbsp;<a href="#rfc.iref.c.18"><b></b></a></li>
2083                        <li>no-cache&nbsp;&nbsp;<a href="#rfc.iref.c.7"><b></b></a>, <a href="#rfc.iref.c.16"><b></b></a></li>
2084                        <li>no-store&nbsp;&nbsp;<a href="#rfc.iref.c.8"><b></b></a>, <a href="#rfc.iref.c.17"><b></b></a></li>
2085                        <li>no-transform&nbsp;&nbsp;<a href="#rfc.iref.c.12"><b></b></a>, <a href="#rfc.iref.c.22"><b></b></a></li>
2086                        <li>only-if-cached&nbsp;&nbsp;<a href="#rfc.iref.c.13"><b></b></a></li>
2087                        <li>private&nbsp;&nbsp;<a href="#rfc.iref.c.15"><b></b></a></li>
2088                        <li>proxy-revalidate&nbsp;&nbsp;<a href="#rfc.iref.c.19"><b></b></a></li>
2089                        <li>public&nbsp;&nbsp;<a href="#rfc.iref.c.14"><b></b></a></li>
2090                        <li>s-maxage&nbsp;&nbsp;<a href="#rfc.iref.c.21"><b></b></a></li>
2091                     </ul>
2092                  </li>
2093                  <li>cache entry&nbsp;&nbsp;<a href="#rfc.iref.c.4">2</a></li>
2094                  <li>cache key&nbsp;&nbsp;<a href="#rfc.iref.c.5">2</a></li>
2095                  <li>Cache-Control header field&nbsp;&nbsp;<a href="#rfc.xref.header.cache-control.1">2.1</a>, <a href="#rfc.iref.c.6"><b>3.2</b></a>, <a href="#rfc.xref.header.cache-control.2">5.3</a></li>
2096                  <li>cacheable&nbsp;&nbsp;<a href="#rfc.iref.c.3">1.2</a></li>
2097               </ul>
2098            </li>
2099            <li><a id="rfc.index.E" href="#rfc.index.E"><b>E</b></a><ul>
2100                  <li>Expires header field&nbsp;&nbsp;<a href="#rfc.xref.header.expires.1">2.1</a>, <a href="#rfc.xref.header.expires.2">2.3</a>, <a href="#rfc.xref.header.expires.3">2.3.1</a>, <a href="#rfc.iref.e.2"><b>3.3</b></a>, <a href="#rfc.xref.header.expires.4">5.3</a></li>
2101                  <li>explicit expiration time&nbsp;&nbsp;<a href="#rfc.iref.e.1">1.2</a></li>
2102               </ul>
2103            </li>
2104            <li><a id="rfc.index.F" href="#rfc.index.F"><b>F</b></a><ul>
2105                  <li>first-hand&nbsp;&nbsp;<a href="#rfc.iref.f.1">1.2</a></li>
2106                  <li>fresh&nbsp;&nbsp;<a href="#rfc.iref.f.3">1.2</a></li>
2107                  <li>freshness lifetime&nbsp;&nbsp;<a href="#rfc.iref.f.2">1.2</a></li>
2108               </ul>
2109            </li>
2110            <li><a id="rfc.index.G" href="#rfc.index.G"><b>G</b></a><ul>
2111                  <li><tt>Grammar</tt>&nbsp;&nbsp;
2112                     <ul>
2113                        <li><tt>Age</tt>&nbsp;&nbsp;<a href="#rfc.iref.g.2"><b>3.1</b></a></li>
2114                        <li><tt>Cache-Control</tt>&nbsp;&nbsp;<a href="#rfc.iref.g.3"><b>3.2</b></a></li>
2115                        <li><tt>cache-directive</tt>&nbsp;&nbsp;<a href="#rfc.iref.g.4"><b>3.2</b></a></li>
2116                        <li><tt>delta-seconds</tt>&nbsp;&nbsp;<a href="#rfc.iref.g.1"><b>1.5</b></a></li>
2117                        <li><tt>Expires</tt>&nbsp;&nbsp;<a href="#rfc.iref.g.5"><b>3.3</b></a></li>
2118                        <li><tt>extension-pragma</tt>&nbsp;&nbsp;<a href="#rfc.iref.g.8"><b>3.4</b></a></li>
2119                        <li><tt>Pragma</tt>&nbsp;&nbsp;<a href="#rfc.iref.g.6"><b>3.4</b></a></li>
2120                        <li><tt>pragma-directive</tt>&nbsp;&nbsp;<a href="#rfc.iref.g.7"><b>3.4</b></a></li>
2121                        <li><tt>Vary</tt>&nbsp;&nbsp;<a href="#rfc.iref.g.9"><b>3.5</b></a></li>
2122                        <li><tt>warn-agent</tt>&nbsp;&nbsp;<a href="#rfc.iref.g.13"><b>3.6</b></a></li>
2123                        <li><tt>warn-code</tt>&nbsp;&nbsp;<a href="#rfc.iref.g.12"><b>3.6</b></a></li>
2124                        <li><tt>warn-date</tt>&nbsp;&nbsp;<a href="#rfc.iref.g.15"><b>3.6</b></a></li>
2125                        <li><tt>warn-text</tt>&nbsp;&nbsp;<a href="#rfc.iref.g.14"><b>3.6</b></a></li>
2126                        <li><tt>Warning</tt>&nbsp;&nbsp;<a href="#rfc.iref.g.10"><b>3.6</b></a></li>
2127                        <li><tt>warning-value</tt>&nbsp;&nbsp;<a href="#rfc.iref.g.11"><b>3.6</b></a></li>
2128                     </ul>
2129                  </li>
2130               </ul>
2131            </li>
2132            <li><a id="rfc.index.H" href="#rfc.index.H"><b>H</b></a><ul>
2133                  <li>Header Fields&nbsp;&nbsp;
2134                     <ul>
2135                        <li>Age&nbsp;&nbsp;<a href="#rfc.xref.header.age.1">2.2</a>, <a href="#rfc.xref.header.age.2">2.3.2</a>, <a href="#rfc.iref.h.2"><b>3.1</b></a>, <a href="#rfc.xref.header.age.3">5.3</a></li>
2136                        <li>Cache-Control&nbsp;&nbsp;<a href="#rfc.xref.header.cache-control.1">2.1</a>, <a href="#rfc.iref.h.3"><b>3.2</b></a>, <a href="#rfc.xref.header.cache-control.2">5.3</a></li>
2137                        <li>Expires&nbsp;&nbsp;<a href="#rfc.xref.header.expires.1">2.1</a>, <a href="#rfc.xref.header.expires.2">2.3</a>, <a href="#rfc.xref.header.expires.3">2.3.1</a>, <a href="#rfc.iref.h.4"><b>3.3</b></a>, <a href="#rfc.xref.header.expires.4">5.3</a></li>
2138                        <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.3</a></li>
2139                        <li>Vary&nbsp;&nbsp;<a href="#rfc.xref.header.vary.1">2.8</a>, <a href="#rfc.iref.h.6"><b>3.5</b></a>, <a href="#rfc.xref.header.vary.2">5.3</a></li>
2140                        <li>Warning&nbsp;&nbsp;<a href="#rfc.xref.header.warning.1">2.3.3</a>, <a href="#rfc.xref.header.warning.2">2.4.1</a>, <a href="#rfc.xref.header.warning.3">2.5</a>, <a href="#rfc.xref.header.warning.4">2.9</a>, <a href="#rfc.iref.h.7"><b>3.6</b></a>, <a href="#rfc.xref.header.warning.5">5.3</a>, <a href="#rfc.xref.header.warning.6">A</a></li>
2141                     </ul>
2142                  </li>
2143                  <li>heuristic expiration time&nbsp;&nbsp;<a href="#rfc.iref.h.1">1.2</a></li>
2144               </ul>
2145            </li>
2146            <li><a id="rfc.index.M" href="#rfc.index.M"><b>M</b></a><ul>
2147                  <li>max-age&nbsp;&nbsp;
2148                     <ul>
2149                        <li>Cache Directive&nbsp;&nbsp;<a href="#rfc.iref.m.1"><b></b></a>, <a href="#rfc.iref.m.5"><b></b></a></li>
2150                     </ul>
2151                  </li>
2152                  <li>max-stale&nbsp;&nbsp;
2153                     <ul>
2154                        <li>Cache Directive&nbsp;&nbsp;<a href="#rfc.iref.m.2"><b></b></a></li>
2155                     </ul>
2156                  </li>
2157                  <li>min-fresh&nbsp;&nbsp;
2158                     <ul>
2159                        <li>Cache Directive&nbsp;&nbsp;<a href="#rfc.iref.m.3"><b></b></a></li>
2160                     </ul>
2161                  </li>
2162                  <li>must-revalidate&nbsp;&nbsp;
2163                     <ul>
2164                        <li>Cache Directive&nbsp;&nbsp;<a href="#rfc.iref.m.4"><b></b></a></li>
2165                     </ul>
2166                  </li>
2167               </ul>
2168            </li>
2169            <li><a id="rfc.index.N" href="#rfc.index.N"><b>N</b></a><ul>
2170                  <li>no-cache&nbsp;&nbsp;
2171                     <ul>
2172                        <li>Cache Directive&nbsp;&nbsp;<a href="#rfc.iref.n.1"><b></b></a>, <a href="#rfc.iref.n.4"><b></b></a></li>
2173                     </ul>
2174                  </li>
2175                  <li>no-store&nbsp;&nbsp;
2176                     <ul>
2177                        <li>Cache Directive&nbsp;&nbsp;<a href="#rfc.iref.n.2"><b></b></a>, <a href="#rfc.iref.n.5"><b></b></a></li>
2178                     </ul>
2179                  </li>
2180                  <li>no-transform&nbsp;&nbsp;
2181                     <ul>
2182                        <li>Cache Directive&nbsp;&nbsp;<a href="#rfc.iref.n.3"><b></b></a>, <a href="#rfc.iref.n.6"><b></b></a></li>
2183                     </ul>
2184                  </li>
2185               </ul>
2186            </li>
2187            <li><a id="rfc.index.O" href="#rfc.index.O"><b>O</b></a><ul>
2188                  <li>only-if-cached&nbsp;&nbsp;
2189                     <ul>
2190                        <li>Cache Directive&nbsp;&nbsp;<a href="#rfc.iref.o.1"><b></b></a></li>
2191                     </ul>
2192                  </li>
2193               </ul>
2194            </li>
2195            <li><a id="rfc.index.P" href="#rfc.index.P"><b>P</b></a><ul>
2196                  <li><em>Part1</em>&nbsp;&nbsp;<a href="#rfc.xref.Part1.1">1.3</a>, <a href="#rfc.xref.Part1.2">1.4</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.1</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.1</a>, <a href="#rfc.xref.Part1.12">2.2</a>, <a href="#rfc.xref.Part1.13">2.6</a>, <a href="#rfc.xref.Part1.14">2.6</a>, <a href="#rfc.xref.Part1.15">2.6</a>, <a href="#rfc.xref.Part1.16">2.8</a>, <a href="#rfc.xref.Part1.17">7</a>, <a href="#Part1"><b>8.1</b></a><ul>
2197                        <li><em>Section 1.2</em>&nbsp;&nbsp;<a href="#rfc.xref.Part1.2">1.4</a></li>
2198                        <li><em>Section 2</em>&nbsp;&nbsp;<a href="#rfc.xref.Part1.1">1.3</a></li>
2199                        <li><em>Section 2.7</em>&nbsp;&nbsp;<a href="#rfc.xref.Part1.8">1.4.2</a>, <a href="#rfc.xref.Part1.10">1.4.2</a></li>
2200                        <li><em>Section 3.2.1</em>&nbsp;&nbsp;<a href="#rfc.xref.Part1.4">1.4.1</a></li>
2201                        <li><em>Section 3.2</em>&nbsp;&nbsp;<a href="#rfc.xref.Part1.7">1.4.2</a>, <a href="#rfc.xref.Part1.16">2.8</a></li>
2202                        <li><em>Section 3.2.4</em>&nbsp;&nbsp;<a href="#rfc.xref.Part1.5">1.4.1</a>, <a href="#rfc.xref.Part1.6">1.4.1</a></li>
2203                        <li><em>Section 5.5</em>&nbsp;&nbsp;<a href="#rfc.xref.Part1.12">2.2</a>, <a href="#rfc.xref.Part1.13">2.6</a>, <a href="#rfc.xref.Part1.14">2.6</a>, <a href="#rfc.xref.Part1.15">2.6</a></li>
2204                        <li><em>Section 6.2</em>&nbsp;&nbsp;<a href="#rfc.xref.Part1.9">1.4.2</a></li>
2205                        <li><em>Section 9</em>&nbsp;&nbsp;<a href="#rfc.xref.Part1.17">7</a></li>
2206                     </ul>
2207                  </li>
2208                  <li><em>Part2</em>&nbsp;&nbsp;<a href="#rfc.xref.Part2.1">1.4.2</a>, <a href="#rfc.xref.Part2.2">2</a>, <a href="#rfc.xref.Part2.3">2.2</a>, <a href="#rfc.xref.Part2.4"></a>, <a href="#rfc.xref.Part2.5">2.3.2</a>, <a href="#rfc.xref.Part2.6">2.6</a>, <a href="#rfc.xref.Part2.7">3.3</a>, <a href="#Part2"><b>8.1</b></a><ul>
2209                        <li><em>Section 2.1.1</em>&nbsp;&nbsp;<a href="#rfc.xref.Part2.3">2.2</a>, <a href="#rfc.xref.Part2.6">2.6</a></li>
2210                        <li><em>Section 4</em>&nbsp;&nbsp;<a href="#rfc.xref.Part2.4"></a></li>
2211                        <li><em>Section 5.1</em>&nbsp;&nbsp;<a href="#rfc.xref.Part2.1">1.4.2</a>, <a href="#rfc.xref.Part2.7">3.3</a></li>
2212                        <li><em>Section 9.10</em>&nbsp;&nbsp;<a href="#rfc.xref.Part2.5">2.3.2</a></li>
2213                     </ul>
2214                  </li>
2215                  <li><em>Part4</em>&nbsp;&nbsp;<a href="#rfc.xref.Part4.1">1.2</a>, <a href="#rfc.xref.Part4.2">1.2</a>, <a href="#rfc.xref.Part4.3">1.2</a>, <a href="#rfc.xref.Part4.4"></a>, <a href="#rfc.xref.Part4.5">2.4</a>, <a href="#Part4"><b>8.1</b></a><ul>
2216                        <li><em>Section 2.1</em>&nbsp;&nbsp;<a href="#rfc.xref.Part4.1">1.2</a></li>
2217                        <li><em>Section 2.2</em>&nbsp;&nbsp;<a href="#rfc.xref.Part4.4"></a></li>
2218                        <li><em>Section 2.2.2</em>&nbsp;&nbsp;<a href="#rfc.xref.Part4.3">1.2</a></li>
2219                        <li><em>Section 2.3</em>&nbsp;&nbsp;<a href="#rfc.xref.Part4.2">1.2</a></li>
2220                     </ul>
2221                  </li>
2222                  <li><em>Part5</em>&nbsp;&nbsp;<a href="#rfc.xref.Part5.1">2.1</a>, <a href="#rfc.xref.Part5.2">2.9</a>, <a href="#rfc.xref.Part5.3">2.9</a>, <a href="#Part5"><b>8.1</b></a><ul>
2223                        <li><em>Section 4.2</em>&nbsp;&nbsp;<a href="#rfc.xref.Part5.3">2.9</a></li>
2224                     </ul>
2225                  </li>
2226                  <li><em>Part7</em>&nbsp;&nbsp;<a href="#rfc.xref.Part7.1">2.1</a>, <a href="#rfc.xref.Part7.2">2.7</a>, <a href="#Part7"><b>8.1</b></a><ul>
2227                        <li><em>Section 4.1</em>&nbsp;&nbsp;<a href="#rfc.xref.Part7.1">2.1</a>, <a href="#rfc.xref.Part7.2">2.7</a></li>
2228                     </ul>
2229                  </li>
2230                  <li>Pragma header field&nbsp;&nbsp;<a href="#rfc.xref.header.pragma.1">2.2</a>, <a href="#rfc.xref.header.pragma.2">3.2</a>, <a href="#rfc.iref.p.5"><b>3.4</b></a>, <a href="#rfc.xref.header.pragma.3">5.3</a></li>
2231                  <li>private&nbsp;&nbsp;
2232                     <ul>
2233                        <li>Cache Directive&nbsp;&nbsp;<a href="#rfc.iref.p.3"><b></b></a></li>
2234                     </ul>
2235                  </li>
2236                  <li>private cache&nbsp;&nbsp;<a href="#rfc.iref.p.1">1.2</a></li>
2237                  <li>proxy-revalidate&nbsp;&nbsp;
2238                     <ul>
2239                        <li>Cache Directive&nbsp;&nbsp;<a href="#rfc.iref.p.4"><b></b></a></li>
2240                     </ul>
2241                  </li>
2242                  <li>public&nbsp;&nbsp;
2243                     <ul>
2244                        <li>Cache Directive&nbsp;&nbsp;<a href="#rfc.iref.p.2"><b></b></a></li>
2245                     </ul>
2246                  </li>
2247               </ul>
2248            </li>
2249            <li><a id="rfc.index.R" href="#rfc.index.R"><b>R</b></a><ul>
2250                  <li><em>RFC1305</em>&nbsp;&nbsp;<a href="#rfc.xref.RFC1305.1">2.2</a>, <a href="#rfc.xref.RFC1305.2">2.3.2</a>, <a href="#RFC1305"><b>8.2</b></a></li>
2251                  <li><em>RFC2119</em>&nbsp;&nbsp;<a href="#rfc.xref.RFC2119.1">1.3</a>, <a href="#RFC2119"><b>8.1</b></a></li>
2252                  <li><em>RFC2616</em>&nbsp;&nbsp;<a href="#rfc.xref.RFC2616.1"></a>, <a href="#RFC2616"><b>8.2</b></a><ul>
2253                        <li><em>Section 13.9</em>&nbsp;&nbsp;<a href="#rfc.xref.RFC2616.1"></a></li>
2254                     </ul>
2255                  </li>
2256                  <li><em>RFC3864</em>&nbsp;&nbsp;<a href="#rfc.xref.RFC3864.1">5.3</a>, <a href="#RFC3864"><b>8.2</b></a></li>
2257                  <li><em>RFC5226</em>&nbsp;&nbsp;<a href="#rfc.xref.RFC5226.1">3.2.3</a>, <a href="#rfc.xref.RFC5226.2">3.6.8</a>, <a href="#RFC5226"><b>8.2</b></a><ul>
2258                        <li><em>Section 4.1</em>&nbsp;&nbsp;<a href="#rfc.xref.RFC5226.1">3.2.3</a>, <a href="#rfc.xref.RFC5226.2">3.6.8</a></li>
2259                     </ul>
2260                  </li>
2261                  <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>
2262                        <li><em>Appendix B.1</em>&nbsp;&nbsp;<a href="#rfc.xref.RFC5234.2">1.4</a></li>
2263                     </ul>
2264                  </li>
2265                  <li><em>RFC5861</em>&nbsp;&nbsp;<a href="#rfc.xref.RFC5861.1">5.1</a>, <a href="#rfc.xref.RFC5861.2">5.1</a>, <a href="#RFC5861"><b>8.2</b></a><ul>
2266                        <li><em>Section 3</em>&nbsp;&nbsp;<a href="#rfc.xref.RFC5861.2">5.1</a></li>
2267                        <li><em>Section 4</em>&nbsp;&nbsp;<a href="#rfc.xref.RFC5861.1">5.1</a></li>
2268                     </ul>
2269                  </li>
2270               </ul>
2271            </li>
2272            <li><a id="rfc.index.S" href="#rfc.index.S"><b>S</b></a><ul>
2273                  <li>s-maxage&nbsp;&nbsp;
2274                     <ul>
2275                        <li>Cache Directive&nbsp;&nbsp;<a href="#rfc.iref.s.4"><b></b></a></li>
2276                     </ul>
2277                  </li>
2278                  <li>shared cache&nbsp;&nbsp;<a href="#rfc.iref.s.1">1.2</a></li>
2279                  <li>stale&nbsp;&nbsp;<a href="#rfc.iref.s.2">1.2</a></li>
2280                  <li>strong validator&nbsp;&nbsp;<a href="#rfc.iref.s.3">1.2</a></li>
2281               </ul>
2282            </li>
2283            <li><a id="rfc.index.V" href="#rfc.index.V"><b>V</b></a><ul>
2284                  <li>validator&nbsp;&nbsp;<a href="#rfc.iref.v.1">1.2</a><ul>
2285                        <li>strong&nbsp;&nbsp;<a href="#rfc.iref.v.2">1.2</a></li>
2286                     </ul>
2287                  </li>
2288                  <li>Vary header field&nbsp;&nbsp;<a href="#rfc.xref.header.vary.1">2.8</a>, <a href="#rfc.iref.v.3"><b>3.5</b></a>, <a href="#rfc.xref.header.vary.2">5.3</a></li>
2289               </ul>
2290            </li>
2291            <li><a id="rfc.index.W" href="#rfc.index.W"><b>W</b></a><ul>
2292                  <li>Warn Codes&nbsp;&nbsp;
2293                     <ul>
2294                        <li>110 Response is Stale&nbsp;&nbsp;<a href="#rfc.iref.w.2"><b>3.6.1</b></a>, <a href="#rfc.xref.warn.110.1">5.2</a></li>
2295                        <li>111 Revalidation Failed&nbsp;&nbsp;<a href="#rfc.iref.w.3"><b>3.6.2</b></a>, <a href="#rfc.xref.warn.111.1">5.2</a></li>
2296                        <li>112 Disconnected Operation&nbsp;&nbsp;<a href="#rfc.iref.w.4"><b>3.6.3</b></a>, <a href="#rfc.xref.warn.112.1">5.2</a></li>
2297                        <li>113 Heuristic Expiration&nbsp;&nbsp;<a href="#rfc.iref.w.5"><b>3.6.4</b></a>, <a href="#rfc.xref.warn.113.1">5.2</a></li>
2298                        <li>199 Miscellaneous Warning&nbsp;&nbsp;<a href="#rfc.iref.w.6"><b>3.6.5</b></a>, <a href="#rfc.xref.warn.199.1">5.2</a></li>
2299                        <li>214 Transformation Applied&nbsp;&nbsp;<a href="#rfc.iref.w.7"><b>3.6.6</b></a>, <a href="#rfc.xref.warn.214.1">5.2</a></li>
2300                        <li>299 Miscellaneous Persistent Warning&nbsp;&nbsp;<a href="#rfc.iref.w.8"><b>3.6.7</b></a>, <a href="#rfc.xref.warn.299.1">5.2</a></li>
2301                     </ul>
2302                  </li>
2303                  <li>Warning header field&nbsp;&nbsp;<a href="#rfc.xref.header.warning.1">2.3.3</a>, <a href="#rfc.xref.header.warning.2">2.4.1</a>, <a href="#rfc.xref.header.warning.3">2.5</a>, <a href="#rfc.xref.header.warning.4">2.9</a>, <a href="#rfc.iref.w.1"><b>3.6</b></a>, <a href="#rfc.xref.header.warning.5">5.3</a>, <a href="#rfc.xref.header.warning.6">A</a></li>
2304               </ul>
2305            </li>
2306         </ul>
2307      </div>
2308   </body>
Note: See TracBrowser for help on using the repository browser.