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

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

update XSLTs, switch to Saxon 9.6 HE in Makefile, regen specs

  • Property svn:eol-style set to native
  • Property svn:mime-type set to text/html;charset=utf-8
File size: 203.0 KB
Line 
1<!DOCTYPE html
2  PUBLIC "-//W3C//DTD HTML 4.01//EN">
3<html lang="en">
4   <head profile="http://dublincore.org/documents/2008/08/04/dc-html/">
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;
8
9function initFeedback() {
10  var fb = document.createElement("div");
11  fb.className = "feedback noprint";
12  fb.setAttribute("onclick", "feedback();");
13  fb.appendChild(document.createTextNode("feedback"));
14
15  document.body.appendChild(fb);
16}
17
18function feedback() {
19  toggleButtonsToElementsByName("h1");
20  toggleButtonsToElementsByName("h2");
21  toggleButtonsToElementsByName("h3");
22  toggleButtonsToElementsByName("h4");
23
24  buttonsAdded = !buttonsAdded;
25}
26
27function toggleButtonsToElementsByName(name) {
28  var list = document.getElementsByTagName(name);
29  for (var i = 0; i < list.length; i++) {
30    toggleButton(list.item(i));
31  }
32}
33
34function toggleButton(node) {
35  if (! buttonsAdded) {
36
37    // docname
38    var template = "mailto:ietf-http-wg@w3.org?subject={docname},%20%22{section}%22&body=<{ref}>:";
39
40    var id = node.getAttribute("id");
41    // better id available?
42    var titlelinks = node.getElementsByTagName("a");
43    for (var i = 0; i < titlelinks.length; i++) {
44      var tl = titlelinks.item(i);
45      if (tl.getAttribute("id")) {
46        id = tl.getAttribute("id");
47      }
48    }
49
50    // ref
51    var ref = window.location.toString();
52    var hash = ref.indexOf("#");
53    if (hash != -1) {
54      ref = ref.substring(0, hash);
55    }
56    if (id != "") {
57      ref += "#" + id;
58    }
59
60    // docname
61    var docname = "draft-ietf-httpbis-p6-cache-latest";
62
63    // section
64    var section = node.textContent;
65    section = section.replace("\u00a0", " ");
66
67    // build URI from template
68    var uri = template.replace("{docname}", encodeURIComponent(docname));
69    uri = uri.replace("{section}", encodeURIComponent(section));
70    uri = uri.replace("{ref}", encodeURIComponent(ref));
71
72    var button = document.createElement("a");
73    button.className = "fbbutton noprint";
74    button.setAttribute("href", uri);
75    button.appendChild(document.createTextNode("send feedback"));
76    node.appendChild(button);
77  }
78  else {
79    var buttons = node.getElementsByTagName("a");
80    for (var i = 0; i < buttons.length; i++) {
81      var b = buttons.item(i);
82      if (b.className == "fbbutton noprint") {
83        node.removeChild(b);
84      }
85    }
86  }
87}</script><style type="text/css" title="Xml2Rfc (sans serif)">
88a {
89  text-decoration: none;
90}
91a.smpl {
92  color: black;
93}
94a:hover {
95  text-decoration: underline;
96}
97a:active {
98  text-decoration: underline;
99}
100address {
101  margin-top: 1em;
102  margin-left: 2em;
103  font-style: normal;
104}
105body {
106  color: black;
107  font-family: cambria, georgia, serif;
108  font-size: 12pt;
109  margin: 2em auto;
110  max-width: 1000px;
111}
112samp, tt, code, pre {
113  font-family: consolas, monaco, monospace;
114}
115cite {
116  font-style: normal;
117}
118div.note {
119  margin-left: 2em;
120}
121dl {
122  margin-left: 2em;
123}
124dl > dt {
125  float: left;
126  margin-right: 1em;
127}
128dl.nohang > dt {
129  float: none;
130}
131dl > dd {
132  margin-bottom: .5em;
133}
134dl.compact > dd {
135  margin-bottom: .0em;
136}
137dl > dd > dl {
138  margin-top: 0.5em;
139}
140ul.empty {
141  list-style-type: none;
142}
143ul.empty li {
144  margin-top: .5em;
145}
146dl p {
147  margin-left: 0em;
148}
149h1 {
150  font-size: 130%;
151  line-height: 21pt;
152  page-break-after: avoid;
153}
154h1.np {
155  page-break-before: always;
156}
157h2 {
158  font-size: 120%;
159  line-height: 15pt;
160  page-break-after: avoid;
161}
162h3 {
163  font-size: 110%;
164  page-break-after: avoid;
165}
166h4, h5, h6 {
167  page-break-after: avoid;
168}
169h1 a, h2 a, h3 a, h4 a, h5 a, h6 a {
170  color: black;
171}
172img {
173  margin-left: 3em;
174}
175li {
176  margin-left: 2em;
177}
178ol {
179  margin-left: 2em;
180}
181ol.la {
182  list-style-type: lower-alpha;
183}
184ol.ua {
185  list-style-type: upper-alpha;
186}
187ol p {
188  margin-left: 0em;
189}
190p {
191  margin-left: 2em;
192}
193pre {
194  font-size: 11pt;
195  margin-left: 3em;
196  background-color: lightyellow;
197  padding: .25em;
198  page-break-inside: avoid;
199}
200pre.text2 {
201  border-style: dotted;
202  border-width: 1px;
203  background-color: #f0f0f0;
204}
205pre.inline {
206  background-color: white;
207  padding: 0em;
208  page-break-inside: auto;
209}
210pre.text {
211  border-style: dotted;
212  border-width: 1px;
213  background-color: #f8f8f8;
214}
215pre.drawing {
216  border-style: solid;
217  border-width: 1px;
218  background-color: #f8f8f8;
219  padding: 2em;
220}
221sup {
222  font-size: 60%;
223}
224table {
225  margin-left: 2em;
226}
227table.tt {
228  vertical-align: top;
229  border-color: gray;
230}
231table.tt th {
232  border-color: gray;
233}
234table.tt td {
235  border-color: gray;
236}
237table.all {
238  border-style: solid;
239  border-width: 2px;
240}
241table.full {
242  border-style: solid;
243  border-width: 2px;
244}
245table.tt td {
246  vertical-align: top;
247}
248table.all td {
249  border-style: solid;
250  border-width: 1px;
251}
252table.full td {
253  border-style: none solid;
254  border-width: 1px;
255}
256table.tt th {
257  vertical-align: top;
258}
259table.all th {
260  border-style: solid;
261  border-width: 1px;
262}
263table.full th {
264  border-style: solid;
265  border-width: 1px 1px 2px 1px;
266}
267table.headers th {
268  border-style: none none solid none;
269  border-width: 2px;
270}
271table.left {
272  margin-right: auto;
273}
274table.right {
275  margin-left: auto;
276}
277table.center {
278  margin-left: auto;
279  margin-right: auto;
280}
281caption {
282  caption-side: bottom;
283  font-weight: bold;
284  font-size: 10pt;
285  margin-top: .5em;
286}
287
288table.header {
289  border-spacing: 1px;
290  width: 95%;
291  font-size: 11pt;
292  color: white;
293}
294td.top {
295  vertical-align: top;
296}
297td.topnowrap {
298  vertical-align: top;
299  white-space: nowrap;
300}
301table.header td {
302  background-color: gray;
303  width: 50%;
304}
305table.header a {
306  color: white;
307}
308td.reference {
309  vertical-align: top;
310  white-space: nowrap;
311  padding-right: 1em;
312}
313thead {
314  display:table-header-group;
315}
316ul.toc, ul.toc ul {
317  list-style: none;
318  margin-left: 1.5em;
319  padding-left: 0em;
320}
321ul.toc li {
322  line-height: 150%;
323  font-weight: bold;
324  margin-left: 0em;
325}
326ul.toc li li {
327  line-height: normal;
328  font-weight: normal;
329  font-size: 11pt;
330  margin-left: 0em;
331}
332li.excluded {
333  font-size: 0pt;
334}
335ul p {
336  margin-left: 0em;
337}
338.title, .filename, h1, h2, h3, h4 {
339  font-family: candara, calibri, segoe, optima, arial, sans-serif;
340}
341ul.ind, ul.ind ul {
342  list-style: none;
343  margin-left: 1.5em;
344  padding-left: 0em;
345  page-break-before: avoid;
346}
347ul.ind li {
348  font-weight: bold;
349  line-height: 200%;
350  margin-left: 0em;
351}
352ul.ind li li {
353  font-weight: normal;
354  line-height: 150%;
355  margin-left: 0em;
356}
357.avoidbreakinside {
358  page-break-inside: avoid;
359}
360.avoidbreakafter {
361  page-break-after: avoid;
362}
363.bcp14 {
364  font-style: normal;
365  text-transform: lowercase;
366  font-variant: small-caps;
367}
368.comment {
369  background-color: yellow;
370}
371.center {
372  text-align: center;
373}
374.error {
375  color: red;
376  font-style: italic;
377  font-weight: bold;
378}
379.figure {
380  font-weight: bold;
381  text-align: center;
382  font-size: 10pt;
383}
384.filename {
385  color: #333333;
386  font-size: 75%;
387  font-weight: bold;
388  line-height: 21pt;
389  text-align: center;
390}
391.fn {
392  font-weight: bold;
393}
394.left {
395  text-align: left;
396}
397.right {
398  text-align: right;
399}
400.title {
401  color: green;
402  font-size: 150%;
403  line-height: 18pt;
404  font-weight: bold;
405  text-align: center;
406  margin-top: 36pt;
407}
408.warning {
409  font-size: 130%;
410  background-color: yellow;
411}.feedback {
412  position: fixed;
413  bottom: 1%;
414  right: 1%;
415  padding: 3px 5px;
416  color: white;
417  border-radius: 5px;
418  background: #006400;
419  border: 1px solid silver;
420  -webkit-user-select: none;
421  -moz-user-select: none;
422  -ms-user-select: none;
423}
424.fbbutton {
425  margin-left: 1em;
426  color: #303030;
427  font-size: small;
428  font-weight: normal;
429  background: #d0d000;
430  padding: 1px 4px;
431  border: 1px solid silver;
432  border-radius: 5px;
433}
434
435@media screen {
436  pre.text, pre.text2 {
437    width: 69em;
438  }
439}
440
441@media print {
442  .noprint {
443    display: none;
444  }
445
446  a {
447    color: black;
448    text-decoration: none;
449  }
450
451  table.header {
452    width: 90%;
453  }
454
455  td.header {
456    width: 50%;
457    color: black;
458    background-color: white;
459    vertical-align: top;
460    font-size: 110%;
461  }
462
463  ul.toc a:last-child::after {
464    content: leader('.') target-counter(attr(href), page);
465  }
466
467  ul.ind li li a {
468    content: target-counter(attr(href), page);
469  }
470
471  pre {
472    font-size: 10pt;
473  }
474
475  .print2col {
476    column-count: 2;
477    -moz-column-count: 2;
478    column-fill: auto;
479  }
480}
481
482@page {
483  @top-left {
484       content: "Internet-Draft";
485  }
486  @top-right {
487       content: "June 2014";
488  }
489  @top-center {
490       content: "HTTP/1.1 Caching";
491  }
492  @bottom-left {
493       content: "Fielding, et al.";
494  }
495  @bottom-center {
496       content: "Expires December 2014";
497  }
498  @bottom-right {
499       content: "[Page " counter(page) "]";
500  }
501}
502
503@page:first {
504    @top-left {
505      content: normal;
506    }
507    @top-right {
508      content: normal;
509    }
510    @top-center {
511      content: normal;
512    }
513}
514</style><link rel="Contents" href="#rfc.toc">
515      <link rel="Author" href="#rfc.authors">
516      <link rel="Copyright" href="#rfc.copyrightnotice">
517      <link rel="Index" href="#rfc.index">
518      <link rel="Chapter" title="1 Introduction" href="#rfc.section.1">
519      <link rel="Chapter" title="2 Overview of Cache Operation" href="#rfc.section.2">
520      <link rel="Chapter" title="3 Storing Responses in Caches" href="#rfc.section.3">
521      <link rel="Chapter" title="4 Constructing Responses from Caches" href="#rfc.section.4">
522      <link rel="Chapter" title="5 Header Field Definitions" href="#rfc.section.5">
523      <link rel="Chapter" title="6 History Lists" href="#rfc.section.6">
524      <link rel="Chapter" title="7 IANA Considerations" href="#rfc.section.7">
525      <link rel="Chapter" title="8 Security Considerations" href="#rfc.section.8">
526      <link rel="Chapter" title="9 Acknowledgments" href="#rfc.section.9">
527      <link rel="Chapter" href="#rfc.section.10" title="10 References">
528      <link rel="Appendix" title="A Changes from RFC 2616" href="#rfc.section.A">
529      <link rel="Appendix" title="B Imported ABNF" href="#rfc.section.B">
530      <link rel="Appendix" title="C Collected ABNF" href="#rfc.section.C">
531      <link rel="Alternate" title="RFC7234" href="http://svn.tools.ietf.org/svn/wg/httpbis/specs/rfc7234.html">
532      <link href="p5-range.html" rel="prev">
533      <link href="p7-auth.html" rel="next">
534      <meta name="generator" content="http://greenbytes.de/tech/webdav/rfc2629.xslt, Revision 1.710, 2014/12/09 13:12:18, XSLT vendor: Saxonica http://www.saxonica.com/">
535      <meta name="keywords" content="Hypertext Transfer Protocol, HTTP, HTTP Caching">
536      <link rel="schema.dct" href="http://purl.org/dc/terms/">
537      <meta name="dct.creator" content="Fielding, R.">
538      <meta name="dct.creator" content="Nottingham, M.">
539      <meta name="dct.creator" content="Reschke, J. F.">
540      <meta name="dct.identifier" content="urn:ietf:id:draft-ietf-httpbis-p6-cache-latest">
541      <meta name="dct.issued" scheme="ISO8601" content="2014-06">
542      <meta name="dct.replaces" content="urn:ietf:rfc:2616">
543      <meta name="dct.abstract" content="The Hypertext Transfer Protocol (HTTP) is a stateless 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.">
544      <meta name="description" content="The Hypertext Transfer Protocol (HTTP) is a stateless 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.">
545   </head>
546   <body onload="initFeedback();">
547      <table class="header" id="rfc.headerblock">
548         <tbody>
549            <tr>
550               <td class="left">HTTPbis Working Group</td>
551               <td class="right">R. Fielding, Editor</td>
552            </tr>
553            <tr>
554               <td class="left">Internet-Draft</td>
555               <td class="right">Adobe</td>
556            </tr>
557            <tr>
558               <td class="left">Obsoletes: <a href="https://tools.ietf.org/html/rfc2616">2616</a> (if approved)
559               </td>
560               <td class="right">M. Nottingham, Editor</td>
561            </tr>
562            <tr>
563               <td class="left">Intended status: Standards Track</td>
564               <td class="right">Akamai</td>
565            </tr>
566            <tr>
567               <td class="left">Expires: December 2014</td>
568               <td class="right">J. Reschke, Editor</td>
569            </tr>
570            <tr>
571               <td class="left"></td>
572               <td class="right">greenbytes</td>
573            </tr>
574            <tr>
575               <td class="left"></td>
576               <td class="right">June 2014</td>
577            </tr>
578         </tbody>
579      </table>
580      <p class="title" id="rfc.title">Hypertext Transfer Protocol (HTTP/1.1): Caching<br><span class="filename">draft-ietf-httpbis-p6-cache-latest</span></p>
581      <p style="color: green; text-align: center; font-size: 14pt; background-color: yellow;"><b>Note:</b> a later version of this document has been published as <a href="http://svn.tools.ietf.org/svn/wg/httpbis/specs/rfc7234.html">RFC7234</a>.
582         
583      </p>
584      <h1 id="rfc.abstract"><a href="#rfc.abstract">Abstract</a></h1>
585      <p>The Hypertext Transfer Protocol (HTTP) is a stateless application-level protocol for
586         distributed, collaborative, hypertext information systems. This document defines HTTP
587         caches and the associated header fields that control cache behavior or indicate cacheable
588         response messages.
589      </p>
590      <h1 id="rfc.note.1"><a href="#rfc.note.1">Editorial Note (To be removed by RFC Editor)</a></h1>
591      <p>Discussion of this draft takes place on the HTTPBIS working group mailing list (ietf-http-wg@w3.org),
592         which is archived at &lt;<a href="http://lists.w3.org/Archives/Public/ietf-http-wg/">http://lists.w3.org/Archives/Public/ietf-http-wg/</a>&gt;.
593      </p>
594      <p>The current issues list is at &lt;<a href="http://tools.ietf.org/wg/httpbis/trac/report/3">http://tools.ietf.org/wg/httpbis/trac/report/3</a>&gt; and related documents (including fancy diffs) can be found at &lt;<a href="http://tools.ietf.org/wg/httpbis/">http://tools.ietf.org/wg/httpbis/</a>&gt;.
595      </p>
596      <p><em>This is a temporary document for the purpose of tracking the editorial changes made
597            during the AUTH48 (RFC publication) phase.</em>
598      </p>
599      <div id="rfc.status">
600         <h1><a href="#rfc.status">Status of This Memo</a></h1>
601         <p>This Internet-Draft is submitted in full conformance with the provisions of BCP 78
602            and BCP 79.
603         </p>
604         <p>Internet-Drafts are working documents of the Internet Engineering Task Force (IETF).
605            Note that other groups may also distribute working documents as Internet-Drafts. The
606            list of current Internet-Drafts is at <a href="http://datatracker.ietf.org/drafts/current/">http://datatracker.ietf.org/drafts/current/</a>.
607         </p>
608         <p>Internet-Drafts are draft documents valid for a maximum of six months and may be updated,
609            replaced, or obsoleted by other documents at any time. It is inappropriate to use
610            Internet-Drafts as reference material or to cite them other than as “work in progress”.
611         </p>
612         <p>This Internet-Draft will expire in December 2014.</p>
613      </div>
614      <div id="rfc.copyrightnotice">
615         <h1><a href="#rfc.copyrightnotice">Copyright Notice</a></h1>
616         <p>Copyright © 2014 IETF Trust and the persons identified as the document authors. All
617            rights reserved.
618         </p>
619         <p>This document is subject to BCP 78 and the IETF Trust's Legal Provisions Relating
620            to IETF Documents (<a href="http://trustee.ietf.org/license-info">http://trustee.ietf.org/license-info</a>) in effect on the date of publication of this document. Please review these documents
621            carefully, as they describe your rights and restrictions with respect to this document.
622            Code Components extracted from this document must include Simplified BSD License text
623            as described in Section 4.e of the Trust Legal Provisions and are provided without
624            warranty as described in the Simplified BSD License.
625         </p>
626         <p>This document may contain material from IETF Documents or IETF Contributions published
627            or made publicly available before November 10, 2008. The person(s) controlling the
628            copyright in some of this material may not have granted the IETF Trust the right to
629            allow modifications of such material outside the IETF Standards Process. Without obtaining
630            an adequate license from the person(s) controlling the copyright in such materials,
631            this document may not be modified outside the IETF Standards Process, and derivative
632            works of it may not be created outside the IETF Standards Process, except to format
633            it for publication as an RFC or to translate it into languages other than English.
634         </p>
635      </div>
636      <hr class="noprint">
637      <div id="rfc.toc">
638         <h1 class="np"><a href="#rfc.toc">Table of Contents</a></h1>
639         <ul class="toc">
640            <li><a href="#rfc.section.1">1.</a>&nbsp;&nbsp;&nbsp;<a href="#caching">Introduction</a><ul>
641                  <li><a href="#rfc.section.1.1">1.1</a>&nbsp;&nbsp;&nbsp;<a href="#conformance">Conformance and Error Handling</a></li>
642                  <li><a href="#rfc.section.1.2">1.2</a>&nbsp;&nbsp;&nbsp;<a href="#notation">Syntax Notation</a><ul>
643                        <li><a href="#rfc.section.1.2.1">1.2.1</a>&nbsp;&nbsp;&nbsp;<a href="#delta-seconds">Delta Seconds</a></li>
644                     </ul>
645                  </li>
646               </ul>
647            </li>
648            <li><a href="#rfc.section.2">2.</a>&nbsp;&nbsp;&nbsp;<a href="#caching.overview">Overview of Cache Operation</a></li>
649            <li><a href="#rfc.section.3">3.</a>&nbsp;&nbsp;&nbsp;<a href="#response.cacheability">Storing Responses in Caches</a><ul>
650                  <li><a href="#rfc.section.3.1">3.1</a>&nbsp;&nbsp;&nbsp;<a href="#incomplete.responses">Storing Incomplete Responses</a></li>
651                  <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>
652                  <li><a href="#rfc.section.3.3">3.3</a>&nbsp;&nbsp;&nbsp;<a href="#combining.responses">Combining Partial Content</a></li>
653               </ul>
654            </li>
655            <li><a href="#rfc.section.4">4.</a>&nbsp;&nbsp;&nbsp;<a href="#constructing.responses.from.caches">Constructing Responses from Caches</a><ul>
656                  <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>
657                  <li><a href="#rfc.section.4.2">4.2</a>&nbsp;&nbsp;&nbsp;<a href="#expiration.model">Freshness</a><ul>
658                        <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>
659                        <li><a href="#rfc.section.4.2.2">4.2.2</a>&nbsp;&nbsp;&nbsp;<a href="#heuristic.freshness">Calculating Heuristic Freshness</a></li>
660                        <li><a href="#rfc.section.4.2.3">4.2.3</a>&nbsp;&nbsp;&nbsp;<a href="#age.calculations">Calculating Age</a></li>
661                        <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>
662                     </ul>
663                  </li>
664                  <li><a href="#rfc.section.4.3">4.3</a>&nbsp;&nbsp;&nbsp;<a href="#validation.model">Validation</a><ul>
665                        <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>
666                        <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>
667                        <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>
668                        <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>
669                        <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>
670                     </ul>
671                  </li>
672                  <li><a href="#rfc.section.4.4">4.4</a>&nbsp;&nbsp;&nbsp;<a href="#invalidation">Invalidation</a></li>
673               </ul>
674            </li>
675            <li><a href="#rfc.section.5">5.</a>&nbsp;&nbsp;&nbsp;<a href="#header.field.definitions">Header Field Definitions</a><ul>
676                  <li><a href="#rfc.section.5.1">5.1</a>&nbsp;&nbsp;&nbsp;<a href="#header.age">Age</a></li>
677                  <li><a href="#rfc.section.5.2">5.2</a>&nbsp;&nbsp;&nbsp;<a href="#header.cache-control">Cache-Control</a><ul>
678                        <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></li>
679                        <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></li>
680                        <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>
681                     </ul>
682                  </li>
683                  <li><a href="#rfc.section.5.3">5.3</a>&nbsp;&nbsp;&nbsp;<a href="#header.expires">Expires</a></li>
684                  <li><a href="#rfc.section.5.4">5.4</a>&nbsp;&nbsp;&nbsp;<a href="#header.pragma">Pragma</a></li>
685                  <li><a href="#rfc.section.5.5">5.5</a>&nbsp;&nbsp;&nbsp;<a href="#header.warning">Warning</a><ul>
686                        <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>
687                        <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>
688                        <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>
689                        <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>
690                        <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>
691                        <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>
692                        <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>
693                     </ul>
694                  </li>
695               </ul>
696            </li>
697            <li><a href="#rfc.section.6">6.</a>&nbsp;&nbsp;&nbsp;<a href="#history.lists">History Lists</a></li>
698            <li><a href="#rfc.section.7">7.</a>&nbsp;&nbsp;&nbsp;<a href="#iana.considerations">IANA Considerations</a><ul>
699                  <li><a href="#rfc.section.7.1">7.1</a>&nbsp;&nbsp;&nbsp;<a href="#cache.directive.registry">Cache Directive Registry</a><ul>
700                        <li><a href="#rfc.section.7.1.1">7.1.1</a>&nbsp;&nbsp;&nbsp;<a href="#cache.directive.registry.procedure">Procedure</a></li>
701                        <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>
702                        <li><a href="#rfc.section.7.1.3">7.1.3</a>&nbsp;&nbsp;&nbsp;<a href="#cache.directive.registration">Registrations</a></li>
703                     </ul>
704                  </li>
705                  <li><a href="#rfc.section.7.2">7.2</a>&nbsp;&nbsp;&nbsp;<a href="#warn.code.registry">Warn Code Registry</a><ul>
706                        <li><a href="#rfc.section.7.2.1">7.2.1</a>&nbsp;&nbsp;&nbsp;<a href="#warn.code.registry.procedure">Procedure</a></li>
707                        <li><a href="#rfc.section.7.2.2">7.2.2</a>&nbsp;&nbsp;&nbsp;<a href="#warn.code.registration">Registrations</a></li>
708                     </ul>
709                  </li>
710                  <li><a href="#rfc.section.7.3">7.3</a>&nbsp;&nbsp;&nbsp;<a href="#header.field.registration">Header Field Registration</a></li>
711               </ul>
712            </li>
713            <li><a href="#rfc.section.8">8.</a>&nbsp;&nbsp;&nbsp;<a href="#security.considerations">Security Considerations</a></li>
714            <li><a href="#rfc.section.9">9.</a>&nbsp;&nbsp;&nbsp;<a href="#acks">Acknowledgments</a></li>
715            <li><a href="#rfc.section.10">10.</a>&nbsp;&nbsp;&nbsp;<a href="#rfc.references">References</a><ul>
716                  <li><a href="#rfc.section.10.1">10.1</a>&nbsp;&nbsp;&nbsp;<a href="#rfc.references.1">Normative References</a></li>
717                  <li><a href="#rfc.section.10.2">10.2</a>&nbsp;&nbsp;&nbsp;<a href="#rfc.references.2">Informative References</a></li>
718               </ul>
719            </li>
720            <li><a href="#rfc.section.A">A.</a>&nbsp;&nbsp;&nbsp;<a href="#changes.from.rfc.2616">Changes from RFC 2616</a></li>
721            <li><a href="#rfc.section.B">B.</a>&nbsp;&nbsp;&nbsp;<a href="#imported.abnf">Imported ABNF</a></li>
722            <li><a href="#rfc.section.C">C.</a>&nbsp;&nbsp;&nbsp;<a href="#collected.abnf">Collected ABNF</a></li>
723            <li><a href="#rfc.index">Index</a></li>
724            <li><a href="#rfc.authors">Authors' Addresses</a></li>
725         </ul>
726      </div>
727      <div id="caching">
728         <h1 id="rfc.section.1" class="np"><a href="#rfc.section.1">1.</a>&nbsp;<a href="#caching">Introduction</a></h1>
729         <div id="rfc.section.1.p.1">
730            <p>HTTP is typically used for distributed information systems, where performance can
731               be improved by the use of response caches. This document defines aspects of HTTP/1.1
732               related to caching and reusing response messages.
733            </p>
734         </div>
735         <div id="rfc.iref.c.1"></div>
736         <div id="rfc.section.1.p.2">
737            <p>An HTTP <dfn>cache</dfn> is a local store of response messages and the subsystem that controls storage, retrieval,
738               and deletion of messages in it. A cache stores cacheable responses in order to reduce
739               the response time and network bandwidth consumption on future, equivalent requests.
740               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.
741            </p>
742         </div>
743         <div id="rfc.iref.s.1"></div>
744         <div id="rfc.iref.p.1"></div>
745         <div id="shared.and.private.caches">
746            <div id="rfc.section.1.p.3">
747               <p>A <dfn>shared cache</dfn> is a cache that stores responses to be reused by more than one user; shared caches
748                  are usually (but not always) deployed as 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
749                  of a user agent.
750               </p>
751            </div>
752         </div>
753         <div id="rfc.section.1.p.4">
754            <p>The goal of caching in HTTP/1.1 is to significantly improve performance by reusing
755               a prior response message to satisfy a current request. A stored response is considered
756               "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
757               to see if the cached response remains valid for this request). A fresh response can
758               therefore reduce both latency and network overhead each time it is reused. When a
759               cached response is not fresh, it might still be reusable if it can be freshened by
760               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>).
761            </p>
762         </div>
763         <div id="conformance">
764            <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>
765            <div id="rfc.section.1.1.p.1">
766               <p>The key words "MUST", "MUST NOT", "REQUIRED", "SHALL", "SHALL NOT", "SHOULD", "SHOULD
767                  NOT", "RECOMMENDED", "MAY", and "OPTIONAL" in this document are to be interpreted
768                  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>.
769               </p>
770            </div>
771            <div id="rfc.section.1.1.p.2">
772               <p>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="#RFC7230" id="rfc.xref.RFC7230.1"><cite title="Hypertext Transfer Protocol (HTTP/1.1): Message Syntax and Routing">[RFC7230]</cite></a>.
773               </p>
774            </div>
775         </div>
776         <div id="notation">
777            <h2 id="rfc.section.1.2"><a href="#rfc.section.1.2">1.2</a>&nbsp;<a href="#notation">Syntax Notation</a></h2>
778            <div id="rfc.section.1.2.p.1">
779               <p>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 a list extension, defined in <a href="p1-messaging.html#abnf.extension" title="ABNF List Extension: #rule">Section 7</a> of <a href="#RFC7230" id="rfc.xref.RFC7230.2"><cite title="Hypertext Transfer Protocol (HTTP/1.1): Message Syntax and Routing">[RFC7230]</cite></a>, that allows for compact definition of comma-separated lists using a '#' operator
780                  (similar to how the '*' operator indicates repetition). <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 grammar with all list operators expanded to standard ABNF notation.
781               </p>
782            </div>
783            <div id="delta-seconds">
784               <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>
785               <div id="rfc.section.1.2.1.p.1">
786                  <p>The delta-seconds rule specifies a non-negative integer, representing time in seconds.</p>
787               </div>
788               <div id="rfc.figure.u.1"><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>
789</pre></div>
790               <div id="rfc.section.1.2.1.p.2">
791                  <p>A recipient parsing a delta-seconds value and converting it to binary form ought to
792                     use an arithmetic type of at least 31 bits of non-negative integer range. If a cache
793                     receives a delta-seconds value greater than the greatest integer it can represent,
794                     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.
795                  </p>
796               </div>
797               <div class="note">
798                  <div id="rfc.section.1.2.1.p.3">
799                     <p><b>Note:</b> The value 2147483648 is here for historical reasons, effectively represents infinity
800                        (over 68 years), and does not need to be stored in binary form; an implementation
801                        could produce it as a canned string if any overflow occurs, even if the calculations
802                        are performed with an arithmetic type incapable of directly representing that number.
803                        What matters here is that an overflow be detected and not treated as a negative value
804                        in later calculations.
805                     </p>
806                  </div>
807               </div>
808            </div>
809         </div>
810      </div>
811      <div id="caching.overview">
812         <h1 id="rfc.section.2"><a href="#rfc.section.2">2.</a>&nbsp;<a href="#caching.overview">Overview of Cache Operation</a></h1>
813         <div id="rfc.section.2.p.1">
814            <p>Proper cache operation preserves the semantics of HTTP transfers (<a href="#RFC7231" id="rfc.xref.RFC7231.1"><cite title="Hypertext Transfer Protocol (HTTP/1.1): Semantics and Content">[RFC7231]</cite></a>) while eliminating the transfer of information already held in the cache. Although
815               caching is an entirely <em class="bcp14">OPTIONAL</em> feature of HTTP, it can be assumed that reusing a cached response is desirable and
816               that such reuse is the default behavior when no requirement or local configuration
817               prevents it. Therefore, HTTP cache requirements are focused on preventing a cache
818               from either storing a non-reusable response or reusing a stored response inappropriately,
819               rather than mandating that caches always store and reuse particular responses.
820            </p>
821         </div>
822         <div id="rfc.section.2.p.2">
823            <p>Each <dfn>cache entry</dfn> consists of a cache key and one or more HTTP responses corresponding to prior requests
824               that used the same key. The most common form of cache entry is a successful result
825               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
826               by the request target (<a href="p2-semantics.html#GET" title="GET">Section 4.3.1</a> of <a href="#RFC7231" id="rfc.xref.RFC7231.2"><cite title="Hypertext Transfer Protocol (HTTP/1.1): Semantics and Content">[RFC7231]</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
827               caching and defines something suitable for use as a cache key.
828            </p>
829         </div>
830         <div id="rfc.iref.c.2"></div>
831         <div id="rfc.section.2.p.3">
832            <p>The primary <dfn>cache key</dfn> consists of the request method and target URI. However, since HTTP caches in common
833               use today are typically limited to caching responses to GET, many caches simply decline
834               other methods and use only the URI as the primary cache key.
835            </p>
836         </div>
837         <div id="rfc.section.2.p.4">
838            <p>If a request target is subject to content negotiation, its cache entry might consist
839               of multiple stored responses, each differentiated by a secondary key for the values
840               of the original request's selecting header fields (<a href="#caching.negotiated.responses" title="Calculating Secondary Keys with Vary">Section&nbsp;4.1</a>).
841            </p>
842         </div>
843      </div>
844      <div id="response.cacheability">
845         <h1 id="rfc.section.3"><a href="#rfc.section.3">3.</a>&nbsp;<a href="#response.cacheability">Storing Responses in Caches</a></h1>
846         <div id="rfc.section.3.p.1">
847            <p>A cache <em class="bcp14">MUST NOT</em> store a response to any request, unless:
848            </p>
849            <ul>
850               <li>The request method is understood by the cache and defined as being cacheable, and</li>
851               <li>the response status code is understood by the cache, and</li>
852               <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
853               </li>
854               <li>the "private" response directive (see <a href="#cache-response-directive.private" title="private">Section&nbsp;5.2.2.6</a>) does not appear in the response, if the cache is shared, and
855               </li>
856               <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.2</a> of <a href="#RFC7235" id="rfc.xref.RFC7235.1"><cite title="Hypertext Transfer Protocol (HTTP/1.1): Authentication">[RFC7235]</cite></a>) does not appear in the request, if the cache is shared, unless the response explicitly
857                  allows it (see <a href="#caching.authenticated.responses" title="Storing Responses to Authenticated Requests">Section&nbsp;3.2</a>), and
858               </li>
859               <li>the response either:
860                  <ul>
861                     <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
862                     </li>
863                     <li>contains a max-age response directive (see <a href="#cache-response-directive.max-age" title="max-age">Section&nbsp;5.2.2.8</a>), or
864                     </li>
865                     <li>contains a s-maxage response directive (see <a href="#cache-response-directive.s-maxage" title="s-maxage">Section&nbsp;5.2.2.9</a>) and the cache is shared, or
866                     </li>
867                     <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
868                     </li>
869                     <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
870                     </li>
871                     <li>contains a public response directive (see <a href="#cache-response-directive.public" title="public">Section&nbsp;5.2.2.5</a>).
872                     </li>
873                  </ul>
874               </li>
875            </ul>
876         </div>
877         <div id="rfc.section.3.p.2">
878            <p>Note that any of the requirements listed above can be overridden by a cache-control
879               extension; see <a href="#cache.control.extensions" title="Cache Control Extensions">Section&nbsp;5.2.3</a>.
880            </p>
881         </div>
882         <div id="rfc.section.3.p.3">
883            <p>In this context, a cache has "understood" a request method or a response status code
884               if it recognizes it and implements all specified caching-related behavior.
885            </p>
886         </div>
887         <div id="rfc.section.3.p.4">
888            <p>Note that, in normal operation, some caches will not store a response that has neither
889               a cache validator nor an explicit expiration time, as such responses are not usually
890               useful to store. However, caches are not prohibited from storing such responses.
891            </p>
892         </div>
893         <div id="incomplete.responses">
894            <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>
895            <div id="rfc.section.3.1.p.1">
896               <p>A response message is considered complete when all of the octets indicated by the
897                  message framing (<a href="#RFC7230" id="rfc.xref.RFC7230.3"><cite title="Hypertext Transfer Protocol (HTTP/1.1): Message Syntax and Routing">[RFC7230]</cite></a>) are received prior to the connection being closed. If the request method is GET,
898                  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.
899                  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
900                     (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.
901               </p>
902            </div>
903            <div id="rfc.section.3.1.p.2">
904               <p>A cache <em class="bcp14">MAY</em> complete a stored incomplete response by making a subsequent range request (<a href="#RFC7233" id="rfc.xref.RFC7233.1"><cite title="Hypertext Transfer Protocol (HTTP/1.1): Range Requests">[RFC7233]</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
905                  or the request is partial and specifies a range that is wholly within the incomplete
906                  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.
907               </p>
908            </div>
909         </div>
910         <div id="caching.authenticated.responses">
911            <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>
912            <div id="rfc.section.3.2.p.1">
913               <p>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.2</a> of <a href="#RFC7235" id="rfc.xref.RFC7235.2"><cite title="Hypertext Transfer Protocol (HTTP/1.1): Authentication">[RFC7235]</cite></a>) to satisfy any subsequent request unless a cache directive that allows such responses
914                  to be stored is present in the response.
915               </p>
916            </div>
917            <div id="rfc.section.3.2.p.2">
918               <p>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, and s-maxage.
919               </p>
920            </div>
921            <div id="rfc.section.3.2.p.3">
922               <p>Note that cached responses that contain the "must-revalidate" and/or "s-maxage" response
923                  directives are not allowed to be 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"
924                  or "s-maxage=0" cannot be used to satisfy a subsequent request without revalidating
925                  it on the origin server.
926               </p>
927            </div>
928         </div>
929         <div id="combining.responses">
930            <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>
931            <div id="rfc.section.3.3.p.1">
932               <p>A response might transfer only a partial representation if the connection closed prematurely
933                  or if the request used one or more Range specifiers (<a href="#RFC7233" id="rfc.xref.RFC7233.2"><cite title="Hypertext Transfer Protocol (HTTP/1.1): Range Requests">[RFC7233]</cite></a>). After several such transfers, a cache might have received several ranges of the
934                  same representation. A cache <em class="bcp14">MAY</em> combine these ranges into a single stored response, and reuse that response to satisfy
935                  later requests, if they all share the same strong validator and the cache complies
936                  with the client requirements in <a href="p5-range.html#combining.byte.ranges" title="Combining Ranges">Section 4.3</a> of <a href="#RFC7233" id="rfc.xref.RFC7233.3"><cite title="Hypertext Transfer Protocol (HTTP/1.1): Range Requests">[RFC7233]</cite></a>.
937               </p>
938            </div>
939            <div id="rfc.section.3.3.p.2">
940               <p>When combining the new response with one or more stored responses, a cache <em class="bcp14">MUST</em>:
941               </p>
942               <ul>
943                  <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>);
944                  </li>
945                  <li>retain any <a href="#header.warning" class="smpl">Warning</a> header fields in the stored response with warn-code 2xx; and,
946                  </li>
947                  <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.
948                  </li>
949               </ul>
950            </div>
951         </div>
952      </div>
953      <div id="constructing.responses.from.caches">
954         <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>
955         <div id="rfc.section.4.p.1">
956            <p>When presented with a request, a cache <em class="bcp14">MUST NOT</em> reuse a stored response, unless:
957            </p>
958            <ul>
959               <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="#RFC7230" id="rfc.xref.RFC7230.4"><cite title="Hypertext Transfer Protocol (HTTP/1.1): Message Syntax and Routing">[RFC7230]</cite></a>) and that of the stored response match, and
960               </li>
961               <li>the request method associated with the stored response allows it to be used for the
962                  presented request, and
963               </li>
964               <li>selecting header fields nominated by the stored response (if any) match those presented
965                  (see <a href="#caching.negotiated.responses" title="Calculating Secondary Keys with Vary">Section&nbsp;4.1</a>), and
966               </li>
967               <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
968               </li>
969               <li>the stored response does not contain the no-cache cache directive (<a href="#cache-response-directive.no-cache" title="no-cache">Section&nbsp;5.2.2.2</a>), unless it is successfully validated (<a href="#validation.model" title="Validation">Section&nbsp;4.3</a>), and
970               </li>
971               <li>the stored response is either:
972                  <ul>
973                     <li>fresh (see <a href="#expiration.model" title="Freshness">Section&nbsp;4.2</a>), or
974                     </li>
975                     <li>allowed to be served stale (see <a href="#serving.stale.responses" title="Serving Stale Responses">Section&nbsp;4.2.4</a>), or
976                     </li>
977                     <li>successfully validated (see <a href="#validation.model" title="Validation">Section&nbsp;4.3</a>).
978                     </li>
979                  </ul>
980               </li>
981            </ul>
982         </div>
983         <div id="rfc.section.4.p.2">
984            <p>Note that any of the requirements listed above can be overridden by a cache-control
985               extension; see <a href="#cache.control.extensions" title="Cache Control Extensions">Section&nbsp;5.2.3</a>.
986            </p>
987         </div>
988         <div id="rfc.section.4.p.3">
989            <p>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
990               current_age; see <a href="#age.calculations" title="Calculating Age">Section&nbsp;4.2.3</a>.
991            </p>
992         </div>
993         <div id="rfc.section.4.p.4">
994            <p>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="#RFC7231" id="rfc.xref.RFC7231.3"><cite title="Hypertext Transfer Protocol (HTTP/1.1): Semantics and Content">[RFC7231]</cite></a>) to the origin server; i.e., a cache is not allowed to generate a reply to such a
995               request before having forwarded the request and having received a corresponding response.
996            </p>
997         </div>
998         <div id="rfc.section.4.p.5">
999            <p>Also, note that unsafe requests might invalidate already-stored responses; see <a href="#invalidation" title="Invalidation">Section&nbsp;4.4</a>.
1000            </p>
1001         </div>
1002         <div id="rfc.section.4.p.6">
1003            <p>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="p2-semantics.html#header.date" class="smpl">Date</a> header field). It can also forward the request with "Cache-Control: max-age=0" or
1004               "Cache-Control: no-cache" to disambiguate which response to use.
1005            </p>
1006         </div>
1007         <div id="rfc.section.4.p.7">
1008            <p>A cache that does not have a clock available <em class="bcp14">MUST NOT</em> use stored responses without revalidating them upon every use.
1009            </p>
1010         </div>
1011         <div id="caching.negotiated.responses">
1012            <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>
1013            <div id="rfc.section.4.1.p.1">
1014               <p>When a cache receives a request that can be satisfied by a stored response that has
1015                  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="#RFC7231" id="rfc.xref.RFC7231.4"><cite title="Hypertext Transfer Protocol (HTTP/1.1): Semantics and Content">[RFC7231]</cite></a>), it <em class="bcp14">MUST NOT</em> use that response unless all of the selecting header fields nominated by the Vary
1016                  header field match in both the original request (i.e., that associated with the stored
1017                  response), and the presented request.
1018               </p>
1019            </div>
1020            <div id="rfc.section.4.1.p.2">
1021               <p>The selecting header fields from two requests are defined to match if and only if
1022                  those in the first request can be transformed to those in the second request by applying
1023                  any of the following:
1024               </p>
1025               <ul>
1026                  <li>adding or removing whitespace, where allowed in the header field's syntax</li>
1027                  <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="#RFC7230" id="rfc.xref.RFC7230.5"><cite title="Hypertext Transfer Protocol (HTTP/1.1): Message Syntax and Routing">[RFC7230]</cite></a>)
1028                  </li>
1029                  <li>normalizing both header field values in a way that is known to have identical semantics,
1030                     according to the header field's specification (e.g., reordering field values when
1031                     order is not significant; case-normalization, where values are defined to be case-insensitive)
1032                  </li>
1033               </ul>
1034            </div>
1035            <div id="rfc.section.4.1.p.3">
1036               <p>If (after any normalization that might take place) a header field is absent from a
1037                  request, it can only match another request if it is also absent there.
1038               </p>
1039            </div>
1040            <div id="rfc.section.4.1.p.4">
1041               <p>A <a href="p2-semantics.html#header.vary" class="smpl">Vary</a> header field-value of "*" always fails to match.
1042               </p>
1043            </div>
1044            <div id="rfc.section.4.1.p.5">
1045               <p>The stored response with matching selecting header fields is known as the selected
1046                  response.
1047               </p>
1048            </div>
1049            <div id="rfc.section.4.1.p.6">
1050               <p>If multiple selected responses are available (potentially including responses without
1051                  a Vary header field), the cache will need to choose one to use. When a selecting header
1052                  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
1053                  (as determined by the <a href="p2-semantics.html#header.date" 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>.
1054               </p>
1055            </div>
1056            <div id="rfc.section.4.1.p.7">
1057               <p>If no selected response is available, the cache cannot satisfy the presented request.
1058                  Typically, it is forwarded to the origin server in a (possibly conditional; see <a href="#validation.model" title="Validation">Section&nbsp;4.3</a>) request.
1059               </p>
1060            </div>
1061         </div>
1062         <div id="expiration.model">
1063            <h2 id="rfc.section.4.2"><a href="#rfc.section.4.2">4.2</a>&nbsp;<a href="#expiration.model">Freshness</a></h2>
1064            <div id="rfc.section.4.2.p.1">
1065               <p>A <dfn>fresh</dfn> response is one whose age has not yet exceeded its freshness lifetime. Conversely,
1066                  a <dfn>stale</dfn> response is one where it has.
1067               </p>
1068            </div>
1069            <div id="rfc.iref.f.1"></div>
1070            <div id="rfc.iref.e.1"></div>
1071            <div id="rfc.iref.h.1"></div>
1072            <div id="rfc.section.4.2.p.2">
1073               <p>A response's <dfn>freshness lifetime</dfn> is the length of time between its generation by the origin server and its expiration
1074                  time. An <dfn>explicit expiration time</dfn> is the time at which the origin server intends that a stored response can no longer
1075                  be used by a cache without further validation, whereas a <dfn>heuristic expiration time</dfn> is assigned by a cache when no explicit expiration time is available.
1076               </p>
1077            </div>
1078            <div id="rfc.iref.a.1"></div>
1079            <div id="rfc.section.4.2.p.3">
1080               <p>A response's <dfn>age</dfn> is the time that has passed since it was generated by, or successfully validated with,
1081                  the origin server.
1082               </p>
1083            </div>
1084            <div id="rfc.section.4.2.p.4">
1085               <p>When a response is "fresh" in the cache, it can be used to satisfy subsequent requests
1086                  without contacting the origin server, thereby improving efficiency.
1087               </p>
1088            </div>
1089            <div id="rfc.section.4.2.p.5">
1090               <p>The primary mechanism for determining freshness is for an origin server to provide
1091                  an explicit expiration time in the future, 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;5.2.2.8</a>). Generally, origin servers will assign future explicit expiration times to responses
1092                  in the belief that the representation is not likely to change in a semantically significant
1093                  way before the expiration time is reached.
1094               </p>
1095            </div>
1096            <div id="rfc.section.4.2.p.6">
1097               <p>If an origin server wishes to force a cache to validate every request, it can assign
1098                  an explicit expiration time in the past to indicate that the response is already stale.
1099                  Compliant caches will normally validate a stale cached response before reusing it
1100                  for subsequent requests (see <a href="#serving.stale.responses" title="Serving Stale Responses">Section&nbsp;4.2.4</a>).
1101               </p>
1102            </div>
1103            <div id="rfc.section.4.2.p.7">
1104               <p>Since origin servers do not always provide explicit expiration times, caches are also
1105                  allowed to use a heuristic to determine an expiration time under certain circumstances
1106                  (see <a href="#heuristic.freshness" title="Calculating Heuristic Freshness">Section&nbsp;4.2.2</a>).
1107               </p>
1108            </div>
1109            <div id="rfc.figure.u.2">
1110               <p>The calculation to determine if a response is fresh is:</p><pre class="text">   response_is_fresh = (freshness_lifetime &gt; current_age)
1111</pre></div>
1112            <div id="rfc.section.4.2.p.8">
1113               <p>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>.
1114               </p>
1115            </div>
1116            <div id="rfc.section.4.2.p.9">
1117               <p>Clients can send the max-age or min-fresh cache directives in a request to constrain
1118                  or relax freshness calculations for the corresponding response (<a href="#cache-request-directive" title="Request Cache-Control Directives">Section&nbsp;5.2.1</a>).
1119               </p>
1120            </div>
1121            <div id="rfc.section.4.2.p.10">
1122               <p>When calculating freshness, to avoid common problems in date parsing:</p>
1123            </div>
1124            <div id="rfc.section.4.2.p.11">
1125               <ul>
1126                  <li>Although all date formats are specified to be case-sensitive, a cache recipient <em class="bcp14">SHOULD</em> match day, week, and time-zone names case-insensitively.
1127                  </li>
1128                  <li>If a cache recipient's internal implementation of time has less resolution than the
1129                     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.
1130                  </li>
1131                  <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
1132                     time.
1133                  </li>
1134                  <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
1135                     expiration.
1136                  </li>
1137               </ul>
1138            </div>
1139            <div id="rfc.section.4.2.p.12">
1140               <p>Note that freshness applies only to cache operation; it cannot be used to force a
1141                  user agent to refresh its display or reload 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.
1142               </p>
1143            </div>
1144            <div id="calculating.freshness.lifetime">
1145               <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>
1146               <div id="rfc.section.4.2.1.p.1">
1147                  <p>A cache can calculate the freshness lifetime (denoted as freshness_lifetime) of a
1148                     response by using the first match of the following:
1149                  </p>
1150                  <ul>
1151                     <li>If the cache is shared and the s-maxage response directive (<a href="#cache-response-directive.s-maxage" title="s-maxage">Section&nbsp;5.2.2.9</a>) is present, use its value, or
1152                     </li>
1153                     <li>If the max-age response directive (<a href="#cache-response-directive.max-age" title="max-age">Section&nbsp;5.2.2.8</a>) is present, use its value, or
1154                     </li>
1155                     <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="p2-semantics.html#header.date" class="smpl">Date</a> response header field, or
1156                     </li>
1157                     <li>Otherwise, no explicit expiration time is present in the response. A heuristic freshness
1158                        lifetime might be applicable; see <a href="#heuristic.freshness" title="Calculating Heuristic Freshness">Section&nbsp;4.2.2</a>.
1159                     </li>
1160                  </ul>
1161               </div>
1162               <div id="rfc.section.4.2.1.p.2">
1163                  <p>Note that this calculation is not vulnerable to clock skew, since all of the information
1164                     comes from the origin server.
1165                  </p>
1166               </div>
1167               <div id="rfc.section.4.2.1.p.3">
1168                  <p>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
1169                     is considered invalid. Caches are encouraged to consider responses that have invalid
1170                     freshness information to be stale.
1171                  </p>
1172               </div>
1173            </div>
1174            <div id="heuristic.freshness">
1175               <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>
1176               <div id="rfc.section.4.2.2.p.1">
1177                  <p>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
1178                     algorithms that use other header field 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
1179                     specific algorithms, but does impose worst-case constraints on their results.
1180                  </p>
1181               </div>
1182               <div id="rfc.section.4.2.2.p.2">
1183                  <p>A cache <em class="bcp14">MUST NOT</em> use heuristics to determine freshness when an explicit expiration time is present
1184                     in the stored response. Because of the requirements 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
1185                     freshness whose status codes are defined as cacheable by default (see <a href="p2-semantics.html#overview.of.status.codes" title="Overview of Status Codes">Section 6.1</a> of <a href="#RFC7231" id="rfc.xref.RFC7231.5"><cite title="Hypertext Transfer Protocol (HTTP/1.1): Semantics and Content">[RFC7231]</cite></a>), and those responses without explicit freshness that have been marked as explicitly
1186                     cacheable (e.g., with a "public" response directive).
1187                  </p>
1188               </div>
1189               <div id="rfc.section.4.2.2.p.3">
1190                  <p>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="#RFC7232" id="rfc.xref.RFC7232.1"><cite title="Hypertext Transfer Protocol (HTTP/1.1): Conditional Requests">[RFC7232]</cite></a>), caches are encouraged to use a heuristic expiration value that is no more than
1191                     some fraction of the interval since that time. A typical setting of this fraction
1192                     might be 10%.
1193                  </p>
1194               </div>
1195               <div id="rfc.section.4.2.2.p.4">
1196                  <p>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
1197                     already present.
1198                  </p>
1199               </div>
1200               <div class="note">
1201                  <div id="rfc.section.4.2.2.p.5">
1202                     <p><b>Note:</b> <a href="https://tools.ietf.org/html/rfc2616#section-13.9">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
1203                        (i.e., those containing '?'). In practice, this has not been widely implemented. Therefore,
1204                        origin servers are encouraged to send explicit directives (e.g., Cache-Control: no-cache)
1205                        if they wish to preclude caching.
1206                     </p>
1207                  </div>
1208               </div>
1209            </div>
1210            <div id="age.calculations">
1211               <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>
1212               <div id="rfc.section.4.2.3.p.1">
1213                  <p>The <a href="#header.age" class="smpl">Age</a> header field is used to convey an estimated age of the response message when obtained
1214                     from a cache. The Age field value is the cache's estimate of the number of seconds
1215                     since the response was generated or validated by the origin server. In essence, the
1216                     Age value is the sum of the time that the response has been resident in each of the
1217                     caches along the path from the origin server, plus the amount of time it has been
1218                     in transit along network paths.
1219                  </p>
1220               </div>
1221               <div id="rfc.section.4.2.3.p.2">
1222                  <p>The following data is used for the age calculation:</p>
1223               </div>
1224               <div id="rfc.section.4.2.3.p.3">
1225                  <p><dfn>age_value</dfn>
1226                  </p>
1227                  <ul class="empty">
1228                     <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.
1229                     </li>
1230                  </ul>
1231               </div>
1232               <div id="rfc.section.4.2.3.p.4">
1233                  <p><dfn>date_value</dfn>
1234                  </p>
1235                  <ul class="empty">
1236                     <li>The term "date_value" denotes the value of the Date header field, in a form appropriate
1237                        for arithmetic operations. See <a href="p2-semantics.html#header.date" title="Date">Section 7.1.1.2</a> of <a href="#RFC7231" id="rfc.xref.RFC7231.6"><cite title="Hypertext Transfer Protocol (HTTP/1.1): Semantics and Content">[RFC7231]</cite></a> for the definition of the Date header field, and for requirements regarding responses
1238                        without it.
1239                     </li>
1240                  </ul>
1241               </div>
1242               <div id="rfc.section.4.2.3.p.5">
1243                  <p><dfn>now</dfn>
1244                  </p>
1245                  <ul class="empty">
1246                     <li>The term "now" means "the current value of the clock at the host performing the calculation".
1247                        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.
1248                     </li>
1249                  </ul>
1250               </div>
1251               <div id="rfc.section.4.2.3.p.6">
1252                  <p><dfn>request_time</dfn>
1253                  </p>
1254                  <ul class="empty">
1255                     <li>The current value of the clock at the host at the time the request resulting in the
1256                        stored response was made.
1257                     </li>
1258                  </ul>
1259               </div>
1260               <div id="rfc.section.4.2.3.p.7">
1261                  <p><dfn>response_time</dfn>
1262                  </p>
1263                  <ul class="empty">
1264                     <li>The current value of the clock at the host at the time the response was received.</li>
1265                  </ul>
1266               </div>
1267               <div id="rfc.section.4.2.3.p.8">
1268                  <p>A response's age can be calculated in two entirely independent ways: </p>
1269                  <ol>
1270                     <li>the "apparent_age": response_time minus date_value, if the local clock is reasonably
1271                        well synchronized to the origin server's clock. If the result is negative, the result
1272                        is replaced by zero.
1273                     </li>
1274                     <li>the "corrected_age_value", if all of the caches along the response path implement
1275                        HTTP/1.1. A cache <em class="bcp14">MUST</em> interpret this value relative to the time the request was initiated, not the time
1276                        that the response was received.
1277                     </li>
1278                  </ol>
1279               </div>
1280               <div id="rfc.figure.u.3"><pre class="text">  apparent_age = max(0, response_time - date_value);
1281
1282  response_delay = response_time - request_time;
1283  corrected_age_value = age_value + response_delay; 
1284</pre></div>
1285               <div id="rfc.figure.u.4">
1286                  <p>These are combined as</p><pre class="text">  corrected_initial_age = max(apparent_age, corrected_age_value);
1287</pre></div>
1288               <div id="rfc.section.4.2.3.p.9">
1289                  <p>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.
1290                  </p>
1291               </div>
1292               <div id="rfc.section.4.2.3.p.10">
1293                  <p>The current_age of a stored response can then be calculated by adding the amount of
1294                     time (in seconds) since the stored response was last validated by the origin server
1295                     to the corrected_initial_age.
1296                  </p>
1297               </div>
1298               <div id="rfc.figure.u.5"><pre class="text">  resident_time = now - response_time;
1299  current_age = corrected_initial_age + resident_time;
1300</pre></div>
1301            </div>
1302            <div id="serving.stale.responses">
1303               <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>
1304               <div id="rfc.section.4.2.4.p.1">
1305                  <p>A "stale" response is one that either has explicit expiry information or is allowed
1306                     to have heuristic expiry calculated, but is not fresh according to the calculations
1307                     in <a href="#expiration.model" title="Freshness">Section&nbsp;4.2</a>.
1308                  </p>
1309               </div>
1310               <div id="rfc.section.4.2.4.p.2">
1311                  <p>A cache <em class="bcp14">MUST NOT</em> generate a stale response if it is prohibited by an explicit in-protocol directive
1312                     (e.g., by a "no-store" or "no-cache" cache directive, a "must-revalidate" cache-response-directive,
1313                     or an applicable "s-maxage" or "proxy-revalidate" cache-response-directive; see <a href="#cache-response-directive" title="Response Cache-Control Directives">Section&nbsp;5.2.2</a>).
1314                  </p>
1315               </div>
1316               <div id="rfc.section.4.2.4.p.3">
1317                  <p>A cache <em class="bcp14">MUST NOT</em> send stale responses unless it is disconnected (i.e., it cannot contact the origin
1318                     server or otherwise find a forward path) or doing so is explicitly allowed (e.g.,
1319                     by the max-stale request directive; see <a href="#cache-request-directive" title="Request Cache-Control Directives">Section&nbsp;5.2.1</a>).
1320                  </p>
1321               </div>
1322               <div id="rfc.section.4.2.4.p.4">
1323                  <p>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.
1324                  </p>
1325               </div>
1326               <div id="rfc.section.4.2.4.p.5">
1327                  <p>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
1328                     that merely became stale in transit.
1329                  </p>
1330               </div>
1331            </div>
1332         </div>
1333         <div id="validation.model">
1334            <h2 id="rfc.section.4.3"><a href="#rfc.section.4.3">4.3</a>&nbsp;<a href="#validation.model">Validation</a></h2>
1335            <div id="rfc.section.4.3.p.1">
1336               <p>When a cache has one or more stored responses for a requested URI, but cannot serve
1337                  any of them (e.g., because they are not 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="#RFC7232" id="rfc.xref.RFC7232.2"><cite title="Hypertext Transfer Protocol (HTTP/1.1): Conditional Requests">[RFC7232]</cite></a> in the forwarded request to give the next inbound server an opportunity to select
1338                  a valid stored response to use, updating the stored metadata in the process, or to
1339                  replace the stored response(s) with a new response. This process is known as "validating"
1340                  or "revalidating" the stored response.
1341               </p>
1342            </div>
1343            <div id="validation.sent">
1344               <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>
1345               <div id="rfc.section.4.3.1.p.1">
1346                  <p>When sending a conditional request for cache validation, a cache sends one or more
1347                     precondition header fields containing <dfn>validator</dfn> metadata from its stored response(s), which is then compared by recipients to determine
1348                     whether a stored response is equivalent to a current representation of the resource.
1349                  </p>
1350               </div>
1351               <div id="rfc.section.4.3.1.p.2">
1352                  <p>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="#RFC7232" id="rfc.xref.RFC7232.3"><cite title="Hypertext Transfer Protocol (HTTP/1.1): Conditional Requests">[RFC7232]</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
1353                     to a previously obtained representation with that timestamp).
1354                  </p>
1355               </div>
1356               <div id="rfc.section.4.3.1.p.3">
1357                  <p>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="#RFC7232" id="rfc.xref.RFC7232.4"><cite title="Hypertext Transfer Protocol (HTTP/1.1): Conditional Requests">[RFC7232]</cite></a>). One or more entity-tags, indicating one or more stored responses, can be used in
1358                     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
1359                     to one or more previously obtained representations with the listed entity-tags).
1360                  </p>
1361               </div>
1362            </div>
1363            <div id="validation.received">
1364               <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>
1365               <div id="rfc.section.4.3.2.p.1">
1366                  <p>Each client in the request chain may have its own cache, so it is common for a cache
1367                     at an intermediary to receive conditional requests from other (outbound) caches. Likewise,
1368                     some user agents make use of conditional requests to limit data transfers to recently
1369                     modified representations or to complete the transfer of a partially retrieved representation.
1370                  </p>
1371               </div>
1372               <div id="rfc.section.4.3.2.p.2">
1373                  <p>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
1374                     with respect to the corresponding validators contained within the selected response.
1375                     A cache <em class="bcp14">MUST NOT</em> evaluate conditional header fields that are only applicable to an origin server, found
1376                     in a request with semantics that cannot be satisfied with a cached response, or applied
1377                     to a target resource for which it has no stored responses; such preconditions are
1378                     likely intended for some other (inbound) server.
1379                  </p>
1380               </div>
1381               <div id="rfc.section.4.3.2.p.3">
1382                  <p>The proper evaluation of conditional requests by a cache depends on the received precondition
1383                     header fields and their precedence, as defined in <a href="p4-conditional.html#precedence" title="Precedence">Section 6</a> of <a href="#RFC7232" id="rfc.xref.RFC7232.5"><cite title="Hypertext Transfer Protocol (HTTP/1.1): Conditional Requests">[RFC7232]</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.
1384                  </p>
1385               </div>
1386               <div id="rfc.section.4.3.2.p.4">
1387                  <p>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="#RFC7232" id="rfc.xref.RFC7232.6"><cite title="Hypertext Transfer Protocol (HTTP/1.1): Conditional Requests">[RFC7232]</cite></a>) indicates that the client wants to validate one or more of its own stored responses
1388                     in comparison to whichever stored response is selected by the cache. If the field-value
1389                     is "*", or if the field-value is a list of entity-tags and at least one of them matches
1390                     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
1391                     stored response.
1392                  </p>
1393               </div>
1394               <div id="rfc.section.4.3.2.p.5">
1395                  <p>When a cache decides to revalidate its own stored responses for a request that contains
1396                     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
1397                     (fresh or stale) and send the union 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
1398                     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
1399                     fully satisfied by that partial stored response. If the response to the forwarded
1400                     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
1401                     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
1402                     the 304 response metadata (<a href="#freshening.responses" title="Freshening Stored Responses upon Validation">Section&nbsp;4.3.4</a>).
1403                  </p>
1404               </div>
1405               <div id="rfc.section.4.3.2.p.6">
1406                  <p>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="#RFC7232" id="rfc.xref.RFC7232.7"><cite title="Hypertext Transfer Protocol (HTTP/1.1): Conditional Requests">[RFC7232]</cite></a>) indicates that the client wants to validate one or more of its own stored responses
1407                     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
1408                     cases is true: 1) the selected stored 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="p2-semantics.html#header.date" 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="p2-semantics.html#header.date" class="smpl">Date</a> is present in the selected stored response, but the cache recorded it as having been
1409                     received at a time earlier than or equal to the conditional timestamp.
1410                  </p>
1411               </div>
1412               <div id="rfc.section.4.3.2.p.7">
1413                  <p>A cache that implements partial responses to range requests, as defined in <a href="#RFC7233" id="rfc.xref.RFC7233.4"><cite title="Hypertext Transfer Protocol (HTTP/1.1): Range Requests">[RFC7233]</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="#RFC7233" id="rfc.xref.RFC7233.5"><cite title="Hypertext Transfer Protocol (HTTP/1.1): Range Requests">[RFC7233]</cite></a>) with respect to its selected stored response.
1414                  </p>
1415               </div>
1416            </div>
1417            <div id="validation.response">
1418               <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>
1419               <div id="rfc.section.4.3.3.p.1">
1420                  <p>Cache handling of a response to a conditional request is dependent upon its status
1421                     code:
1422                  </p>
1423               </div>
1424               <div id="rfc.section.4.3.3.p.2">
1425                  <ul>
1426                     <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;
1427                        see <a href="#freshening.responses" title="Freshening Stored Responses upon Validation">Section&nbsp;4.3.4</a>.
1428                     </li>
1429                     <li>A full response (i.e., one with a payload body) indicates that none of the stored
1430                        responses nominated in the conditional request 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).
1431                     </li>
1432                     <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
1433                        to the requesting client, or act as if the server failed to respond. In the latter
1434                        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>).
1435                     </li>
1436                  </ul>
1437               </div>
1438            </div>
1439            <div id="freshening.responses">
1440               <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>
1441               <div id="rfc.section.4.3.4.p.1">
1442                  <p>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
1443                     responses are updated by this new response and then update the stored response(s)
1444                     with the new information provided in the <a href="p4-conditional.html#status.304" class="smpl">304</a> response.
1445                  </p>
1446               </div>
1447               <div id="rfc.iref.s.2"></div>
1448               <div id="rfc.section.4.3.4.p.2">
1449                  <p>The stored response to update is identified by using the first match (if any) of the
1450                     following:
1451                  </p>
1452                  <ul>
1453                     <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="#RFC7232" id="rfc.xref.RFC7232.8"><cite title="Hypertext Transfer Protocol (HTTP/1.1): Conditional Requests">[RFC7232]</cite></a>), then that strong validator identifies the selected representation for update. All
1454                        of the stored responses with the same strong validator are selected. If none of the
1455                        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.
1456                     </li>
1457                     <li>If the new response contains a weak validator and that validator corresponds to one
1458                        of the cache's stored responses, then the most recent of those matching stored responses
1459                        is selected for update.
1460                     </li>
1461                     <li>If the new response does not include any form of validator (such as in the case where
1462                        a client generates an If-Modified-Since request from a source other than the Last-Modified
1463                        response header field), and there is only one stored response, and that stored response
1464                        also lacks a validator, then that stored response is selected for update.
1465                     </li>
1466                  </ul>
1467               </div>
1468               <div id="rfc.section.4.3.4.p.3">
1469                  <p>If a stored response is selected for update, the cache <em class="bcp14">MUST</em>:
1470                  </p>
1471                  <ul>
1472                     <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>);
1473                     </li>
1474                     <li>retain any <a href="#header.warning" class="smpl">Warning</a> header fields in the stored response with warn-code 2xx; and,
1475                     </li>
1476                     <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
1477                        response.
1478                     </li>
1479                  </ul>
1480               </div>
1481            </div>
1482            <div id="head.effects">
1483               <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>
1484               <div id="rfc.section.4.3.5.p.1">
1485                  <p>A response to the HEAD method is identical to what an equivalent request made with
1486                     a GET would have been, except it lacks a body. This property of HEAD responses can
1487                     be used to invalidate or update a cached GET response if the more efficient conditional
1488                     GET request mechanism is not available (due to no validators being present in the
1489                     stored response) or if transmission of the representation body is not desired even
1490                     if it has changed.
1491                  </p>
1492               </div>
1493               <div id="rfc.section.4.3.5.p.2">
1494                  <p>When a cache makes an inbound HEAD request for a given request target and receives
1495                     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
1496                     for that request (see <a href="#caching.negotiated.responses" title="Calculating Secondary Keys with Vary">Section&nbsp;4.1</a>).
1497                  </p>
1498               </div>
1499               <div id="rfc.section.4.3.5.p.3">
1500                  <p>For each of the stored responses that could have been selected, if the stored response
1501                     and HEAD response have matching values 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.
1502                  </p>
1503               </div>
1504               <div id="rfc.section.4.3.5.p.4">
1505                  <p>If a cache updates a stored response with the metadata provided in a HEAD response,
1506                     the cache <em class="bcp14">MUST</em>:
1507                  </p>
1508                  <ul>
1509                     <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>);
1510                     </li>
1511                     <li>retain any <a href="#header.warning" class="smpl">Warning</a> header fields in the stored response with warn-code 2xx; and,
1512                     </li>
1513                     <li>use other header fields provided in the HEAD response to replace all instances of
1514                        the corresponding header fields in the stored response and append new header fields
1515                        to the stored response's header section unless otherwise restricted by the <a href="#header.cache-control" class="smpl">Cache-Control</a> header field.
1516                     </li>
1517                  </ul>
1518               </div>
1519            </div>
1520         </div>
1521         <div id="invalidation">
1522            <h2 id="rfc.section.4.4"><a href="#rfc.section.4.4">4.4</a>&nbsp;<a href="#invalidation">Invalidation</a></h2>
1523            <div id="rfc.section.4.4.p.1">
1524               <p>Because unsafe request methods (<a href="p2-semantics.html#safe.methods" title="Safe Methods">Section 4.2.1</a> of <a href="#RFC7231" id="rfc.xref.RFC7231.7"><cite title="Hypertext Transfer Protocol (HTTP/1.1): Semantics and Content">[RFC7231]</cite></a>) such as PUT, POST or DELETE have the potential for changing state on the origin
1525                  server, intervening caches can use them to keep their contents up to date.
1526               </p>
1527            </div>
1528            <div id="rfc.section.4.4.p.2">
1529               <p>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="#RFC7230" id="rfc.xref.RFC7230.6"><cite title="Hypertext Transfer Protocol (HTTP/1.1): Message Syntax and Routing">[RFC7230]</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
1530                  to an unsafe request method.
1531               </p>
1532            </div>
1533            <div id="rfc.section.4.4.p.3">
1534               <p>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
1535                  effective request URI (<a href="p1-messaging.html#effective.request.uri" title="Effective Request URI">Section 5.5</a> of <a href="#RFC7230" id="rfc.xref.RFC7230.7"><cite title="Hypertext Transfer Protocol (HTTP/1.1): Message Syntax and Routing">[RFC7230]</cite></a>). This helps prevent denial-of-service attacks.
1536               </p>
1537            </div>
1538            <div id="rfc.section.4.4.p.4">
1539               <p>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="#RFC7230" id="rfc.xref.RFC7230.8"><cite title="Hypertext Transfer Protocol (HTTP/1.1): Message Syntax and Routing">[RFC7230]</cite></a>) when it receives a non-error response to a request with a method whose safety is
1540                  unknown.
1541               </p>
1542            </div>
1543            <div id="rfc.section.4.4.p.5">
1544               <p>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
1545                  related to the effective request URI or will mark these as "invalid" and in need of
1546                  a mandatory validation before they can be sent in response to a subsequent request.
1547               </p>
1548            </div>
1549            <div id="rfc.section.4.4.p.6">
1550               <p>Note that this does not guarantee that all appropriate responses are invalidated.
1551                  For example, a state-changing request might invalidate responses in the caches it
1552                  travels through, but relevant responses still might be stored in other caches that
1553                  it has not.
1554               </p>
1555            </div>
1556         </div>
1557      </div>
1558      <div id="header.field.definitions">
1559         <h1 id="rfc.section.5"><a href="#rfc.section.5">5.</a>&nbsp;<a href="#header.field.definitions">Header Field Definitions</a></h1>
1560         <div id="rfc.section.5.p.1">
1561            <p>This section defines the syntax and semantics of HTTP/1.1 header fields related to
1562               caching.
1563            </p>
1564         </div>
1565         <div id="header.age">
1566            <h2 id="rfc.section.5.1"><a href="#rfc.section.5.1">5.1</a>&nbsp;<a href="#header.age">Age</a></h2>
1567            <div id="rfc.section.5.1.p.1">
1568               <p>The "Age" header field conveys the sender's estimate of the amount of time since the
1569                  response was generated or successfully validated at the origin server. Age values
1570                  are calculated as specified in <a href="#age.calculations" title="Calculating Age">Section&nbsp;4.2.3</a>.
1571               </p>
1572            </div>
1573            <div id="rfc.figure.u.6"><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>
1574</pre></div>
1575            <div id="rfc.section.5.1.p.2">
1576               <p>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>).
1577               </p>
1578            </div>
1579            <div id="rfc.section.5.1.p.3">
1580               <p>The presence of an Age header field implies that the response was not generated or
1581                  validated by the origin server for this request. However, lack of an Age header field
1582                  does not imply the origin was contacted, since the response might have been received
1583                  from an HTTP/1.0 cache that does not implement Age.
1584               </p>
1585            </div>
1586         </div>
1587         <div id="header.cache-control">
1588            <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>
1589            <div id="rfc.section.5.2.p.1">
1590               <p>The "Cache-Control" header field is used to specify directives for caches along the
1591                  request/response chain. Such cache directives are unidirectional in that the presence
1592                  of a directive in a request does not imply that the same directive is to be given
1593                  in the response.
1594               </p>
1595            </div>
1596            <div id="rfc.section.5.2.p.2">
1597               <p>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.
1598               </p>
1599            </div>
1600            <div class="note">
1601               <div id="rfc.section.5.2.p.3">
1602                  <p><b>Note:</b> Some HTTP/1.0 caches might not implement Cache-Control.
1603                  </p>
1604               </div>
1605            </div>
1606            <div id="rfc.section.5.2.p.4">
1607               <p>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
1608                  to that application, since the directives might be applicable to all recipients along
1609                  the request/response chain. It is not possible to target a directive to a specific
1610                  cache.
1611               </p>
1612            </div>
1613            <div id="rfc.section.5.2.p.5">
1614               <p>Cache directives are identified by a token, to be compared case-insensitively, and
1615                  have an optional argument, that can use both token and quoted-string syntax. For the
1616                  directives defined below that define arguments, recipients ought to accept both forms,
1617                  even if one is documented to be preferred. For any directive not defined by this specification,
1618                  a recipient <em class="bcp14">MUST</em> accept both forms.
1619               </p>
1620            </div>
1621            <div id="rfc.figure.u.7"><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>
1622
1623  <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> ) ]
1624</pre></div>
1625            <div id="rfc.section.5.2.p.6">
1626               <p>For the cache directives defined below, no argument is defined (nor allowed) unless
1627                  stated otherwise.
1628               </p>
1629            </div>
1630            <div id="cache-request-directive">
1631               <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>
1632               <div id="cache-request-directive.max-age">
1633                  <h4 id="rfc.section.5.2.1.1"><a href="#rfc.section.5.2.1.1">5.2.1.1</a>&nbsp;<a href="#cache-request-directive.max-age">max-age</a></h4>
1634                  <div id="rfc.section.5.2.1.1.p.1">
1635                     <p>Argument syntax: </p>
1636                     <ul class="empty">
1637                        <li><a href="#delta-seconds" class="smpl">delta-seconds</a> (see <a href="#delta-seconds" title="Delta Seconds">Section&nbsp;1.2.1</a>)
1638                        </li>
1639                     </ul>
1640                  </div>
1641                  <div id="rfc.section.5.2.1.1.p.2">
1642                     <p>The "max-age" request directive indicates that the client is unwilling to accept a
1643                        response whose age is greater than the specified number of seconds. Unless the max-stale
1644                        request directive is also present, the client is not willing to accept a stale response.
1645                     </p>
1646                  </div>
1647                  <div id="rfc.section.5.2.1.1.p.3">
1648                     <p>This directive uses the token form of the argument syntax: e.g., 'max-age=5' not 'max-age="5"'.
1649                        A sender <em class="bcp14">SHOULD NOT</em> generate the quoted-string form.
1650                     </p>
1651                  </div>
1652               </div>
1653               <div id="cache-request-directive.max-stale">
1654                  <h4 id="rfc.section.5.2.1.2"><a href="#rfc.section.5.2.1.2">5.2.1.2</a>&nbsp;<a href="#cache-request-directive.max-stale">max-stale</a></h4>
1655                  <div id="rfc.section.5.2.1.2.p.1">
1656                     <p>Argument syntax: </p>
1657                     <ul class="empty">
1658                        <li><a href="#delta-seconds" class="smpl">delta-seconds</a> (see <a href="#delta-seconds" title="Delta Seconds">Section&nbsp;1.2.1</a>)
1659                        </li>
1660                     </ul>
1661                  </div>
1662                  <div id="rfc.section.5.2.1.2.p.2">
1663                     <p>The "max-stale" request directive indicates that the client is willing to accept a
1664                        response that has exceeded its freshness lifetime. If max-stale is assigned a value,
1665                        then the client is willing to accept a response that has exceeded its freshness lifetime
1666                        by no more than the specified number of seconds. If no value is assigned to max-stale,
1667                        then the client is willing to accept a stale response of any age.
1668                     </p>
1669                  </div>
1670                  <div id="rfc.section.5.2.1.2.p.3">
1671                     <p>This directive uses the token form of the argument syntax: e.g., 'max-stale=10' not
1672                        'max-stale="10"'. A sender <em class="bcp14">SHOULD NOT</em> generate the quoted-string form.
1673                     </p>
1674                  </div>
1675               </div>
1676               <div id="cache-request-directive.min-fresh">
1677                  <h4 id="rfc.section.5.2.1.3"><a href="#rfc.section.5.2.1.3">5.2.1.3</a>&nbsp;<a href="#cache-request-directive.min-fresh">min-fresh</a></h4>
1678                  <div id="rfc.section.5.2.1.3.p.1">
1679                     <p>Argument syntax: </p>
1680                     <ul class="empty">
1681                        <li><a href="#delta-seconds" class="smpl">delta-seconds</a> (see <a href="#delta-seconds" title="Delta Seconds">Section&nbsp;1.2.1</a>)
1682                        </li>
1683                     </ul>
1684                  </div>
1685                  <div id="rfc.section.5.2.1.3.p.2">
1686                     <p>The "min-fresh" request directive indicates that the client is willing to accept a
1687                        response whose freshness lifetime is no less than its current age plus the specified
1688                        time in seconds. That is, the client wants a response that will still be fresh for
1689                        at least the specified number of seconds.
1690                     </p>
1691                  </div>
1692                  <div id="rfc.section.5.2.1.3.p.3">
1693                     <p>This directive uses the token form of the argument syntax: e.g., 'min-fresh=20' not
1694                        'min-fresh="20"'. A sender <em class="bcp14">SHOULD NOT</em> generate the quoted-string form.
1695                     </p>
1696                  </div>
1697               </div>
1698               <div id="cache-request-directive.no-cache">
1699                  <h4 id="rfc.section.5.2.1.4"><a href="#rfc.section.5.2.1.4">5.2.1.4</a>&nbsp;<a href="#cache-request-directive.no-cache">no-cache</a></h4>
1700                  <div id="rfc.section.5.2.1.4.p.1">
1701                     <p>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
1702                        origin server.
1703                     </p>
1704                  </div>
1705               </div>
1706               <div id="cache-request-directive.no-store">
1707                  <h4 id="rfc.section.5.2.1.5"><a href="#rfc.section.5.2.1.5">5.2.1.5</a>&nbsp;<a href="#cache-request-directive.no-store">no-store</a></h4>
1708                  <div id="rfc.section.5.2.1.5.p.1">
1709                     <p>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
1710                        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
1711                        as possible after forwarding it.
1712                     </p>
1713                  </div>
1714                  <div id="rfc.section.5.2.1.5.p.2">
1715                     <p>This directive is NOT a reliable or sufficient mechanism for ensuring privacy. In
1716                        particular, malicious or compromised caches might not recognize or obey this directive,
1717                        and communications networks might be vulnerable to eavesdropping.
1718                     </p>
1719                  </div>
1720                  <div id="rfc.section.5.2.1.5.p.3">
1721                     <p>Note that if a request containing this directive is satisfied from a cache, the no-store
1722                        request directive does not apply to the already stored response.
1723                     </p>
1724                  </div>
1725               </div>
1726               <div id="cache-request-directive.no-transform">
1727                  <h4 id="rfc.section.5.2.1.6"><a href="#rfc.section.5.2.1.6">5.2.1.6</a>&nbsp;<a href="#cache-request-directive.no-transform">no-transform</a></h4>
1728                  <div id="rfc.section.5.2.1.6.p.1">
1729                     <p>The "no-transform" request directive indicates that an intermediary (whether or not
1730                        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="#RFC7230" id="rfc.xref.RFC7230.9"><cite title="Hypertext Transfer Protocol (HTTP/1.1): Message Syntax and Routing">[RFC7230]</cite></a>.
1731                     </p>
1732                  </div>
1733               </div>
1734               <div id="cache-request-directive.only-if-cached">
1735                  <h4 id="rfc.section.5.2.1.7"><a href="#rfc.section.5.2.1.7">5.2.1.7</a>&nbsp;<a href="#cache-request-directive.only-if-cached">only-if-cached</a></h4>
1736                  <div id="rfc.section.5.2.1.7.p.1">
1737                     <p>The "only-if-cached" request directive indicates that the client only wishes to obtain
1738                        a stored response. If it receives this directive, a cache <em class="bcp14">SHOULD</em> either respond using a stored response that is consistent with the other constraints
1739                        of the request, or respond with a <a href="p2-semantics.html#status.504" class="smpl">504 (Gateway
1740                           Timeout)</a> status code. If a group of caches is being operated as a unified system with good
1741                        internal connectivity, a member cache <em class="bcp14">MAY</em> forward such a request within that group of caches.
1742                     </p>
1743                  </div>
1744               </div>
1745            </div>
1746            <div id="cache-response-directive">
1747               <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>
1748               <div id="cache-response-directive.must-revalidate">
1749                  <h4 id="rfc.section.5.2.2.1"><a href="#rfc.section.5.2.2.1">5.2.2.1</a>&nbsp;<a href="#cache-response-directive.must-revalidate">must-revalidate</a></h4>
1750                  <div id="rfc.section.5.2.2.1.p.1">
1751                     <p>The "must-revalidate" response directive indicates that once it has become stale,
1752                        a cache <em class="bcp14">MUST NOT</em> use the response to satisfy subsequent requests without successful validation on the
1753                        origin server.
1754                     </p>
1755                  </div>
1756                  <div id="rfc.section.5.2.2.1.p.2">
1757                     <p>The must-revalidate directive is necessary to support reliable operation for certain
1758                        protocol features. In all circumstances a cache <em class="bcp14">MUST</em> obey the must-revalidate directive; in particular, if a cache cannot reach the origin
1759                        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.
1760                     </p>
1761                  </div>
1762                  <div id="rfc.section.5.2.2.1.p.3">
1763                     <p>The must-revalidate directive ought to be used by servers if and only if failure to
1764                        validate a request on the representation could result in incorrect operation, such
1765                        as a silently unexecuted financial transaction.
1766                     </p>
1767                  </div>
1768               </div>
1769               <div id="cache-response-directive.no-cache">
1770                  <h4 id="rfc.section.5.2.2.2"><a href="#rfc.section.5.2.2.2">5.2.2.2</a>&nbsp;<a href="#cache-response-directive.no-cache">no-cache</a></h4>
1771                  <div id="rfc.section.5.2.2.2.p.1">
1772                     <p>Argument syntax: </p>
1773                     <ul class="empty">
1774                        <li>#<a href="#imported.abnf" class="smpl">field-name</a>
1775                        </li>
1776                     </ul>
1777                  </div>
1778                  <div id="rfc.section.5.2.2.2.p.2">
1779                     <p>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
1780                        server. This allows an origin server to prevent a cache from using it to satisfy a
1781                        request without contacting it, even by caches that have been configured to send stale
1782                        responses.
1783                     </p>
1784                  </div>
1785                  <div id="rfc.section.5.2.2.2.p.3">
1786                     <p>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
1787                        on caching. However, any header fields in the response that have the field-name(s)
1788                        listed <em class="bcp14">MUST NOT</em> be sent in the response to a subsequent request without successful revalidation with
1789                        the origin server. This allows an origin server to prevent the re-use of certain header
1790                        fields in a response, while still allowing caching of the rest of the response.
1791                     </p>
1792                  </div>
1793                  <div id="rfc.section.5.2.2.2.p.4">
1794                     <p>The field-names given are not limited to the set of header fields defined by this
1795                        specification. Field names are case-insensitive.
1796                     </p>
1797                  </div>
1798                  <div id="rfc.section.5.2.2.2.p.5">
1799                     <p>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
1800                        lists).
1801                     </p>
1802                  </div>
1803                  <div id="rfc.section.5.2.2.2.p.6">
1804                     <p><b>Note:</b> Although it has been back-ported to many implementations, some HTTP/1.0 caches will
1805                        not recognize or obey this directive. Also, no-cache response directives with field-names
1806                        are often handled by caches as if an unqualified no-cache directive was received;
1807                        i.e., the special handling for the qualified form is not widely implemented.
1808                     </p>
1809                  </div>
1810               </div>
1811               <div id="cache-response-directive.no-store">
1812                  <h4 id="rfc.section.5.2.2.3"><a href="#rfc.section.5.2.2.3">5.2.2.3</a>&nbsp;<a href="#cache-response-directive.no-store">no-store</a></h4>
1813                  <div id="rfc.section.5.2.2.3.p.1">
1814                     <p>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
1815                        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
1816                        as possible after forwarding it.
1817                     </p>
1818                  </div>
1819                  <div id="rfc.section.5.2.2.3.p.2">
1820                     <p>This directive is NOT a reliable or sufficient mechanism for ensuring privacy. In
1821                        particular, malicious or compromised caches might not recognize or obey this directive,
1822                        and communications networks might be vulnerable to eavesdropping.
1823                     </p>
1824                  </div>
1825               </div>
1826               <div id="cache-response-directive.no-transform">
1827                  <h4 id="rfc.section.5.2.2.4"><a href="#rfc.section.5.2.2.4">5.2.2.4</a>&nbsp;<a href="#cache-response-directive.no-transform">no-transform</a></h4>
1828                  <div id="rfc.section.5.2.2.4.p.1">
1829                     <p>The "no-transform" response directive indicates that an intermediary (regardless of
1830                        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="#RFC7230" id="rfc.xref.RFC7230.10"><cite title="Hypertext Transfer Protocol (HTTP/1.1): Message Syntax and Routing">[RFC7230]</cite></a>.
1831                     </p>
1832                  </div>
1833               </div>
1834               <div id="cache-response-directive.public">
1835                  <h4 id="rfc.section.5.2.2.5"><a href="#rfc.section.5.2.2.5">5.2.2.5</a>&nbsp;<a href="#cache-response-directive.public">public</a></h4>
1836                  <div id="rfc.section.5.2.2.5.p.1">
1837                     <p>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
1838                        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
1839                        to their status codes not being defined as cacheable by default; see <a href="#heuristic.freshness" title="Calculating Heuristic Freshness">Section&nbsp;4.2.2</a>.)
1840                     </p>
1841                  </div>
1842               </div>
1843               <div id="cache-response-directive.private">
1844                  <h4 id="rfc.section.5.2.2.6"><a href="#rfc.section.5.2.2.6">5.2.2.6</a>&nbsp;<a href="#cache-response-directive.private">private</a></h4>
1845                  <div id="rfc.section.5.2.2.6.p.1">
1846                     <p>Argument syntax: </p>
1847                     <ul class="empty">
1848                        <li>#<a href="#imported.abnf" class="smpl">field-name</a>
1849                        </li>
1850                     </ul>
1851                  </div>
1852                  <div id="rfc.section.5.2.2.6.p.2">
1853                     <p>The "private" response directive indicates that the response message is intended for
1854                        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
1855                        be non-cacheable.
1856                     </p>
1857                  </div>
1858                  <div id="rfc.section.5.2.2.6.p.3">
1859                     <p>If the private response directive specifies one or more field-names, this requirement
1860                        is limited to the field-values associated with the listed response header fields.
1861                        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.
1862                     </p>
1863                  </div>
1864                  <div id="rfc.section.5.2.2.6.p.4">
1865                     <p>The field-names given are not limited to the set of header fields defined by this
1866                        specification. Field names are case-insensitive.
1867                     </p>
1868                  </div>
1869                  <div id="rfc.section.5.2.2.6.p.5">
1870                     <p>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
1871                        lists).
1872                     </p>
1873                  </div>
1874                  <div id="rfc.section.5.2.2.6.p.6">
1875                     <p><b>Note:</b> This usage of the word "private" only controls where the response can be stored; it
1876                        cannot ensure the privacy of the message content. Also, private response directives
1877                        with field-names are often handled by caches as if an unqualified private directive
1878                        was received; i.e., the special handling for the qualified form is not widely implemented.
1879                     </p>
1880                  </div>
1881               </div>
1882               <div id="cache-response-directive.proxy-revalidate">
1883                  <h4 id="rfc.section.5.2.2.7"><a href="#rfc.section.5.2.2.7">5.2.2.7</a>&nbsp;<a href="#cache-response-directive.proxy-revalidate">proxy-revalidate</a></h4>
1884                  <div id="rfc.section.5.2.2.7.p.1">
1885                     <p>The "proxy-revalidate" response directive has the same meaning as the must-revalidate
1886                        response directive, except that it does not apply to private caches.
1887                     </p>
1888                  </div>
1889               </div>
1890               <div id="cache-response-directive.max-age">
1891                  <h4 id="rfc.section.5.2.2.8"><a href="#rfc.section.5.2.2.8">5.2.2.8</a>&nbsp;<a href="#cache-response-directive.max-age">max-age</a></h4>
1892                  <div id="rfc.section.5.2.2.8.p.1">
1893                     <p>Argument syntax: </p>
1894                     <ul class="empty">
1895                        <li><a href="#delta-seconds" class="smpl">delta-seconds</a> (see <a href="#delta-seconds" title="Delta Seconds">Section&nbsp;1.2.1</a>)
1896                        </li>
1897                     </ul>
1898                  </div>
1899                  <div id="rfc.section.5.2.2.8.p.2">
1900                     <p>The "max-age" response directive indicates that the response is to be considered stale
1901                        after its age is greater than the specified number of seconds.
1902                     </p>
1903                  </div>
1904                  <div id="rfc.section.5.2.2.8.p.3">
1905                     <p>This directive uses the token form of the argument syntax: e.g., 'max-age=5' not 'max-age="5"'.
1906                        A sender <em class="bcp14">SHOULD NOT</em> generate the quoted-string form.
1907                     </p>
1908                  </div>
1909               </div>
1910               <div id="cache-response-directive.s-maxage">
1911                  <h4 id="rfc.section.5.2.2.9"><a href="#rfc.section.5.2.2.9">5.2.2.9</a>&nbsp;<a href="#cache-response-directive.s-maxage">s-maxage</a></h4>
1912                  <div id="rfc.section.5.2.2.9.p.1">
1913                     <p>Argument syntax: </p>
1914                     <ul class="empty">
1915                        <li><a href="#delta-seconds" class="smpl">delta-seconds</a> (see <a href="#delta-seconds" title="Delta Seconds">Section&nbsp;1.2.1</a>)
1916                        </li>
1917                     </ul>
1918                  </div>
1919                  <div id="rfc.section.5.2.2.9.p.2">
1920                     <p>The "s-maxage" response directive indicates that, in shared caches, the maximum age
1921                        specified by this directive overrides the maximum age specified by either the max-age
1922                        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
1923                        response directive.
1924                     </p>
1925                  </div>
1926                  <div id="rfc.section.5.2.2.9.p.3">
1927                     <p>This directive uses the token form of the argument syntax: e.g., 's-maxage=10' not
1928                        's-maxage="10"'. A sender <em class="bcp14">SHOULD NOT</em> generate the quoted-string form.
1929                     </p>
1930                  </div>
1931               </div>
1932            </div>
1933            <div id="cache.control.extensions">
1934               <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>
1935               <div id="rfc.section.5.2.3.p.1">
1936                  <p>The Cache-Control header field can be extended through the use of one or more cache-extension
1937                     tokens, each with an optional value. A cache <em class="bcp14">MUST</em> ignore unrecognized cache directives.
1938                  </p>
1939               </div>
1940               <div id="rfc.section.5.2.3.p.2">
1941                  <p>Informational extensions (those that do not require a change in cache behavior) can
1942                     be added without changing the semantics of other directives.
1943                  </p>
1944               </div>
1945               <div id="rfc.section.5.2.3.p.3">
1946                  <p>Behavioral extensions are designed to work by acting as modifiers to the existing
1947                     base of cache directives. Both the new directive and the old directive are supplied,
1948                     such that applications that do not understand the new directive will default to the
1949                     behavior specified by the old directive, and those that understand the new directive
1950                     will recognize it as modifying the requirements associated with the old directive.
1951                     In this way, extensions to the existing cache-control directives can be made without
1952                     breaking deployed caches.
1953                  </p>
1954               </div>
1955               <div id="rfc.section.5.2.3.p.4">
1956                  <p>For example, consider a hypothetical new response directive called "community" that
1957                     acts as a modifier to the private directive: in addition to private caches, any cache
1958                     that is shared only by members of the named community is allowed to cache the response.
1959                     An origin server wishing to allow the UCI community to use an otherwise private response
1960                     in their shared cache(s) could do so by including
1961                  </p>
1962               </div>
1963               <div id="rfc.figure.u.8"><pre class="text">  Cache-Control: private, community="UCI"
1964</pre></div>
1965               <div id="rfc.section.5.2.3.p.5">
1966                  <p>A cache that recognizes such a community cache-extension could broaden its behavior
1967                     in accordance with that extension. A cache that does not recognize the community cache-extension
1968                     would ignore it and adhere to the private directive.
1969                  </p>
1970               </div>
1971            </div>
1972         </div>
1973         <div id="header.expires">
1974            <h2 id="rfc.section.5.3"><a href="#rfc.section.5.3">5.3</a>&nbsp;<a href="#header.expires">Expires</a></h2>
1975            <div id="rfc.section.5.3.p.1">
1976               <p>The "Expires" header field gives the date/time after which the response is considered
1977                  stale. See <a href="#expiration.model" title="Freshness">Section&nbsp;4.2</a> for further discussion of the freshness model.
1978               </p>
1979            </div>
1980            <div id="rfc.section.5.3.p.2">
1981               <p>The presence of an Expires field does not imply that the original resource will change
1982                  or cease to exist at, before, or after that time.
1983               </p>
1984            </div>
1985            <div id="rfc.section.5.3.p.3">
1986               <p>The Expires value is an HTTP-date timestamp, as defined in <a href="p2-semantics.html#http.date" title="Date/Time Formats">Section 7.1.1.1</a> of <a href="#RFC7231" id="rfc.xref.RFC7231.8"><cite title="Hypertext Transfer Protocol (HTTP/1.1): Semantics and Content">[RFC7231]</cite></a>.
1987               </p>
1988            </div>
1989            <div id="rfc.figure.u.9"><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>
1990</pre></div>
1991            <div id="rfc.figure.u.10">
1992               <p>For example</p><pre class="text">  Expires: Thu, 01 Dec 1994 16:00:00 GMT
1993</pre></div>
1994            <div id="rfc.section.5.3.p.4">
1995               <p>A cache recipient <em class="bcp14">MUST</em> interpret invalid date formats, especially the value "0", as representing a time in
1996                  the past (i.e., "already expired").
1997               </p>
1998            </div>
1999            <div id="rfc.section.5.3.p.5">
2000               <p>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;5.2.2.8</a>), a recipient <em class="bcp14">MUST</em> ignore the Expires field. Likewise, if a response includes the s-maxage directive
2001                  (<a href="#cache-response-directive.s-maxage" title="s-maxage">Section&nbsp;5.2.2.9</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
2002                  for recipients that have not yet implemented the Cache-Control field.
2003               </p>
2004            </div>
2005            <div id="rfc.section.5.3.p.6">
2006               <p>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
2007                  expired) or its value has been associated with the resource by a system or user with
2008                  a reliable clock.
2009               </p>
2010            </div>
2011            <div id="rfc.section.5.3.p.7">
2012               <p>Historically, HTTP required the Expires field-value to be no more than a year in the
2013                  future. While longer freshness lifetimes are no longer prohibited, extremely large
2014                  values have been demonstrated to cause problems (e.g., clock overflows due to use
2015                  of 32-bit integers for time values), and many caches will evict a response far sooner
2016                  than that.
2017               </p>
2018            </div>
2019         </div>
2020         <div id="header.pragma">
2021            <h2 id="rfc.section.5.4"><a href="#rfc.section.5.4">5.4</a>&nbsp;<a href="#header.pragma">Pragma</a></h2>
2022            <div id="rfc.section.5.4.p.1">
2023               <p>The "Pragma" header field allows backwards compatibility with HTTP/1.0 caches, so
2024                  that clients can specify a "no-cache" request 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
2025                  and understood in a request, Pragma is ignored.
2026               </p>
2027            </div>
2028            <div id="rfc.section.5.4.p.2">
2029               <p>In HTTP/1.0, Pragma was defined as an extensible field for implementation-specified
2030                  directives for recipients. This specification deprecates such extensions to improve
2031                  interoperability.
2032               </p>
2033            </div>
2034            <div id="rfc.figure.u.11"><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>
2035  <a href="#header.pragma" class="smpl">pragma-directive</a> = "no-cache" / <a href="#header.pragma" class="smpl">extension-pragma</a>
2036  <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> ) ]
2037</pre></div>
2038            <div id="rfc.section.5.4.p.3">
2039               <p>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:
2040                  no-cache" were present (see <a href="#cache-request-directive" title="Request Cache-Control Directives">Section&nbsp;5.2.1</a>).
2041               </p>
2042            </div>
2043            <div id="rfc.section.5.4.p.4">
2044               <p>When sending a no-cache request, a client ought to include both the pragma and cache-control
2045                  directives, unless Cache-Control: 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:
2046               </p>
2047            </div>
2048            <div id="rfc.figure.u.12"><pre class="text">GET / HTTP/1.1
2049Host: www.example.com
2050Cache-Control: max-age=30
2051Pragma: no-cache
2052
2053</pre></div>
2054            <div id="rfc.section.5.4.p.5">
2055               <p>will constrain HTTP/1.1 caches to serve a response no older than 30 seconds, while
2056                  precluding implementations that do not understand <a href="#header.cache-control" class="smpl">Cache-Control</a> from serving a cached response.
2057               </p>
2058            </div>
2059            <div class="note">
2060               <div id="rfc.section.5.4.p.6">
2061                  <p><b>Note:</b> Because the meaning of "Pragma: no-cache" in responses is not specified, it does not
2062                     provide a reliable replacement for "Cache-Control: no-cache" in them.
2063                  </p>
2064               </div>
2065            </div>
2066         </div>
2067         <div id="header.warning">
2068            <h2 id="rfc.section.5.5"><a href="#rfc.section.5.5">5.5</a>&nbsp;<a href="#header.warning">Warning</a></h2>
2069            <div id="rfc.section.5.5.p.1">
2070               <p>The "Warning" header field is used to carry additional information about the status
2071                  or transformation of a message that might not be reflected in the status code. This
2072                  information is typically used to warn about possible incorrectness introduced by caching
2073                  operations or transformations applied to the payload of the message.
2074               </p>
2075            </div>
2076            <div id="rfc.section.5.5.p.2">
2077               <p>Warnings can be used for other purposes, both cache-related and otherwise. The use
2078                  of a warning, rather than an error status code, distinguishes these responses from
2079                  true failures.
2080               </p>
2081            </div>
2082            <div id="rfc.section.5.5.p.3">
2083               <p>Warning header fields can in general be applied to any message, however some warn-codes
2084                  are specific to caches and can only be applied to response messages.
2085               </p>
2086            </div>
2087            <div id="rfc.figure.u.13"><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>
2088 
2089  <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>
2090                                        [ <a href="#imported.abnf" class="smpl">SP</a> <a href="#header.warning" class="smpl">warn-date</a> ]
2091 
2092  <a href="#header.warning" class="smpl">warn-code</a>  = 3<a href="#imported.abnf" class="smpl">DIGIT</a>
2093  <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>
2094                  ; the name or pseudonym of the server adding
2095                  ; the Warning header field, for use in debugging
2096                  ; a single "-" is recommended when agent unknown
2097  <a href="#header.warning" class="smpl">warn-text</a>  = <a href="#imported.abnf" class="smpl">quoted-string</a>
2098  <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>
2099</pre></div>
2100            <div id="rfc.section.5.5.p.4">
2101               <p>Multiple warnings can be generated in a response (either by the origin server or by
2102                  a cache), including multiple warnings with the same warn-code number that only differ
2103                  in warn-text.
2104               </p>
2105            </div>
2106            <div id="rfc.section.5.5.p.5">
2107               <p>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
2108                  response. Senders that generate multiple Warning header fields are encouraged to order
2109                  them with this user agent behavior in mind. A sender that generates new Warning header
2110                  fields <em class="bcp14">MUST</em> append them after any existing Warning header fields.
2111               </p>
2112            </div>
2113            <div id="rfc.section.5.5.p.6">
2114               <p>Warnings are assigned three digit warn-codes. The first digit indicates whether the
2115                  Warning is required to be deleted from a stored response after validation:
2116               </p>
2117               <ul>
2118                  <li>1xx warn-codes describe the freshness or validation status of the response, and so
2119                     they <em class="bcp14">MUST</em> be deleted by a cache after validation. They can only be generated by a cache when
2120                     validating a cached entry, and <em class="bcp14">MUST NOT</em> be generated in any other situation.
2121                  </li>
2122                  <li>2xx warn-codes describe some aspect of the representation that is not rectified by
2123                     a validation (for example, a lossy compression of the representation) and they <em class="bcp14">MUST NOT</em> be deleted by a cache after validation, unless a full response is sent, in which case
2124                     they <em class="bcp14">MUST</em> be.
2125                  </li>
2126               </ul>
2127            </div>
2128            <div id="rfc.section.5.5.p.7">
2129               <p>If a sender generates one or more 1xx warn-codes in a message to be sent to a recipient
2130                  known to implement only HTTP/1.0, the sender <em class="bcp14">MUST</em> include in each corresponding warning-value a warn-date that matches the <a href="p2-semantics.html#header.date" class="smpl">Date</a> header field in the message. For example:
2131               </p>
2132            </div>
2133            <div id="rfc.figure.u.14"><pre class="text">HTTP/1.1 200 OK
2134Date: Sat, 25 Aug 2012 23:34:45 GMT
2135Warning: 112 - "network down" "Sat, 25 Aug 2012 23:34:45 GMT"
2136
2137</pre></div>
2138            <div id="rfc.section.5.5.p.8">
2139               <p>Warnings have accompanying warn-text that describes the error, e.g., for logging.
2140                  It is advisory only, and its content does not affect interpretation of the warn-code.
2141               </p>
2142            </div>
2143            <div id="rfc.section.5.5.p.9">
2144               <p>If a recipient that uses, evaluates, or displays Warning header fields receives a
2145                  warn-date that is different from the <a href="p2-semantics.html#header.date" 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
2146                  using the message. This allows recipients to exclude warning-values that were improperly
2147                  retained after a cache validation. If all of the warning-values are excluded, the
2148                  recipient <em class="bcp14">MUST</em> exclude the Warning header field as well.
2149               </p>
2150            </div>
2151            <div id="rfc.section.5.5.p.10">
2152               <p>The following warn-codes are defined by this specification, each with a recommended
2153                  warn-text in English, and a description of its meaning. The procedure for defining
2154                  additional warn codes is described in <a href="#warn.code.registry.procedure" title="Procedure">Section&nbsp;7.2.1</a>.
2155               </p>
2156            </div>
2157            <div id="warn.110">
2158               <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>
2159               <div id="rfc.section.5.5.1.p.1">
2160                  <p>A cache <em class="bcp14">SHOULD</em> generate this whenever the sent response is stale.
2161                  </p>
2162               </div>
2163            </div>
2164            <div id="warn.111">
2165               <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>
2166               <div id="rfc.section.5.5.2.p.1">
2167                  <p>A cache <em class="bcp14">SHOULD</em> generate this when sending a stale response because an attempt to validate the response
2168                     failed, due to an inability to reach the server.
2169                  </p>
2170               </div>
2171            </div>
2172            <div id="warn.112">
2173               <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>
2174               <div id="rfc.section.5.5.3.p.1">
2175                  <p>A cache <em class="bcp14">SHOULD</em> generate this if it is intentionally disconnected from the rest of the network for
2176                     a period of time.
2177                  </p>
2178               </div>
2179            </div>
2180            <div id="warn.113">
2181               <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>
2182               <div id="rfc.section.5.5.4.p.1">
2183                  <p>A cache <em class="bcp14">SHOULD</em> generate this if it heuristically chose a freshness lifetime greater than 24 hours
2184                     and the response's age is greater than 24 hours.
2185                  </p>
2186               </div>
2187            </div>
2188            <div id="warn.199">
2189               <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>
2190               <div id="rfc.section.5.5.5.p.1">
2191                  <p>The warning text can include arbitrary information to be presented to a human user
2192                     or logged. A system receiving this warning <em class="bcp14">MUST NOT</em> take any automated action, besides presenting the warning to the user.
2193                  </p>
2194               </div>
2195            </div>
2196            <div id="warn.214">
2197               <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>
2198               <div id="rfc.section.5.5.6.p.1">
2199                  <p>This Warning code <em class="bcp14">MUST</em> be added by a proxy if it applies any transformation to the representation, such as
2200                     changing the content-coding, media-type, or modifying the representation data, unless
2201                     this Warning code already appears in the response.
2202                  </p>
2203               </div>
2204            </div>
2205            <div id="warn.299">
2206               <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>
2207               <div id="rfc.section.5.5.7.p.1">
2208                  <p>The warning text can include arbitrary information to be presented to a human user
2209                     or logged. A system receiving this warning <em class="bcp14">MUST NOT</em> take any automated action.
2210                  </p>
2211               </div>
2212            </div>
2213         </div>
2214      </div>
2215      <div id="history.lists">
2216         <h1 id="rfc.section.6"><a href="#rfc.section.6">6.</a>&nbsp;<a href="#history.lists">History Lists</a></h1>
2217         <div id="rfc.section.6.p.1">
2218            <p>User agents often have history mechanisms, such as "Back" buttons and history lists,
2219               that can be used to redisplay a representation retrieved earlier in a session.
2220            </p>
2221         </div>
2222         <div id="rfc.section.6.p.2">
2223            <p>The freshness model (<a href="#expiration.model" title="Freshness">Section&nbsp;4.2</a>) does not necessarily apply to history mechanisms. That is, a history mechanism can
2224               display a previous representation even if it has expired.
2225            </p>
2226         </div>
2227         <div id="rfc.section.6.p.3">
2228            <p>This does not prohibit the history mechanism from telling the user that a view might
2229               be stale or from honoring cache directives (e.g., Cache-Control: no-store).
2230            </p>
2231         </div>
2232      </div>
2233      <div id="iana.considerations">
2234         <h1 id="rfc.section.7"><a href="#rfc.section.7">7.</a>&nbsp;<a href="#iana.considerations">IANA Considerations</a></h1>
2235         <div id="cache.directive.registry">
2236            <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>
2237            <div id="rfc.section.7.1.p.1">
2238               <p>The "Hypertext Transfer Protocol (HTTP) Cache Directive Registry" defines the namespace
2239                  for the cache directives. It has been created and is now maintained at &lt;<a href="http://www.iana.org/assignments/http-cache-directives">http://www.iana.org/assignments/http-cache-directives</a>&gt;.
2240               </p>
2241            </div>
2242            <div id="cache.directive.registry.procedure">
2243               <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>
2244               <div id="rfc.section.7.1.1.p.1">
2245                  <p>A registration <em class="bcp14">MUST</em> include the following fields:
2246                  </p>
2247                  <ul>
2248                     <li>Cache Directive Name</li>
2249                     <li>Pointer to specification text</li>
2250                  </ul>
2251               </div>
2252               <div id="rfc.section.7.1.1.p.2">
2253                  <p>Values to be added to this namespace 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="https://tools.ietf.org/html/rfc5226#section-4.1">Section 4.1</a>).
2254                  </p>
2255               </div>
2256            </div>
2257            <div id="cache.directive.considerations">
2258               <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>
2259               <div id="rfc.section.7.1.2.p.1">
2260                  <p>New extension directives ought to consider defining:</p>
2261               </div>
2262               <div id="rfc.section.7.1.2.p.2">
2263                  <ul>
2264                     <li>What it means for a directive to be specified multiple times,</li>
2265                     <li>When the directive does not take an argument, what it means when an argument is present,</li>
2266                     <li>When the directive requires an argument, what it means when it is missing,</li>
2267                     <li>Whether the directive is specific to requests, responses, or able to be used in either.</li>
2268                  </ul>
2269               </div>
2270               <div id="rfc.section.7.1.2.p.3">
2271                  <p>See also <a href="#cache.control.extensions" title="Cache Control Extensions">Section&nbsp;5.2.3</a>.
2272                  </p>
2273               </div>
2274            </div>
2275            <div id="cache.directive.registration">
2276               <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>
2277               <div id="rfc.section.7.1.3.p.1">
2278                  <p>The registry has been populated with the registrations below:</p>
2279               </div>
2280               <div id="rfc.table.1">
2281                  <div id="iana.cache.directive.registration.table"></div>
2282                  <table class="tt full left" cellpadding="3" cellspacing="0">
2283                     <thead>
2284                        <tr>
2285                           <th>Cache Directive</th>
2286                           <th>Reference</th>
2287                        </tr>
2288                     </thead>
2289                     <tbody>
2290                        <tr>
2291                           <td class="left">max-age</td>
2292                           <td class="left"><a href="#cache-request-directive.max-age" title="max-age">Section&nbsp;5.2.1.1</a>, <a href="#cache-response-directive.max-age" title="max-age">Section&nbsp;5.2.2.8</a>
2293                           </td>
2294                        </tr>
2295                        <tr>
2296                           <td class="left">max-stale</td>
2297                           <td class="left"><a href="#cache-request-directive.max-stale" title="max-stale">Section&nbsp;5.2.1.2</a>
2298                           </td>
2299                        </tr>
2300                        <tr>
2301                           <td class="left">min-fresh</td>
2302                           <td class="left"><a href="#cache-request-directive.min-fresh" title="min-fresh">Section&nbsp;5.2.1.3</a>
2303                           </td>
2304                        </tr>
2305                        <tr>
2306                           <td class="left">must-revalidate</td>
2307                           <td class="left"><a href="#cache-response-directive.must-revalidate" title="must-revalidate">Section&nbsp;5.2.2.1</a>
2308                           </td>
2309                        </tr>
2310                        <tr>
2311                           <td class="left">no-cache</td>
2312                           <td class="left"><a href="#cache-request-directive.no-cache" title="no-cache">Section&nbsp;5.2.1.4</a>, <a href="#cache-response-directive.no-cache" title="no-cache">Section&nbsp;5.2.2.2</a>
2313                           </td>
2314                        </tr>
2315                        <tr>
2316                           <td class="left">no-store</td>
2317                           <td class="left"><a href="#cache-request-directive.no-store" title="no-store">Section&nbsp;5.2.1.5</a>, <a href="#cache-response-directive.no-store" title="no-store">Section&nbsp;5.2.2.3</a>
2318                           </td>
2319                        </tr>
2320                        <tr>
2321                           <td class="left">no-transform</td>
2322                           <td class="left"><a href="#cache-request-directive.no-transform" title="no-transform">Section&nbsp;5.2.1.6</a>, <a href="#cache-response-directive.no-transform" title="no-transform">Section&nbsp;5.2.2.4</a>
2323                           </td>
2324                        </tr>
2325                        <tr>
2326                           <td class="left">only-if-cached</td>
2327                           <td class="left"><a href="#cache-request-directive.only-if-cached" title="only-if-cached">Section&nbsp;5.2.1.7</a>
2328                           </td>
2329                        </tr>
2330                        <tr>
2331                           <td class="left">private</td>
2332                           <td class="left"><a href="#cache-response-directive.private" title="private">Section&nbsp;5.2.2.6</a>
2333                           </td>
2334                        </tr>
2335                        <tr>
2336                           <td class="left">proxy-revalidate</td>
2337                           <td class="left"><a href="#cache-response-directive.proxy-revalidate" title="proxy-revalidate">Section&nbsp;5.2.2.7</a>
2338                           </td>
2339                        </tr>
2340                        <tr>
2341                           <td class="left">public</td>
2342                           <td class="left"><a href="#cache-response-directive.public" title="public">Section&nbsp;5.2.2.5</a>
2343                           </td>
2344                        </tr>
2345                        <tr>
2346                           <td class="left">s-maxage</td>
2347                           <td class="left"><a href="#cache-response-directive.s-maxage" title="s-maxage">Section&nbsp;5.2.2.9</a>
2348                           </td>
2349                        </tr>
2350                        <tr>
2351                           <td class="left">stale-if-error</td>
2352                           <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="https://tools.ietf.org/html/rfc5861#section-4">Section 4</a>
2353                           </td>
2354                        </tr>
2355                        <tr>
2356                           <td class="left">stale-while-revalidate</td>
2357                           <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="https://tools.ietf.org/html/rfc5861#section-3">Section 3</a>
2358                           </td>
2359                        </tr>
2360                     </tbody>
2361                  </table>
2362               </div>
2363            </div>
2364         </div>
2365         <div id="warn.code.registry">
2366            <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>
2367            <div id="rfc.section.7.2.p.1">
2368               <p>The "Hypertext Transfer Protocol (HTTP) Warn Codes" registry defines the namespace
2369                  for warn codes. It has been created and is now maintained at &lt;<a href="http://www.iana.org/assignments/http-warn-codes">http://www.iana.org/assignments/http-warn-codes</a>&gt;.
2370               </p>
2371            </div>
2372            <div id="warn.code.registry.procedure">
2373               <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>
2374               <div id="rfc.section.7.2.1.p.1">
2375                  <p>A registration <em class="bcp14">MUST</em> include the following fields:
2376                  </p>
2377                  <ul>
2378                     <li>Warn Code (3 digits)</li>
2379                     <li>Short Description</li>
2380                     <li>Pointer to specification text</li>
2381                  </ul>
2382               </div>
2383               <div id="rfc.section.7.2.1.p.2">
2384                  <p>Values to be added to this namespace 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="https://tools.ietf.org/html/rfc5226#section-4.1">Section 4.1</a>).
2385                  </p>
2386               </div>
2387            </div>
2388            <div id="warn.code.registration">
2389               <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>
2390               <div id="rfc.section.7.2.2.p.1">
2391                  <p>The registry has been populated with the registrations below:</p>
2392               </div>
2393               <div id="rfc.table.2">
2394                  <div id="iana.warn.code.registration.table"></div>
2395                  <table class="tt full left" cellpadding="3" cellspacing="0">
2396                     <thead>
2397                        <tr>
2398                           <th>Warn Code</th>
2399                           <th>Short Description</th>
2400                           <th>Reference</th>
2401                        </tr>
2402                     </thead>
2403                     <tbody>
2404                        <tr>
2405                           <td class="left">110</td>
2406                           <td class="left">Response is Stale</td>
2407                           <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>
2408                           </td>
2409                        </tr>
2410                        <tr>
2411                           <td class="left">111</td>
2412                           <td class="left">Revalidation Failed</td>
2413                           <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>
2414                           </td>
2415                        </tr>
2416                        <tr>
2417                           <td class="left">112</td>
2418                           <td class="left">Disconnected Operation</td>
2419                           <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>
2420                           </td>
2421                        </tr>
2422                        <tr>
2423                           <td class="left">113</td>
2424                           <td class="left">Heuristic Expiration</td>
2425                           <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>
2426                           </td>
2427                        </tr>
2428                        <tr>
2429                           <td class="left">199</td>
2430                           <td class="left">Miscellaneous Warning</td>
2431                           <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>
2432                           </td>
2433                        </tr>
2434                        <tr>
2435                           <td class="left">214</td>
2436                           <td class="left">Transformation Applied</td>
2437                           <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>
2438                           </td>
2439                        </tr>
2440                        <tr>
2441                           <td class="left">299</td>
2442                           <td class="left">Miscellaneous Persistent Warning</td>
2443                           <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>
2444                           </td>
2445                        </tr>
2446                     </tbody>
2447                  </table>
2448               </div>
2449            </div>
2450         </div>
2451         <div id="header.field.registration">
2452            <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>
2453            <div id="rfc.section.7.3.p.1">
2454               <p>HTTP header fields are registered within the "Message Headers" registry maintained
2455                  at &lt;<a href="http://www.iana.org/assignments/message-headers/">http://www.iana.org/assignments/message-headers/</a>&gt;.
2456               </p>
2457            </div>
2458            <div id="rfc.section.7.3.p.2">
2459               <p>This document defines the following HTTP header fields, so the "Permanent Message
2460                  Header Field Names" registry has been updated accordingly (see <a href="#BCP90" id="rfc.xref.BCP90.1"><cite title="Registration Procedures for Message Header Fields">[BCP90]</cite></a>).
2461               </p>
2462            </div>
2463            <div id="rfc.table.3">
2464               <div id="iana.header.registration.table"></div>
2465               <table class="tt full left" cellpadding="3" cellspacing="0">
2466                  <thead>
2467                     <tr>
2468                        <th>Header Field Name</th>
2469                        <th>Protocol</th>
2470                        <th>Status</th>
2471                        <th>Reference</th>
2472                     </tr>
2473                  </thead>
2474                  <tbody>
2475                     <tr>
2476                        <td class="left">Age</td>
2477                        <td class="left">http</td>
2478                        <td class="left">standard</td>
2479                        <td class="left"><a href="#header.age" id="rfc.xref.header.age.3" title="Age">Section&nbsp;5.1</a>
2480                        </td>
2481                     </tr>
2482                     <tr>
2483                        <td class="left">Cache-Control</td>
2484                        <td class="left">http</td>
2485                        <td class="left">standard</td>
2486                        <td class="left"><a href="#header.cache-control" id="rfc.xref.header.cache-control.2" title="Cache-Control">Section&nbsp;5.2</a>
2487                        </td>
2488                     </tr>
2489                     <tr>
2490                        <td class="left">Expires</td>
2491                        <td class="left">http</td>
2492                        <td class="left">standard</td>
2493                        <td class="left"><a href="#header.expires" id="rfc.xref.header.expires.4" title="Expires">Section&nbsp;5.3</a>
2494                        </td>
2495                     </tr>
2496                     <tr>
2497                        <td class="left">Pragma</td>
2498                        <td class="left">http</td>
2499                        <td class="left">standard</td>
2500                        <td class="left"><a href="#header.pragma" id="rfc.xref.header.pragma.2" title="Pragma">Section&nbsp;5.4</a>
2501                        </td>
2502                     </tr>
2503                     <tr>
2504                        <td class="left">Warning</td>
2505                        <td class="left">http</td>
2506                        <td class="left">standard</td>
2507                        <td class="left"><a href="#header.warning" id="rfc.xref.header.warning.4" title="Warning">Section&nbsp;5.5</a>
2508                        </td>
2509                     </tr>
2510                  </tbody>
2511               </table>
2512            </div>
2513            <div id="rfc.section.7.3.p.3">
2514               <p>The change controller is: "IETF (iesg@ietf.org) - Internet Engineering Task Force".</p>
2515            </div>
2516         </div>
2517      </div>
2518      <div id="security.considerations">
2519         <h1 id="rfc.section.8"><a href="#rfc.section.8">8.</a>&nbsp;<a href="#security.considerations">Security Considerations</a></h1>
2520         <div id="rfc.section.8.p.1">
2521            <p>This section is meant to inform developers, information providers, and users of known
2522               security concerns specific to HTTP caching. More general security considerations are
2523               addressed in HTTP messaging <a href="#RFC7230" id="rfc.xref.RFC7230.11"><cite title="Hypertext Transfer Protocol (HTTP/1.1): Message Syntax and Routing">[RFC7230]</cite></a> and semantics <a href="#RFC7231" id="rfc.xref.RFC7231.9"><cite title="Hypertext Transfer Protocol (HTTP/1.1): Semantics and Content">[RFC7231]</cite></a>.
2524            </p>
2525         </div>
2526         <div id="rfc.section.8.p.2">
2527            <p>Caches expose additional potential vulnerabilities, since the contents of the cache
2528               represent an attractive target for malicious exploitation. Because cache contents
2529               persist after an HTTP request is complete, an attack on the cache can reveal information
2530               long after a user believes that the information has been removed from the network.
2531               Therefore, cache contents need to be protected as sensitive information.
2532            </p>
2533         </div>
2534         <div id="rfc.section.8.p.3">
2535            <p>In particular, various attacks might be amplified by being stored in a shared cache;
2536               such "cache poisoning" attacks use the cache to distribute a malicious payload to
2537               many clients, and are especially effective when an attacker can use implementation
2538               flaws, elevated privileges, or other techniques to insert such a response into a cache.
2539               One common attack vector for cache poisoning is to exploit differences in message
2540               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="#RFC7230" id="rfc.xref.RFC7230.12"><cite title="Hypertext Transfer Protocol (HTTP/1.1): Message Syntax and Routing">[RFC7230]</cite></a> for the relevant requirements.
2541            </p>
2542         </div>
2543         <div id="rfc.section.8.p.4">
2544            <p>Likewise, implementation flaws (as well as misunderstanding of cache operation) might
2545               lead to caching of sensitive information (e.g., authentication credentials) that is
2546               thought to be private, exposing it to unauthorized parties.
2547            </p>
2548         </div>
2549         <div id="rfc.section.8.p.5">
2550            <p>Furthermore, the very use of a cache can bring about privacy concerns. For example,
2551               if two users share a cache, and the first one browses to a site, the second may be
2552               able to detect that the other has been to that site, because the resources from it
2553               load more quickly, thanks to the cache.
2554            </p>
2555         </div>
2556         <div id="rfc.section.8.p.6">
2557            <p>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
2558               be (and often is) used to satisfy subsequent requests to caches. Servers who wish
2559               to control caching of these responses are encouraged to emit appropriate Cache-Control
2560               response header fields.
2561            </p>
2562         </div>
2563      </div>
2564      <div id="acks">
2565         <h1 id="rfc.section.9"><a href="#rfc.section.9">9.</a>&nbsp;<a href="#acks">Acknowledgments</a></h1>
2566         <div id="rfc.section.9.p.1">
2567            <p>See <a href="p1-messaging.html#acks" title="Acknowledgments">Section 10</a> of <a href="#RFC7230" id="rfc.xref.RFC7230.13"><cite title="Hypertext Transfer Protocol (HTTP/1.1): Message Syntax and Routing">[RFC7230]</cite></a>.
2568            </p>
2569         </div>
2570      </div>
2571      <h1 id="rfc.references"><a id="rfc.section.10" href="#rfc.section.10">10.</a> References
2572      </h1>
2573      <h2 id="rfc.references.1"><a href="#rfc.section.10.1" id="rfc.section.10.1">10.1</a> Normative References
2574      </h2>
2575      <table>
2576         <tr>
2577            <td class="reference"><b id="RFC2119">[RFC2119]</b></td>
2578            <td class="top">Bradner, S., “<a href="https://tools.ietf.org/html/rfc2119">Key words for use in RFCs to Indicate Requirement Levels</a>”, BCP&nbsp;14, RFC&nbsp;2119, March&nbsp;1997.
2579            </td>
2580         </tr>
2581         <tr>
2582            <td class="reference"><b id="RFC5234">[RFC5234]</b></td>
2583            <td class="top">Crocker, D., Ed. and P. Overell, “<a href="https://tools.ietf.org/html/rfc5234">Augmented BNF for Syntax Specifications: ABNF</a>”, STD&nbsp;68, RFC&nbsp;5234, January&nbsp;2008.
2584            </td>
2585         </tr>
2586         <tr>
2587            <td class="reference"><b id="RFC7230">[RFC7230]</b></td>
2588            <td class="top">Fielding, R., Ed. and J. Reschke, Ed., “<a href="https://tools.ietf.org/html/rfc7230">Hypertext Transfer Protocol (HTTP/1.1): Message Syntax and Routing</a>”, RFC&nbsp;7230, June&nbsp;2014.
2589            </td>
2590         </tr>
2591         <tr>
2592            <td class="reference"><b id="RFC7231">[RFC7231]</b></td>
2593            <td class="top">Fielding, R., Ed. and J. Reschke, Ed., “<a href="https://tools.ietf.org/html/draft-ietf-httpbis-p2-semantics-latest">Hypertext Transfer Protocol (HTTP/1.1): Semantics and Content</a>”, Internet-Draft&nbsp;draft-ietf-httpbis-p2-semantics-latest (work in progress), June&nbsp;2014.
2594            </td>
2595         </tr>
2596         <tr>
2597            <td class="reference"><b id="RFC7232">[RFC7232]</b></td>
2598            <td class="top">Fielding, R., Ed. and J. Reschke, Ed., “<a href="https://tools.ietf.org/html/draft-ietf-httpbis-p4-conditional-latest">Hypertext Transfer Protocol (HTTP/1.1): Conditional Requests</a>”, Internet-Draft&nbsp;draft-ietf-httpbis-p4-conditional-latest (work in progress), June&nbsp;2014.
2599            </td>
2600         </tr>
2601         <tr>
2602            <td class="reference"><b id="RFC7233">[RFC7233]</b></td>
2603            <td class="top">Fielding, R., Ed., Lafon, Y., Ed., and J. Reschke, Ed., “<a href="https://tools.ietf.org/html/draft-ietf-httpbis-p5-range-latest">Hypertext Transfer Protocol (HTTP/1.1): Range Requests</a>”, Internet-Draft&nbsp;draft-ietf-httpbis-p5-range-latest (work in progress), June&nbsp;2014.
2604            </td>
2605         </tr>
2606         <tr>
2607            <td class="reference"><b id="RFC7235">[RFC7235]</b></td>
2608            <td class="top">Fielding, R., Ed. and J. Reschke, Ed., “<a href="https://tools.ietf.org/html/draft-ietf-httpbis-p7-auth-latest">Hypertext Transfer Protocol (HTTP/1.1): Authentication</a>”, Internet-Draft&nbsp;draft-ietf-httpbis-p7-auth-latest (work in progress), June&nbsp;2014.
2609            </td>
2610         </tr>
2611      </table>
2612      <h2 id="rfc.references.2"><a href="#rfc.section.10.2" id="rfc.section.10.2">10.2</a> Informative References
2613      </h2>
2614      <table>
2615         <tr>
2616            <td class="reference"><b id="BCP90">[BCP90]</b></td>
2617            <td class="top">Klyne, G., Nottingham, M., and J. Mogul, “<a href="https://tools.ietf.org/html/rfc3864">Registration Procedures for Message Header Fields</a>”, BCP&nbsp;90, RFC&nbsp;3864, September&nbsp;2004.
2618            </td>
2619         </tr>
2620         <tr>
2621            <td class="reference"><b id="RFC2616">[RFC2616]</b></td>
2622            <td class="top">Fielding, R., Gettys, J., Mogul, J., Frystyk, H., Masinter, L., Leach, P., and T. Berners-Lee, “<a href="https://tools.ietf.org/html/rfc2616">Hypertext Transfer Protocol -- HTTP/1.1</a>”, RFC&nbsp;2616, June&nbsp;1999.
2623            </td>
2624         </tr>
2625         <tr>
2626            <td class="reference"><b id="RFC5226">[RFC5226]</b></td>
2627            <td class="top">Narten, T. and H. Alvestrand, “<a href="https://tools.ietf.org/html/rfc5226">Guidelines for Writing an IANA Considerations Section in RFCs</a>”, BCP&nbsp;26, RFC&nbsp;5226, May&nbsp;2008.
2628            </td>
2629         </tr>
2630         <tr>
2631            <td class="reference"><b id="RFC5861">[RFC5861]</b></td>
2632            <td class="top">Nottingham, M., “<a href="https://tools.ietf.org/html/rfc5861">HTTP Cache-Control Extensions for Stale Content</a>”, RFC&nbsp;5861, April&nbsp;2010.
2633            </td>
2634         </tr>
2635         <tr>
2636            <td class="reference"><b id="RFC5905">[RFC5905]</b></td>
2637            <td class="top">Mills, D., Martin, J., Ed., Burbank, J., and W. Kasch, “<a href="https://tools.ietf.org/html/rfc5905">Network Time Protocol Version 4: Protocol and Algorithms Specification</a>”, RFC&nbsp;5905, June&nbsp;2010.
2638            </td>
2639         </tr>
2640         <tr>
2641            <td class="reference"><b id="RFC6265">[RFC6265]</b></td>
2642            <td class="top">Barth, A., “<a href="https://tools.ietf.org/html/rfc6265">HTTP State Management Mechanism</a>”, RFC&nbsp;6265, April&nbsp;2011.
2643            </td>
2644         </tr>
2645      </table>
2646      <div id="changes.from.rfc.2616">
2647         <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>
2648         <div id="rfc.section.A.p.1">
2649            <p>The specification has been substantially rewritten for clarity.</p>
2650         </div>
2651         <div id="rfc.section.A.p.2">
2652            <p>The conditions under which an authenticated response can be cached have been clarified.
2653               (<a href="#caching.authenticated.responses" title="Storing Responses to Authenticated Requests">Section&nbsp;3.2</a>)
2654            </p>
2655         </div>
2656         <div id="rfc.section.A.p.3">
2657            <p>New status codes can now define that caches are allowed to use heuristic freshness
2658               with them. Caches are now allowed to calculate heuristic freshness for URIs with query
2659               components. (<a href="#heuristic.freshness" title="Calculating Heuristic Freshness">Section&nbsp;4.2.2</a>)
2660            </p>
2661         </div>
2662         <div id="rfc.section.A.p.4">
2663            <p>The algorithm for calculating age is now less conservative. Caches are now required
2664               to handle dates with time zones as if they're invalid, because it's not possible to
2665               accurately guess. (<a href="#age.calculations" title="Calculating Age">Section&nbsp;4.2.3</a>)
2666            </p>
2667         </div>
2668         <div id="rfc.section.A.p.5">
2669            <p>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
2670               when validating. (<a href="#validation.model" title="Validation">Section&nbsp;4.3</a>)
2671            </p>
2672         </div>
2673         <div id="rfc.section.A.p.6">
2674            <p>The algorithm for selecting a cached negotiated response to use has been clarified
2675               in several ways. In particular, it now explicitly allows header-specific canonicalization
2676               when processing selecting header fields. (<a href="#caching.negotiated.responses" title="Calculating Secondary Keys with Vary">Section&nbsp;4.1</a>)
2677            </p>
2678         </div>
2679         <div id="rfc.section.A.p.7">
2680            <p>Requirements regarding denial-of-service attack avoidance when performing invalidation
2681               have been clarified. (<a href="#invalidation" title="Invalidation">Section&nbsp;4.4</a>)
2682            </p>
2683         </div>
2684         <div id="rfc.section.A.p.8">
2685            <p>Cache invalidation only occurs when a successful response is received. (<a href="#invalidation" title="Invalidation">Section&nbsp;4.4</a>)
2686            </p>
2687         </div>
2688         <div id="rfc.section.A.p.9">
2689            <p>Cache directives are explicitly defined to be case-insensitive. Handling of multiple
2690               instances of cache directives when only 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>)
2691            </p>
2692         </div>
2693         <div id="rfc.section.A.p.10">
2694            <p>The "no-store" request directive doesn't apply to responses; i.e., a cache can satisfy
2695               a request with no-store on it and does not invalidate it. (<a href="#cache-request-directive.no-store" title="no-store">Section&nbsp;5.2.1.5</a>)
2696            </p>
2697         </div>
2698         <div id="rfc.section.A.p.11">
2699            <p>The qualified forms of the private and no-cache cache directives are noted to not
2700               be widely implemented; for example, "private=foo" is interpreted by many caches as
2701               simply "private". Additionally, the meaning of the qualified form of no-cache has
2702               been clarified. (<a href="#cache-response-directive" title="Response Cache-Control Directives">Section&nbsp;5.2.2</a>)
2703            </p>
2704         </div>
2705         <div id="rfc.section.A.p.12">
2706            <p>The "no-cache" response directive's meaning has been clarified. (<a href="#cache-response-directive.no-cache" title="no-cache">Section&nbsp;5.2.2.2</a>)
2707            </p>
2708         </div>
2709         <div id="rfc.section.A.p.13">
2710            <p>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
2711               value is given. (<a href="#header.expires" id="rfc.xref.header.expires.5" title="Expires">Section&nbsp;5.3</a>)
2712            </p>
2713         </div>
2714         <div id="rfc.section.A.p.14">
2715            <p>The <a href="#header.pragma" class="smpl">Pragma</a> header field is now only defined for backwards compatibility; future pragmas are deprecated.
2716               (<a href="#header.pragma" id="rfc.xref.header.pragma.3" title="Pragma">Section&nbsp;5.4</a>)
2717            </p>
2718         </div>
2719         <div id="rfc.section.A.p.15">
2720            <p>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 does it allow multiple languages,
2721               as these aspects were not implemented. (<a href="#header.warning" id="rfc.xref.header.warning.5" title="Warning">Section&nbsp;5.5</a>)
2722            </p>
2723         </div>
2724         <div id="rfc.section.A.p.16">
2725            <p>This specification introduces the Cache Directive and Warn Code Registries, and defines
2726               considerations for new cache directives. (<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>)
2727            </p>
2728         </div>
2729      </div>
2730      <div id="imported.abnf">
2731         <h1 id="rfc.section.B"><a href="#rfc.section.B">B.</a>&nbsp;<a href="#imported.abnf">Imported ABNF</a></h1>
2732         <div id="rfc.section.B.p.1">
2733            <p>The following core rules are included by reference, as defined in <a href="https://tools.ietf.org/html/rfc5234#appendix-B.1">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
2734               0-9), DQUOTE (double quote), HEXDIG (hexadecimal 0-9/A-F/a-f), LF (line feed), OCTET
2735               (any 8-bit sequence of data), SP (space), and VCHAR (any visible US-ASCII character).
2736            </p>
2737         </div>
2738         <div id="rfc.section.B.p.2">
2739            <p>The rules below are defined in <a href="#RFC7230" id="rfc.xref.RFC7230.14"><cite title="Hypertext Transfer Protocol (HTTP/1.1): Message Syntax and Routing">[RFC7230]</cite></a>:
2740            </p>
2741         </div>
2742         <div id="rfc.figure.u.15"><pre class="inline">  <a href="#imported.abnf" class="smpl">OWS</a>           = &lt;OWS, see <a href="#RFC7230" id="rfc.xref.RFC7230.15"><cite title="Hypertext Transfer Protocol (HTTP/1.1): Message Syntax and Routing">[RFC7230]</cite></a>, <a href="p1-messaging.html#whitespace" title="Whitespace">Section 3.2.3</a>&gt;
2743  <a href="#imported.abnf" class="smpl">field-name</a>    = &lt;field-name, see <a href="#RFC7230" id="rfc.xref.RFC7230.16"><cite title="Hypertext Transfer Protocol (HTTP/1.1): Message Syntax and Routing">[RFC7230]</cite></a>, <a href="p1-messaging.html#header.fields" title="Header Fields">Section 3.2</a>&gt;
2744  <a href="#imported.abnf" class="smpl">quoted-string</a> = &lt;quoted-string, see <a href="#RFC7230" id="rfc.xref.RFC7230.17"><cite title="Hypertext Transfer Protocol (HTTP/1.1): Message Syntax and Routing">[RFC7230]</cite></a>, <a href="p1-messaging.html#field.components" title="Field Value Components">Section 3.2.6</a>&gt;
2745  <a href="#imported.abnf" class="smpl">token</a>         = &lt;token, see <a href="#RFC7230" id="rfc.xref.RFC7230.18"><cite title="Hypertext Transfer Protocol (HTTP/1.1): Message Syntax and Routing">[RFC7230]</cite></a>, <a href="p1-messaging.html#field.components" title="Field Value Components">Section 3.2.6</a>&gt;
2746
2747  <a href="#imported.abnf" class="smpl">port</a>          = &lt;port, see <a href="#RFC7230" id="rfc.xref.RFC7230.19"><cite title="Hypertext Transfer Protocol (HTTP/1.1): Message Syntax and Routing">[RFC7230]</cite></a>, <a href="p1-messaging.html#uri" title="Uniform Resource Identifiers">Section 2.7</a>&gt;
2748  <a href="#imported.abnf" class="smpl">pseudonym</a>     = &lt;pseudonym, see <a href="#RFC7230" id="rfc.xref.RFC7230.20"><cite title="Hypertext Transfer Protocol (HTTP/1.1): Message Syntax and Routing">[RFC7230]</cite></a>, <a href="p1-messaging.html#header.via" title="Via">Section 5.7.1</a>&gt;
2749  <a href="#imported.abnf" class="smpl">uri-host</a>      = &lt;uri-host, see <a href="#RFC7230" id="rfc.xref.RFC7230.21"><cite title="Hypertext Transfer Protocol (HTTP/1.1): Message Syntax and Routing">[RFC7230]</cite></a>, <a href="p1-messaging.html#uri" title="Uniform Resource Identifiers">Section 2.7</a>&gt;
2750</pre></div>
2751         <div id="rfc.section.B.p.3">
2752            <p>The rules below are defined in other parts:</p>
2753         </div>
2754         <div id="rfc.figure.u.16"><pre class="inline">  <a href="#imported.abnf" class="smpl">HTTP-date</a>     = &lt;HTTP-date, see <a href="#RFC7231" id="rfc.xref.RFC7231.10"><cite title="Hypertext Transfer Protocol (HTTP/1.1): Semantics and Content">[RFC7231]</cite></a>, <a href="p2-semantics.html#http.date" title="Date/Time Formats">Section 7.1.1.1</a>&gt;
2755</pre></div>
2756      </div>
2757      <div id="collected.abnf">
2758         <h1 id="rfc.section.C"><a href="#rfc.section.C">C.</a>&nbsp;<a href="#collected.abnf">Collected ABNF</a></h1>
2759         <div id="rfc.section.C.p.1">
2760            <p>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="#RFC7230" id="rfc.xref.RFC7230.22"><cite title="Hypertext Transfer Protocol (HTTP/1.1): Message Syntax and Routing">[RFC7230]</cite></a>.
2761            </p>
2762         </div>
2763         <div id="rfc.figure.u.17"><pre class="inline"><a href="#header.age" class="smpl">Age</a> = delta-seconds
2764
2765<a href="#header.cache-control" class="smpl">Cache-Control</a> = *( "," OWS ) cache-directive *( OWS "," [ OWS
2766 cache-directive ] )
2767
2768<a href="#header.expires" class="smpl">Expires</a> = HTTP-date
2769
2770<a href="#imported.abnf" class="smpl">HTTP-date</a> = &lt;HTTP-date, see [RFC7231], Section 7.1.1.1&gt;
2771
2772<a href="#imported.abnf" class="smpl">OWS</a> = &lt;OWS, see [RFC7230], Section 3.2.3&gt;
2773
2774<a href="#header.pragma" class="smpl">Pragma</a> = *( "," OWS ) pragma-directive *( OWS "," [ OWS
2775 pragma-directive ] )
2776
2777<a href="#header.warning" class="smpl">Warning</a> = *( "," OWS ) warning-value *( OWS "," [ OWS warning-value ]
2778 )
2779
2780<a href="#header.cache-control" class="smpl">cache-directive</a> = token [ "=" ( token / quoted-string ) ]
2781
2782<a href="#delta-seconds" class="smpl">delta-seconds</a> = 1*DIGIT
2783
2784<a href="#header.pragma" class="smpl">extension-pragma</a> = token [ "=" ( token / quoted-string ) ]
2785
2786<a href="#imported.abnf" class="smpl">field-name</a> = &lt;field-name, see [RFC7230], Section 3.2&gt;
2787
2788<a href="#imported.abnf" class="smpl">port</a> = &lt;port, see [RFC7230], Section 2.7&gt;
2789<a href="#header.pragma" class="smpl">pragma-directive</a> = "no-cache" / extension-pragma
2790<a href="#imported.abnf" class="smpl">pseudonym</a> = &lt;pseudonym, see [RFC7230], Section 5.7.1&gt;
2791
2792<a href="#imported.abnf" class="smpl">quoted-string</a> = &lt;quoted-string, see [RFC7230], Section 3.2.6&gt;
2793
2794<a href="#imported.abnf" class="smpl">token</a> = &lt;token, see [RFC7230], Section 3.2.6&gt;
2795
2796<a href="#imported.abnf" class="smpl">uri-host</a> = &lt;uri-host, see [RFC7230], Section 2.7&gt;
2797
2798<a href="#header.warning" class="smpl">warn-agent</a> = ( uri-host [ ":" port ] ) / pseudonym
2799<a href="#header.warning" class="smpl">warn-code</a> = 3DIGIT
2800<a href="#header.warning" class="smpl">warn-date</a> = DQUOTE HTTP-date DQUOTE
2801<a href="#header.warning" class="smpl">warn-text</a> = quoted-string
2802<a href="#header.warning" class="smpl">warning-value</a> = warn-code SP warn-agent SP warn-text [ SP warn-date
2803 ]
2804</pre></div>
2805      </div>
2806      <h1 id="rfc.index"><a href="#rfc.index">Index</a></h1>
2807      <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>
2808      </p>
2809      <div class="print2col">
2810         <ul class="ind">
2811            <li><a id="rfc.index.1" href="#rfc.index.1"><b>1</b></a><ul>
2812                  <li>110 (warn-code)&nbsp;&nbsp;<a href="#rfc.xref.warn.110.1">4.2.4</a>, <a href="#rfc.section.5.5.1"><b>5.5.1</b></a>, <a href="#rfc.xref.warn.110.2">7.2.2</a></li>
2813                  <li>111 (warn-code)&nbsp;&nbsp;<a href="#rfc.section.5.5.2"><b>5.5.2</b></a>, <a href="#rfc.xref.warn.111.1">7.2.2</a></li>
2814                  <li>112 (warn-code)&nbsp;&nbsp;<a href="#rfc.xref.warn.112.1">4.2.4</a>, <a href="#rfc.section.5.5.3"><b>5.5.3</b></a>, <a href="#rfc.xref.warn.112.2">7.2.2</a></li>
2815                  <li>113 (warn-code)&nbsp;&nbsp;<a href="#rfc.xref.warn.113.1">4.2.2</a>, <a href="#rfc.section.5.5.4"><b>5.5.4</b></a>, <a href="#rfc.xref.warn.113.2">7.2.2</a></li>
2816                  <li>199 (warn-code)&nbsp;&nbsp;<a href="#rfc.section.5.5.5"><b>5.5.5</b></a>, <a href="#rfc.xref.warn.199.1">7.2.2</a></li>
2817               </ul>
2818            </li>
2819            <li><a id="rfc.index.2" href="#rfc.index.2"><b>2</b></a><ul>
2820                  <li>214 (warn-code)&nbsp;&nbsp;<a href="#rfc.section.5.5.6"><b>5.5.6</b></a>, <a href="#rfc.xref.warn.214.1">7.2.2</a></li>
2821                  <li>299 (warn-code)&nbsp;&nbsp;<a href="#rfc.section.5.5.7"><b>5.5.7</b></a>, <a href="#rfc.xref.warn.299.1">7.2.2</a></li>
2822               </ul>
2823            </li>
2824            <li><a id="rfc.index.A" href="#rfc.index.A"><b>A</b></a><ul>
2825                  <li>age&nbsp;&nbsp;<a href="#rfc.iref.a.1">4.2</a></li>
2826                  <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.section.5.1"><b>5.1</b></a>, <a href="#rfc.xref.header.age.3">7.3</a></li>
2827               </ul>
2828            </li>
2829            <li><a id="rfc.index.B" href="#rfc.index.B"><b>B</b></a><ul>
2830                  <li><em>BCP90</em>&nbsp;&nbsp;<a href="#rfc.xref.BCP90.1">7.3</a>, <a href="#BCP90"><b>10.2</b></a></li>
2831               </ul>
2832            </li>
2833            <li><a id="rfc.index.C" href="#rfc.index.C"><b>C</b></a><ul>
2834                  <li>cache&nbsp;&nbsp;<a href="#rfc.iref.c.1">1</a></li>
2835                  <li>cache entry&nbsp;&nbsp;<a href="#rfc.section.2">2</a></li>
2836                  <li>cache key&nbsp;&nbsp;<a href="#rfc.section.2">2</a>, <a href="#rfc.iref.c.2">2</a></li>
2837                  <li>Cache-Control header field&nbsp;&nbsp;<a href="#rfc.xref.header.cache-control.1">3</a>, <a href="#rfc.section.5.2"><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>
2838               </ul>
2839            </li>
2840            <li><a id="rfc.index.D" href="#rfc.index.D"><b>D</b></a><ul>
2841                  <li>Disconnected Operation (warn-text)&nbsp;&nbsp;<a href="#rfc.xref.warn.112.1">4.2.4</a>, <a href="#rfc.section.5.5.3"><b>5.5.3</b></a>, <a href="#rfc.xref.warn.112.2">7.2.2</a></li>
2842               </ul>
2843            </li>
2844            <li><a id="rfc.index.E" href="#rfc.index.E"><b>E</b></a><ul>
2845                  <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.section.5.3"><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>
2846                  <li>explicit expiration time&nbsp;&nbsp;<a href="#rfc.iref.e.1">4.2</a></li>
2847               </ul>
2848            </li>
2849            <li><a id="rfc.index.F" href="#rfc.index.F"><b>F</b></a><ul>
2850                  <li>fresh&nbsp;&nbsp;<a href="#rfc.section.4.2">4.2</a></li>
2851                  <li>freshness lifetime&nbsp;&nbsp;<a href="#rfc.iref.f.1">4.2</a></li>
2852               </ul>
2853            </li>
2854            <li><a id="rfc.index.G" href="#rfc.index.G"><b>G</b></a><ul>
2855                  <li><tt>Grammar</tt>&nbsp;&nbsp;
2856                     <ul>
2857                        <li><tt>Age</tt>&nbsp;&nbsp;<a href="#rfc.iref.g.2"><b>5.1</b></a></li>
2858                        <li><tt>Cache-Control</tt>&nbsp;&nbsp;<a href="#rfc.iref.g.3"><b>5.2</b></a></li>
2859                        <li><tt>cache-directive</tt>&nbsp;&nbsp;<a href="#rfc.iref.g.4"><b>5.2</b></a></li>
2860                        <li><tt>delta-seconds</tt>&nbsp;&nbsp;<a href="#rfc.iref.g.1"><b>1.2.1</b></a></li>
2861                        <li><tt>Expires</tt>&nbsp;&nbsp;<a href="#rfc.iref.g.5"><b>5.3</b></a></li>
2862                        <li><tt>extension-pragma</tt>&nbsp;&nbsp;<a href="#rfc.iref.g.8"><b>5.4</b></a></li>
2863                        <li><tt>Pragma</tt>&nbsp;&nbsp;<a href="#rfc.iref.g.6"><b>5.4</b></a></li>
2864                        <li><tt>pragma-directive</tt>&nbsp;&nbsp;<a href="#rfc.iref.g.7"><b>5.4</b></a></li>
2865                        <li><tt>warn-agent</tt>&nbsp;&nbsp;<a href="#rfc.iref.g.12"><b>5.5</b></a></li>
2866                        <li><tt>warn-code</tt>&nbsp;&nbsp;<a href="#rfc.iref.g.11"><b>5.5</b></a></li>
2867                        <li><tt>warn-date</tt>&nbsp;&nbsp;<a href="#rfc.iref.g.14"><b>5.5</b></a></li>
2868                        <li><tt>warn-text</tt>&nbsp;&nbsp;<a href="#rfc.iref.g.13"><b>5.5</b></a></li>
2869                        <li><tt>Warning</tt>&nbsp;&nbsp;<a href="#rfc.iref.g.9"><b>5.5</b></a></li>
2870                        <li><tt>warning-value</tt>&nbsp;&nbsp;<a href="#rfc.iref.g.10"><b>5.5</b></a></li>
2871                     </ul>
2872                  </li>
2873               </ul>
2874            </li>
2875            <li><a id="rfc.index.H" href="#rfc.index.H"><b>H</b></a><ul>
2876                  <li>Heuristic Expiration (warn-text)&nbsp;&nbsp;<a href="#rfc.xref.warn.113.1">4.2.2</a>, <a href="#rfc.section.5.5.4"><b>5.5.4</b></a>, <a href="#rfc.xref.warn.113.2">7.2.2</a></li>
2877                  <li>heuristic expiration time&nbsp;&nbsp;<a href="#rfc.iref.h.1">4.2</a></li>
2878               </ul>
2879            </li>
2880            <li><a id="rfc.index.M" href="#rfc.index.M"><b>M</b></a><ul>
2881                  <li>max-age (cache directive)&nbsp;&nbsp;<a href="#rfc.section.5.2.1.1"><b>5.2.1.1</b></a>, <a href="#rfc.section.5.2.2.8"><b>5.2.2.8</b></a></li>
2882                  <li>max-stale (cache directive)&nbsp;&nbsp;<a href="#rfc.section.5.2.1.2"><b>5.2.1.2</b></a></li>
2883                  <li>min-fresh (cache directive)&nbsp;&nbsp;<a href="#rfc.section.5.2.1.3"><b>5.2.1.3</b></a></li>
2884                  <li>Miscellaneous Persistent Warning (warn-text)&nbsp;&nbsp;<a href="#rfc.section.5.5.7"><b>5.5.7</b></a>, <a href="#rfc.xref.warn.299.1">7.2.2</a></li>
2885                  <li>Miscellaneous Warning (warn-text)&nbsp;&nbsp;<a href="#rfc.section.5.5.5"><b>5.5.5</b></a>, <a href="#rfc.xref.warn.199.1">7.2.2</a></li>
2886                  <li>must-revalidate (cache directive)&nbsp;&nbsp;<a href="#rfc.section.5.2.2.1"><b>5.2.2.1</b></a></li>
2887               </ul>
2888            </li>
2889            <li><a id="rfc.index.N" href="#rfc.index.N"><b>N</b></a><ul>
2890                  <li>no-cache (cache directive)&nbsp;&nbsp;<a href="#rfc.section.5.2.1.4"><b>5.2.1.4</b></a>, <a href="#rfc.section.5.2.2.2"><b>5.2.2.2</b></a></li>
2891                  <li>no-store (cache directive)&nbsp;&nbsp;<a href="#rfc.section.5.2.1.5"><b>5.2.1.5</b></a>, <a href="#rfc.section.5.2.2.3"><b>5.2.2.3</b></a></li>
2892                  <li>no-transform (cache directive)&nbsp;&nbsp;<a href="#rfc.section.5.2.1.6"><b>5.2.1.6</b></a>, <a href="#rfc.section.5.2.2.4"><b>5.2.2.4</b></a></li>
2893               </ul>
2894            </li>
2895            <li><a id="rfc.index.O" href="#rfc.index.O"><b>O</b></a><ul>
2896                  <li>only-if-cached (cache directive)&nbsp;&nbsp;<a href="#rfc.section.5.2.1.7"><b>5.2.1.7</b></a></li>
2897               </ul>
2898            </li>
2899            <li><a id="rfc.index.P" href="#rfc.index.P"><b>P</b></a><ul>
2900                  <li>Pragma header field&nbsp;&nbsp;<a href="#rfc.xref.header.pragma.1">4</a>, <a href="#rfc.section.5.4"><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>
2901                  <li>private (cache directive)&nbsp;&nbsp;<a href="#rfc.section.5.2.2.6"><b>5.2.2.6</b></a></li>
2902                  <li>private cache&nbsp;&nbsp;<a href="#rfc.iref.p.1">1</a></li>
2903                  <li>proxy-revalidate (cache directive)&nbsp;&nbsp;<a href="#rfc.section.5.2.2.7"><b>5.2.2.7</b></a></li>
2904                  <li>public (cache directive)&nbsp;&nbsp;<a href="#rfc.section.5.2.2.5"><b>5.2.2.5</b></a></li>
2905               </ul>
2906            </li>
2907            <li><a id="rfc.index.R" href="#rfc.index.R"><b>R</b></a><ul>
2908                  <li>Response is Stale (warn-text)&nbsp;&nbsp;<a href="#rfc.xref.warn.110.1">4.2.4</a>, <a href="#rfc.section.5.5.1"><b>5.5.1</b></a>, <a href="#rfc.xref.warn.110.2">7.2.2</a></li>
2909                  <li>Revalidation Failed (warn-text)&nbsp;&nbsp;<a href="#rfc.section.5.5.2"><b>5.5.2</b></a>, <a href="#rfc.xref.warn.111.1">7.2.2</a></li>
2910                  <li><em>RFC2119</em>&nbsp;&nbsp;<a href="#rfc.xref.RFC2119.1">1.1</a>, <a href="#RFC2119"><b>10.1</b></a></li>
2911                  <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>
2912                        <li><em>Section 13.9</em>&nbsp;&nbsp;<a href="#rfc.xref.RFC2616.1">4.2.2</a></li>
2913                     </ul>
2914                  </li>
2915                  <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>
2916                        <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>
2917                     </ul>
2918                  </li>
2919                  <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>
2920                        <li><em>Appendix B.1</em>&nbsp;&nbsp;<a href="#rfc.xref.RFC5234.2">B</a></li>
2921                     </ul>
2922                  </li>
2923                  <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>
2924                        <li><em>Section 3</em>&nbsp;&nbsp;<a href="#rfc.xref.RFC5861.2">7.1.3</a></li>
2925                        <li><em>Section 4</em>&nbsp;&nbsp;<a href="#rfc.xref.RFC5861.1">7.1.3</a></li>
2926                     </ul>
2927                  </li>
2928                  <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>
2929                  <li><em>RFC6265</em>&nbsp;&nbsp;<a href="#rfc.xref.RFC6265.1">8</a>, <a href="#RFC6265"><b>10.2</b></a></li>
2930                  <li><em>RFC7230</em>&nbsp;&nbsp;<a href="#rfc.xref.RFC7230.1">1.1</a>, <a href="#rfc.xref.RFC7230.2">1.2</a>, <a href="#rfc.xref.RFC7230.3">3.1</a>, <a href="#rfc.xref.RFC7230.4">4</a>, <a href="#rfc.xref.RFC7230.5">4.1</a>, <a href="#rfc.xref.RFC7230.6">4.4</a>, <a href="#rfc.xref.RFC7230.7">4.4</a>, <a href="#rfc.xref.RFC7230.8">4.4</a>, <a href="#rfc.xref.RFC7230.9">5.2.1.6</a>, <a href="#rfc.xref.RFC7230.10">5.2.2.4</a>, <a href="#rfc.xref.RFC7230.11">8</a>, <a href="#rfc.xref.RFC7230.12">8</a>, <a href="#rfc.xref.RFC7230.13">9</a>, <a href="#RFC7230"><b>10.1</b></a>, <a href="#rfc.xref.RFC7230.14">B</a>, <a href="#rfc.xref.RFC7230.15">B</a>, <a href="#rfc.xref.RFC7230.16">B</a>, <a href="#rfc.xref.RFC7230.17">B</a>, <a href="#rfc.xref.RFC7230.18">B</a>, <a href="#rfc.xref.RFC7230.19">B</a>, <a href="#rfc.xref.RFC7230.20">B</a>, <a href="#rfc.xref.RFC7230.21">B</a>, <a href="#rfc.xref.RFC7230.22">C</a><ul>
2931                        <li><em>Section 1.2</em>&nbsp;&nbsp;<a href="#rfc.xref.RFC7230.22">C</a></li>
2932                        <li><em>Section 2.5</em>&nbsp;&nbsp;<a href="#rfc.xref.RFC7230.1">1.1</a></li>
2933                        <li><em>Section 2.7</em>&nbsp;&nbsp;<a href="#rfc.xref.RFC7230.19">B</a>, <a href="#rfc.xref.RFC7230.21">B</a></li>
2934                        <li><em>Section 3.2</em>&nbsp;&nbsp;<a href="#rfc.xref.RFC7230.5">4.1</a>, <a href="#rfc.xref.RFC7230.16">B</a></li>
2935                        <li><em>Section 3.2.3</em>&nbsp;&nbsp;<a href="#rfc.xref.RFC7230.15">B</a></li>
2936                        <li><em>Section 3.2.6</em>&nbsp;&nbsp;<a href="#rfc.xref.RFC7230.17">B</a>, <a href="#rfc.xref.RFC7230.18">B</a></li>
2937                        <li><em>Section 3.3.3</em>&nbsp;&nbsp;<a href="#rfc.xref.RFC7230.12">8</a></li>
2938                        <li><em>Section 5.5</em>&nbsp;&nbsp;<a href="#rfc.xref.RFC7230.4">4</a>, <a href="#rfc.xref.RFC7230.6">4.4</a>, <a href="#rfc.xref.RFC7230.7">4.4</a>, <a href="#rfc.xref.RFC7230.8">4.4</a></li>
2939                        <li><em>Section 5.7.1</em>&nbsp;&nbsp;<a href="#rfc.xref.RFC7230.20">B</a></li>
2940                        <li><em>Section 5.7.2</em>&nbsp;&nbsp;<a href="#rfc.xref.RFC7230.9">5.2.1.6</a>, <a href="#rfc.xref.RFC7230.10">5.2.2.4</a></li>
2941                        <li><em>Section 7</em>&nbsp;&nbsp;<a href="#rfc.xref.RFC7230.2">1.2</a></li>
2942                        <li><em>Section 10</em>&nbsp;&nbsp;<a href="#rfc.xref.RFC7230.13">9</a></li>
2943                     </ul>
2944                  </li>
2945                  <li><em>RFC7231</em>&nbsp;&nbsp;<a href="#rfc.xref.RFC7231.1">2</a>, <a href="#rfc.xref.RFC7231.2">2</a>, <a href="#rfc.xref.RFC7231.3">4</a>, <a href="#rfc.xref.RFC7231.4">4.1</a>, <a href="#rfc.xref.RFC7231.5">4.2.2</a>, <a href="#rfc.xref.RFC7231.6">4.2.3</a>, <a href="#rfc.xref.RFC7231.7">4.4</a>, <a href="#rfc.xref.RFC7231.8">5.3</a>, <a href="#rfc.xref.RFC7231.9">8</a>, <a href="#RFC7231"><b>10.1</b></a>, <a href="#rfc.xref.RFC7231.10">B</a><ul>
2946                        <li><em>Section 4.2.1</em>&nbsp;&nbsp;<a href="#rfc.xref.RFC7231.3">4</a>, <a href="#rfc.xref.RFC7231.7">4.4</a></li>
2947                        <li><em>Section 4.3.1</em>&nbsp;&nbsp;<a href="#rfc.xref.RFC7231.2">2</a></li>
2948                        <li><em>Section 6.1</em>&nbsp;&nbsp;<a href="#rfc.xref.RFC7231.5">4.2.2</a></li>
2949                        <li><em>Section 7.1.1.1</em>&nbsp;&nbsp;<a href="#rfc.xref.RFC7231.8">5.3</a>, <a href="#rfc.xref.RFC7231.10">B</a></li>
2950                        <li><em>Section 7.1.1.2</em>&nbsp;&nbsp;<a href="#rfc.xref.RFC7231.6">4.2.3</a></li>
2951                        <li><em>Section 7.1.4</em>&nbsp;&nbsp;<a href="#rfc.xref.RFC7231.4">4.1</a></li>
2952                     </ul>
2953                  </li>
2954                  <li><em>RFC7232</em>&nbsp;&nbsp;<a href="#rfc.xref.RFC7232.1">4.2.2</a>, <a href="#rfc.xref.RFC7232.2">4.3</a>, <a href="#rfc.xref.RFC7232.3">4.3.1</a>, <a href="#rfc.xref.RFC7232.4">4.3.1</a>, <a href="#rfc.xref.RFC7232.5">4.3.2</a>, <a href="#rfc.xref.RFC7232.6">4.3.2</a>, <a href="#rfc.xref.RFC7232.7">4.3.2</a>, <a href="#rfc.xref.RFC7232.8">4.3.4</a>, <a href="#RFC7232"><b>10.1</b></a><ul>
2955                        <li><em>Section 2.1</em>&nbsp;&nbsp;<a href="#rfc.xref.RFC7232.8">4.3.4</a></li>
2956                        <li><em>Section 2.2</em>&nbsp;&nbsp;<a href="#rfc.xref.RFC7232.1">4.2.2</a>, <a href="#rfc.xref.RFC7232.3">4.3.1</a></li>
2957                        <li><em>Section 2.3</em>&nbsp;&nbsp;<a href="#rfc.xref.RFC7232.4">4.3.1</a></li>
2958                        <li><em>Section 3.2</em>&nbsp;&nbsp;<a href="#rfc.xref.RFC7232.6">4.3.2</a></li>
2959                        <li><em>Section 3.3</em>&nbsp;&nbsp;<a href="#rfc.xref.RFC7232.7">4.3.2</a></li>
2960                        <li><em>Section 6</em>&nbsp;&nbsp;<a href="#rfc.xref.RFC7232.5">4.3.2</a></li>
2961                     </ul>
2962                  </li>
2963                  <li><em>RFC7233</em>&nbsp;&nbsp;<a href="#rfc.xref.RFC7233.1">3.1</a>, <a href="#rfc.xref.RFC7233.2">3.3</a>, <a href="#rfc.xref.RFC7233.3">3.3</a>, <a href="#rfc.xref.RFC7233.4">4.3.2</a>, <a href="#rfc.xref.RFC7233.5">4.3.2</a>, <a href="#RFC7233"><b>10.1</b></a><ul>
2964                        <li><em>Section 3.2</em>&nbsp;&nbsp;<a href="#rfc.xref.RFC7233.5">4.3.2</a></li>
2965                        <li><em>Section 4.3</em>&nbsp;&nbsp;<a href="#rfc.xref.RFC7233.3">3.3</a></li>
2966                     </ul>
2967                  </li>
2968                  <li><em>RFC7235</em>&nbsp;&nbsp;<a href="#rfc.xref.RFC7235.1">3</a>, <a href="#rfc.xref.RFC7235.2">3.2</a>, <a href="#RFC7235"><b>10.1</b></a><ul>
2969                        <li><em>Section 4.2</em>&nbsp;&nbsp;<a href="#rfc.xref.RFC7235.1">3</a>, <a href="#rfc.xref.RFC7235.2">3.2</a></li>
2970                     </ul>
2971                  </li>
2972               </ul>
2973            </li>
2974            <li><a id="rfc.index.S" href="#rfc.index.S"><b>S</b></a><ul>
2975                  <li>s-maxage (cache directive)&nbsp;&nbsp;<a href="#rfc.section.5.2.2.9"><b>5.2.2.9</b></a></li>
2976                  <li>shared cache&nbsp;&nbsp;<a href="#rfc.iref.s.1">1</a></li>
2977                  <li>stale&nbsp;&nbsp;<a href="#rfc.section.4.2">4.2</a></li>
2978                  <li>strong validator&nbsp;&nbsp;<a href="#rfc.iref.s.2">4.3.4</a></li>
2979               </ul>
2980            </li>
2981            <li><a id="rfc.index.T" href="#rfc.index.T"><b>T</b></a><ul>
2982                  <li>Transformation Applied (warn-text)&nbsp;&nbsp;<a href="#rfc.section.5.5.6"><b>5.5.6</b></a>, <a href="#rfc.xref.warn.214.1">7.2.2</a></li>
2983               </ul>
2984            </li>
2985            <li><a id="rfc.index.V" href="#rfc.index.V"><b>V</b></a><ul>
2986                  <li>validator&nbsp;&nbsp;<a href="#rfc.section.4.3.1">4.3.1</a></li>
2987               </ul>
2988            </li>
2989            <li><a id="rfc.index.W" href="#rfc.index.W"><b>W</b></a><ul>
2990                  <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.section.5.5"><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>
2991               </ul>
2992            </li>
2993         </ul>
2994      </div>
2995      <div class="avoidbreakinside">
2996         <h1 id="rfc.authors"><a href="#rfc.authors">Authors' Addresses</a></h1>
2997         <p><b>Roy T. Fielding</b>
2998            (editor)
2999            <br>Adobe Systems Incorporated<br>345 Park Ave<br>San Jose, CA&nbsp;95110<br>USA<br>Email: fielding@gbiv.com<br>URI: <a href="http://roy.gbiv.com/">http://roy.gbiv.com/</a></p>
3000         <p><b>Mark Nottingham</b>
3001            (editor)
3002            <br>Akamai<br>Email: mnot@mnot.net<br>URI: <a href="http://www.mnot.net/">http://www.mnot.net/</a></p>
3003         <p><b>Julian F. Reschke</b>
3004            (editor)
3005            <br>greenbytes GmbH<br>Hafenweg 16<br>Muenster, NW&nbsp;48155<br>Germany<br>Email: julian.reschke@greenbytes.de<br>URI: <a href="http://greenbytes.de/tech/webdav/">http://greenbytes.de/tech/webdav/</a></p>
3006      </div>
3007   </body>
3008</html>
Note: See TracBrowser for help on using the repository browser.