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

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

improve introduction of list operator (see #542)

  • Property svn:eol-style set to native
  • Property svn:mime-type set to text/html;charset=utf-8
File size: 195.4 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>Hypertext Transfer Protocol (HTTP/1.1): 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: cambria, helvetica, arial, sans-serif;
109  font-size: 11pt;
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: 130%;
135  line-height: 21pt;
136  page-break-after: avoid;
137} {
139  page-break-before: always;
141h2 {
142  font-size: 120%;
143  line-height: 15pt;
144  page-break-after: avoid;
146h3 {
147  font-size: 110%;
148  page-break-after: avoid;
150h4, h5, h6 {
151  page-break-after: avoid;
153h1 a, h2 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: 10pt;
254  margin-top: .5em;
257table.header {
258  border-spacing: 1px;
259  width: 95%;
260  font-size: 11pt;
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  margin-left: 0em;
295ul.toc li li {
296  line-height: normal;
297  font-weight: normal;
298  font-size: 10pt;
299  margin-left: 0em;
301li.excluded {
302  font-size: 0pt;
304ul p {
305  margin-left: 0em;
307.title, .filename, h1, h2, h3, h4 {
308  font-family: candara, helvetica, arial, sans-serif;
310samp, tt, code, pre {
311  font: consolas, monospace;
313ul.ind, ul.ind ul {
314  list-style: none;
315  margin-left: 1.5em;
316  padding-left: 0em;
317  page-break-before: avoid;
319ul.ind li {
320  font-weight: bold;
321  line-height: 200%;
322  margin-left: 0em;
324ul.ind li li {
325  font-weight: normal;
326  line-height: 150%;
327  margin-left: 0em;
329.avoidbreak {
330  page-break-inside: avoid;
332.bcp14 {
333  font-style: normal;
334  text-transform: lowercase;
335  font-variant: small-caps;
337.comment {
338  background-color: yellow;
339} {
341  text-align: center;
343.error {
344  color: red;
345  font-style: italic;
346  font-weight: bold;
348.figure {
349  font-weight: bold;
350  text-align: center;
351  font-size: 10pt;
353.filename {
354  color: #333333;
355  font-size: 75%;
356  font-weight: bold;
357  line-height: 21pt;
358  text-align: center;
360.fn {
361  font-weight: bold;
363.left {
364  text-align: left;
366.right {
367  text-align: right;
369.title {
370  color: green;
371  font-size: 150%;
372  line-height: 18pt;
373  font-weight: bold;
374  text-align: center;
375  margin-top: 36pt;
377.warning {
378  font-size: 130%;
379  background-color: yellow;
380} {
382  position: fixed;
383  bottom: 1%;
384  right: 1%;
385  padding: 3px 5px;
386  color: white;
387  border-radius: 5px;
388  background: #a00000;
389  border: 1px solid silver;
391.fbbutton {
392  margin-left: 1em;
393  color: #303030;
394  font-size: small;
395  font-weight: normal;
396  background: #d0d000;
397  padding: 1px 4px;
398  border: 1px solid silver;
399  border-radius: 5px;
402@media print {
403  .noprint {
404    display: none;
405  }
407  a {
408    color: black;
409    text-decoration: none;
410  }
412  table.header {
413    width: 90%;
414  }
416  td.header {
417    width: 50%;
418    color: black;
419    background-color: white;
420    vertical-align: top;
421    font-size: 110%;
422  }
424  ul.toc a:nth-child(2)::after {
425    content: leader('.') target-counter(attr(href), page);
426  }
428  ul.ind li li a {
429    content: target-counter(attr(href), page);
430  }
432  .print2col {
433    column-count: 2;
434    -moz-column-count: 2;
435    column-fill: auto;
436  }
439@page {
440  @top-left {
441       content: "Internet-Draft";
442  }
443  @top-right {
444       content: "December 2013";
445  }
446  @top-center {
447       content: "HTTP/1.1 Caching";
448  }
449  @bottom-left {
450       content: "Fielding, et al.";
451  }
452  @bottom-center {
453       content: "Expires June 30, 2014";
454  }
455  @bottom-right {
456       content: "[Page " counter(page) "]";
457  }
460@page:first {
461    @top-left {
462      content: normal;
463    }
464    @top-right {
465      content: normal;
466    }
467    @top-center {
468      content: normal;
469    }
471</style><link rel="Contents" href="#rfc.toc">
472      <link rel="Author" href="#rfc.authors">
473      <link rel="Copyright" href="#rfc.copyrightnotice">
474      <link rel="Index" href="#rfc.index">
475      <link rel="Chapter" title="1 Introduction" href="#rfc.section.1">
476      <link rel="Chapter" title="2 Overview of Cache Operation" href="#rfc.section.2">
477      <link rel="Chapter" title="3 Storing Responses in Caches" href="#rfc.section.3">
478      <link rel="Chapter" title="4 Constructing Responses from Caches" href="#rfc.section.4">
479      <link rel="Chapter" title="5 Header Field Definitions" href="#rfc.section.5">
480      <link rel="Chapter" title="6 History Lists" href="#rfc.section.6">
481      <link rel="Chapter" title="7 IANA Considerations" href="#rfc.section.7">
482      <link rel="Chapter" title="8 Security Considerations" href="#rfc.section.8">
483      <link rel="Chapter" title="9 Acknowledgments" href="#rfc.section.9">
484      <link rel="Chapter" href="#rfc.section.10" title="10 References">
485      <link rel="Appendix" title="A Changes from RFC 2616" href="#rfc.section.A">
486      <link rel="Appendix" title="B Imported ABNF" href="#rfc.section.B">
487      <link rel="Appendix" title="C Collected ABNF" href="#rfc.section.C">
488      <link rel="Appendix" title="D Change Log (to be removed by RFC Editor before publication)" href="#rfc.section.D">
489      <link href="p5-range.html" rel="prev">
490      <link href="p7-auth.html" rel="next">
491      <meta name="generator" content=", Revision 1.611, 2013/11/27 12:23:51, XSLT vendor: SAXON 8.9 from Saxonica">
492      <link rel="schema.dct" href="">
493      <meta name="dct.creator" content="Fielding, R.">
494      <meta name="dct.creator" content="Nottingham, M.">
495      <meta name="dct.creator" content="Reschke, J. F.">
496      <meta name="dct.identifier" content="urn:ietf:id:draft-ietf-httpbis-p6-cache-latest">
497      <meta name="dct.issued" scheme="ISO8601" content="2013-12-27">
498      <meta name="dct.replaces" content="urn:ietf:rfc:2616">
499      <meta name="dct.abstract" content="The Hypertext Transfer Protocol (HTTP) is an application-level protocol for distributed, collaborative, hypertext information systems. This document defines HTTP caches and the associated header fields that control cache behavior or indicate cacheable response messages.">
500      <meta name="description" content="The Hypertext Transfer Protocol (HTTP) is an application-level protocol for distributed, collaborative, hypertext information systems. This document defines HTTP caches and the associated header fields that control cache behavior or indicate cacheable response messages.">
501   </head>
502   <body onload="init();">
503      <table class="header">
504         <tbody>
505            <tr>
506               <td class="left">HTTPbis Working Group</td>
507               <td class="right">R. Fielding, Editor</td>
508            </tr>
509            <tr>
510               <td class="left">Internet-Draft</td>
511               <td class="right">Adobe</td>
512            </tr>
513            <tr>
514               <td class="left">Obsoletes: <a href="">2616</a> (if approved)
515               </td>
516               <td class="right">M. Nottingham, Editor</td>
517            </tr>
518            <tr>
519               <td class="left">Intended status: Standards Track</td>
520               <td class="right">Akamai</td>
521            </tr>
522            <tr>
523               <td class="left">Expires: June 30, 2014</td>
524               <td class="right">J. Reschke, Editor</td>
525            </tr>
526            <tr>
527               <td class="left"></td>
528               <td class="right">greenbytes</td>
529            </tr>
530            <tr>
531               <td class="left"></td>
532               <td class="right">December 27, 2013</td>
533            </tr>
534         </tbody>
535      </table>
536      <p class="title">Hypertext Transfer Protocol (HTTP/1.1): Caching<br><span class="filename">draft-ietf-httpbis-p6-cache-latest</span></p>
537      <h1 id="rfc.abstract"><a href="#rfc.abstract">Abstract</a></h1>
538      <p>The Hypertext Transfer Protocol (HTTP) is an application-level protocol for distributed, collaborative, hypertext information
539         systems. This document defines HTTP caches and the associated header fields that control cache behavior or indicate cacheable
540         response messages.
541      </p>
542      <h1 id="rfc.note.1"><a href="#rfc.note.1">Editorial Note (To be removed by RFC Editor)</a></h1>
543      <p>Discussion of this draft takes place on the HTTPBIS working group mailing list (, which is archived at &lt;<a href=""></a>&gt;.
544      </p>
545      <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;.
546      </p>
547      <p>The changes in this draft are summarized in <a href="#changes.since.25" title="Since draft-ietf-httpbis-p6-cache-25">Appendix&nbsp;D.2</a>.
548      </p>
549      <div id="rfc.status">
550         <h1><a href="#rfc.status">Status of This Memo</a></h1>
551         <p>This Internet-Draft is submitted in full conformance with the provisions of BCP 78 and BCP 79.</p>
552         <p>Internet-Drafts are working documents of the Internet Engineering Task Force (IETF). Note that other groups may also distribute
553            working documents as Internet-Drafts. The list of current Internet-Drafts is at <a href=""></a>.
554         </p>
555         <p>Internet-Drafts are draft documents valid for a maximum of six months and may be updated, replaced, or obsoleted by other
556            documents at any time. It is inappropriate to use Internet-Drafts as reference material or to cite them other than as “work
557            in progress”.
558         </p>
559         <p>This Internet-Draft will expire on June 30, 2014.</p>
560      </div>
561      <div id="rfc.copyrightnotice">
562         <h1><a href="#rfc.copyrightnotice">Copyright Notice</a></h1>
563         <p>Copyright © 2013 IETF Trust and the persons identified as the document authors. All rights reserved.</p>
564         <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
565            and restrictions with respect to this document. Code Components extracted from this document must include Simplified BSD License
566            text as described in Section 4.e of the Trust Legal Provisions and are provided without warranty as described in the Simplified
567            BSD License.
568         </p>
569         <p>This document may contain material from IETF Documents or IETF Contributions published or made publicly available before November
570            10, 2008. The person(s) controlling the copyright in some of this material may not have granted the IETF Trust the right to
571            allow modifications of such material outside the IETF Standards Process. Without obtaining an adequate license from the person(s)
572            controlling the copyright in such materials, this document may not be modified outside the IETF Standards Process, and derivative
573            works of it may not be created outside the IETF Standards Process, except to format it for publication as an RFC or to translate
574            it into languages other than English.
575         </p>
576      </div>
577      <hr class="noprint">
578      <h1 class="np" id="rfc.toc"><a href="#rfc.toc">Table of Contents</a></h1>
579      <ul class="toc">
580         <li><a href="#rfc.section.1">1.</a>&nbsp;&nbsp;&nbsp;<a href="#caching">Introduction</a><ul>
581               <li><a href="#rfc.section.1.1">1.1</a>&nbsp;&nbsp;&nbsp;<a href="#conformance">Conformance and Error Handling</a></li>
582               <li><a href="#rfc.section.1.2">1.2</a>&nbsp;&nbsp;&nbsp;<a href="#notation">Syntax Notation</a><ul>
583                     <li><a href="#rfc.section.1.2.1">1.2.1</a>&nbsp;&nbsp;&nbsp;<a href="#delta-seconds">Delta Seconds</a></li>
584                  </ul>
585               </li>
586            </ul>
587         </li>
588         <li><a href="#rfc.section.2">2.</a>&nbsp;&nbsp;&nbsp;<a href="#caching.overview">Overview of Cache Operation</a></li>
589         <li><a href="#rfc.section.3">3.</a>&nbsp;&nbsp;&nbsp;<a href="#response.cacheability">Storing Responses in Caches</a><ul>
590               <li><a href="#rfc.section.3.1">3.1</a>&nbsp;&nbsp;&nbsp;<a href="#incomplete.responses">Storing Incomplete Responses</a></li>
591               <li><a href="#rfc.section.3.2">3.2</a>&nbsp;&nbsp;&nbsp;<a href="#caching.authenticated.responses">Storing Responses to Authenticated Requests</a></li>
592               <li><a href="#rfc.section.3.3">3.3</a>&nbsp;&nbsp;&nbsp;<a href="#combining.responses">Combining Partial Content</a></li>
593            </ul>
594         </li>
595         <li><a href="#rfc.section.4">4.</a>&nbsp;&nbsp;&nbsp;<a href="#constructing.responses.from.caches">Constructing Responses from Caches</a><ul>
596               <li><a href="#rfc.section.4.1">4.1</a>&nbsp;&nbsp;&nbsp;<a href="#caching.negotiated.responses">Calculating Secondary Keys with Vary</a></li>
597               <li><a href="#rfc.section.4.2">4.2</a>&nbsp;&nbsp;&nbsp;<a href="#expiration.model">Freshness</a><ul>
598                     <li><a href="#rfc.section.4.2.1">4.2.1</a>&nbsp;&nbsp;&nbsp;<a href="#calculating.freshness.lifetime">Calculating Freshness Lifetime</a></li>
599                     <li><a href="#rfc.section.4.2.2">4.2.2</a>&nbsp;&nbsp;&nbsp;<a href="#heuristic.freshness">Calculating Heuristic Freshness</a></li>
600                     <li><a href="#rfc.section.4.2.3">4.2.3</a>&nbsp;&nbsp;&nbsp;<a href="#age.calculations">Calculating Age</a></li>
601                     <li><a href="#rfc.section.4.2.4">4.2.4</a>&nbsp;&nbsp;&nbsp;<a href="#serving.stale.responses">Serving Stale Responses</a></li>
602                  </ul>
603               </li>
604               <li><a href="#rfc.section.4.3">4.3</a>&nbsp;&nbsp;&nbsp;<a href="#validation.model">Validation</a><ul>
605                     <li><a href="#rfc.section.4.3.1">4.3.1</a>&nbsp;&nbsp;&nbsp;<a href="#validation.sent">Sending a Validation Request</a></li>
606                     <li><a href="#rfc.section.4.3.2">4.3.2</a>&nbsp;&nbsp;&nbsp;<a href="#validation.received">Handling a Received Validation Request</a></li>
607                     <li><a href="#rfc.section.4.3.3">4.3.3</a>&nbsp;&nbsp;&nbsp;<a href="#validation.response">Handling a Validation Response</a></li>
608                     <li><a href="#rfc.section.4.3.4">4.3.4</a>&nbsp;&nbsp;&nbsp;<a href="#freshening.responses">Freshening Stored Responses upon Validation</a></li>
609                     <li><a href="#rfc.section.4.3.5">4.3.5</a>&nbsp;&nbsp;&nbsp;<a href="#head.effects">Freshening Responses via HEAD</a></li>
610                  </ul>
611               </li>
612               <li><a href="#rfc.section.4.4">4.4</a>&nbsp;&nbsp;&nbsp;<a href="#invalidation">Invalidation</a></li>
613            </ul>
614         </li>
615         <li><a href="#rfc.section.5">5.</a>&nbsp;&nbsp;&nbsp;<a href="#header.field.definitions">Header Field Definitions</a><ul>
616               <li><a href="#rfc.section.5.1">5.1</a>&nbsp;&nbsp;&nbsp;<a href="#header.age">Age</a></li>
617               <li><a href="#rfc.section.5.2">5.2</a>&nbsp;&nbsp;&nbsp;<a href="#header.cache-control">Cache-Control</a><ul>
618                     <li><a href="#rfc.section.5.2.1">5.2.1</a>&nbsp;&nbsp;&nbsp;<a href="#cache-request-directive">Request Cache-Control Directives</a><ul>
619                           <li><a href="#rfc.section."></a>&nbsp;&nbsp;&nbsp;<a href="#cache-request-directive.max-age">max-age</a></li>
620                           <li><a href="#rfc.section."></a>&nbsp;&nbsp;&nbsp;<a href="#cache-request-directive.max-stale">max-stale</a></li>
621                           <li><a href="#rfc.section."></a>&nbsp;&nbsp;&nbsp;<a href="#cache-request-directive.min-fresh">min-fresh</a></li>
622                           <li><a href="#rfc.section."></a>&nbsp;&nbsp;&nbsp;<a href="">no-cache</a></li>
623                           <li><a href="#rfc.section."></a>&nbsp;&nbsp;&nbsp;<a href="">no-store</a></li>
624                           <li><a href="#rfc.section."></a>&nbsp;&nbsp;&nbsp;<a href="">no-transform</a></li>
625                           <li><a href="#rfc.section."></a>&nbsp;&nbsp;&nbsp;<a href="#cache-request-directive.only-if-cached">only-if-cached</a></li>
626                        </ul>
627                     </li>
628                     <li><a href="#rfc.section.5.2.2">5.2.2</a>&nbsp;&nbsp;&nbsp;<a href="#cache-response-directive">Response Cache-Control Directives</a><ul>
629                           <li><a href="#rfc.section."></a>&nbsp;&nbsp;&nbsp;<a href="#cache-response-directive.must-revalidate">must-revalidate</a></li>
630                           <li><a href="#rfc.section."></a>&nbsp;&nbsp;&nbsp;<a href="">no-cache</a></li>
631                           <li><a href="#rfc.section."></a>&nbsp;&nbsp;&nbsp;<a href="">no-store</a></li>
632                           <li><a href="#rfc.section."></a>&nbsp;&nbsp;&nbsp;<a href="">no-transform</a></li>
633                           <li><a href="#rfc.section."></a>&nbsp;&nbsp;&nbsp;<a href="#cache-response-directive.public">public</a></li>
634                           <li><a href="#rfc.section."></a>&nbsp;&nbsp;&nbsp;<a href="#cache-response-directive.private">private</a></li>
635                           <li><a href="#rfc.section."></a>&nbsp;&nbsp;&nbsp;<a href="#cache-response-directive.proxy-revalidate">proxy-revalidate</a></li>
636                           <li><a href="#rfc.section."></a>&nbsp;&nbsp;&nbsp;<a href="#cache-response-directive.max-age">max-age</a></li>
637                           <li><a href="#rfc.section."></a>&nbsp;&nbsp;&nbsp;<a href="#cache-response-directive.s-maxage">s-maxage</a></li>
638                        </ul>
639                     </li>
640                     <li><a href="#rfc.section.5.2.3">5.2.3</a>&nbsp;&nbsp;&nbsp;<a href="#cache.control.extensions">Cache Control Extensions</a></li>
641                  </ul>
642               </li>
643               <li><a href="#rfc.section.5.3">5.3</a>&nbsp;&nbsp;&nbsp;<a href="#header.expires">Expires</a></li>
644               <li><a href="#rfc.section.5.4">5.4</a>&nbsp;&nbsp;&nbsp;<a href="#header.pragma">Pragma</a></li>
645               <li><a href="#rfc.section.5.5">5.5</a>&nbsp;&nbsp;&nbsp;<a href="#header.warning">Warning</a><ul>
646                     <li><a href="#rfc.section.5.5.1">5.5.1</a>&nbsp;&nbsp;&nbsp;<a href="#warn.110">Warning: 110 - "Response is Stale"</a></li>
647                     <li><a href="#rfc.section.5.5.2">5.5.2</a>&nbsp;&nbsp;&nbsp;<a href="#warn.111">Warning: 111 - "Revalidation Failed"</a></li>
648                     <li><a href="#rfc.section.5.5.3">5.5.3</a>&nbsp;&nbsp;&nbsp;<a href="#warn.112">Warning: 112 - "Disconnected Operation"</a></li>
649                     <li><a href="#rfc.section.5.5.4">5.5.4</a>&nbsp;&nbsp;&nbsp;<a href="#warn.113">Warning: 113 - "Heuristic Expiration"</a></li>
650                     <li><a href="#rfc.section.5.5.5">5.5.5</a>&nbsp;&nbsp;&nbsp;<a href="#warn.199">Warning: 199 - "Miscellaneous Warning"</a></li>
651                     <li><a href="#rfc.section.5.5.6">5.5.6</a>&nbsp;&nbsp;&nbsp;<a href="#warn.214">Warning: 214 - "Transformation Applied"</a></li>
652                     <li><a href="#rfc.section.5.5.7">5.5.7</a>&nbsp;&nbsp;&nbsp;<a href="#warn.299">Warning: 299 - "Miscellaneous Persistent Warning"</a></li>
653                  </ul>
654               </li>
655            </ul>
656         </li>
657         <li><a href="#rfc.section.6">6.</a>&nbsp;&nbsp;&nbsp;<a href="#history.lists">History Lists</a></li>
658         <li><a href="#rfc.section.7">7.</a>&nbsp;&nbsp;&nbsp;<a href="#iana.considerations">IANA Considerations</a><ul>
659               <li><a href="#rfc.section.7.1">7.1</a>&nbsp;&nbsp;&nbsp;<a href="#cache.directive.registry">Cache Directive Registry</a><ul>
660                     <li><a href="#rfc.section.7.1.1">7.1.1</a>&nbsp;&nbsp;&nbsp;<a href="#cache.directive.registry.procedure">Procedure</a></li>
661                     <li><a href="#rfc.section.7.1.2">7.1.2</a>&nbsp;&nbsp;&nbsp;<a href="#cache.directive.considerations">Considerations for New Cache Control Directives</a></li>
662                     <li><a href="#rfc.section.7.1.3">7.1.3</a>&nbsp;&nbsp;&nbsp;<a href="#cache.directive.registration">Registrations</a></li>
663                  </ul>
664               </li>
665               <li><a href="#rfc.section.7.2">7.2</a>&nbsp;&nbsp;&nbsp;<a href="#warn.code.registry">Warn Code Registry</a><ul>
666                     <li><a href="#rfc.section.7.2.1">7.2.1</a>&nbsp;&nbsp;&nbsp;<a href="#warn.code.registry.procedure">Procedure</a></li>
667                     <li><a href="#rfc.section.7.2.2">7.2.2</a>&nbsp;&nbsp;&nbsp;<a href="#warn.code.registration">Registrations</a></li>
668                  </ul>
669               </li>
670               <li><a href="#rfc.section.7.3">7.3</a>&nbsp;&nbsp;&nbsp;<a href="#header.field.registration">Header Field Registration</a></li>
671            </ul>
672         </li>
673         <li><a href="#rfc.section.8">8.</a>&nbsp;&nbsp;&nbsp;<a href="#security.considerations">Security Considerations</a></li>
674         <li><a href="#rfc.section.9">9.</a>&nbsp;&nbsp;&nbsp;<a href="#acks">Acknowledgments</a></li>
675         <li><a href="#rfc.section.10">10.</a>&nbsp;&nbsp;&nbsp;<a href="#rfc.references">References</a><ul>
676               <li><a href="#rfc.section.10.1">10.1</a>&nbsp;&nbsp;&nbsp;<a href="#rfc.references.1">Normative References</a></li>
677               <li><a href="#rfc.section.10.2">10.2</a>&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 href="#rfc.section.A">A.</a>&nbsp;&nbsp;&nbsp;<a href="#changes.from.rfc.2616">Changes from RFC 2616</a></li>
682         <li><a href="#rfc.section.B">B.</a>&nbsp;&nbsp;&nbsp;<a href="#imported.abnf">Imported ABNF</a></li>
683         <li><a href="#rfc.section.C">C.</a>&nbsp;&nbsp;&nbsp;<a href="#collected.abnf">Collected ABNF</a></li>
684         <li><a href="#rfc.section.D">D.</a>&nbsp;&nbsp;&nbsp;<a href="#change.log">Change Log (to be removed by RFC Editor before publication)</a><ul>
685               <li><a href="#rfc.section.D.1">D.1</a>&nbsp;&nbsp;&nbsp;<a href="#changes.since.24">Since draft-ietf-httpbis-p6-cache-24</a></li>
686               <li><a href="#rfc.section.D.2">D.2</a>&nbsp;&nbsp;&nbsp;<a href="#changes.since.25">Since draft-ietf-httpbis-p6-cache-25</a></li>
687            </ul>
688         </li>
689         <li><a href="#rfc.index">Index</a></li>
690      </ul>
691      <div id="caching">
692         <h1 id="rfc.section.1" class="np"><a href="#rfc.section.1">1.</a>&nbsp;<a href="#caching">Introduction</a></h1>
693         <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.
694            This document defines aspects of HTTP/1.1 related to caching and reusing response messages.
695         </p>
696         <div id="rfc.iref.c.1"></div>
697         <p id="rfc.section.1.p.2">An HTTP <dfn>cache</dfn> is a local store of response messages and the subsystem that controls storage, retrieval, and deletion of messages in it.
698            A cache stores cacheable responses in order to reduce the response time and network bandwidth consumption on future, equivalent
699            requests. 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.
700         </p>
701         <div id="rfc.iref.s.1"></div>
702         <div id="rfc.iref.p.1"></div>
703         <div id="shared.and.private.caches">
704            <p id="rfc.section.1.p.3">A <dfn>shared cache</dfn> is a cache that stores responses to be reused by more than one user; shared caches are usually (but not always) deployed as
705               a part of an intermediary. A <dfn>private cache</dfn>, in contrast, is dedicated to a single user; often, they are deployed as a component of a user agent.
706            </p>
707         </div>
708         <p id="rfc.section.1.p.4">The goal of caching in HTTP/1.1 is to significantly improve performance by reusing a prior response message to satisfy a current
709            request. A stored response is considered "fresh", as defined in <a href="#expiration.model" title="Freshness">Section&nbsp;4.2</a>, if the response can be reused without "validation" (checking with the origin server to see if the cached response remains
710            valid for this request). A fresh response can therefore reduce both latency and network overhead each time it is reused. When
711            a cached response is not fresh, it might still be reusable if it can be freshened by validation (<a href="#validation.model" title="Validation">Section&nbsp;4.3</a>) or if the origin is unavailable (<a href="#serving.stale.responses" title="Serving Stale Responses">Section&nbsp;4.2.4</a>).
712         </p>
713         <div id="conformance">
714            <h2 id="rfc.section.1.1"><a href="#rfc.section.1.1">1.1</a>&nbsp;<a href="#conformance">Conformance and Error Handling</a></h2>
715            <p id="rfc.section.1.1.p.1">The key words "MUST", "MUST NOT", "REQUIRED", "SHALL", "SHALL NOT", "SHOULD", "SHOULD NOT", "RECOMMENDED", "MAY", and "OPTIONAL"
716               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>.
717            </p>
718            <p id="rfc.section.1.1.p.2">Conformance criteria and considerations regarding error handling are defined in <a href="p1-messaging.html#conformance" title="Conformance and Error Handling">Section 2.5</a> of <a href="#Part1" id="rfc.xref.Part1.1"><cite title="Hypertext Transfer Protocol (HTTP/1.1): Message Syntax and Routing">[Part1]</cite></a>.
719            </p>
720         </div>
721         <div id="notation">
722            <h2 id="rfc.section.1.2"><a href="#rfc.section.1.2">1.2</a>&nbsp;<a href="#notation">Syntax Notation</a></h2>
723            <p id="rfc.section.1.2.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 an extension defined in <a href="p1-messaging.html#abnf.extension" title="ABNF list extension: #rule">Section 7</a> of <a href="#Part1" id="rfc.xref.Part1.2"><cite title="Hypertext Transfer Protocol (HTTP/1.1): Message Syntax and Routing">[Part1]</cite></a> that adds compact support for comma-separated lists with the addition of a '#' operator, similar to the '*' operator. <a href="#imported.abnf" title="Imported ABNF">Appendix&nbsp;B</a> describes rules imported from other documents. <a href="#collected.abnf" title="Collected ABNF">Appendix&nbsp;C</a> shows the collected ABNF with the rules using the list operator expanded to standard ABNF notation.
724            </p>
725            <div id="delta-seconds">
726               <h3 id="rfc.section.1.2.1"><a href="#rfc.section.1.2.1">1.2.1</a>&nbsp;<a href="#delta-seconds">Delta Seconds</a></h3>
727               <p id="rfc.section.1.2.1.p.1">The delta-seconds rule specifies a non-negative integer, representing time in seconds.</p>
728               <div id="rfc.figure.u.1"></div><pre class="inline"><span id="rfc.iref.g.1"></span>  <a href="#delta-seconds" class="smpl">delta-seconds</a>  = 1*<a href="#imported.abnf" class="smpl">DIGIT</a>
729</pre><p id="rfc.section.1.2.1.p.3">A recipient parsing a delta-seconds value and converting it to binary form ought to use an arithmetic type of at least 31
730                  bits of non-negative integer range. If a cache receives a delta-seconds value greater than the greatest integer it can represent,
731                  or if any of its subsequent calculations overflows, the cache <em class="bcp14">MUST</em> consider the value to be either 2147483648 (2<sup>31</sup>) or the greatest positive integer it can conveniently represent.
732               </p>
733               <div class="note" id="rfc.section.1.2.1.p.4">
734                  <p><b>Note:</b> The value 2147483648 is here for historical reasons, effectively represents infinity (over 68 years), and does not need to
735                     be stored in binary form; an implementation could produce it as a canned string if any overflow occurs, even if the calculations
736                     are performed with an arithmetic type incapable of directly representing that number. What matters here is that an overflow
737                     be detected and not treated as a negative value in later calculations.
738                  </p>
739               </div>
740            </div>
741         </div>
742      </div>
743      <div id="caching.overview">
744         <div id="rfc.iref.c.2"></div>
745         <div id="rfc.iref.c.3"></div>
746         <h1 id="rfc.section.2"><a href="#rfc.section.2">2.</a>&nbsp;<a href="#caching.overview">Overview of Cache Operation</a></h1>
747         <p id="rfc.section.2.p.1">Proper cache operation preserves the semantics of HTTP transfers (<a href="#Part2" id="rfc.xref.Part2.1"><cite title="Hypertext Transfer Protocol (HTTP/1.1): Semantics and Content">[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
748            no requirement or local configuration prevents it. Therefore, HTTP cache requirements are focused on preventing a cache from
749            either storing a non-reusable response or reusing a stored response inappropriately, rather than mandating that caches always
750            store and reuse particular responses.
751         </p>
752         <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
753            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 to a GET request, which contains a representation of the resource identified by the request target (<a href="p2-semantics.html#GET" title="GET">Section 4.3.1</a> of <a href="#Part2" id="rfc.xref.Part2.2"><cite title="Hypertext Transfer Protocol (HTTP/1.1): Semantics and Content">[Part2]</cite></a>). However, it is also possible to cache permanent redirects, 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 methods other than GET if the method's definition allows such caching and defines something suitable for
754            use as a cache key.
755         </p>
756         <div id="rfc.iref.c.4"></div>
757         <p id="rfc.section.2.p.3">The primary <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
758            responses to GET, many caches simply decline other methods and use only the URI as the primary cache key.
759         </p>
760         <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
761            by a secondary key for the values of the original request's selecting header fields (<a href="#caching.negotiated.responses" title="Calculating Secondary Keys with Vary">Section&nbsp;4.1</a>).
762         </p>
763      </div>
764      <div id="response.cacheability">
765         <h1 id="rfc.section.3"><a href="#rfc.section.3">3.</a>&nbsp;<a href="#response.cacheability">Storing Responses in Caches</a></h1>
766         <p id="rfc.section.3.p.1">A cache <em class="bcp14">MUST NOT</em> store a response to any request, unless:
767         </p>
768         <ul>
769            <li>The request method is understood by the cache and defined as being cacheable, and</li>
770            <li>the response status code is understood by the cache, and</li>
771            <li>the "no-store" cache directive (see <a href="#header.cache-control" id="rfc.xref.header.cache-control.1" title="Cache-Control">Section&nbsp;5.2</a>) does not appear in request or response header fields, and
772            </li>
773            <li>the "private" response directive (see <a href="#cache-response-directive.private" title="private">Section&nbsp;</a>) does not appear in the response, if the cache is shared, and
774            </li>
775            <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="Hypertext Transfer Protocol (HTTP/1.1): 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="Storing Responses to Authenticated Requests">Section&nbsp;3.2</a>), and
776            </li>
777            <li>the response either:
778               <ul>
779                  <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;5.3</a>), or
780                  </li>
781                  <li>contains a max-age response directive (see <a href="#cache-response-directive.max-age" title="max-age">Section&nbsp;</a>), or
782                  </li>
783                  <li>contains a s-maxage response directive (see <a href="#cache-response-directive.s-maxage" title="s-maxage">Section&nbsp;</a>) and the cache is shared, or
784                  </li>
785                  <li>contains a Cache Control Extension (see <a href="#cache.control.extensions" title="Cache Control Extensions">Section&nbsp;5.2.3</a>) that allows it to be cached, or
786                  </li>
787                  <li>has a status code that is defined as cacheable by default (see <a href="#heuristic.freshness" title="Calculating Heuristic Freshness">Section&nbsp;4.2.2</a>), or
788                  </li>
789                  <li>contains a public response directive (see <a href="#cache-response-directive.public" title="public">Section&nbsp;</a>).
790                  </li>
791               </ul>
792            </li>
793         </ul>
794         <p id="rfc.section.3.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;5.2.3</a>.
795         </p>
796         <p id="rfc.section.3.p.3">In this context, a cache has "understood" a request method or a response status code if it recognizes it and implements all
797            specified caching-related behavior.
798         </p>
799         <p id="rfc.section.3.p.4">Note that, in normal operation, some caches will not store a response that has neither a cache validator nor an explicit expiration
800            time, as such responses are not usually useful to store. However, caches are not prohibited from storing such responses.
801         </p>
802         <div id="incomplete.responses">
803            <h2 id="rfc.section.3.1"><a href="#rfc.section.3.1">3.1</a>&nbsp;<a href="#incomplete.responses">Storing Incomplete Responses</a></h2>
804            <p id="rfc.section.3.1.p.1">A response message is considered complete when all of the octets indicated by the message framing (<a href="#Part1" id="rfc.xref.Part1.3"><cite title="Hypertext Transfer Protocol (HTTP/1.1): Message Syntax and Routing">[Part1]</cite></a>) are received prior to the connection being closed. If the request method is GET, the response status code is <a href="p2-semantics.html#status.200" class="smpl">200 (OK)</a>, and the entire response header section 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
805                  (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#header.range" 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.
806            </p>
807            <p id="rfc.section.3.1.p.2">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="Hypertext Transfer Protocol (HTTP/1.1): Range Requests">[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;3.3</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
808               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.
809            </p>
810         </div>
811         <div id="caching.authenticated.responses">
812            <h2 id="rfc.section.3.2"><a href="#rfc.section.3.2">3.2</a>&nbsp;<a href="#caching.authenticated.responses">Storing Responses to Authenticated Requests</a></h2>
813            <p id="rfc.section.3.2.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="Hypertext Transfer Protocol (HTTP/1.1): 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.
814            </p>
815            <p id="rfc.section.3.2.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;5.2.2</a>) have such an effect: must-revalidate, public, s-maxage.
816            </p>
817            <p id="rfc.section.3.2.p.3">Note that cached responses that contain the "must-revalidate" and/or "s-maxage" response directives are not allowed to be
818               served stale (<a href="#serving.stale.responses" title="Serving Stale Responses">Section&nbsp;4.2.4</a>) by shared caches. In particular, a response with either "max-age=0, must-revalidate" or "s-maxage=0" cannot be used to satisfy
819               a subsequent request without revalidating it on the origin server.
820            </p>
821         </div>
822         <div id="combining.responses">
823            <h2 id="rfc.section.3.3"><a href="#rfc.section.3.3">3.3</a>&nbsp;<a href="#combining.responses">Combining Partial Content</a></h2>
824            <p id="rfc.section.3.3.p.1">A response might transfer only a partial representation if the connection closed prematurely or if the request used one or
825               more Range specifiers (<a href="#Part5" id="rfc.xref.Part5.2"><cite title="Hypertext Transfer Protocol (HTTP/1.1): Range Requests">[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
826               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.3</a> of <a href="#Part5" id="rfc.xref.Part5.3"><cite title="Hypertext Transfer Protocol (HTTP/1.1): Range Requests">[Part5]</cite></a>.
827            </p>
828            <p id="rfc.section.3.3.p.2">When combining the new response with one or more stored responses, a cache <em class="bcp14">MUST</em>:
829            </p>
830            <ul>
831               <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.1" title="Warning">Section&nbsp;5.5</a>);
832               </li>
833               <li>retain any <a href="#header.warning" class="smpl">Warning</a> header fields in the stored response with warn-code 2xx; and,
834               </li>
835               <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.
836               </li>
837            </ul>
838         </div>
839      </div>
840      <div id="constructing.responses.from.caches">
841         <h1 id="rfc.section.4"><a href="#rfc.section.4">4.</a>&nbsp;<a href="#constructing.responses.from.caches">Constructing Responses from Caches</a></h1>
842         <p id="rfc.section.4.p.1">When presented with a request, a cache <em class="bcp14">MUST NOT</em> reuse a stored response, unless:
843         </p>
844         <ul>
845            <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.4"><cite title="Hypertext Transfer Protocol (HTTP/1.1): Message Syntax and Routing">[Part1]</cite></a>) and that of the stored response match, and
846            </li>
847            <li>the request method associated with the stored response allows it to be used for the presented request, and</li>
848            <li>selecting header fields nominated by the stored response (if any) match those presented (see <a href="#caching.negotiated.responses" title="Calculating Secondary Keys with Vary">Section&nbsp;4.1</a>), and
849            </li>
850            <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;5.4</a>), nor the no-cache cache directive (<a href="#cache-request-directive" title="Request Cache-Control Directives">Section&nbsp;5.2.1</a>), unless the stored response is successfully validated (<a href="#validation.model" title="Validation">Section&nbsp;4.3</a>), and
851            </li>
852            <li>the stored response does not contain the no-cache cache directive (<a href="" title="no-cache">Section&nbsp;</a>), unless it is successfully validated (<a href="#validation.model" title="Validation">Section&nbsp;4.3</a>), and
853            </li>
854            <li>the stored response is either:
855               <ul>
856                  <li>fresh (see <a href="#expiration.model" title="Freshness">Section&nbsp;4.2</a>), or
857                  </li>
858                  <li>allowed to be served stale (see <a href="#serving.stale.responses" title="Serving Stale Responses">Section&nbsp;4.2.4</a>), or
859                  </li>
860                  <li>successfully validated (see <a href="#validation.model" title="Validation">Section&nbsp;4.3</a>).
861                  </li>
862               </ul>
863            </li>
864         </ul>
865         <p id="rfc.section.4.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;5.2.3</a>.
866         </p>
867         <p id="rfc.section.4.p.3">When a stored response is used to satisfy a request without validation, a cache <em class="bcp14">MUST</em> generate an <a href="#header.age" class="smpl">Age</a> header field (<a href="#header.age" id="rfc.xref.header.age.1" title="Age">Section&nbsp;5.1</a>), replacing any present in the response with a value equal to the stored response's current_age; see <a href="#age.calculations" title="Calculating Age">Section&nbsp;4.2.3</a>.
868         </p>
869         <p id="rfc.section.4.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 4.2.1</a> of <a href="#Part2" id="rfc.xref.Part2.3"><cite title="Hypertext Transfer Protocol (HTTP/1.1): Semantics and Content">[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
870            and having received a corresponding response.
871         </p>
872         <p id="rfc.section.4.p.5">Also, note that unsafe requests might invalidate already stored responses; see <a href="#invalidation" title="Invalidation">Section&nbsp;4.4</a>.
873         </p>
874         <p id="rfc.section.4.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 <a href="" class="smpl">Date</a> header field). It can also forward the request with "Cache-Control: max-age=0" or "Cache-Control: no-cache" to disambiguate
875            which response to use.
876         </p>
877         <p id="rfc.section.4.p.7">A cache that does not have a clock available <em class="bcp14">MUST NOT</em> use stored responses without revalidating them upon every use.
878         </p>
879         <div id="caching.negotiated.responses">
880            <h2 id="rfc.section.4.1"><a href="#rfc.section.4.1">4.1</a>&nbsp;<a href="#caching.negotiated.responses">Calculating Secondary Keys with Vary</a></h2>
881            <p id="rfc.section.4.1.p.1">When a cache receives a request that can be satisfied by a stored response that has a <a href="p2-semantics.html#header.vary" class="smpl">Vary</a> header field (<a href="p2-semantics.html#header.vary" title="Vary">Section 7.1.4</a> of <a href="#Part2" id="rfc.xref.Part2.4"><cite title="Hypertext Transfer Protocol (HTTP/1.1): Semantics and Content">[Part2]</cite></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
882               request (i.e., that associated with the stored response), and the presented request.
883            </p>
884            <p id="rfc.section.4.1.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
885               to those in the second request by applying any of the following:
886            </p>
887            <ul>
888               <li>adding or removing whitespace, where allowed in the header field's syntax</li>
889               <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.5"><cite title="Hypertext Transfer Protocol (HTTP/1.1): Message Syntax and Routing">[Part1]</cite></a>)
890               </li>
891               <li>normalizing both header field values in a way that is known to have identical semantics, according to the header field's specification
892                  (e.g., re-ordering field values when order is not significant; case-normalization, where values are defined to be case-insensitive)
893               </li>
894            </ul>
895            <p id="rfc.section.4.1.p.3">If (after any normalization that might take place) a header field is absent from a request, it can only match another request
896               if it is also absent there.
897            </p>
898            <p id="rfc.section.4.1.p.4">A <a href="p2-semantics.html#header.vary" class="smpl">Vary</a> header field-value of "*" always fails to match.
899            </p>
900            <p id="rfc.section.4.1.p.5">The stored response with matching selecting header fields is known as the selected response.</p>
901            <p id="rfc.section.4.1.p.6">If multiple selected responses are available (potentially including responses without a Vary header field), the cache will
902               need to choose one to use. When a selecting header field has a known mechanism for doing so (e.g., qvalues on <a href="p2-semantics.html#header.accept" class="smpl">Accept</a> and similar request header fields), that mechanism <em class="bcp14">MAY</em> be used to select preferred responses; of the remainder, the most recent response (as determined by the <a href="" class="smpl">Date</a> header field) is used, as per <a href="#constructing.responses.from.caches" title="Constructing Responses from Caches">Section&nbsp;4</a>.
903            </p>
904            <p id="rfc.section.4.1.p.7">If no selected response is available, the cache cannot satisfy the presented request. Typically, it is forwarded to the origin
905               server in a (possibly conditional; see <a href="#validation.model" title="Validation">Section&nbsp;4.3</a>) request.
906            </p>
907         </div>
908         <div id="expiration.model">
909            <div id="rfc.iref.f.1"></div>
910            <div id="rfc.iref.s.2"></div>
911            <h2 id="rfc.section.4.2"><a href="#rfc.section.4.2">4.2</a>&nbsp;<a href="#expiration.model">Freshness</a></h2>
912            <p id="rfc.section.4.2.p.1">A <dfn>fresh</dfn> response is one whose age has not yet exceeded its freshness lifetime. Conversely, a <dfn>stale</dfn> response is one where it has.
913            </p>
914            <div id="rfc.iref.f.2"></div>
915            <div id="rfc.iref.e.1"></div>
916            <div id="rfc.iref.h.1"></div>
917            <p id="rfc.section.4.2.p.2">A response's <dfn>freshness lifetime</dfn> is the length of time between its generation by the origin server and its expiration time. An <dfn>explicit expiration time</dfn> is the time at which the origin server intends that a stored response can no longer be used by a cache without further validation,
918               whereas a <dfn>heuristic expiration time</dfn> is assigned by a cache when no explicit expiration time is available.
919            </p>
920            <div id="rfc.iref.a.1"></div>
921            <p id="rfc.section.4.2.p.3">A response's <dfn>age</dfn> is the time that has passed since it was generated by, or successfully validated with, the origin server.
922            </p>
923            <p id="rfc.section.4.2.p.4">When a response is "fresh" in the cache, it can be used to satisfy subsequent requests without contacting the origin server,
924               thereby improving efficiency.
925            </p>
926            <p id="rfc.section.4.2.p.5">The primary mechanism for determining freshness is for an origin server to provide an explicit expiration time in the future,
927               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;5.3</a>) or the max-age response directive (<a href="#cache-response-directive.max-age" title="max-age">Section&nbsp;</a>). Generally, origin servers will assign future explicit expiration times to responses in the belief that the representation
928               is not likely to change in a semantically significant way before the expiration time is reached.
929            </p>
930            <p id="rfc.section.4.2.p.6">If an origin server wishes to force a cache to validate every request, it can assign an explicit expiration time in the past
931               to indicate that the response is already stale. Compliant caches will normally validate a stale cached response before reusing
932               it for subsequent requests (see <a href="#serving.stale.responses" title="Serving Stale Responses">Section&nbsp;4.2.4</a>).
933            </p>
934            <p id="rfc.section.4.2.p.7">Since origin servers do not always provide explicit expiration times, caches are also allowed to use a heuristic to determine
935               an expiration time under certain circumstances (see <a href="#heuristic.freshness" title="Calculating Heuristic Freshness">Section&nbsp;4.2.2</a>).
936            </p>
937            <div id="rfc.figure.u.2"></div>
938            <p>The calculation to determine if a response is fresh is:</p><pre class="text">   response_is_fresh = (freshness_lifetime &gt; current_age)
939</pre><p id="rfc.section.4.2.p.9">freshness_lifetime is defined in <a href="#calculating.freshness.lifetime" title="Calculating Freshness Lifetime">Section&nbsp;4.2.1</a>; current_age is defined in <a href="#age.calculations" title="Calculating Age">Section&nbsp;4.2.3</a>.
940            </p>
941            <p id="rfc.section.4.2.p.10">Clients can send the max-age or min-fresh cache directives in a request to constrain or relax freshness calculations for the
942               corresponding response (<a href="#cache-request-directive" title="Request Cache-Control Directives">Section&nbsp;5.2.1</a>).
943            </p>
944            <p id="rfc.section.4.2.p.11">When calculating freshness, to avoid common problems in date parsing:</p>
945            <p id="rfc.section.4.2.p.12"></p>
946            <ul>
947               <li>Although all date formats are specified to be case-sensitive, a cache recipient <em class="bcp14">SHOULD</em> match day, week, and timezone names case-insensitively.
948               </li>
949               <li>If a cache recipient's internal implementation of time has less resolution than the value of an HTTP-date, the recipient <em class="bcp14">MUST</em> internally represent a parsed <a href="#header.expires" class="smpl">Expires</a> date as the nearest time equal to or earlier than the received value.
950               </li>
951               <li>A cache recipient <em class="bcp14">MUST NOT</em> allow local time zones to influence the calculation or comparison of an age or expiration time.
952               </li>
953               <li>A cache recipient <em class="bcp14">SHOULD</em> consider a date with a zone abbreviation other than GMT or UTC to be invalid for calculating expiration.
954               </li>
955            </ul>
956            <p id="rfc.section.4.2.p.13">Note that freshness applies only to cache operation; it cannot be used to force a user agent to refresh its display or reload
957               a resource. See <a href="#history.lists" title="History Lists">Section&nbsp;6</a> for an explanation of the difference between caches and history mechanisms.
958            </p>
959            <div id="calculating.freshness.lifetime">
960               <h3 id="rfc.section.4.2.1"><a href="#rfc.section.4.2.1">4.2.1</a>&nbsp;<a href="#calculating.freshness.lifetime">Calculating Freshness Lifetime</a></h3>
961               <p id="rfc.section.4.2.1.p.1">A cache can calculate the freshness lifetime (denoted as freshness_lifetime) of a response by using the first match of: </p>
962               <ul>
963                  <li>If the cache is shared and the s-maxage response directive (<a href="#cache-response-directive.s-maxage" title="s-maxage">Section&nbsp;</a>) is present, use its value, or
964                  </li>
965                  <li>If the max-age response directive (<a href="#cache-response-directive.max-age" title="max-age">Section&nbsp;</a>) is present, use its value, or
966                  </li>
967                  <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;5.3</a>) is present, use its value minus the value of the <a href="" class="smpl">Date</a> response header field, or
968                  </li>
969                  <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;4.2.2</a>.
970                  </li>
971               </ul>
972               <p id="rfc.section.4.2.1.p.2">Note that this calculation is not vulnerable to clock skew, since all of the information comes from the origin server.</p>
973               <p id="rfc.section.4.2.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), the directive's value is considered invalid. Caches are encouraged
974                  to consider responses that have invalid freshness information to be stale.
975               </p>
976            </div>
977            <div id="heuristic.freshness">
978               <h3 id="rfc.section.4.2.2"><a href="#rfc.section.4.2.2">4.2.2</a>&nbsp;<a href="#heuristic.freshness">Calculating Heuristic Freshness</a></h3>
979               <p id="rfc.section.4.2.2.p.1">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
980                  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
981                  constraints on their results.
982               </p>
983               <p id="rfc.section.4.2.2.p.2">A cache <em class="bcp14">MUST NOT</em> use heuristics to determine freshness when an explicit expiration time is present in the stored response. Because of the requirements
984                  in <a href="#response.cacheability" title="Storing Responses in Caches">Section&nbsp;3</a>, this means that, effectively, heuristics can only be used on responses without explicit freshness whose status codes are
985                  defined as cacheable by default (see <a href="" title="Overview of Status Codes">Section 6.1</a> of <a href="#Part2" id="rfc.xref.Part2.5"><cite title="Hypertext Transfer Protocol (HTTP/1.1): Semantics and Content">[Part2]</cite></a>), and those responses without explicit freshness that have been marked as explicitly cacheable (e.g., with a "public" response
986                  directive).
987               </p>
988               <p id="rfc.section.4.2.2.p.3">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.1"><cite title="Hypertext Transfer Protocol (HTTP/1.1): 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
989                  time. A typical setting of this fraction might be 10%.
990               </p>
991               <p id="rfc.section.4.2.2.p.4">When a heuristic is used to calculate freshness lifetime, a cache <em class="bcp14">SHOULD</em> generate a <a href="#header.warning" class="smpl">Warning</a> header field with a 113 warn-code (see <a href="#warn.113" id="rfc.xref.warn.113.1" title="Warning: 113 - &#34;Heuristic Expiration&#34;">Section&nbsp;5.5.4</a>) in the response if its current_age is more than 24 hours and such a warning is not already present.
992               </p>
993               <div class="note" id="rfc.section.4.2.2.p.5">
994                  <p><b>Note:</b> <a href="">Section 13.9</a> of <a href="#RFC2616" id="rfc.xref.RFC2616.1"><cite title="Hypertext Transfer Protocol -- HTTP/1.1">[RFC2616]</cite></a> prohibited caches from calculating heuristic freshness for URIs with query components (i.e., those containing '?'). In practice,
995                     this has not been widely implemented. Therefore, origin servers are encouraged to send explicit directives (e.g., Cache-Control:
996                     no-cache) if they wish to preclude caching.
997                  </p>
998               </div>
999            </div>
1000            <div id="age.calculations">
1001               <h3 id="rfc.section.4.2.3"><a href="#rfc.section.4.2.3">4.2.3</a>&nbsp;<a href="#age.calculations">Calculating Age</a></h3>
1002               <p id="rfc.section.4.2.3.p.1">The <a href="#header.age" class="smpl">Age</a> header field is used to convey an estimated age of the response message when obtained from a cache. The Age field value is
1003                  the cache's estimate of the number of seconds since the response was generated or validated by the origin server. In essence,
1004                  the Age value is the sum of the time that the response has been resident in each of the caches along the path from the origin
1005                  server, plus the amount of time it has been in transit along network paths.
1006               </p>
1007               <p id="rfc.section.4.2.3.p.2">The following data is used for the age calculation:</p>
1008               <p id="rfc.section.4.2.3.p.3"><dfn>age_value</dfn>
1009               </p>
1010               <ul class="empty">
1011                  <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;5.1</a>), in a form appropriate for arithmetic operation; or 0, if not available.
1012                  </li>
1013               </ul>
1014               <p id="rfc.section.4.2.3.p.4"><dfn>date_value</dfn>
1015               </p>
1016               <ul class="empty">
1017                  <li>The term "date_value" denotes the value of the Date header field, in a form appropriate for arithmetic operations. See <a href="" title="Date">Section</a> of <a href="#Part2" id="rfc.xref.Part2.6"><cite title="Hypertext Transfer Protocol (HTTP/1.1): Semantics and Content">[Part2]</cite></a> for the definition of the Date header field, and for requirements regarding responses without it.
1018                  </li>
1019               </ul>
1020               <p id="rfc.section.4.2.3.p.5"><dfn>now</dfn>
1021               </p>
1022               <ul class="empty">
1023                  <li>The term "now" means "the current value of the clock at the host performing the calculation". A host ought to use NTP (<a href="#RFC5905" id="rfc.xref.RFC5905.1"><cite title="Network Time Protocol Version 4: Protocol and Algorithms Specification">[RFC5905]</cite></a>) or some similar protocol to synchronize its clocks to Coordinated Universal Time.
1024                  </li>
1025               </ul>
1026               <p id="rfc.section.4.2.3.p.6"><dfn>request_time</dfn>
1027               </p>
1028               <ul class="empty">
1029                  <li>The current value of the clock at the host at the time the request resulting in the stored response was made.</li>
1030               </ul>
1031               <p id="rfc.section.4.2.3.p.7"><dfn>response_time</dfn>
1032               </p>
1033               <ul class="empty">
1034                  <li>The current value of the clock at the host at the time the response was received.</li>
1035               </ul>
1036               <p id="rfc.section.4.2.3.p.8">A response's age can be calculated in two entirely independent ways: </p>
1037               <ol>
1038                  <li>the "apparent_age": response_time minus date_value, if the local clock is reasonably well synchronized to the origin server's
1039                     clock. If the result is negative, the result is replaced by zero.
1040                  </li>
1041                  <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.
1042                  </li>
1043               </ol>
1044               <div id="rfc.figure.u.3"></div><pre class="text">  apparent_age = max(0, response_time - date_value);
1046  response_delay = response_time - request_time;
1047  corrected_age_value = age_value + response_delay; 
1048</pre><div id="rfc.figure.u.4"></div>
1049               <p>These are combined as</p><pre class="text">  corrected_initial_age = max(apparent_age, corrected_age_value);
1050</pre><p id="rfc.section.4.2.3.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 <a href="p1-messaging.html#header.via" class="smpl">Via</a> header field), in which case the corrected_age_value <em class="bcp14">MAY</em> be used as the corrected_initial_age.
1051               </p>
1052               <p id="rfc.section.4.2.3.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
1053                  was last validated by the origin server to the corrected_initial_age.
1054               </p>
1055               <div id="rfc.figure.u.5"></div><pre class="text">  resident_time = now - response_time;
1056  current_age = corrected_initial_age + resident_time;
1058            <div id="serving.stale.responses">
1059               <h3 id="rfc.section.4.2.4"><a href="#rfc.section.4.2.4">4.2.4</a>&nbsp;<a href="#serving.stale.responses">Serving Stale Responses</a></h3>
1060               <p id="rfc.section.4.2.4.p.1">A "stale" response is one that either has explicit expiry information or is allowed to have heuristic expiry calculated, but
1061                  is not fresh according to the calculations in <a href="#expiration.model" title="Freshness">Section&nbsp;4.2</a>.
1062               </p>
1063               <p id="rfc.section.4.2.4.p.2">A cache <em class="bcp14">MUST NOT</em> generate a stale response if it is prohibited by an explicit in-protocol directive (e.g., by a "no-store" or "no-cache" cache
1064                  directive, a "must-revalidate" cache-response-directive, or an applicable "s-maxage" or "proxy-revalidate" cache-response-directive;
1065                  see <a href="#cache-response-directive" title="Response Cache-Control Directives">Section&nbsp;5.2.2</a>).
1066               </p>
1067               <p id="rfc.section.4.2.4.p.3">A cache <em class="bcp14">MUST NOT</em> send stale responses unless it is disconnected (i.e., it cannot contact the origin server or otherwise find a forward path)
1068                  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;5.2.1</a>).
1069               </p>
1070               <p id="rfc.section.4.2.4.p.4">A cache <em class="bcp14">SHOULD</em> generate a <a href="#header.warning" class="smpl">Warning</a> header field with the 110 warn-code (see <a href="#warn.110" id="rfc.xref.warn.110.1" title="Warning: 110 - &#34;Response is Stale&#34;">Section&nbsp;5.5.1</a>) in stale responses. Likewise, a cache <em class="bcp14">SHOULD</em> generate a 112 warn-code (see <a href="#warn.112" id="rfc.xref.warn.112.1" title="Warning: 112 - &#34;Disconnected Operation&#34;">Section&nbsp;5.5.3</a>) in stale responses if the cache is disconnected.
1071               </p>
1072               <p id="rfc.section.4.2.4.p.5">A cache <em class="bcp14">SHOULD NOT</em> generate a new <a href="#header.warning" class="smpl">Warning</a> header field when forwarding a response that does not have an <a href="#header.age" class="smpl">Age</a> header field, even if the response is already stale. A cache need not validate a response that merely became stale in transit.
1073               </p>
1074            </div>
1075         </div>
1076         <div id="validation.model">
1077            <h2 id="rfc.section.4.3"><a href="#rfc.section.4.3">4.3</a>&nbsp;<a href="#validation.model">Validation</a></h2>
1078            <p id="rfc.section.4.3.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
1079               fresh, or one cannot be selected; see <a href="#caching.negotiated.responses" title="Calculating Secondary Keys with Vary">Section&nbsp;4.1</a>), it can use the conditional request mechanism <a href="#Part4" id="rfc.xref.Part4.2"><cite title="Hypertext Transfer Protocol (HTTP/1.1): Conditional Requests">[Part4]</cite></a> in the forwarded request to give the next inbound server an opportunity to select a valid stored response to use, updating
1080               the stored metadata in the process, or to replace the stored response(s) with a new response. This process is known as "validating"
1081               or "revalidating" the stored response.
1082            </p>
1083            <div id="validation.sent">
1084               <div id="rfc.iref.v.1"></div>
1085               <h3 id="rfc.section.4.3.1"><a href="#rfc.section.4.3.1">4.3.1</a>&nbsp;<a href="#validation.sent">Sending a Validation Request</a></h3>
1086               <p id="rfc.section.4.3.1.p.1">When sending a conditional request for cache validation, a cache sends one or more precondition header fields containing <dfn>validator</dfn> metadata from its stored response(s), which is then compared by recipients to determine whether a stored response is equivalent
1087                  to a current representation of the resource.
1088               </p>
1089               <p id="rfc.section.4.3.1.p.2">One such validator is the timestamp given in 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.3"><cite title="Hypertext Transfer Protocol (HTTP/1.1): Conditional Requests">[Part4]</cite></a>), which can be used in an <a href="p4-conditional.html#header.if-modified-since" class="smpl">If-Modified-Since</a> header field for response validation, or in an <a href="p4-conditional.html#header.if-unmodified-since" class="smpl">If-Unmodified-Since</a> or <a href="p5-range.html#header.if-range" class="smpl">If-Range</a> header field for representation selection (i.e., the client is referring specifically to a previously obtained representation
1090                  with that timestamp).
1091               </p>
1092               <p id="rfc.section.4.3.1.p.3">Another validator is the entity-tag given in an <a href="p4-conditional.html#header.etag" class="smpl">ETag</a> header field (<a href="p4-conditional.html#header.etag" title="ETag">Section 2.3</a> of <a href="#Part4" id="rfc.xref.Part4.4"><cite title="Hypertext Transfer Protocol (HTTP/1.1): Conditional Requests">[Part4]</cite></a>). One or more entity-tags, indicating one or more stored responses, can be used in an <a href="p4-conditional.html#header.if-none-match" class="smpl">If-None-Match</a> header field for response validation, or in an <a href="p4-conditional.html#header.if-match" class="smpl">If-Match</a> or <a href="p5-range.html#header.if-range" class="smpl">If-Range</a> header field for representation selection (i.e., the client is referring specifically to one or more previously obtained representations
1093                  with the listed entity-tags).
1094               </p>
1095            </div>
1096            <div id="validation.received">
1097               <h3 id="rfc.section.4.3.2"><a href="#rfc.section.4.3.2">4.3.2</a>&nbsp;<a href="#validation.received">Handling a Received Validation Request</a></h3>
1098               <p id="rfc.section.4.3.2.p.1">Each client in the request chain may have its own cache, so it is common for a cache at an intermediary to receive conditional
1099                  requests from other (outbound) caches. Likewise, some user agents make use of conditional requests to limit data transfers
1100                  to recently modified representations or to complete the transfer of a partially retrieved representation.
1101               </p>
1102               <p id="rfc.section.4.3.2.p.2">If a cache receives a request that can be satisfied by reusing one of its stored <a href="p2-semantics.html#status.200" class="smpl">200 (OK)</a> or <a href="p5-range.html#status.206" class="smpl">206 (Partial Content)</a> responses, the cache <em class="bcp14">SHOULD</em> evaluate any applicable conditional header field preconditions received in that request with respect to the corresponding
1103                  validators contained within the selected response. A cache <em class="bcp14">MUST NOT</em> evaluate conditional header fields that are only applicable to an origin server, found in a request with semantics that cannot
1104                  be satisfied with a cached response, or applied to a target resource for which it has no stored responses; such preconditions
1105                  are likely intended for some other (inbound) server.
1106               </p>
1107               <p id="rfc.section.4.3.2.p.3">The proper evaluation of conditional requests by a cache depends on the received precondition header fields and their precedence,
1108                  as defined in <a href="p4-conditional.html#precedence" title="Precedence">Section 6</a> of <a href="#Part4" id="rfc.xref.Part4.5"><cite title="Hypertext Transfer Protocol (HTTP/1.1): Conditional Requests">[Part4]</cite></a>. The <a href="p4-conditional.html#header.if-match" class="smpl">If-Match</a> and <a href="p4-conditional.html#header.if-unmodified-since" class="smpl">If-Unmodified-Since</a> conditional header fields are not applicable to a cache.
1109               </p>
1110               <p id="rfc.section.4.3.2.p.4">A request containing an <a href="p4-conditional.html#header.if-none-match" class="smpl">If-None-Match</a> header field (<a href="p4-conditional.html#header.if-none-match" title="If-None-Match">Section 3.2</a> of <a href="#Part4" id="rfc.xref.Part4.6"><cite title="Hypertext Transfer Protocol (HTTP/1.1): Conditional Requests">[Part4]</cite></a>) indicates that the client wants to validate one or more of its own stored responses in comparison to whichever stored response
1111                  is selected by the cache. If the field-value is "*", or if the field-value is a list of entity-tags and at least one of them
1112                  match the entity-tag of the selected stored response, a cache recipient <em class="bcp14">SHOULD</em> generate a <a href="p4-conditional.html#status.304" class="smpl">304 (Not Modified)</a> response (using the metadata of the selected stored response) instead of sending that stored response.
1113               </p>
1114               <p id="rfc.section.4.3.2.p.5">When a cache decides to revalidate its own stored responses for a request that contains an <a href="p4-conditional.html#header.if-none-match" class="smpl">If-None-Match</a> list of entity-tags, the cache <em class="bcp14">MAY</em> combine the received list with a list of entity-tags from its own stored set of responses (fresh or stale) and send the union
1115                  of the two lists as a replacement <a href="p4-conditional.html#header.if-none-match" class="smpl">If-None-Match</a> header field value in the forwarded request. If a stored response contains only partial content, the cache <em class="bcp14">MUST NOT</em> include its entity-tag in the union unless the request is for a range that would be fully satisfied by that partial stored
1116                  response. If the response to the forwarded request is <a href="p4-conditional.html#status.304" class="smpl">304 (Not Modified)</a> and has an ETag header field value with an entity-tag that is not in the client's list, the cache <em class="bcp14">MUST</em> generate a <a href="p2-semantics.html#status.200" class="smpl">200 (OK)</a> response for the client by reusing its corresponding stored response, as updated by the 304 response metadata (<a href="#freshening.responses" title="Freshening Stored Responses upon Validation">Section&nbsp;4.3.4</a>).
1117               </p>
1118               <p id="rfc.section.4.3.2.p.6">If an <a href="p4-conditional.html#header.if-none-match" class="smpl">If-None-Match</a> header field is not present, a request containing an <a href="p4-conditional.html#header.if-modified-since" class="smpl">If-Modified-Since</a> header field (<a href="p4-conditional.html#header.if-modified-since" title="If-Modified-Since">Section 3.3</a> of <a href="#Part4" id="rfc.xref.Part4.7"><cite title="Hypertext Transfer Protocol (HTTP/1.1): Conditional Requests">[Part4]</cite></a>) indicates that the client wants to validate one or more of its own stored responses by modification date. A cache recipient <em class="bcp14">SHOULD</em> generate a <a href="p4-conditional.html#status.304" class="smpl">304 (Not Modified)</a> response (using the metadata of the selected stored response) if one of the following cases is true: 1) the selected stored
1119                  response has a <a href="p4-conditional.html#header.last-modified" class="smpl">Last-Modified</a> field-value that is earlier than or equal to the conditional timestamp; 2) no <a href="p4-conditional.html#header.last-modified" class="smpl">Last-Modified</a> field is present in the selected stored response, but it has a <a href="" class="smpl">Date</a> field-value that is earlier than or equal to the conditional timestamp; or, 3) neither <a href="p4-conditional.html#header.last-modified" class="smpl">Last-Modified</a> nor <a href="" class="smpl">Date</a> is present in the selected stored response, but the cache recorded it as having been received at a time earlier than or equal
1120                  to the conditional timestamp.
1121               </p>
1122               <p id="rfc.section.4.3.2.p.7">A cache that implements partial responses to range requests, as defined in <a href="#Part5" id="rfc.xref.Part5.4"><cite title="Hypertext Transfer Protocol (HTTP/1.1): Range Requests">[Part5]</cite></a>, also needs to evaluate a received <a href="p5-range.html#header.if-range" class="smpl">If-Range</a> header field (<a href="p5-range.html#header.if-range" title="If-Range">Section 3.2</a> of <a href="#Part5" id="rfc.xref.Part5.5"><cite title="Hypertext Transfer Protocol (HTTP/1.1): Range Requests">[Part5]</cite></a>) with respect to its selected stored response.
1123               </p>
1124            </div>
1125            <div id="validation.response">
1126               <h3 id="rfc.section.4.3.3"><a href="#rfc.section.4.3.3">4.3.3</a>&nbsp;<a href="#validation.response">Handling a Validation Response</a></h3>
1127               <p id="rfc.section.4.3.3.p.1">Cache handling of a response to a conditional request is dependent upon its status code:</p>
1128               <p id="rfc.section.4.3.3.p.2"></p>
1129               <ul>
1130                  <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 Stored Responses upon Validation">Section&nbsp;4.3.4</a>.
1131                  </li>
1132                  <li>A full response (i.e., one with a payload body) indicates that none of the stored responses nominated in the conditional request
1133                     is suitable. Instead, the cache <em class="bcp14">MUST</em> use the full response to satisfy the request and <em class="bcp14">MAY</em> replace the stored response(s).
1134                  </li>
1135                  <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
1136                     if the server failed to respond. In the latter case, the cache <em class="bcp14">MAY</em> send a previously stored response (see <a href="#serving.stale.responses" title="Serving Stale Responses">Section&nbsp;4.2.4</a>).
1137                  </li>
1138               </ul>
1139            </div>
1140            <div id="freshening.responses">
1141               <h3 id="rfc.section.4.3.4"><a href="#rfc.section.4.3.4">4.3.4</a>&nbsp;<a href="#freshening.responses">Freshening Stored Responses upon Validation</a></h3>
1142               <p id="rfc.section.4.3.4.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
1143                  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.
1144               </p>
1145               <div id="rfc.iref.s.3"></div>
1146               <p id="rfc.section.4.3.4.p.2">The stored response to update is identified by using the first match (if any) of: </p>
1147               <ul>
1148                  <li>If the new response contains a <dfn>strong validator</dfn> (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.8"><cite title="Hypertext Transfer Protocol (HTTP/1.1): Conditional Requests">[Part4]</cite></a>), then that strong validator identifies the selected representation for update. All of the stored responses with the same
1149                     strong validator are selected. If none of the stored responses contain the same strong validator, then the cache <em class="bcp14">MUST NOT</em> use the new response to update any stored responses.
1150                  </li>
1151                  <li>If the new response contains a weak validator and that validator corresponds to one of the cache's stored responses, then
1152                     the most recent of those matching stored responses is selected for update.
1153                  </li>
1154                  <li>If the new response does not include any form of validator (such as in the case where a client generates an If-Modified-Since
1155                     request from a source other than the Last-Modified response header field), and there is only one stored response, and that
1156                     stored response also lacks a validator, then that stored response is selected for update.
1157                  </li>
1158               </ul>
1159               <p id="rfc.section.4.3.4.p.3">If a stored response is selected for update, the cache <em class="bcp14">MUST</em>:
1160               </p>
1161               <ul>
1162                  <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;5.5</a>);
1163                  </li>
1164                  <li>retain any <a href="#header.warning" class="smpl">Warning</a> header fields in the stored response with warn-code 2xx; and,
1165                  </li>
1166                  <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.
1167                  </li>
1168               </ul>
1169            </div>
1170            <div id="head.effects">
1171               <h3 id="rfc.section.4.3.5"><a href="#rfc.section.4.3.5">4.3.5</a>&nbsp;<a href="#head.effects">Freshening Responses via HEAD</a></h3>
1172               <p id="rfc.section.4.3.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
1173                  a body. This property of HEAD responses can be used to invalidate or update a cached GET response if the more efficient conditional
1174                  GET request mechanism is not available (due to no validators being present in the stored response) or if transmission of the
1175                  representation body is not desired even if it has changed.
1176               </p>
1177               <p id="rfc.section.4.3.5.p.2">When a cache makes an inbound HEAD request for a given request target and receives a <a href="p2-semantics.html#status.200" class="smpl">200 (OK)</a> response, the cache <em class="bcp14">SHOULD</em> update or invalidate each of its stored GET responses that could have been selected for that request (see <a href="#caching.negotiated.responses" title="Calculating Secondary Keys with Vary">Section&nbsp;4.1</a>).
1178               </p>
1179               <p id="rfc.section.4.3.5.p.3">For each of the stored responses that could have been selected, if the stored response and HEAD response have matching values
1180                  for any received validator fields (<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>) and, if the HEAD response has a <a href="p1-messaging.html#header.content-length" class="smpl">Content-Length</a> header field, the value of <a href="p1-messaging.html#header.content-length" class="smpl">Content-Length</a> matches that of the stored response, the cache <em class="bcp14">SHOULD</em> update the stored response as described below; otherwise, the cache <em class="bcp14">SHOULD</em> consider the stored response to be stale.
1181               </p>
1182               <p id="rfc.section.4.3.5.p.4">If a cache updates a stored response with the metadata provided in a HEAD response, the cache <em class="bcp14">MUST</em>:
1183               </p>
1184               <ul>
1185                  <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;5.5</a>);
1186                  </li>
1187                  <li>retain any <a href="#header.warning" class="smpl">Warning</a> header fields in the stored response with warn-code 2xx; and,
1188                  </li>
1189                  <li>use other header fields provided in the HEAD response to replace all instances of the corresponding header fields in the stored
1190                     response and append new header fields to the stored response's header section unless otherwise restricted by the <a href="#header.cache-control" class="smpl">Cache-Control</a> header field.
1191                  </li>
1192               </ul>
1193            </div>
1194         </div>
1195         <div id="invalidation">
1196            <h2 id="rfc.section.4.4"><a href="#rfc.section.4.4">4.4</a>&nbsp;<a href="#invalidation">Invalidation</a></h2>
1197            <p id="rfc.section.4.4.p.1">Because unsafe request methods (<a href="p2-semantics.html#safe.methods" title="Safe Methods">Section 4.2.1</a> of <a href="#Part2" id="rfc.xref.Part2.7"><cite title="Hypertext Transfer Protocol (HTTP/1.1): Semantics and Content">[Part2]</cite></a>) such as PUT, POST or DELETE have the potential for changing state on the origin server, intervening caches can use them
1198               to keep their contents up-to-date.
1199            </p>
1200            <p id="rfc.section.4.4.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.6"><cite title="Hypertext Transfer Protocol (HTTP/1.1): Message Syntax and Routing">[Part1]</cite></a>) as well as the URI(s) in the <a href="p2-semantics.html#header.location" class="smpl">Location</a> and <a href="p2-semantics.html#header.content-location" class="smpl">Content-Location</a> response header fields (if present) when a non-error status code is received in response to an unsafe request method.
1201            </p>
1202            <p id="rfc.section.4.4.p.3">However, a cache <em class="bcp14">MUST NOT</em> invalidate a URI from a <a href="p2-semantics.html#header.location" class="smpl">Location</a> or <a href="p2-semantics.html#header.content-location" class="smpl">Content-Location</a> response header field if the host part of that URI differs from the host 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.7"><cite title="Hypertext Transfer Protocol (HTTP/1.1): Message Syntax and Routing">[Part1]</cite></a>). This helps prevent denial of service attacks.
1203            </p>
1204            <p id="rfc.section.4.4.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.8"><cite title="Hypertext Transfer Protocol (HTTP/1.1): Message Syntax and Routing">[Part1]</cite></a>) when it receives a non-error response to a request with a method whose safety is unknown.
1205            </p>
1206            <p id="rfc.section.4.4.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,
1207               or will mark these as "invalid" and in need of a mandatory validation before they can be sent in response to a subsequent
1208               request.
1209            </p>
1210            <p id="rfc.section.4.4.p.6">Note that this does not guarantee that all appropriate responses are invalidated. For example, a state-changing request might
1211               invalidate responses in the caches it travels through, but relevant responses still might be stored in other caches that it
1212               has not.
1213            </p>
1214         </div>
1215      </div>
1216      <div id="header.field.definitions">
1217         <h1 id="rfc.section.5"><a href="#rfc.section.5">5.</a>&nbsp;<a href="#header.field.definitions">Header Field Definitions</a></h1>
1218         <p id="rfc.section.5.p.1">This section defines the syntax and semantics of HTTP/1.1 header fields related to caching.</p>
1219         <div id="header.age">
1220            <div id="rfc.iref.a.2"></div>
1221            <h2 id="rfc.section.5.1"><a href="#rfc.section.5.1">5.1</a>&nbsp;<a href="#header.age">Age</a></h2>
1222            <p id="rfc.section.5.1.p.1">The "Age" header field conveys the sender's estimate of the amount of time since the response was generated or successfully
1223               validated at the origin server. Age values are calculated as specified in <a href="#age.calculations" title="Calculating Age">Section&nbsp;4.2.3</a>.
1224            </p>
1225            <div id="rfc.figure.u.6"></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>
1226</pre><p id="rfc.section.5.1.p.3">The Age field-value is a non-negative integer, representing time in seconds (see <a href="#delta-seconds" title="Delta Seconds">Section&nbsp;1.2.1</a>).
1227            </p>
1228            <p id="rfc.section.5.1.p.4">The presence of an Age header field implies that the response was not generated or validated by the origin server for this
1229               request. However, lack of an Age header field does not imply the origin was contacted, since the response might have been
1230               received from an HTTP/1.0 cache that does not implement Age.
1231            </p>
1232         </div>
1233         <div id="header.cache-control">
1234            <div id="rfc.iref.c.5"></div>
1235            <h2 id="rfc.section.5.2"><a href="#rfc.section.5.2">5.2</a>&nbsp;<a href="#header.cache-control">Cache-Control</a></h2>
1236            <p id="rfc.section.5.2.p.1">The "Cache-Control" header field is used to specify directives for caches along the request/response chain. Such cache directives
1237               are unidirectional in that the presence of a directive in a request does not imply that the same directive is to be given
1238               in the response.
1239            </p>
1240            <p id="rfc.section.5.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;5.2.3</a> for information about how Cache-Control directives defined elsewhere are handled.
1241            </p>
1242            <div class="note" id="rfc.section.5.2.p.3">
1243               <p><b>Note:</b> Some HTTP/1.0 caches might not implement Cache-Control.
1244               </p>
1245            </div>
1246            <p id="rfc.section.5.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
1247               might be applicable to all recipients along the request/response chain. It is not possible to target a directive to a specific
1248               cache.
1249            </p>
1250            <p id="rfc.section.5.2.p.5">Cache directives are identified by a token, to be compared case-insensitively, and have an optional argument, that can use
1251               both token and quoted-string syntax. For the directives defined below that define arguments, recipients ought to accept both
1252               forms, even if one is documented to be preferred. For any directive not defined by this specification, a recipient <em class="bcp14">MUST</em> accept both forms.
1253            </p>
1254            <div id="rfc.figure.u.7"></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>
1256  <a href="#header.cache-control" class="smpl">cache-directive</a> = <a href="#imported.abnf" class="smpl">token</a> [ "=" ( <a href="#imported.abnf" class="smpl">token</a> / <a href="#imported.abnf" class="smpl">quoted-string</a> ) ]
1257</pre><p id="rfc.section.5.2.p.7">For the cache directives defined below, no argument is defined (nor allowed) unless stated otherwise.</p>
1258            <div id="cache-request-directive">
1259               <h3 id="rfc.section.5.2.1"><a href="#rfc.section.5.2.1">5.2.1</a>&nbsp;<a href="#cache-request-directive">Request Cache-Control Directives</a></h3>
1260               <div id="cache-request-directive.max-age">
1261                  <div id="rfc.iref.m.1"></div>
1262                  <h4 id="rfc.section."><a href="#rfc.section."></a>&nbsp;<a href="#cache-request-directive.max-age">max-age</a></h4>
1263                  <p id="rfc.section.">Argument syntax: </p>
1264                  <ul class="empty">
1265                     <li><a href="#delta-seconds" class="smpl">delta-seconds</a> (see <a href="#delta-seconds" title="Delta Seconds">Section&nbsp;1.2.1</a>)
1266                     </li>
1267                  </ul>
1268                  <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
1269                     specified number of seconds. Unless the max-stale request directive is also present, the client is not willing to accept a
1270                     stale response.
1271                  </p>
1272                  <p id="rfc.section.">This directive uses the token form of the argument syntax; e.g., 'max-age=5', not 'max-age="5"'. A sender <em class="bcp14">SHOULD NOT</em> generate the quoted-string form.
1273                  </p>
1274               </div>
1275               <div id="cache-request-directive.max-stale">
1276                  <div id="rfc.iref.m.2"></div>
1277                  <h4 id="rfc.section."><a href="#rfc.section."></a>&nbsp;<a 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.2.1</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 freshness
1284                     lifetime. If max-stale is assigned a value, then the client is willing to accept a response that has exceeded its freshness
1285                     lifetime by no more than the specified number of seconds. If no value is assigned to max-stale, then the client is willing
1286                     to accept a stale response of any age.
1287                  </p>
1288                  <p id="rfc.section.">This directive uses the token form of the argument syntax; e.g., 'max-stale=10', not 'max-stale="10"'. A sender <em class="bcp14">SHOULD NOT</em> generate the quoted-string form.
1289                  </p>
1290               </div>
1291               <div id="cache-request-directive.min-fresh">
1292                  <div id="rfc.iref.m.3"></div>
1293                  <h4 id="rfc.section."><a href="#rfc.section."></a>&nbsp;<a href="#cache-request-directive.min-fresh">min-fresh</a></h4>
1294                  <p id="rfc.section.">Argument syntax: </p>
1295                  <ul class="empty">
1296                     <li><a href="#delta-seconds" class="smpl">delta-seconds</a> (see <a href="#delta-seconds" title="Delta Seconds">Section&nbsp;1.2.1</a>)
1297                     </li>
1298                  </ul>
1299                  <p id="rfc.section.">The "min-fresh" request directive indicates that the client is willing to accept a response whose freshness lifetime is no
1300                     less than its current age plus the specified time in seconds. That is, the client wants a response that will still be fresh
1301                     for at least the specified number of seconds.
1302                  </p>
1303                  <p id="rfc.section.">This directive uses the token form of the argument syntax; e.g., 'min-fresh=20', not 'min-fresh="20"'. A sender <em class="bcp14">SHOULD NOT</em> generate the quoted-string form.
1304                  </p>
1305               </div>
1306               <div id="">
1307                  <div id="rfc.iref.n.1"></div>
1308                  <h4 id="rfc.section."><a href="#rfc.section."></a>&nbsp;<a href="">no-cache</a></h4>
1309                  <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.
1310                  </p>
1311               </div>
1312               <div id="">
1313                  <div id="rfc.iref.n.2"></div>
1314                  <h4 id="rfc.section."><a href="#rfc.section."></a>&nbsp;<a href="">no-store</a></h4>
1315                  <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.
1316                  </p>
1317                  <p id="rfc.section.">This directive is NOT a reliable or sufficient mechanism for ensuring privacy. In particular, malicious or compromised caches
1318                     might not recognize or obey this directive, and communications networks might be vulnerable to eavesdropping.
1319                  </p>
1320                  <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
1321                     to the already stored response.
1322                  </p>
1323               </div>
1324               <div id="">
1325                  <div id="rfc.iref.n.3"></div>
1326                  <h4 id="rfc.section."><a href="#rfc.section."></a>&nbsp;<a href="">no-transform</a></h4>
1327                  <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> transform the payload, as defined in <a href="p1-messaging.html#message.transformations" title="Transformations">Section 5.7.2</a> of <a href="#Part1" id="rfc.xref.Part1.9"><cite title="Hypertext Transfer Protocol (HTTP/1.1): Message Syntax and Routing">[Part1]</cite></a>.
1328                  </p>
1329               </div>
1330               <div id="cache-request-directive.only-if-cached">
1331                  <div id="rfc.iref.o.1"></div>
1332                  <h4 id="rfc.section."><a href="#rfc.section."></a>&nbsp;<a href="#cache-request-directive.only-if-cached">only-if-cached</a></h4>
1333                  <p id="rfc.section.">The "only-if-cached" request directive indicates that the client only wishes to obtain a stored response. If it receives this
1334                     directive, a cache <em class="bcp14">SHOULD</em> either respond using a stored response that is consistent with the other constraints of the request, or respond with a <a href="p2-semantics.html#status.504" class="smpl">504 (Gateway
1335                        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.
1336                  </p>
1337               </div>
1338            </div>
1339            <div id="cache-response-directive">
1340               <h3 id="rfc.section.5.2.2"><a href="#rfc.section.5.2.2">5.2.2</a>&nbsp;<a href="#cache-response-directive">Response Cache-Control Directives</a></h3>
1341               <div id="cache-response-directive.must-revalidate">
1342                  <div id="rfc.iref.m.4"></div>
1343                  <h4 id="rfc.section."><a href="#rfc.section."></a>&nbsp;<a href="#cache-response-directive.must-revalidate">must-revalidate</a></h4>
1344                  <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.
1345                  </p>
1346                  <p id="rfc.section.">The must-revalidate directive is necessary to support reliable operation for certain protocol features. In all circumstances
1347                     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.
1348                  </p>
1349                  <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
1350                     could result in incorrect operation, such as a silently unexecuted financial transaction.
1351                  </p>
1352               </div>
1353               <div id="">
1354                  <div id="rfc.iref.n.4"></div>
1355                  <h4 id="rfc.section."><a href="#rfc.section."></a>&nbsp;<a href="">no-cache</a></h4>
1356                  <p id="rfc.section.">Argument syntax: </p>
1357                  <ul class="empty">
1358                     <li>#<a href="#imported.abnf" class="smpl">field-name</a>
1359                     </li>
1360                  </ul>
1361                  <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
1362                     prevent a cache from using it to satisfy a request without contacting it, even by caches that have been configured to send
1363                     stale responses.
1364                  </p>
1365                  <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
1366                     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
1367                     server to prevent the re-use of certain header fields in a response, while still allowing caching of the rest of the response.
1368                  </p>
1369                  <p id="rfc.section.">The field-names given are not limited to the set of header fields defined by this specification. Field names are case-insensitive.</p>
1370                  <p id="rfc.section.">This directive uses the quoted-string form of the argument syntax. A sender <em class="bcp14">SHOULD NOT</em> generate the token form (even if quoting appears not to be needed for single-entry lists).
1371                  </p>
1372                  <p id="rfc.section."><b>Note:</b> Although it has been back-ported to many implementations, some HTTP/1.0 caches will not recognize or obey this directive.
1373                     Also, no-cache response directives with field-names are often handled by caches as if an unqualified no-cache directive was
1374                     received; i.e., the special handling for the qualified form is not widely implemented.
1375                  </p>
1376               </div>
1377               <div id="">
1378                  <div id="rfc.iref.n.5"></div>
1379                  <h4 id="rfc.section."><a href="#rfc.section."></a>&nbsp;<a href="">no-store</a></h4>
1380                  <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.
1381                  </p>
1382                  <p id="rfc.section.">This directive is NOT a reliable or sufficient mechanism for ensuring privacy. In particular, malicious or compromised caches
1383                     might not recognize or obey this directive, and communications networks might be vulnerable to eavesdropping.
1384                  </p>
1385               </div>
1386               <div id="">
1387                  <div id="rfc.iref.n.6"></div>
1388                  <h4 id="rfc.section."><a href="#rfc.section."></a>&nbsp;<a href="">no-transform</a></h4>
1389                  <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> transform the payload, as defined in <a href="p1-messaging.html#message.transformations" title="Transformations">Section 5.7.2</a> of <a href="#Part1" id="rfc.xref.Part1.10"><cite title="Hypertext Transfer Protocol (HTTP/1.1): Message Syntax and Routing">[Part1]</cite></a>.
1390                  </p>
1391               </div>
1392               <div id="cache-response-directive.public">
1393                  <div id="rfc.iref.p.2"></div>
1394                  <h4 id="rfc.section."><a href="#rfc.section."></a>&nbsp;<a href="#cache-response-directive.public">public</a></h4>
1395                  <p id="rfc.section.">The "public" response directive indicates that any cache <em class="bcp14">MAY</em> store the response, even if the response would normally be non-cacheable or cacheable only within a private cache. (See <a href="#caching.authenticated.responses" title="Storing Responses to Authenticated Requests">Section&nbsp;3.2</a> for additional details related to the use of public in response to a request containing <a href="p7-auth.html#header.authorization" class="smpl">Authorization</a>, and <a href="#response.cacheability" title="Storing Responses in Caches">Section&nbsp;3</a> for details of how public affects responses that would normally not be stored, due to their status codes not being defined
1396                     as cacheable by default; see <a href="#heuristic.freshness" title="Calculating Heuristic Freshness">Section&nbsp;4.2.2</a>.)
1397                  </p>
1398               </div>
1399               <div id="cache-response-directive.private">
1400                  <div id="rfc.iref.p.3"></div>
1401                  <h4 id="rfc.section."><a href="#rfc.section."></a>&nbsp;<a href="#cache-response-directive.private">private</a></h4>
1402                  <p id="rfc.section.">Argument syntax: </p>
1403                  <ul class="empty">
1404                     <li>#<a href="#imported.abnf" class="smpl">field-name</a>
1405                     </li>
1406                  </ul>
1407                  <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 and reuse it for later requests, even if the response would normally be non-cacheable.
1408                  </p>
1409                  <p id="rfc.section.">If the private response directive specifies one or more field-names, this requirement is limited to the field-values associated
1410                     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.
1411                  </p>
1412                  <p id="rfc.section.">The field-names given are not limited to the set of header fields defined by this specification. Field names are case-insensitive.</p>
1413                  <p id="rfc.section.">This directive uses the quoted-string form of the argument syntax. A sender <em class="bcp14">SHOULD NOT</em> generate the token form (even if quoting appears not to be needed for single-entry lists).
1414                  </p>
1415                  <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
1416                     content. Also, private response directives with field-names are often handled by caches as if an unqualified private directive
1417                     was received; i.e., the special handling for the qualified form is not widely implemented.
1418                  </p>
1419               </div>
1420               <div id="cache-response-directive.proxy-revalidate">
1421                  <div id="rfc.iref.p.4"></div>
1422                  <h4 id="rfc.section."><a href="#rfc.section."></a>&nbsp;<a href="#cache-response-directive.proxy-revalidate">proxy-revalidate</a></h4>
1423                  <p id="rfc.section.">The "proxy-revalidate" response directive has the same meaning as the must-revalidate response directive, except that it does
1424                     not apply to private caches.
1425                  </p>
1426               </div>
1427               <div id="cache-response-directive.max-age">
1428                  <div id="rfc.iref.m.5"></div>
1429                  <h4 id="rfc.section."><a href="#rfc.section."></a>&nbsp;<a href="#cache-response-directive.max-age">max-age</a></h4>
1430                  <p id="rfc.section.">Argument syntax: </p>
1431                  <ul class="empty">
1432                     <li><a href="#delta-seconds" class="smpl">delta-seconds</a> (see <a href="#delta-seconds" title="Delta Seconds">Section&nbsp;1.2.1</a>)
1433                     </li>
1434                  </ul>
1435                  <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
1436                     number of seconds.
1437                  </p>
1438                  <p id="rfc.section.">This directive uses the token form of the argument syntax; e.g., 'max-age=5', not 'max-age="5"'. A sender <em class="bcp14">SHOULD NOT</em> generate the quoted-string form.
1439                  </p>
1440               </div>
1441               <div id="cache-response-directive.s-maxage">
1442                  <div id="rfc.iref.s.4"></div>
1443                  <h4 id="rfc.section."><a href="#rfc.section."></a>&nbsp;<a href="#cache-response-directive.s-maxage">s-maxage</a></h4>
1444                  <p id="rfc.section.">Argument syntax: </p>
1445                  <ul class="empty">
1446                     <li><a href="#delta-seconds" class="smpl">delta-seconds</a> (see <a href="#delta-seconds" title="Delta Seconds">Section&nbsp;1.2.1</a>)
1447                     </li>
1448                  </ul>
1449                  <p id="rfc.section.">The "s-maxage" response directive indicates that, in shared caches, the maximum age specified by this directive overrides
1450                     the 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.
1451                  </p>
1452                  <p id="rfc.section.">This directive uses the token form of the argument syntax; e.g., 's-maxage=10', not 's-maxage="10"'. A sender <em class="bcp14">SHOULD NOT</em> generate the quoted-string form.
1453                  </p>
1454               </div>
1455            </div>
1456            <div id="cache.control.extensions">
1457               <h3 id="rfc.section.5.2.3"><a href="#rfc.section.5.2.3">5.2.3</a>&nbsp;<a href="#cache.control.extensions">Cache Control Extensions</a></h3>
1458               <p id="rfc.section.5.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
1459                  value.
1460               </p>
1461               <p id="rfc.section.5.2.3.p.2">Informational extensions (those that do not require a change in cache behavior) can be added without changing the semantics
1462                  of other directives. Behavioral extensions are designed to work by acting as modifiers to the existing base of cache directives.
1463               </p>
1464               <p id="rfc.section.5.2.3.p.3">Both the new directive and the standard directive are supplied, such that applications that do not understand the new directive
1465                  will default to the behavior specified by the standard directive, and those that understand the new directive will recognize
1466                  it as modifying the requirements associated with the standard directive. In this way, extensions to the cache-control directives
1467                  can be made without requiring changes to the base protocol.
1468               </p>
1469               <p id="rfc.section.5.2.3.p.4">This extension mechanism depends on an HTTP cache obeying all of the cache-control directives defined for its native HTTP-version,
1470                  obeying certain extensions, and ignoring all directives that it does not understand.
1471               </p>
1472               <p id="rfc.section.5.2.3.p.5">For example, consider a hypothetical new response directive called "community" that acts as a modifier to the private directive.
1473                  We define this new directive to mean that, in addition to any private cache, any cache that is shared only by members of the
1474                  community named within its value is allowed to cache the response. An origin server wishing to allow the UCI community to
1475                  use an otherwise private response in their shared cache(s) could do so by including
1476               </p>
1477               <div id="rfc.figure.u.8"></div><pre class="text">  Cache-Control: private, community="UCI"
1478</pre><p id="rfc.section.5.2.3.p.7">A cache seeing this header field will act correctly even if the cache does not understand the community cache-extension, since
1479                  it will also see and understand the private directive and thus default to the safe behavior.
1480               </p>
1481               <p id="rfc.section.5.2.3.p.8">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
1482                  will be combined with standard directives (or the response's default cacheability) such that the cache behavior will remain
1483                  minimally correct even if the cache does not understand the extension(s).
1484               </p>
1485            </div>
1486         </div>
1487         <div id="header.expires">
1488            <div id="rfc.iref.e.2"></div>
1489            <h2 id="rfc.section.5.3"><a href="#rfc.section.5.3">5.3</a>&nbsp;<a href="#header.expires">Expires</a></h2>
1490            <p id="rfc.section.5.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">Section&nbsp;4.2</a> for further discussion of the freshness model.
1491            </p>
1492            <p id="rfc.section.5.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
1493               that time.
1494            </p>
1495            <p id="rfc.section.5.3.p.3">The Expires value is an HTTP-date timestamp, as defined in <a href="" title="Date/Time Formats">Section</a> of <a href="#Part2" id="rfc.xref.Part2.8"><cite title="Hypertext Transfer Protocol (HTTP/1.1): Semantics and Content">[Part2]</cite></a>.
1496            </p>
1497            <div id="rfc.figure.u.9"></div><pre class="inline"><span id="rfc.iref.g.5"></span>  <a href="#header.expires" class="smpl">Expires</a> = <a href="#imported.abnf" class="smpl">HTTP-date</a>
1498</pre><div id="rfc.figure.u.10"></div>
1499            <p>For example</p><pre class="text">  Expires: Thu, 01 Dec 1994 16:00:00 GMT
1500</pre><p id="rfc.section.5.3.p.6">A cache recipient <em class="bcp14">MUST</em> interpret invalid date formats, especially the value "0", as representing a time in the past (i.e., "already expired").
1501            </p>
1502            <p id="rfc.section.5.3.p.7">If a response includes a <a href="#header.cache-control" class="smpl">Cache-Control</a> field with the max-age directive (<a href="#cache-response-directive.max-age" title="max-age">Section&nbsp;</a>), a recipient <em class="bcp14">MUST</em> ignore the Expires field. Likewise, if a response includes the s-maxage directive (<a href="#cache-response-directive.s-maxage" title="s-maxage">Section&nbsp;</a>), a shared cache recipient <em class="bcp14">MUST</em> ignore the Expires field. In both these cases, the value in Expires is only intended for recipients that have not yet implemented
1503               the Cache-Control field.
1504            </p>
1505            <p id="rfc.section.5.3.p.8">An origin server without a clock <em class="bcp14">MUST NOT</em> generate an Expires field unless its value represents a fixed time in the past (always expired) or its value has been associated
1506               with the resource by a system or user with a reliable clock.
1507            </p>
1508            <p id="rfc.section.5.3.p.9">Historically, HTTP required the Expires field-value to be no more than a year in the future. While longer freshness lifetimes
1509               are no longer prohibited, extremely large values have been demonstrated to cause problems (e.g., clock overflows due to use
1510               of 32-bit integers for time values), and many caches will evict a response far sooner than that.
1511            </p>
1512         </div>
1513         <div id="header.pragma">
1514            <div id="rfc.iref.p.5"></div>
1515            <h2 id="rfc.section.5.4"><a href="#rfc.section.5.4">5.4</a>&nbsp;<a href="#header.pragma">Pragma</a></h2>
1516            <p id="rfc.section.5.4.p.1">The "Pragma" header field allows backwards compatibility with HTTP/1.0 caches, so that clients can specify a "no-cache" request
1517               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
1518               ignored.
1519            </p>
1520            <p id="rfc.section.5.4.p.2">In HTTP/1.0, Pragma was defined as an extensible field for implementation-specified directives for recipients. This specification
1521               deprecates such extensions to improve interoperability.
1522            </p>
1523            <div id="rfc.figure.u.11"></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>
1524  <a href="#header.pragma" class="smpl">pragma-directive</a> = "no-cache" / <a href="#header.pragma" class="smpl">extension-pragma</a>
1525  <a href="#header.pragma" class="smpl">extension-pragma</a> = <a href="#imported.abnf" class="smpl">token</a> [ "=" ( <a href="#imported.abnf" class="smpl">token</a> / <a href="#imported.abnf" class="smpl">quoted-string</a> ) ]
1526</pre><p id="rfc.section.5.4.p.4">When the <a href="#header.cache-control" class="smpl">Cache-Control</a> header field is not present in a request, caches <em class="bcp14">MUST</em> consider the no-cache request pragma-directive as having the same effect as if "Cache-Control: no-cache" were present (see <a href="#cache-request-directive" title="Request Cache-Control Directives">Section&nbsp;5.2.1</a>).
1527            </p>
1528            <p id="rfc.section.5.4.p.5">When sending a no-cache request, a client ought to include both the pragma and cache-control directives, unless Cache-Control:
1529               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:
1530            </p>
1531            <div id="rfc.figure.u.12"></div><pre class="text">GET / HTTP/1.1
1533Cache-Control: max-age=30
1534Pragma: no-cache
1536</pre><p id="rfc.section.5.4.p.7">will constrain HTTP/1.1 caches to serve a response no older than 30 seconds, while precluding implementations that do not
1537               understand <a href="#header.cache-control" class="smpl">Cache-Control</a> from serving a cached response.
1538            </p>
1539            <div class="note" id="rfc.section.5.4.p.8">
1540               <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:
1541                  no-cache" in them.
1542               </p>
1543            </div>
1544         </div>
1545         <div id="header.warning">
1546            <div id="rfc.iref.w.1"></div>
1547            <h2 id="rfc.section.5.5"><a href="#rfc.section.5.5">5.5</a>&nbsp;<a href="#header.warning">Warning</a></h2>
1548            <p id="rfc.section.5.5.p.1">The "Warning" header field is used to carry additional information about the status or transformation of a message that might
1549               not be reflected in the status code. This information is typically used to warn about possible incorrectness introduced by
1550               caching operations or transformations applied to the payload of the message.
1551            </p>
1552            <p id="rfc.section.5.5.p.2">Warnings can be used for other purposes, both cache-related and otherwise. The use of a warning, rather than an error status
1553               code, distinguishes these responses from true failures.
1554            </p>
1555            <p id="rfc.section.5.5.p.3">Warning header fields can in general be applied to any message, however some warn-codes are specific to caches and can only
1556               be applied to response messages.
1557            </p>
1558            <div id="rfc.figure.u.13"></div><pre class="inline"><span id="rfc.iref.g.9"></span><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>  <a href="#header.warning" class="smpl">Warning</a>       = 1#<a href="#header.warning" class="smpl">warning-value</a>
1560  <a href="#header.warning" class="smpl">warning-value</a> = <a href="#header.warning" class="smpl">warn-code</a> <a href="#imported.abnf" class="smpl">SP</a> <a href="#header.warning" class="smpl">warn-agent</a> <a href="#imported.abnf" class="smpl">SP</a> <a href="#header.warning" class="smpl">warn-text</a>
1561                                        [ <a href="#imported.abnf" class="smpl">SP</a> <a href="#header.warning" class="smpl">warn-date</a> ]
1563  <a href="#header.warning" class="smpl">warn-code</a>  = 3<a href="#imported.abnf" class="smpl">DIGIT</a>
1564  <a href="#header.warning" class="smpl">warn-agent</a> = ( <a href="#imported.abnf" class="smpl">uri-host</a> [ ":" <a href="#imported.abnf" class="smpl">port</a> ] ) / <a href="#imported.abnf" class="smpl">pseudonym</a>
1565                  ; the name or pseudonym of the server adding
1566                  ; the Warning header field, for use in debugging
1567                  ; a single "-" is recommended when agent unknown
1568  <a href="#header.warning" class="smpl">warn-text</a>  = <a href="#imported.abnf" class="smpl">quoted-string</a>
1569  <a href="#header.warning" class="smpl">warn-date</a>  = <a href="#imported.abnf" class="smpl">DQUOTE</a> <a href="#imported.abnf" class="smpl">HTTP-date</a> <a href="#imported.abnf" class="smpl">DQUOTE</a>
1570</pre><p id="rfc.section.5.5.p.5">Multiple warnings can be generated in a response (either by the origin server or by a cache), including multiple warnings
1571               with the same warn-code number that only differ in warn-text.
1572            </p>
1573            <p id="rfc.section.5.5.p.6">A user agent that receives one or more Warning header fields <em class="bcp14">SHOULD</em> inform the user of as many of them as possible, in the order that they appear in the response. Senders that generate multiple
1574               Warning header fields are encouraged to order them with this user agent behavior in mind. A sender that generates new Warning
1575               header fields <em class="bcp14">MUST</em> append them after any existing Warning header fields.
1576            </p>
1577            <p id="rfc.section.5.5.p.7">Warnings are assigned three digit warn-codes. The first digit indicates whether the Warning is required to be deleted from
1578               a stored response after validation:
1579            </p>
1580            <ul>
1581               <li>1xx warn-codes 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.
1582               </li>
1583               <li>2xx warn-codes describe some aspect of the representation that is not rectified by a validation (for example, a lossy compression
1584                  of the representation) and <em class="bcp14">MUST NOT</em> be deleted by a cache after validation, unless a full response is sent, in which case they <em class="bcp14">MUST</em> be.
1585               </li>
1586            </ul>
1587            <p id="rfc.section.5.5.p.8">If a sender generates one or more 1xx warn-codes in a message to be sent to a recipient known to implement only HTTP/1.0,
1588               the sender <em class="bcp14">MUST</em> include in each corresponding warning-value a warn-date that matches the <a href="" class="smpl">Date</a> header field in the message. For example:
1589            </p>
1590            <div id="rfc.figure.u.14"></div><pre class="text">HTTP/1.1 200 OK
1591Date: Sat, 25 Aug 2012 23:34:45 GMT
1592Warning: 112 - "network down" "Sat, 25 Aug 2012 23:34:45 GMT"
1594</pre><p id="rfc.section.5.5.p.10">Warnings have accompanying warn-text that describes the error, e.g., for logging. It is advisory only, and its content does
1595               not affect interpretation of the warn-code.
1596            </p>
1597            <p id="rfc.section.5.5.p.11">If a recipient that uses, evaluates, or displays Warning header fields receives a warn-date that is different from the <a href="" class="smpl">Date</a> value in the same message, the recipient <em class="bcp14">MUST</em> exclude the warning-value containing that warn-date before storing, forwarding, or using the message. This allows recipients
1598               to exclude warning-values that were improperly retained after a cache validation. If all of the warning-values are excluded,
1599               the recipient <em class="bcp14">MUST</em> exclude the Warning header field as well.
1600            </p>
1601            <p id="rfc.section.5.5.p.12">The following warn-codes are defined by this specification, each with a recommended warn-text in English, and a description
1602               of its meaning. The procedure for defining additional warn codes is described in <a href="#warn.code.registry.procedure" title="Procedure">Section&nbsp;7.2.1</a>.
1603            </p>
1604            <div id="warn.110">
1605               <div id="rfc.iref.49"></div>
1606               <div id="rfc.iref.r.1"></div>
1607               <h3 id="rfc.section.5.5.1"><a href="#rfc.section.5.5.1">5.5.1</a>&nbsp;<a href="#warn.110">Warning: 110 - "Response is Stale"</a></h3>
1608               <p id="rfc.section.5.5.1.p.1">A cache <em class="bcp14">SHOULD</em> generate this whenever the sent response is stale.
1609               </p>
1610            </div>
1611            <div id="warn.111">
1612               <div id="rfc.iref.50"></div>
1613               <div id="rfc.iref.r.2"></div>
1614               <h3 id="rfc.section.5.5.2"><a href="#rfc.section.5.5.2">5.5.2</a>&nbsp;<a href="#warn.111">Warning: 111 - "Revalidation Failed"</a></h3>
1615               <p id="rfc.section.5.5.2.p.1">A cache <em class="bcp14">SHOULD</em> generate this when sending a stale response because an attempt to validate the response failed, due to an inability to reach
1616                  the server.
1617               </p>
1618            </div>
1619            <div id="warn.112">
1620               <div id="rfc.iref.51"></div>
1621               <div id="rfc.iref.d.1"></div>
1622               <h3 id="rfc.section.5.5.3"><a href="#rfc.section.5.5.3">5.5.3</a>&nbsp;<a href="#warn.112">Warning: 112 - "Disconnected Operation"</a></h3>
1623               <p id="rfc.section.5.5.3.p.1">A cache <em class="bcp14">SHOULD</em> generate this if it is intentionally disconnected from the rest of the network for a period of time.
1624               </p>
1625            </div>
1626            <div id="warn.113">
1627               <div id="rfc.iref.52"></div>
1628               <div id="rfc.iref.h.2"></div>
1629               <h3 id="rfc.section.5.5.4"><a href="#rfc.section.5.5.4">5.5.4</a>&nbsp;<a href="#warn.113">Warning: 113 - "Heuristic Expiration"</a></h3>
1630               <p id="rfc.section.5.5.4.p.1">A cache <em class="bcp14">SHOULD</em> generate this if it heuristically chose a freshness lifetime greater than 24 hours and the response's age is greater than
1631                  24 hours.
1632               </p>
1633            </div>
1634            <div id="warn.199">
1635               <div id="rfc.iref.53"></div>
1636               <div id="rfc.iref.m.6"></div>
1637               <h3 id="rfc.section.5.5.5"><a href="#rfc.section.5.5.5">5.5.5</a>&nbsp;<a href="#warn.199">Warning: 199 - "Miscellaneous Warning"</a></h3>
1638               <p id="rfc.section.5.5.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.
1639               </p>
1640            </div>
1641            <div id="warn.214">
1642               <div id="rfc.iref.54"></div>
1643               <div id="rfc.iref.t.1"></div>
1644               <h3 id="rfc.section.5.5.6"><a href="#rfc.section.5.5.6">5.5.6</a>&nbsp;<a href="#warn.214">Warning: 214 - "Transformation Applied"</a></h3>
1645               <p id="rfc.section.5.5.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,
1646                  or modifying the representation data, unless this Warning code already appears in the response.
1647               </p>
1648            </div>
1649            <div id="warn.299">
1650               <div id="rfc.iref.55"></div>
1651               <div id="rfc.iref.m.7"></div>
1652               <h3 id="rfc.section.5.5.7"><a href="#rfc.section.5.5.7">5.5.7</a>&nbsp;<a href="#warn.299">Warning: 299 - "Miscellaneous Persistent Warning"</a></h3>
1653               <p id="rfc.section.5.5.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.
1654               </p>
1655            </div>
1656         </div>
1657      </div>
1658      <div id="history.lists">
1659         <h1 id="rfc.section.6"><a href="#rfc.section.6">6.</a>&nbsp;<a href="#history.lists">History Lists</a></h1>
1660         <p id="rfc.section.6.p.1">User agents often have history mechanisms, such as "Back" buttons and history lists, that can be used to redisplay a representation
1661            retrieved earlier in a session.
1662         </p>
1663         <p id="rfc.section.6.p.2">The freshness model (<a href="#expiration.model" title="Freshness">Section&nbsp;4.2</a>) does not necessarily apply to history mechanisms. I.e., a history mechanism can display a previous representation even if
1664            it has expired.
1665         </p>
1666         <p id="rfc.section.6.p.3">This does not prohibit the history mechanism from telling the user that a view might be stale, or from honoring cache directives
1667            (e.g., Cache-Control: no-store).
1668         </p>
1669      </div>
1670      <div id="iana.considerations">
1671         <h1 id="rfc.section.7"><a href="#rfc.section.7">7.</a>&nbsp;<a href="#iana.considerations">IANA Considerations</a></h1>
1672         <div id="cache.directive.registry">
1673            <h2 id="rfc.section.7.1"><a href="#rfc.section.7.1">7.1</a>&nbsp;<a href="#cache.directive.registry">Cache Directive Registry</a></h2>
1674            <p id="rfc.section.7.1.p.1">The HTTP Cache Directive Registry defines the name space for the cache directives. It will be created and maintained at (the
1675               suggested URI) &lt;<a href=""></a>&gt;.
1676            </p>
1677            <div id="cache.directive.registry.procedure">
1678               <h3 id="rfc.section.7.1.1"><a href="#rfc.section.7.1.1">7.1.1</a>&nbsp;<a href="#cache.directive.registry.procedure">Procedure</a></h3>
1679               <p id="rfc.section.7.1.1.p.1">A registration <em class="bcp14">MUST</em> include the following fields:
1680               </p>
1681               <ul>
1682                  <li>Cache Directive Name</li>
1683                  <li>Pointer to specification text</li>
1684               </ul>
1685               <p id="rfc.section.7.1.1.p.2">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>).
1686               </p>
1687            </div>
1688            <div id="cache.directive.considerations">
1689               <h3 id="rfc.section.7.1.2"><a href="#rfc.section.7.1.2">7.1.2</a>&nbsp;<a href="#cache.directive.considerations">Considerations for New Cache Control Directives</a></h3>
1690               <p id="rfc.section.7.1.2.p.1">New extension directives ought to consider defining:</p>
1691               <p id="rfc.section.7.1.2.p.2"></p>
1692               <ul>
1693                  <li>What it means for a directive to be specified multiple times,</li>
1694                  <li>When the directive does not take an argument, what it means when an argument is present,</li>
1695                  <li>When the directive requires an argument, what it means when it is missing,</li>
1696                  <li>Whether the directive is specific to requests, responses, or able to be used in either.</li>
1697               </ul>
1698               <p id="rfc.section.7.1.2.p.3">See also <a href="#cache.control.extensions" title="Cache Control Extensions">Section&nbsp;5.2.3</a>.
1699               </p>
1700            </div>
1701            <div id="cache.directive.registration">
1702               <h3 id="rfc.section.7.1.3"><a href="#rfc.section.7.1.3">7.1.3</a>&nbsp;<a href="#cache.directive.registration">Registrations</a></h3>
1703               <p id="rfc.section.7.1.3.p.1">The HTTP Cache Directive Registry shall be populated with the registrations below:</p>
1704               <div id="rfc.table.1">
1705                  <div id="iana.cache.directive.registration.table"></div>
1706                  <table class="tt full left" cellpadding="3" cellspacing="0">
1707                     <thead>
1708                        <tr>
1709                           <th>Cache Directive</th>
1710                           <th>Reference</th>
1711                        </tr>
1712                     </thead>
1713                     <tbody>
1714                        <tr>
1715                           <td class="left">max-age</td>
1716                           <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>
1717                           </td>
1718                        </tr>
1719                        <tr>
1720                           <td class="left">max-stale</td>
1721                           <td class="left"><a href="#cache-request-directive.max-stale" title="max-stale">Section&nbsp;</a>
1722                           </td>
1723                        </tr>
1724                        <tr>
1725                           <td class="left">min-fresh</td>
1726                           <td class="left"><a href="#cache-request-directive.min-fresh" title="min-fresh">Section&nbsp;</a>
1727                           </td>
1728                        </tr>
1729                        <tr>
1730                           <td class="left">must-revalidate</td>
1731                           <td class="left"><a href="#cache-response-directive.must-revalidate" title="must-revalidate">Section&nbsp;</a>
1732                           </td>
1733                        </tr>
1734                        <tr>
1735                           <td class="left">no-cache</td>
1736                           <td class="left"><a href="" title="no-cache">Section&nbsp;</a>, <a href="" title="no-cache">Section&nbsp;</a>
1737                           </td>
1738                        </tr>
1739                        <tr>
1740                           <td class="left">no-store</td>
1741                           <td class="left"><a href="" title="no-store">Section&nbsp;</a>, <a href="" title="no-store">Section&nbsp;</a>
1742                           </td>
1743                        </tr>
1744                        <tr>
1745                           <td class="left">no-transform</td>
1746                           <td class="left"><a href="" title="no-transform">Section&nbsp;</a>, <a href="" title="no-transform">Section&nbsp;</a>
1747                           </td>
1748                        </tr>
1749                        <tr>
1750                           <td class="left">only-if-cached</td>
1751                           <td class="left"><a href="#cache-request-directive.only-if-cached" title="only-if-cached">Section&nbsp;</a>
1752                           </td>
1753                        </tr>
1754                        <tr>
1755                           <td class="left">private</td>
1756                           <td class="left"><a href="#cache-response-directive.private" title="private">Section&nbsp;</a>
1757                           </td>
1758                        </tr>
1759                        <tr>
1760                           <td class="left">proxy-revalidate</td>
1761                           <td class="left"><a href="#cache-response-directive.proxy-revalidate" title="proxy-revalidate">Section&nbsp;</a>
1762                           </td>
1763                        </tr>
1764                        <tr>
1765                           <td class="left">public</td>
1766                           <td class="left"><a href="#cache-response-directive.public" title="public">Section&nbsp;</a>
1767                           </td>
1768                        </tr>
1769                        <tr>
1770                           <td class="left">s-maxage</td>
1771                           <td class="left"><a href="#cache-response-directive.s-maxage" title="s-maxage">Section&nbsp;</a>
1772                           </td>
1773                        </tr>
1774                        <tr>
1775                           <td class="left">stale-if-error</td>
1776                           <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>
1777                           </td>
1778                        </tr>
1779                        <tr>
1780                           <td class="left">stale-while-revalidate</td>
1781                           <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>
1782                           </td>
1783                        </tr>
1784                     </tbody>
1785                  </table>
1786               </div>
1787            </div>
1788         </div>
1789         <div id="warn.code.registry">
1790            <h2 id="rfc.section.7.2"><a href="#rfc.section.7.2">7.2</a>&nbsp;<a href="#warn.code.registry">Warn Code Registry</a></h2>
1791            <p id="rfc.section.7.2.p.1">The HTTP Warn Code Registry defines the name space for warn codes. It will be created and maintained at (the suggested URI) &lt;<a href=""></a>&gt;.
1792            </p>
1793            <div id="warn.code.registry.procedure">
1794               <h3 id="rfc.section.7.2.1"><a href="#rfc.section.7.2.1">7.2.1</a>&nbsp;<a href="#warn.code.registry.procedure">Procedure</a></h3>
1795               <p id="rfc.section.7.2.1.p.1">A registration <em class="bcp14">MUST</em> include the following fields:
1796               </p>
1797               <ul>
1798                  <li>Warn Code (3 digits)</li>
1799                  <li>Short Description</li>
1800                  <li>Pointer to specification text</li>
1801               </ul>
1802               <p id="rfc.section.7.2.1.p.2">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>).
1803               </p>
1804            </div>
1805            <div id="warn.code.registration">
1806               <h3 id="rfc.section.7.2.2"><a href="#rfc.section.7.2.2">7.2.2</a>&nbsp;<a href="#warn.code.registration">Registrations</a></h3>
1807               <p id="rfc.section.7.2.2.p.1">The HTTP Warn Code Registry shall be populated with the registrations below:</p>
1808               <div id="rfc.table.2">
1809                  <div id="iana.warn.code.registration.table"></div>
1810                  <table class="tt full left" cellpadding="3" cellspacing="0">
1811                     <thead>
1812                        <tr>
1813                           <th>Warn Code</th>
1814                           <th>Short Description</th>
1815                           <th>Reference</th>
1816                        </tr>
1817                     </thead>
1818                     <tbody>
1819                        <tr>
1820                           <td class="left">110</td>
1821                           <td class="left">Response is Stale</td>
1822                           <td class="left"><a href="#warn.110" id="rfc.xref.warn.110.2" title="Warning: 110 - &#34;Response is Stale&#34;">Section&nbsp;5.5.1</a>
1823                           </td>
1824                        </tr>
1825                        <tr>
1826                           <td class="left">111</td>
1827                           <td class="left">Revalidation Failed</td>
1828                           <td class="left"><a href="#warn.111" id="rfc.xref.warn.111.1" title="Warning: 111 - &#34;Revalidation Failed&#34;">Section&nbsp;5.5.2</a>
1829                           </td>
1830                        </tr>
1831                        <tr>
1832                           <td class="left">112</td>
1833                           <td class="left">Disconnected Operation</td>
1834                           <td class="left"><a href="#warn.112" id="rfc.xref.warn.112.2" title="Warning: 112 - &#34;Disconnected Operation&#34;">Section&nbsp;5.5.3</a>
1835                           </td>
1836                        </tr>
1837                        <tr>
1838                           <td class="left">113</td>
1839                           <td class="left">Heuristic Expiration</td>
1840                           <td class="left"><a href="#warn.113" id="rfc.xref.warn.113.2" title="Warning: 113 - &#34;Heuristic Expiration&#34;">Section&nbsp;5.5.4</a>
1841                           </td>
1842                        </tr>
1843                        <tr>
1844                           <td class="left">199</td>
1845                           <td class="left">Miscellaneous Warning</td>
1846                           <td class="left"><a href="#warn.199" id="rfc.xref.warn.199.1" title="Warning: 199 - &#34;Miscellaneous Warning&#34;">Section&nbsp;5.5.5</a>
1847                           </td>
1848                        </tr>
1849                        <tr>
1850                           <td class="left">214</td>
1851                           <td class="left">Transformation Applied</td>
1852                           <td class="left"><a href="#warn.214" id="rfc.xref.warn.214.1" title="Warning: 214 - &#34;Transformation Applied&#34;">Section&nbsp;5.5.6</a>
1853                           </td>
1854                        </tr>
1855                        <tr>
1856                           <td class="left">299</td>
1857                           <td class="left">Miscellaneous Persistent Warning</td>
1858                           <td class="left"><a href="#warn.299" id="rfc.xref.warn.299.1" title="Warning: 299 - &#34;Miscellaneous Persistent Warning&#34;">Section&nbsp;5.5.7</a>
1859                           </td>
1860                        </tr>
1861                     </tbody>
1862                  </table>
1863               </div>
1864            </div>
1865         </div>
1866         <div id="header.field.registration">
1867            <h2 id="rfc.section.7.3"><a href="#rfc.section.7.3">7.3</a>&nbsp;<a href="#header.field.registration">Header Field Registration</a></h2>
1868            <p id="rfc.section.7.3.p.1">HTTP header fields are registered within the Message Header Field Registry maintained at &lt;<a href=""></a>&gt;.
1869            </p>
1870            <p id="rfc.section.7.3.p.2">This document defines the following HTTP header fields, so their associated registry entries shall be updated according to
1871               the permanent registrations below (see <a href="#BCP90" id="rfc.xref.BCP90.1"><cite title="Registration Procedures for Message Header Fields">[BCP90]</cite></a>):
1872            </p>
1873            <div id="rfc.table.3">
1874               <div id="iana.header.registration.table"></div>
1875               <table class="tt full left" cellpadding="3" cellspacing="0">
1876                  <thead>
1877                     <tr>
1878                        <th>Header Field Name</th>
1879                        <th>Protocol</th>
1880                        <th>Status</th>
1881                        <th>Reference</th>
1882                     </tr>
1883                  </thead>
1884                  <tbody>
1885                     <tr>
1886                        <td class="left">Age</td>
1887                        <td class="left">http</td>
1888                        <td class="left">standard</td>
1889                        <td class="left"><a href="#header.age" id="rfc.xref.header.age.3" title="Age">Section&nbsp;5.1</a>
1890                        </td>
1891                     </tr>
1892                     <tr>
1893                        <td class="left">Cache-Control</td>
1894                        <td class="left">http</td>
1895                        <td class="left">standard</td>
1896                        <td class="left"><a href="#header.cache-control" id="rfc.xref.header.cache-control.2" title="Cache-Control">Section&nbsp;5.2</a>
1897                        </td>
1898                     </tr>
1899                     <tr>
1900                        <td class="left">Expires</td>
1901                        <td class="left">http</td>
1902                        <td class="left">standard</td>
1903                        <td class="left"><a href="#header.expires" id="rfc.xref.header.expires.4" title="Expires">Section&nbsp;5.3</a>
1904                        </td>
1905                     </tr>
1906                     <tr>
1907                        <td class="left">Pragma</td>
1908                        <td class="left">http</td>
1909                        <td class="left">standard</td>
1910                        <td class="left"><a href="#header.pragma" id="rfc.xref.header.pragma.2" title="Pragma">Section&nbsp;5.4</a>
1911                        </td>
1912                     </tr>
1913                     <tr>
1914                        <td class="left">Warning</td>
1915                        <td class="left">http</td>
1916                        <td class="left">standard</td>
1917                        <td class="left"><a href="#header.warning" id="rfc.xref.header.warning.4" title="Warning">Section&nbsp;5.5</a>
1918                        </td>
1919                     </tr>
1920                  </tbody>
1921               </table>
1922            </div>
1923            <p id="rfc.section.7.3.p.3">The change controller is: "IETF ( - Internet Engineering Task Force".</p>
1924         </div>
1925      </div>
1926      <div id="security.considerations">
1927         <h1 id="rfc.section.8"><a href="#rfc.section.8">8.</a>&nbsp;<a href="#security.considerations">Security Considerations</a></h1>
1928         <p id="rfc.section.8.p.1">This section is meant to inform developers, information providers, and users of known security concerns specific to HTTP/1.1
1929            caching. More general security considerations are addressed in HTTP messaging <a href="#Part1" id="rfc.xref.Part1.11"><cite title="Hypertext Transfer Protocol (HTTP/1.1): Message Syntax and Routing">[Part1]</cite></a> and semantics <a href="#Part2" id="rfc.xref.Part2.9"><cite title="Hypertext Transfer Protocol (HTTP/1.1): Semantics and Content">[Part2]</cite></a>.
1930         </p>
1931         <p id="rfc.section.8.p.2">Caches expose additional potential vulnerabilities, since the contents of the cache represent an attractive target for malicious
1932            exploitation. Because cache contents persist after an HTTP request is complete, an attack on the cache can reveal information
1933            long after a user believes that the information has been removed from the network. Therefore, cache contents need to be protected
1934            as sensitive information.
1935         </p>
1936         <p id="rfc.section.8.p.3">In particular, various attacks might be amplified by being stored in a shared cache; such "cache poisoning" attacks use the
1937            cache to distribute a malicious payload to many clients, and are especially effective when an attacker can use implmentation
1938            flaws, elevated priviledges or other techniques to insert such a response into a cache. One common attack vector for cache
1939            poisoning is to exploit differences in message parsing on proxies and in user agents; see <a href="p1-messaging.html#message.body.length" title="Message Body Length">Section 3.3.3</a> of <a href="#Part1" id="rfc.xref.Part1.12"><cite title="Hypertext Transfer Protocol (HTTP/1.1): Message Syntax and Routing">[Part1]</cite></a> for the relevant requirements.
1940         </p>
1941         <p id="rfc.section.8.p.4">Likewise, implementation flaws (as well as misunderstanding of cache operation) might lead to caching of sensitive information
1942            (e.g., authentication credentials) that is thought to be private, exposing it to unauthorized parties.
1943         </p>
1944         <p id="rfc.section.8.p.5">Furthermore, the very use of a cache can bring about privacy concerns. For example, if two users share a cache, and the first
1945            one browses to a site, the second may be able to detect that the other has been to that site, because the resources from it
1946            load more quickly, thanks to the cache.
1947         </p>
1948         <p id="rfc.section.8.p.6">Note that the Set-Cookie response header field <a href="#RFC6265" id="rfc.xref.RFC6265.1"><cite title="HTTP State Management Mechanism">[RFC6265]</cite></a> does not inhibit caching; a cacheable response with a Set-Cookie header field can be (and often is) used to satisfy subsequent
1949            requests to caches. Servers who wish to control caching of these responses are encouraged to emit appropriate Cache-Control
1950            response header fields.
1951         </p>
1952      </div>
1953      <div id="acks">
1954         <h1 id="rfc.section.9"><a href="#rfc.section.9">9.</a>&nbsp;<a href="#acks">Acknowledgments</a></h1>
1955         <p id="rfc.section.9.p.1">See <a href="p1-messaging.html#acks" title="Acknowledgments">Section 10</a> of <a href="#Part1" id="rfc.xref.Part1.13"><cite title="Hypertext Transfer Protocol (HTTP/1.1): Message Syntax and Routing">[Part1]</cite></a>.
1956         </p>
1957      </div>
1958      <h1 id="rfc.references"><a id="rfc.section.10" href="#rfc.section.10">10.</a> References
1959      </h1>
1960      <h2 id="rfc.references.1"><a href="#rfc.section.10.1" id="rfc.section.10.1">10.1</a> Normative References
1961      </h2>
1962      <table>
1963         <tr>
1964            <td class="reference"><b id="Part1">[Part1]</b></td>
1965            <td class="top"><a href="" title="Adobe Systems Incorporated">Fielding, R., Ed.</a> and <a href="" title="greenbytes GmbH">J. Reschke, Ed.</a>, “<a href="">Hypertext Transfer Protocol (HTTP/1.1): Message Syntax and Routing</a>”, Internet-Draft&nbsp;draft-ietf-httpbis-p1-messaging-latest (work in progress), December&nbsp;2013.
1966            </td>
1967         </tr>
1968         <tr>
1969            <td class="reference"><b id="Part2">[Part2]</b></td>
1970            <td class="top"><a href="" title="Adobe Systems Incorporated">Fielding, R., Ed.</a> and <a href="" title="greenbytes GmbH">J. Reschke, Ed.</a>, “<a href="">Hypertext Transfer Protocol (HTTP/1.1): Semantics and Content</a>”, Internet-Draft&nbsp;draft-ietf-httpbis-p2-semantics-latest (work in progress), December&nbsp;2013.
1971            </td>
1972         </tr>
1973         <tr>
1974            <td class="reference"><b id="Part4">[Part4]</b></td>
1975            <td class="top"><a href="" title="Adobe Systems Incorporated">Fielding, R., Ed.</a> and <a href="" title="greenbytes GmbH">J. Reschke, Ed.</a>, “<a href="">Hypertext Transfer Protocol (HTTP/1.1): Conditional Requests</a>”, Internet-Draft&nbsp;draft-ietf-httpbis-p4-conditional-latest (work in progress), December&nbsp;2013.
1976            </td>
1977         </tr>
1978         <tr>
1979            <td class="reference"><b id="Part5">[Part5]</b></td>
1980            <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="">Hypertext Transfer Protocol (HTTP/1.1): Range Requests</a>”, Internet-Draft&nbsp;draft-ietf-httpbis-p5-range-latest (work in progress), December&nbsp;2013.
1981            </td>
1982         </tr>
1983         <tr>
1984            <td class="reference"><b id="Part7">[Part7]</b></td>
1985            <td class="top"><a href="" title="Adobe Systems Incorporated">Fielding, R., Ed.</a> and <a href="" title="greenbytes GmbH">J. Reschke, Ed.</a>, “<a href="">Hypertext Transfer Protocol (HTTP/1.1): Authentication</a>”, Internet-Draft&nbsp;draft-ietf-httpbis-p7-auth-latest (work in progress), December&nbsp;2013.
1986            </td>
1987         </tr>
1988         <tr>
1989            <td class="reference"><b id="RFC2119">[RFC2119]</b></td>
1990            <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.
1991            </td>
1992         </tr>
1993         <tr>
1994            <td class="reference"><b id="RFC5234">[RFC5234]</b></td>
1995            <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.
1996            </td>
1997         </tr>
1998      </table>
1999      <h2 id="rfc.references.2"><a href="#rfc.section.10.2" id="rfc.section.10.2">10.2</a> Informative References
2000      </h2>
2001      <table>
2002         <tr>
2003            <td class="reference"><b id="BCP90">[BCP90]</b></td>
2004            <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.
2005            </td>
2006         </tr>
2007         <tr>
2008            <td class="reference"><b id="RFC2616">[RFC2616]</b></td>
2009            <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.
2010            </td>
2011         </tr>
2012         <tr>
2013            <td class="reference"><b id="RFC5226">[RFC5226]</b></td>
2014            <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.
2015            </td>
2016         </tr>
2017         <tr>
2018            <td class="reference"><b id="RFC5861">[RFC5861]</b></td>
2019            <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.
2020            </td>
2021         </tr>
2022         <tr>
2023            <td class="reference"><b id="RFC5905">[RFC5905]</b></td>
2024            <td class="top">Mills, D., Martin, J., Ed., Burbank, J., and W. Kasch, “<a href="">Network Time Protocol Version 4: Protocol and Algorithms Specification</a>”, RFC&nbsp;5905, June&nbsp;2010.
2025            </td>
2026         </tr>
2027         <tr>
2028            <td class="reference"><b id="RFC6265">[RFC6265]</b></td>
2029            <td class="top"><a href="" title="&#xA;          University of California, Berkeley&#xA;        ">Barth, A.</a>, “<a href="">HTTP State Management Mechanism</a>”, RFC&nbsp;6265, April&nbsp;2011.
2030            </td>
2031         </tr>
2032      </table>
2033      <div class="avoidbreak">
2034         <h1 id="rfc.authors"><a href="#rfc.authors">Authors' Addresses</a></h1>
2035         <p><b>Roy T. Fielding</b>
2036            (editor)
2037            <br>Adobe Systems Incorporated<br>345 Park Ave<br>San Jose, CA&nbsp;95110<br>USA<br>Email: <a href=""></a><br>URI: <a href=""></a></p>
2038         <p><b>Mark Nottingham</b>
2039            (editor)
2040            <br>Akamai<br>Email: <a href=""></a><br>URI: <a href=""></a></p>
2041         <p><b>Julian F. Reschke</b>
2042            (editor)
2043            <br>greenbytes GmbH<br>Hafenweg 16<br>Muenster, NW&nbsp;48155<br>Germany<br>Email: <a href=""></a><br>URI: <a href=""></a></p>
2044      </div>
2045      <div id="changes.from.rfc.2616">
2046         <h1 id="rfc.section.A" class="np"><a href="#rfc.section.A">A.</a>&nbsp;<a href="#changes.from.rfc.2616">Changes from RFC 2616</a></h1>
2047         <p id="rfc.section.A.p.1">The specification has been substantially rewritten for clarity.</p>
2048         <p id="rfc.section.A.p.2">The conditions under which an authenticated response can be cached have been clarified. (<a href="#caching.authenticated.responses" title="Storing Responses to Authenticated Requests">Section&nbsp;3.2</a>)
2049         </p>
2050         <p id="rfc.section.A.p.3">New status codes can now define that caches are allowed to use heuristic freshness with them. Caches are now allowed to calculate
2051            heuristic freshness for URIs with query components. (<a href="#heuristic.freshness" title="Calculating Heuristic Freshness">Section&nbsp;4.2.2</a>)
2052         </p>
2053         <p id="rfc.section.A.p.4">The algorithm for calculating age is now less conservative. Caches are now required to handle dates with timezones as if they're
2054            invalid, because it's not possible to accurately guess. (<a href="#age.calculations" title="Calculating Age">Section&nbsp;4.2.3</a>)
2055         </p>
2056         <p id="rfc.section.A.p.5">The <a href="p2-semantics.html#header.content-location" class="smpl">Content-Location</a> response header field is no longer used to determine the appropriate response to use when validating. (<a href="#validation.model" title="Validation">Section&nbsp;4.3</a>)
2057         </p>
2058         <p id="rfc.section.A.p.6">The algorithm for selecting a cached negotiated response to use has been clarified in several ways. In particular, it now
2059            explicitly allows header-specific canonicalization when processing selecting header fields. (<a href="#caching.negotiated.responses" title="Calculating Secondary Keys with Vary">Section&nbsp;4.1</a>)
2060         </p>
2061         <p id="rfc.section.A.p.7">Requirements regarding denial of service attack avoidance when performing invalidation have been clarified. (<a href="#invalidation" title="Invalidation">Section&nbsp;4.4</a>)
2062         </p>
2063         <p id="rfc.section.A.p.8">Cache invalidation only occurs when a successful response is received. (<a href="#invalidation" title="Invalidation">Section&nbsp;4.4</a>)
2064         </p>
2065         <p id="rfc.section.A.p.9">Cache directives are explicitly defined to be case-insensitive. Handling of multiple instances of cache directives when only
2066            one is expected is now defined. (<a href="#header.cache-control" id="rfc.xref.header.cache-control.3" title="Cache-Control">Section&nbsp;5.2</a>)
2067         </p>
2068         <p id="rfc.section.A.p.10">The "no-store" request directive doesn't apply to responses; i.e., a cache can satisfy a request with no-store on it, and
2069            does not invalidate it. (<a href="" title="no-store">Section&nbsp;</a>)
2070         </p>
2071         <p id="rfc.section.A.p.11">The qualified forms of the private and no-cache cache directives are noted to not be widely implemented; e.g., "private=foo"
2072            is interpreted by many caches as simply "private". Additionally, the meaning of the qualified form of no-cache has been clarified.
2073            (<a href="#cache-response-directive" title="Response Cache-Control Directives">Section&nbsp;5.2.2</a>)
2074         </p>
2075         <p id="rfc.section.A.p.12">The "no-cache" response directive's meaning has been clarified. (<a href="" title="no-cache">Section&nbsp;</a>)
2076         </p>
2077         <p id="rfc.section.A.p.13">The one-year limit on <a href="#header.expires" class="smpl">Expires</a> header field values has been removed; instead, the reasoning for using a sensible value is given. (<a href="#header.expires" id="rfc.xref.header.expires.5" title="Expires">Section&nbsp;5.3</a>)
2078         </p>
2079         <p id="rfc.section.A.p.14">The <a href="#header.pragma" class="smpl">Pragma</a> header field is now only defined for backwards compatibility; future pragmas are deprecated. (<a href="#header.pragma" id="rfc.xref.header.pragma.3" title="Pragma">Section&nbsp;5.4</a>)
2080         </p>
2081         <p id="rfc.section.A.p.15">Some requirements regarding production and processing of the <a href="#header.warning" class="smpl">Warning</a> header fields have been relaxed, as it is not widely implemented. Furthermore, the <a href="#header.warning" class="smpl">Warning</a> header field no longer uses RFC 2047 encoding, nor allows multiple languages, as these aspects were not implemented. (<a href="#header.warning" id="rfc.xref.header.warning.5" title="Warning">Section&nbsp;5.5</a>)
2082         </p>
2083         <p id="rfc.section.A.p.16">This specification introduces the Cache Directive and Warn Code Registries, and defines considerations for new cache directives.
2084            (<a href="#cache.directive.registry" title="Cache Directive Registry">Section&nbsp;7.1</a> and <a href="#warn.code.registry" title="Warn Code Registry">Section&nbsp;7.2</a>)
2085         </p>
2086      </div>
2087      <div id="imported.abnf">
2088         <h1 id="rfc.section.B"><a href="#rfc.section.B">B.</a>&nbsp;<a href="#imported.abnf">Imported ABNF</a></h1>
2089         <p id="rfc.section.B.p.1">The following core rules are included by reference, as defined in <a href="">Appendix B.1</a> of <a href="#RFC5234" id="rfc.xref.RFC5234.2"><cite title="Augmented BNF for Syntax Specifications: ABNF">[RFC5234]</cite></a>: ALPHA (letters), CR (carriage return), CRLF (CR LF), CTL (controls), DIGIT (decimal 0-9), DQUOTE (double quote), HEXDIG
2090            (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
2091            character).
2092         </p>
2093         <p id="rfc.section.B.p.2">The rules below are defined in <a href="#Part1" id="rfc.xref.Part1.14"><cite title="Hypertext Transfer Protocol (HTTP/1.1): Message Syntax and Routing">[Part1]</cite></a>:
2094         </p>
2095         <div id="rfc.figure.u.15"></div><pre class="inline">  <a href="#imported.abnf" class="smpl">OWS</a>           = &lt;OWS, defined in <a href="#Part1" id="rfc.xref.Part1.15"><cite title="Hypertext Transfer Protocol (HTTP/1.1): Message Syntax and Routing">[Part1]</cite></a>, <a href="p1-messaging.html#whitespace" title="Whitespace">Section 3.2.3</a>&gt;
2096  <a href="#imported.abnf" class="smpl">field-name</a>    = &lt;field-name, defined in <a href="#Part1" id="rfc.xref.Part1.16"><cite title="Hypertext Transfer Protocol (HTTP/1.1): Message Syntax and Routing">[Part1]</cite></a>, <a href="p1-messaging.html#header.fields" title="Header Fields">Section 3.2</a>&gt;
2097  <a href="#imported.abnf" class="smpl">quoted-string</a> = &lt;quoted-string, defined in <a href="#Part1" id="rfc.xref.Part1.17"><cite title="Hypertext Transfer Protocol (HTTP/1.1): Message Syntax and Routing">[Part1]</cite></a>, <a href="p1-messaging.html#field.components" title="Field value components">Section 3.2.6</a>&gt;
2098  <a href="#imported.abnf" class="smpl">token</a>         = &lt;token, defined in <a href="#Part1" id="rfc.xref.Part1.18"><cite title="Hypertext Transfer Protocol (HTTP/1.1): Message Syntax and Routing">[Part1]</cite></a>, <a href="p1-messaging.html#field.components" title="Field value components">Section 3.2.6</a>&gt;
2100  <a href="#imported.abnf" class="smpl">port</a>          = &lt;port, defined in <a href="#Part1" id="rfc.xref.Part1.19"><cite title="Hypertext Transfer Protocol (HTTP/1.1): Message Syntax and Routing">[Part1]</cite></a>, <a href="p1-messaging.html#uri" title="Uniform Resource Identifiers">Section 2.7</a>&gt;
2101  <a href="#imported.abnf" class="smpl">pseudonym</a>     = &lt;pseudonym, defined in <a href="#Part1" id="rfc.xref.Part1.20"><cite title="Hypertext Transfer Protocol (HTTP/1.1): Message Syntax and Routing">[Part1]</cite></a>, <a href="p1-messaging.html#header.via" title="Via">Section 5.7.1</a>&gt;
2102  <a href="#imported.abnf" class="smpl">uri-host</a>      = &lt;uri-host, defined in <a href="#Part1" id="rfc.xref.Part1.21"><cite title="Hypertext Transfer Protocol (HTTP/1.1): Message Syntax and Routing">[Part1]</cite></a>, <a href="p1-messaging.html#uri" title="Uniform Resource Identifiers">Section 2.7</a>&gt;
2103</pre><p id="rfc.section.B.p.4">The rules below are defined in other parts:</p>
2104         <div id="rfc.figure.u.16"></div><pre class="inline">  <a href="#imported.abnf" class="smpl">HTTP-date</a>     = &lt;HTTP-date, defined in <a href="#Part2" id="rfc.xref.Part2.10"><cite title="Hypertext Transfer Protocol (HTTP/1.1): Semantics and Content">[Part2]</cite></a>, <a href="" title="Date/Time Formats">Section</a>&gt;
2106      <div id="collected.abnf">
2107         <h1 id="rfc.section.C"><a href="#rfc.section.C">C.</a>&nbsp;<a href="#collected.abnf">Collected ABNF</a></h1>
2108         <p id="rfc.section.C.p.1">In the collected ABNF below, list rules are expanded as per <a href="p1-messaging.html#notation" title="Syntax Notation">Section 1.2</a> of <a href="#Part1" id="rfc.xref.Part1.22"><cite title="Hypertext Transfer Protocol (HTTP/1.1): Message Syntax and Routing">[Part1]</cite></a>.
2109         </p>
2110         <div id="rfc.figure.u.17"></div><pre class="inline"><a href="#header.age" class="smpl">Age</a> = delta-seconds
2112<a href="#header.cache-control" class="smpl">Cache-Control</a> = *( "," OWS ) cache-directive *( OWS "," [ OWS
2113 cache-directive ] )
2115<a href="#header.expires" class="smpl">Expires</a> = HTTP-date
2117<a href="#imported.abnf" class="smpl">HTTP-date</a> = &lt;HTTP-date, defined in [Part2], Section;
2119<a href="#imported.abnf" class="smpl">OWS</a> = &lt;OWS, defined in [Part1], Section 3.2.3&gt;
2121<a href="#header.pragma" class="smpl">Pragma</a> = *( "," OWS ) pragma-directive *( OWS "," [ OWS
2122 pragma-directive ] )
2124<a href="#header.warning" class="smpl">Warning</a> = *( "," OWS ) warning-value *( OWS "," [ OWS warning-value ]
2125 )
2127<a href="#header.cache-control" class="smpl">cache-directive</a> = token [ "=" ( token / quoted-string ) ]
2129<a href="#delta-seconds" class="smpl">delta-seconds</a> = 1*DIGIT
2131<a href="#header.pragma" class="smpl">extension-pragma</a> = token [ "=" ( token / quoted-string ) ]
2133<a href="#imported.abnf" class="smpl">field-name</a> = &lt;field-name, defined in [Part1], Section 3.2&gt;
2135<a href="#imported.abnf" class="smpl">port</a> = &lt;port, defined in [Part1], Section 2.7&gt;
2136<a href="#header.pragma" class="smpl">pragma-directive</a> = "no-cache" / extension-pragma
2137<a href="#imported.abnf" class="smpl">pseudonym</a> = &lt;pseudonym, defined in [Part1], Section 5.7.1&gt;
2139<a href="#imported.abnf" class="smpl">quoted-string</a> = &lt;quoted-string, defined in [Part1], Section 3.2.6&gt;
2141<a href="#imported.abnf" class="smpl">token</a> = &lt;token, defined in [Part1], Section 3.2.6&gt;
2143<a href="#imported.abnf" class="smpl">uri-host</a> = &lt;uri-host, defined in [Part1], Section 2.7&gt;
2145<a href="#header.warning" class="smpl">warn-agent</a> = ( uri-host [ ":" port ] ) / pseudonym
2146<a href="#header.warning" class="smpl">warn-code</a> = 3DIGIT
2147<a href="#header.warning" class="smpl">warn-date</a> = DQUOTE HTTP-date DQUOTE
2148<a href="#header.warning" class="smpl">warn-text</a> = quoted-string
2149<a href="#header.warning" class="smpl">warning-value</a> = warn-code SP warn-agent SP warn-text [ SP warn-date
2150 ]
2152      <div id="change.log">
2153         <h1 id="rfc.section.D"><a href="#rfc.section.D">D.</a>&nbsp;<a href="#change.log">Change Log (to be removed by RFC Editor before publication)</a></h1>
2154         <p id="rfc.section.D.p.1">Changes up to the IETF Last Call draft are summarized in &lt;<a href=""></a>&gt;.
2155         </p>
2156         <div id="changes.since.24">
2157            <h2 id="rfc.section.D.1"><a href="#rfc.section.D.1">D.1</a>&nbsp;<a href="#changes.since.24">Since draft-ietf-httpbis-p6-cache-24</a></h2>
2158            <p id="rfc.section.D.1.p.1">Closed issues: </p>
2159            <ul>
2160               <li>&lt;<a href=""></a>&gt;: "RFC 1305 ref needs to be updated to 5905"
2161               </li>
2162               <li>&lt;<a href=""></a>&gt;: "dangling reference to cacheable status codes"
2163               </li>
2164               <li>&lt;<a href=""></a>&gt;: "APPSDIR review of draft-ietf-httpbis-p6-cache-24"
2165               </li>
2166            </ul>
2167         </div>
2168         <div id="changes.since.25">
2169            <h2 id="rfc.section.D.2"><a href="#rfc.section.D.2">D.2</a>&nbsp;<a href="#changes.since.25">Since draft-ietf-httpbis-p6-cache-25</a></h2>
2170            <p id="rfc.section.D.2.p.1">Closed issues: </p>
2171            <ul>
2172               <li>&lt;<a href=""></a>&gt;: "improve introduction of list rule"
2173               </li>
2174            </ul>
2175            <p id="rfc.section.D.2.p.2">Partly closed issues: </p>
2176            <ul>
2177               <li>&lt;<a href=""></a>&gt;: "IESG ballot on draft-ietf-httpbis-p6-cache-25"
2178               </li>
2179            </ul>
2180         </div>
2181      </div>
2182      <h1 id="rfc.index"><a href="#rfc.index">Index</a></h1>
2183      <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.B">B</a> <a href="#rfc.index.C">C</a> <a href="#rfc.index.D">D</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.T">T</a> <a href="#rfc.index.V">V</a> <a href="#rfc.index.W">W</a>
2184      </p>
2185      <div class="print2col">
2186         <ul class="ind">
2187            <li><a id="rfc.index.1" href="#rfc.index.1"><b>1</b></a><ul>
2188                  <li>110 (warn-code)&nbsp;&nbsp;<a href="#rfc.xref.warn.110.1">4.2.4</a>, <a href="#rfc.iref.49"><b>5.5.1</b></a>, <a href="#rfc.xref.warn.110.2">7.2.2</a></li>
2189                  <li>111 (warn-code)&nbsp;&nbsp;<a href="#rfc.iref.50"><b>5.5.2</b></a>, <a href="#rfc.xref.warn.111.1">7.2.2</a></li>
2190                  <li>112 (warn-code)&nbsp;&nbsp;<a href="#rfc.xref.warn.112.1">4.2.4</a>, <a href="#rfc.iref.51"><b>5.5.3</b></a>, <a href="#rfc.xref.warn.112.2">7.2.2</a></li>
2191                  <li>113 (warn-code)&nbsp;&nbsp;<a href="#rfc.xref.warn.113.1">4.2.2</a>, <a href="#rfc.iref.52"><b>5.5.4</b></a>, <a href="#rfc.xref.warn.113.2">7.2.2</a></li>
2192                  <li>199 (warn-code)&nbsp;&nbsp;<a href="#rfc.iref.53"><b>5.5.5</b></a>, <a href="#rfc.xref.warn.199.1">7.2.2</a></li>
2193               </ul>
2194            </li>
2195            <li><a id="rfc.index.2" href="#rfc.index.2"><b>2</b></a><ul>
2196                  <li>214 (warn-code)&nbsp;&nbsp;<a href="#rfc.iref.54"><b>5.5.6</b></a>, <a href="#rfc.xref.warn.214.1">7.2.2</a></li>
2197                  <li>299 (warn-code)&nbsp;&nbsp;<a href="#rfc.iref.55"><b>5.5.7</b></a>, <a href="#rfc.xref.warn.299.1">7.2.2</a></li>
2198               </ul>
2199            </li>
2200            <li><a id="rfc.index.A" href="#rfc.index.A"><b>A</b></a><ul>
2201                  <li>age&nbsp;&nbsp;<a href="#rfc.iref.a.1">4.2</a></li>
2202                  <li>Age header field&nbsp;&nbsp;<a href="#rfc.xref.header.age.1">4</a>, <a href="#rfc.xref.header.age.2">4.2.3</a>, <a href="#rfc.iref.a.2"><b>5.1</b></a>, <a href="#rfc.xref.header.age.3">7.3</a></li>
2203               </ul>
2204            </li>
2205            <li><a id="rfc.index.B" href="#rfc.index.B"><b>B</b></a><ul>
2206                  <li><em>BCP90</em>&nbsp;&nbsp;<a href="#rfc.xref.BCP90.1">7.3</a>, <a href="#BCP90"><b>10.2</b></a></li>
2207               </ul>
2208            </li>
2209            <li><a id="rfc.index.C" href="#rfc.index.C"><b>C</b></a><ul>
2210                  <li>cache&nbsp;&nbsp;<a href="#rfc.iref.c.1">1</a></li>
2211                  <li>cache entry&nbsp;&nbsp;<a href="#rfc.iref.c.2">2</a></li>
2212                  <li>cache key&nbsp;&nbsp;<a href="#rfc.iref.c.3">2</a>, <a href="#rfc.iref.c.4">2</a></li>
2213                  <li>Cache-Control header field&nbsp;&nbsp;<a href="#rfc.xref.header.cache-control.1">3</a>, <a href="#rfc.iref.c.5"><b>5.2</b></a>, <a href="#rfc.xref.header.cache-control.2">7.3</a>, <a href="#rfc.xref.header.cache-control.3">A</a></li>
2214               </ul>
2215            </li>
2216            <li><a id="rfc.index.D" href="#rfc.index.D"><b>D</b></a><ul>
2217                  <li>Disconnected Operation (warn-text)&nbsp;&nbsp;<a href="#rfc.xref.warn.112.1">4.2.4</a>, <a href="#rfc.iref.d.1"><b>5.5.3</b></a>, <a href="#rfc.xref.warn.112.2">7.2.2</a></li>
2218               </ul>
2219            </li>
2220            <li><a id="rfc.index.E" href="#rfc.index.E"><b>E</b></a><ul>
2221                  <li>Expires header field&nbsp;&nbsp;<a href="#rfc.xref.header.expires.1">3</a>, <a href="#rfc.xref.header.expires.2">4.2</a>, <a href="#rfc.xref.header.expires.3">4.2.1</a>, <a href="#rfc.iref.e.2"><b>5.3</b></a>, <a href="#rfc.xref.header.expires.4">7.3</a>, <a href="#rfc.xref.header.expires.5">A</a></li>
2222                  <li>explicit expiration time&nbsp;&nbsp;<a href="#rfc.iref.e.1">4.2</a></li>
2223               </ul>
2224            </li>
2225            <li><a id="rfc.index.F" href="#rfc.index.F"><b>F</b></a><ul>
2226                  <li>fresh&nbsp;&nbsp;<a href="#rfc.iref.f.1">4.2</a></li>
2227                  <li>freshness lifetime&nbsp;&nbsp;<a href="#rfc.iref.f.2">4.2</a></li>
2228               </ul>
2229            </li>
2230            <li><a id="rfc.index.G" href="#rfc.index.G"><b>G</b></a><ul>
2231                  <li><tt>Grammar</tt>&nbsp;&nbsp;
2232                     <ul>
2233                        <li><tt>Age</tt>&nbsp;&nbsp;<a href="#rfc.iref.g.2"><b>5.1</b></a></li>
2234                        <li><tt>Cache-Control</tt>&nbsp;&nbsp;<a href="#rfc.iref.g.3"><b>5.2</b></a></li>
2235                        <li><tt>cache-directive</tt>&nbsp;&nbsp;<a href="#rfc.iref.g.4"><b>5.2</b></a></li>
2236                        <li><tt>delta-seconds</tt>&nbsp;&nbsp;<a href="#rfc.iref.g.1"><b>1.2.1</b></a></li>
2237                        <li><tt>Expires</tt>&nbsp;&nbsp;<a href="#rfc.iref.g.5"><b>5.3</b></a></li>
2238                        <li><tt>extension-pragma</tt>&nbsp;&nbsp;<a href="#rfc.iref.g.8"><b>5.4</b></a></li>
2239                        <li><tt>Pragma</tt>&nbsp;&nbsp;<a href="#rfc.iref.g.6"><b>5.4</b></a></li>
2240                        <li><tt>pragma-directive</tt>&nbsp;&nbsp;<a href="#rfc.iref.g.7"><b>5.4</b></a></li>
2241                        <li><tt>warn-agent</tt>&nbsp;&nbsp;<a href="#rfc.iref.g.12"><b>5.5</b></a></li>
2242                        <li><tt>warn-code</tt>&nbsp;&nbsp;<a href="#rfc.iref.g.11"><b>5.5</b></a></li>
2243                        <li><tt>warn-date</tt>&nbsp;&nbsp;<a href="#rfc.iref.g.14"><b>5.5</b></a></li>
2244                        <li><tt>warn-text</tt>&nbsp;&nbsp;<a href="#rfc.iref.g.13"><b>5.5</b></a></li>
2245                        <li><tt>Warning</tt>&nbsp;&nbsp;<a href="#rfc.iref.g.9"><b>5.5</b></a></li>
2246                        <li><tt>warning-value</tt>&nbsp;&nbsp;<a href="#rfc.iref.g.10"><b>5.5</b></a></li>
2247                     </ul>
2248                  </li>
2249               </ul>
2250            </li>
2251            <li><a id="rfc.index.H" href="#rfc.index.H"><b>H</b></a><ul>
2252                  <li>Heuristic Expiration (warn-text)&nbsp;&nbsp;<a href="#rfc.xref.warn.113.1">4.2.2</a>, <a href="#rfc.iref.h.2"><b>5.5.4</b></a>, <a href="#rfc.xref.warn.113.2">7.2.2</a></li>
2253                  <li>heuristic expiration time&nbsp;&nbsp;<a href="#rfc.iref.h.1">4.2</a></li>
2254               </ul>
2255            </li>
2256            <li><a id="rfc.index.M" href="#rfc.index.M"><b>M</b></a><ul>
2257                  <li>max-age (cache directive)&nbsp;&nbsp;<a href="#rfc.iref.m.1"><b></b></a>, <a href="#rfc.iref.m.5"><b></b></a></li>
2258                  <li>max-stale (cache directive)&nbsp;&nbsp;<a href="#rfc.iref.m.2"><b></b></a></li>
2259                  <li>min-fresh (cache directive)&nbsp;&nbsp;<a href="#rfc.iref.m.3"><b></b></a></li>
2260                  <li>Miscellaneous Persistent Warning (warn-text)&nbsp;&nbsp;<a href="#rfc.iref.m.7"><b>5.5.7</b></a>, <a href="#rfc.xref.warn.299.1">7.2.2</a></li>
2261                  <li>Miscellaneous Warning (warn-text)&nbsp;&nbsp;<a href="#rfc.iref.m.6"><b>5.5.5</b></a>, <a href="#rfc.xref.warn.199.1">7.2.2</a></li>
2262                  <li>must-revalidate (cache directive)&nbsp;&nbsp;<a href="#rfc.iref.m.4"><b></b></a></li>
2263               </ul>
2264            </li>
2265            <li><a id="rfc.index.N" href="#rfc.index.N"><b>N</b></a><ul>
2266                  <li>no-cache (cache directive)&nbsp;&nbsp;<a href="#rfc.iref.n.1"><b></b></a>, <a href="#rfc.iref.n.4"><b></b></a></li>
2267                  <li>no-store (cache directive)&nbsp;&nbsp;<a href="#rfc.iref.n.2"><b></b></a>, <a href="#rfc.iref.n.5"><b></b></a></li>
2268                  <li>no-transform (cache directive)&nbsp;&nbsp;<a href="#rfc.iref.n.3"><b></b></a>, <a href="#rfc.iref.n.6"><b></b></a></li>
2269               </ul>
2270            </li>
2271            <li><a id="rfc.index.O" href="#rfc.index.O"><b>O</b></a><ul>
2272                  <li>only-if-cached (cache directive)&nbsp;&nbsp;<a href="#rfc.iref.o.1"><b></b></a></li>
2273               </ul>
2274            </li>
2275            <li><a id="rfc.index.P" href="#rfc.index.P"><b>P</b></a><ul>
2276                  <li><em>Part1</em>&nbsp;&nbsp;<a href="#rfc.xref.Part1.1">1.1</a>, <a href="#rfc.xref.Part1.2">1.2</a>, <a href="#rfc.xref.Part1.3">3.1</a>, <a href="#rfc.xref.Part1.4">4</a>, <a href="#rfc.xref.Part1.5">4.1</a>, <a href="#rfc.xref.Part1.6">4.4</a>, <a href="#rfc.xref.Part1.7">4.4</a>, <a href="#rfc.xref.Part1.8">4.4</a>, <a href="#rfc.xref.Part1.9"></a>, <a href="#rfc.xref.Part1.10"></a>, <a href="#rfc.xref.Part1.11">8</a>, <a href="#rfc.xref.Part1.12">8</a>, <a href="#rfc.xref.Part1.13">9</a>, <a href="#Part1"><b>10.1</b></a>, <a href="#rfc.xref.Part1.14">B</a>, <a href="#rfc.xref.Part1.15">B</a>, <a href="#rfc.xref.Part1.16">B</a>, <a href="#rfc.xref.Part1.17">B</a>, <a href="#rfc.xref.Part1.18">B</a>, <a href="#rfc.xref.Part1.19">B</a>, <a href="#rfc.xref.Part1.20">B</a>, <a href="#rfc.xref.Part1.21">B</a>, <a href="#rfc.xref.Part1.22">C</a><ul>
2277                        <li><em>Section 1.2</em>&nbsp;&nbsp;<a href="#rfc.xref.Part1.22">C</a></li>
2278                        <li><em>Section 2.5</em>&nbsp;&nbsp;<a href="#rfc.xref.Part1.1">1.1</a></li>
2279                        <li><em>Section 2.7</em>&nbsp;&nbsp;<a href="#rfc.xref.Part1.19">B</a>, <a href="#rfc.xref.Part1.21">B</a></li>
2280                        <li><em>Section 3.2</em>&nbsp;&nbsp;<a href="#rfc.xref.Part1.5">4.1</a>, <a href="#rfc.xref.Part1.16">B</a></li>
2281                        <li><em>Section 3.2.3</em>&nbsp;&nbsp;<a href="#rfc.xref.Part1.15">B</a></li>
2282                        <li><em>Section 3.2.6</em>&nbsp;&nbsp;<a href="#rfc.xref.Part1.17">B</a>, <a href="#rfc.xref.Part1.18">B</a></li>
2283                        <li><em>Section 3.3.3</em>&nbsp;&nbsp;<a href="#rfc.xref.Part1.12">8</a></li>
2284                        <li><em>Section 5.5</em>&nbsp;&nbsp;<a href="#rfc.xref.Part1.4">4</a>, <a href="#rfc.xref.Part1.6">4.4</a>, <a href="#rfc.xref.Part1.7">4.4</a>, <a href="#rfc.xref.Part1.8">4.4</a></li>
2285                        <li><em>Section 5.7.1</em>&nbsp;&nbsp;<a href="#rfc.xref.Part1.20">B</a></li>
2286                        <li><em>Section 5.7.2</em>&nbsp;&nbsp;<a href="#rfc.xref.Part1.9"></a>, <a href="#rfc.xref.Part1.10"></a></li>
2287                        <li><em>Section 7</em>&nbsp;&nbsp;<a href="#rfc.xref.Part1.2">1.2</a></li>
2288                        <li><em>Section 10</em>&nbsp;&nbsp;<a href="#rfc.xref.Part1.13">9</a></li>
2289                     </ul>
2290                  </li>
2291                  <li><em>Part2</em>&nbsp;&nbsp;<a href="#rfc.xref.Part2.1">2</a>, <a href="#rfc.xref.Part2.2">2</a>, <a href="#rfc.xref.Part2.3">4</a>, <a href="#rfc.xref.Part2.4">4.1</a>, <a href="#rfc.xref.Part2.5">4.2.2</a>, <a href="#rfc.xref.Part2.6">4.2.3</a>, <a href="#rfc.xref.Part2.7">4.4</a>, <a href="#rfc.xref.Part2.8">5.3</a>, <a href="#rfc.xref.Part2.9">8</a>, <a href="#Part2"><b>10.1</b></a>, <a href="#rfc.xref.Part2.10">B</a><ul>
2292                        <li><em>Section 4.2.1</em>&nbsp;&nbsp;<a href="#rfc.xref.Part2.3">4</a>, <a href="#rfc.xref.Part2.7">4.4</a></li>
2293                        <li><em>Section 4.3.1</em>&nbsp;&nbsp;<a href="#rfc.xref.Part2.2">2</a></li>
2294                        <li><em>Section 6.1</em>&nbsp;&nbsp;<a href="#rfc.xref.Part2.5">4.2.2</a></li>
2295                        <li><em>Section</em>&nbsp;&nbsp;<a href="#rfc.xref.Part2.8">5.3</a>, <a href="#rfc.xref.Part2.10">B</a></li>
2296                        <li><em>Section</em>&nbsp;&nbsp;<a href="#rfc.xref.Part2.6">4.2.3</a></li>
2297                        <li><em>Section 7.1.4</em>&nbsp;&nbsp;<a href="#rfc.xref.Part2.4">4.1</a></li>
2298                     </ul>
2299                  </li>
2300                  <li><em>Part4</em>&nbsp;&nbsp;<a href="#rfc.xref.Part4.1">4.2.2</a>, <a href="#rfc.xref.Part4.2">4.3</a>, <a href="#rfc.xref.Part4.3">4.3.1</a>, <a href="#rfc.xref.Part4.4">4.3.1</a>, <a href="#rfc.xref.Part4.5">4.3.2</a>, <a href="#rfc.xref.Part4.6">4.3.2</a>, <a href="#rfc.xref.Part4.7">4.3.2</a>, <a href="#rfc.xref.Part4.8">4.3.4</a>, <a href="#Part4"><b>10.1</b></a><ul>
2301                        <li><em>Section 2.1</em>&nbsp;&nbsp;<a href="#rfc.xref.Part4.8">4.3.4</a></li>
2302                        <li><em>Section 2.2</em>&nbsp;&nbsp;<a href="#rfc.xref.Part4.1">4.2.2</a>, <a href="#rfc.xref.Part4.3">4.3.1</a></li>
2303                        <li><em>Section 2.3</em>&nbsp;&nbsp;<a href="#rfc.xref.Part4.4">4.3.1</a></li>
2304                        <li><em>Section 3.2</em>&nbsp;&nbsp;<a href="#rfc.xref.Part4.6">4.3.2</a></li>
2305                        <li><em>Section 3.3</em>&nbsp;&nbsp;<a href="#rfc.xref.Part4.7">4.3.2</a></li>
2306                        <li><em>Section 6</em>&nbsp;&nbsp;<a href="#rfc.xref.Part4.5">4.3.2</a></li>
2307                     </ul>
2308                  </li>
2309                  <li><em>Part5</em>&nbsp;&nbsp;<a href="#rfc.xref.Part5.1">3.1</a>, <a href="#rfc.xref.Part5.2">3.3</a>, <a href="#rfc.xref.Part5.3">3.3</a>, <a href="#rfc.xref.Part5.4">4.3.2</a>, <a href="#rfc.xref.Part5.5">4.3.2</a>, <a href="#Part5"><b>10.1</b></a><ul>
2310                        <li><em>Section 3.2</em>&nbsp;&nbsp;<a href="#rfc.xref.Part5.5">4.3.2</a></li>
2311                        <li><em>Section 4.3</em>&nbsp;&nbsp;<a href="#rfc.xref.Part5.3">3.3</a></li>
2312                     </ul>
2313                  </li>
2314                  <li><em>Part7</em>&nbsp;&nbsp;<a href="#rfc.xref.Part7.1">3</a>, <a href="#rfc.xref.Part7.2">3.2</a>, <a href="#Part7"><b>10.1</b></a><ul>
2315                        <li><em>Section 4.1</em>&nbsp;&nbsp;<a href="#rfc.xref.Part7.1">3</a>, <a href="#rfc.xref.Part7.2">3.2</a></li>
2316                     </ul>
2317                  </li>
2318                  <li>Pragma header field&nbsp;&nbsp;<a href="#rfc.xref.header.pragma.1">4</a>, <a href="#rfc.iref.p.5"><b>5.4</b></a>, <a href="#rfc.xref.header.pragma.2">7.3</a>, <a href="#rfc.xref.header.pragma.3">A</a></li>
2319                  <li>private (cache directive)&nbsp;&nbsp;<a href="#rfc.iref.p.3"><b></b></a></li>
2320                  <li>private cache&nbsp;&nbsp;<a href="#rfc.iref.p.1">1</a></li>
2321                  <li>proxy-revalidate (cache directive)&nbsp;&nbsp;<a href="#rfc.iref.p.4"><b></b></a></li>
2322                  <li>public (cache directive)&nbsp;&nbsp;<a href="#rfc.iref.p.2"><b></b></a></li>
2323               </ul>
2324            </li>
2325            <li><a id="rfc.index.R" href="#rfc.index.R"><b>R</b></a><ul>
2326                  <li>Response is Stale (warn-text)&nbsp;&nbsp;<a href="#rfc.xref.warn.110.1">4.2.4</a>, <a href="#rfc.iref.r.1"><b>5.5.1</b></a>, <a href="#rfc.xref.warn.110.2">7.2.2</a></li>
2327                  <li>Revalidation Failed (warn-text)&nbsp;&nbsp;<a href="#rfc.iref.r.2"><b>5.5.2</b></a>, <a href="#rfc.xref.warn.111.1">7.2.2</a></li>
2328                  <li><em>RFC2119</em>&nbsp;&nbsp;<a href="#rfc.xref.RFC2119.1">1.1</a>, <a href="#RFC2119"><b>10.1</b></a></li>
2329                  <li><em>RFC2616</em>&nbsp;&nbsp;<a href="#rfc.xref.RFC2616.1">4.2.2</a>, <a href="#RFC2616"><b>10.2</b></a><ul>
2330                        <li><em>Section 13.9</em>&nbsp;&nbsp;<a href="#rfc.xref.RFC2616.1">4.2.2</a></li>
2331                     </ul>
2332                  </li>
2333                  <li><em>RFC5226</em>&nbsp;&nbsp;<a href="#rfc.xref.RFC5226.1">7.1.1</a>, <a href="#rfc.xref.RFC5226.2">7.2.1</a>, <a href="#RFC5226"><b>10.2</b></a><ul>
2334                        <li><em>Section 4.1</em>&nbsp;&nbsp;<a href="#rfc.xref.RFC5226.1">7.1.1</a>, <a href="#rfc.xref.RFC5226.2">7.2.1</a></li>
2335                     </ul>
2336                  </li>
2337                  <li><em>RFC5234</em>&nbsp;&nbsp;<a href="#rfc.xref.RFC5234.1">1.2</a>, <a href="#RFC5234"><b>10.1</b></a>, <a href="#rfc.xref.RFC5234.2">B</a><ul>
2338                        <li><em>Appendix B.1</em>&nbsp;&nbsp;<a href="#rfc.xref.RFC5234.2">B</a></li>
2339                     </ul>
2340                  </li>
2341                  <li><em>RFC5861</em>&nbsp;&nbsp;<a href="#rfc.xref.RFC5861.1">7.1.3</a>, <a href="#rfc.xref.RFC5861.2">7.1.3</a>, <a href="#RFC5861"><b>10.2</b></a><ul>
2342                        <li><em>Section 3</em>&nbsp;&nbsp;<a href="#rfc.xref.RFC5861.2">7.1.3</a></li>
2343                        <li><em>Section 4</em>&nbsp;&nbsp;<a href="#rfc.xref.RFC5861.1">7.1.3</a></li>
2344                     </ul>
2345                  </li>
2346                  <li><em>RFC5905</em>&nbsp;&nbsp;<a href="#rfc.xref.RFC5905.1">4.2.3</a>, <a href="#RFC5905"><b>10.2</b></a></li>
2347                  <li><em>RFC6265</em>&nbsp;&nbsp;<a href="#rfc.xref.RFC6265.1">8</a>, <a href="#RFC6265"><b>10.2</b></a></li>
2348               </ul>
2349            </li>
2350            <li><a id="rfc.index.S" href="#rfc.index.S"><b>S</b></a><ul>
2351                  <li>s-maxage (cache directive)&nbsp;&nbsp;<a href="#rfc.iref.s.4"><b></b></a></li>
2352                  <li>shared cache&nbsp;&nbsp;<a href="#rfc.iref.s.1">1</a></li>
2353                  <li>stale&nbsp;&nbsp;<a href="#rfc.iref.s.2">4.2</a></li>
2354                  <li>strong validator&nbsp;&nbsp;<a href="#rfc.iref.s.3">4.3.4</a></li>
2355               </ul>
2356            </li>
2357            <li><a id="rfc.index.T" href="#rfc.index.T"><b>T</b></a><ul>
2358                  <li>Transformation Applied (warn-text)&nbsp;&nbsp;<a href="#rfc.iref.t.1"><b>5.5.6</b></a>, <a href="#rfc.xref.warn.214.1">7.2.2</a></li>
2359               </ul>
2360            </li>
2361            <li><a id="rfc.index.V" href="#rfc.index.V"><b>V</b></a><ul>
2362                  <li>validator&nbsp;&nbsp;<a href="#rfc.iref.v.1">4.3.1</a></li>
2363               </ul>
2364            </li>
2365            <li><a id="rfc.index.W" href="#rfc.index.W"><b>W</b></a><ul>
2366                  <li>Warning header field&nbsp;&nbsp;<a href="#rfc.xref.header.warning.1">3.3</a>, <a href="#rfc.xref.header.warning.2">4.3.4</a>, <a href="#rfc.xref.header.warning.3">4.3.5</a>, <a href="#rfc.iref.w.1"><b>5.5</b></a>, <a href="#rfc.xref.header.warning.4">7.3</a>, <a href="#rfc.xref.header.warning.5">A</a></li>
2367               </ul>
2368            </li>
2369         </ul>
2370      </div>
2371   </body>
Note: See TracBrowser for help on using the repository browser.