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

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

use list item xrefs in P4, regen HTML throughout

  • Property svn:eol-style set to native
  • Property svn:mime-type set to text/html;charset=utf-8
File size: 175.5 KB
RevLine 
[52]1<!DOCTYPE html
2  PUBLIC "-//W3C//DTD HTML 4.01//EN">
3<html lang="en">
[573]4   <head profile="http://www.w3.org/2006/03/hcard http://dublincore.org/documents/2008/08/04/dc-html/">
[52]5      <meta http-equiv="Content-Type" content="text/html; charset=UTF-8">
[1864]6      <title>Hypertext Transfer Protocol (HTTP/1.1): Caching</title><script>
[1522]7var buttonsAdded = false;
8
9function init() {
10  var fb = document.createElement("div");
[1528]11  fb.className = "feedback noprint";
[1522]12  fb.setAttribute("onclick", "feedback();");
13  fb.appendChild(document.createTextNode("feedback"));
14
15  var bodyl = document.getElementsByTagName("body");
16  bodyl.item(0).appendChild(fb);
17}
18
19function feedback() {
20  toggleButtonsToElementsByName("h1");
21  toggleButtonsToElementsByName("h2");
22  toggleButtonsToElementsByName("h3");
23  toggleButtonsToElementsByName("h4");
[2273]24
[1522]25  buttonsAdded = !buttonsAdded;
26}
27
28function toggleButtonsToElementsByName(name) {
29  var list = document.getElementsByTagName(name);
30  for (var i = 0; i < list.length; i++) {
31    toggleButton(list.item(i));
32  }
33}
34
35function toggleButton(node) {
36  if (! buttonsAdded) {
[2273]37
[1522]38    // docname
39    var template = "mailto:ietf-http-wg@w3.org?subject={docname},%20%22{section}%22&body=<{ref}>:";
40
41    var id = node.getAttribute("id");
42    // better id available?
43    var titlelinks = node.getElementsByTagName("a");
44    for (var i = 0; i < titlelinks.length; i++) {
45      var tl = titlelinks.item(i);
46      if (tl.getAttribute("id")) {
47        id = tl.getAttribute("id");
48      }
49    }
50
51    // ref
52    var ref = window.location.toString();
53    var hash = ref.indexOf("#");
54    if (hash != -1) {
55      ref = ref.substring(0, hash);
56    }
57    if (id != "") {
58      ref += "#" + id;
59    }
[2273]60
[1522]61    // docname
62    var docname = "draft-ietf-httpbis-p6-cache-latest";
63
64    // section
65    var section = node.textContent;
[1528]66    section = section.replace("\u00a0", " ");
[2273]67
[1522]68    // build URI from template
69    var uri = template.replace("{docname}", encodeURIComponent(docname));
70    uri = uri.replace("{section}", encodeURIComponent(section));
71    uri = uri.replace("{ref}", encodeURIComponent(ref));
[2273]72
[1522]73    var button = document.createElement("a");
[1528]74    button.className = "fbbutton noprint";
[1522]75    button.setAttribute("href", uri);
76    button.appendChild(document.createTextNode("send feedback"));
77    node.appendChild(button);
78  }
79  else {
80    var buttons = node.getElementsByTagName("a");
81    for (var i = 0; i < buttons.length; i++) {
82      var b = buttons.item(i);
[1528]83      if (b.className == "fbbutton noprint") {
[1522]84        node.removeChild(b);
85      }
86    }
87  }
88}</script><style type="text/css" title="Xml2Rfc (sans serif)">
[52]89a {
90  text-decoration: none;
91}
92a.smpl {
93  color: black;
94}
95a:hover {
96  text-decoration: underline;
97}
98a:active {
99  text-decoration: underline;
100}
101address {
102  margin-top: 1em;
103  margin-left: 2em;
104  font-style: normal;
105}
106body {
107  color: black;
108  font-family: verdana, helvetica, arial, sans-serif;
109  font-size: 10pt;
[1667]110  margin-right: 2em;
[52]111}
112cite {
113  font-style: normal;
114}
[540]115div.note {
116  margin-left: 2em;
117}
[52]118dl {
119  margin-left: 2em;
120}
[729]121ul.empty {
122  list-style-type: none;
123}
124ul.empty li {
[52]125  margin-top: .5em;
126}
127dl p {
128  margin-left: 0em;
129}
130dt {
131  margin-top: .5em;
132}
133h1 {
134  font-size: 14pt;
135  line-height: 21pt;
136  page-break-after: avoid;
137}
138h1.np {
139  page-break-before: always;
140}
141h1 a {
142  color: #333333;
143}
144h2 {
145  font-size: 12pt;
146  line-height: 15pt;
147  page-break-after: avoid;
148}
[446]149h3, h4, h5, h6 {
[52]150  font-size: 10pt;
151  page-break-after: avoid;
152}
[446]153h2 a, h3 a, h4 a, h5 a, h6 a {
[52]154  color: black;
155}
156img {
157  margin-left: 3em;
158}
159li {
160  margin-left: 2em;
161}
162ol {
163  margin-left: 2em;
164}
[1145]165ol.la {
166  list-style-type: lower-alpha;
167}
168ol.ua {
169  list-style-type: upper-alpha;
170}
[52]171ol p {
172  margin-left: 0em;
173}
174p {
175  margin-left: 2em;
176}
177pre {
178  margin-left: 3em;
179  background-color: lightyellow;
180  padding: .25em;
[1667]181  page-break-inside: avoid;
[52]182}
183pre.text2 {
184  border-style: dotted;
185  border-width: 1px;
186  background-color: #f0f0f0;
187  width: 69em;
188}
189pre.inline {
190  background-color: white;
191  padding: 0em;
192}
193pre.text {
194  border-style: dotted;
195  border-width: 1px;
196  background-color: #f8f8f8;
197  width: 69em;
198}
199pre.drawing {
200  border-style: solid;
201  border-width: 1px;
202  background-color: #f8f8f8;
203  padding: 2em;
204}
[247]205sup {
206  font-size: 60%;
207}
[52]208table {
209  margin-left: 2em;
210}
[253]211table.tt {
212  vertical-align: top;
213}
214table.full {
215  border-style: outset;
216  border-width: 1px;
217}
218table.headers {
219  border-style: outset;
220  border-width: 1px;
221}
222table.tt td {
223  vertical-align: top;
224}
225table.full td {
226  border-style: inset;
227  border-width: 1px;
228}
229table.tt th {
230  vertical-align: top;
231}
232table.full th {
233  border-style: inset;
234  border-width: 1px;
235}
236table.headers th {
237  border-style: none none inset none;
238  border-width: 1px;
239}
[669]240table.left {
241  margin-right: auto;
242}
243table.right {
244  margin-left: auto;
245}
246table.center {
247  margin-left: auto;
248  margin-right: auto;
249}
[454]250caption {
251  caption-side: bottom;
252  font-weight: bold;
253  font-size: 9pt;
254  margin-top: .5em;
255}
256
[52]257table.header {
[729]258  border-spacing: 1px;
[52]259  width: 95%;
260  font-size: 10pt;
261  color: white;
262}
263td.top {
264  vertical-align: top;
265}
266td.topnowrap {
267  vertical-align: top;
[2273]268  white-space: nowrap;
[52]269}
[729]270table.header td {
[52]271  background-color: gray;
272  width: 50%;
273}
[729]274table.header a {
[227]275  color: white;
276}
[52]277td.reference {
278  vertical-align: top;
279  white-space: nowrap;
280  padding-right: 1em;
281}
282thead {
283  display:table-header-group;
284}
[1072]285ul.toc, ul.toc ul {
[52]286  list-style: none;
287  margin-left: 1.5em;
288  padding-left: 0em;
289}
[1072]290ul.toc li {
[52]291  line-height: 150%;
292  font-weight: bold;
293  font-size: 10pt;
294  margin-left: 0em;
295}
[1072]296ul.toc li li {
[52]297  line-height: normal;
298  font-weight: normal;
299  font-size: 9pt;
300  margin-left: 0em;
301}
[1072]302li.excluded {
[52]303  font-size: 0pt;
304}
305ul p {
306  margin-left: 0em;
307}
[1095]308ul.ind, ul.ind ul {
[52]309  list-style: none;
310  margin-left: 1.5em;
311  padding-left: 0em;
[440]312  page-break-before: avoid;
[52]313}
[1072]314ul.ind li {
[52]315  font-weight: bold;
316  line-height: 200%;
317  margin-left: 0em;
318}
[1072]319ul.ind li li {
[52]320  font-weight: normal;
321  line-height: 150%;
322  margin-left: 0em;
323}
[662]324.avoidbreak {
325  page-break-inside: avoid;
326}
[52]327.bcp14 {
328  font-style: normal;
329  text-transform: lowercase;
330  font-variant: small-caps;
331}
332.comment {
333  background-color: yellow;
334}
335.center {
336  text-align: center;
337}
338.error {
339  color: red;
340  font-style: italic;
341  font-weight: bold;
342}
343.figure {
344  font-weight: bold;
345  text-align: center;
346  font-size: 9pt;
347}
348.filename {
349  color: #333333;
350  font-weight: bold;
351  font-size: 12pt;
352  line-height: 21pt;
353  text-align: center;
354}
355.fn {
356  font-weight: bold;
357}
358.hidden {
359  display: none;
360}
361.left {
362  text-align: left;
363}
364.right {
365  text-align: right;
366}
367.title {
368  color: #990000;
369  font-size: 18pt;
370  line-height: 18pt;
371  font-weight: bold;
372  text-align: center;
373  margin-top: 36pt;
374}
375.vcardline {
376  display: block;
377}
378.warning {
379  font-size: 14pt;
380  background-color: yellow;
381}
[1522]382.feedback {
383  position: fixed;
384  bottom: 1%;
385  right: 1%;
386  padding: 3px 5px;
387  color: white;
388  border-radius: 5px;
389  background: #a00000;
390  border: 1px solid silver;
391}
392.fbbutton {
393  margin-left: 1em;
394  color: #303030;
395  font-size: small;
396  font-weight: normal;
397  background: #d0d000;
398  padding: 1px 4px;
399  border: 1px solid silver;
400  border-radius: 5px;
401}
[52]402
403@media print {
404  .noprint {
405    display: none;
406  }
[2273]407
[52]408  a {
409    color: black;
410    text-decoration: none;
411  }
412
413  table.header {
414    width: 90%;
415  }
416
417  td.header {
418    width: 50%;
419    color: black;
420    background-color: white;
421    vertical-align: top;
422    font-size: 12pt;
423  }
424
[1825]425  ul.toc a:nth-child(2)::after {
[52]426    content: leader('.') target-counter(attr(href), page);
427  }
[2273]428
[1072]429  ul.ind li li a {
[52]430    content: target-counter(attr(href), page);
431  }
[2273]432
[52]433  .print2col {
434    column-count: 2;
[1528]435    -moz-column-count: 2;
[52]436    column-fill: auto;
437  }
438}
439
440@page {
441  @top-left {
[2273]442       content: "Internet-Draft";
443  }
[52]444  @top-right {
[2273]445       content: "May 2013";
446  }
[52]447  @top-center {
[2273]448       content: "HTTP/1.1 Caching";
449  }
[52]450  @bottom-left {
[2273]451       content: "Fielding, et al.";
452  }
[52]453  @bottom-center {
[2273]454       content: "Expires November 25, 2013";
455  }
[52]456  @bottom-right {
[2273]457       content: "[Page " counter(page) "]";
458  }
[52]459}
460
[2273]461@page:first {
[52]462    @top-left {
463      content: normal;
464    }
465    @top-right {
466      content: normal;
467    }
468    @top-center {
469      content: normal;
470    }
471}
472</style><link rel="Contents" href="#rfc.toc">
473      <link rel="Author" href="#rfc.authors">
[754]474      <link rel="Copyright" href="#rfc.copyrightnotice">
[52]475      <link rel="Index" href="#rfc.index">
476      <link rel="Chapter" title="1 Introduction" href="#rfc.section.1">
[1751]477      <link rel="Chapter" title="2 Overview of Cache Operation" href="#rfc.section.2">
478      <link rel="Chapter" title="3 Storing Responses in Caches" href="#rfc.section.3">
479      <link rel="Chapter" title="4 Constructing Responses from Caches" href="#rfc.section.4">
480      <link rel="Chapter" title="5 Updating Caches with HEAD Responses" href="#rfc.section.5">
481      <link rel="Chapter" title="6 Request Methods that Invalidate" href="#rfc.section.6">
482      <link rel="Chapter" title="7 Header Field Definitions" href="#rfc.section.7">
483      <link rel="Chapter" title="8 History Lists" href="#rfc.section.8">
484      <link rel="Chapter" title="9 IANA Considerations" href="#rfc.section.9">
485      <link rel="Chapter" title="10 Security Considerations" href="#rfc.section.10">
486      <link rel="Chapter" title="11 Acknowledgments" href="#rfc.section.11">
487      <link rel="Chapter" href="#rfc.section.12" title="12 References">
[912]488      <link rel="Appendix" title="A Changes from RFC 2616" href="#rfc.section.A">
[1805]489      <link rel="Appendix" title="B Imported ABNF" href="#rfc.section.B">
490      <link rel="Appendix" title="C Collected ABNF" href="#rfc.section.C">
491      <link rel="Appendix" title="D Change Log (to be removed by RFC Editor before publication)" href="#rfc.section.D">
[1472]492      <link href="p5-range.html" rel="prev">
493      <link href="p7-auth.html" rel="next">
[2273]494      <meta name="generator" content="http://greenbytes.de/tech/webdav/rfc2629.xslt, Revision 1.596, 2013/05/16 08:38:33, XSLT vendor: SAXON 8.9 from Saxonica http://www.saxonica.com/">
[754]495      <link rel="schema.dct" href="http://purl.org/dc/terms/">
496      <meta name="dct.creator" content="Fielding, R.">
497      <meta name="dct.creator" content="Nottingham, M.">
498      <meta name="dct.creator" content="Reschke, J. F.">
499      <meta name="dct.identifier" content="urn:ietf:id:draft-ietf-httpbis-p6-cache-latest">
[2273]500      <meta name="dct.issued" scheme="ISO8601" content="2013-05-24">
[754]501      <meta name="dct.replaces" content="urn:ietf:rfc:2616">
[1808]502      <meta name="dct.abstract" content="The Hypertext Transfer Protocol (HTTP) is an application-level protocol for distributed, collaborative, hypertext information systems. This document defines requirements on HTTP caches and the associated header fields that control cache behavior or indicate cacheable response messages.">
503      <meta name="description" content="The Hypertext Transfer Protocol (HTTP) is an application-level protocol for distributed, collaborative, hypertext information systems. This document defines requirements on HTTP caches and the associated header fields that control cache behavior or indicate cacheable response messages.">
[52]504   </head>
[1522]505   <body onload="init();">
[729]506      <table class="header">
507         <tbody>
508            <tr>
509               <td class="left">HTTPbis Working Group</td>
510               <td class="right">R. Fielding, Editor</td>
511            </tr>
512            <tr>
[754]513               <td class="left">Internet-Draft</td>
[1106]514               <td class="right">Adobe</td>
[729]515            </tr>
516            <tr>
[741]517               <td class="left">Obsoletes: <a href="http://tools.ietf.org/html/rfc2616">2616</a> (if approved)
[729]518               </td>
[1917]519               <td class="right">M. Nottingham, Editor</td>
[729]520            </tr>
521            <tr>
[741]522               <td class="left">Intended status: Standards Track</td>
[1914]523               <td class="right">Akamai</td>
524            </tr>
525            <tr>
[2273]526               <td class="left">Expires: November 25, 2013</td>
[832]527               <td class="right">J. Reschke, Editor</td>
[729]528            </tr>
529            <tr>
530               <td class="left"></td>
531               <td class="right">greenbytes</td>
532            </tr>
533            <tr>
534               <td class="left"></td>
[2273]535               <td class="right">May 24, 2013</td>
[729]536            </tr>
537         </tbody>
[52]538      </table>
[1864]539      <p class="title">Hypertext Transfer Protocol (HTTP/1.1): Caching<br><span class="filename">draft-ietf-httpbis-p6-cache-latest</span></p>
[2273]540      <h1 id="rfc.abstract"><a href="#rfc.abstract">Abstract</a></h1>
[1373]541      <p>The Hypertext Transfer Protocol (HTTP) is an application-level protocol for distributed, collaborative, hypertext information
[1808]542         systems. This document defines requirements on HTTP caches and the associated header fields that control cache behavior or
543         indicate cacheable response messages.
[2273]544      </p>
545      <h1 id="rfc.note.1"><a href="#rfc.note.1">Editorial Note (To be removed by RFC Editor)</a></h1>
[1764]546      <p>Discussion of this draft takes place on the HTTPBIS working group mailing list (ietf-http-wg@w3.org), 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;.
[2273]547      </p>
[1268]548      <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;.
[2273]549      </p>
[2190]550      <p>The changes in this draft are summarized in <a href="#changes.since.22" title="Since draft-ietf-httpbis-p6-cache-22">Appendix&nbsp;D.4</a>.
[2273]551      </p>
[799]552      <h1><a id="rfc.status" href="#rfc.status">Status of This Memo</a></h1>
553      <p>This Internet-Draft is submitted in full conformance with the provisions of BCP 78 and BCP 79.</p>
554      <p>Internet-Drafts are working documents of the Internet Engineering Task Force (IETF). Note that other groups may also distribute
555         working documents as Internet-Drafts. The list of current Internet-Drafts is at <a href="http://datatracker.ietf.org/drafts/current/">http://datatracker.ietf.org/drafts/current/</a>.
[52]556      </p>
557      <p>Internet-Drafts are draft documents valid for a maximum of six months and may be updated, replaced, or obsoleted by other
558         documents at any time. It is inappropriate to use Internet-Drafts as reference material or to cite them other than as “work
559         in progress”.
560      </p>
[2273]561      <p>This Internet-Draft will expire on November 25, 2013.</p>
[446]562      <h1><a id="rfc.copyrightnotice" href="#rfc.copyrightnotice">Copyright Notice</a></h1>
[2080]563      <p>Copyright © 2013 IETF Trust and the persons identified as the document authors. All rights reserved.</p>
[723]564      <p>This document is subject to BCP 78 and the IETF Trust's Legal Provisions Relating to IETF Documents (<a href="http://trustee.ietf.org/license-info">http://trustee.ietf.org/license-info</a>) in effect on the date of publication of this document. Please review these documents carefully, as they describe your rights
565         and restrictions with respect to this document. Code Components extracted from this document must include Simplified BSD License
[799]566         text as described in Section 4.e of the Trust Legal Provisions and are provided without warranty as described in the Simplified
567         BSD License.
[446]568      </p>
[723]569      <p>This document may contain material from IETF Documents or IETF Contributions published or made publicly available before November
570         10, 2008. The person(s) controlling the copyright in some of this material may not have granted the IETF Trust the right to
571         allow modifications of such material outside the IETF Standards Process. Without obtaining an adequate license from the person(s)
572         controlling the copyright in such materials, this document may not be modified outside the IETF Standards Process, and derivative
573         works of it may not be created outside the IETF Standards Process, except to format it for publication as an RFC or to translate
574         it into languages other than English.
575      </p>
[52]576      <hr class="noprint">
577      <h1 class="np" id="rfc.toc"><a href="#rfc.toc">Table of Contents</a></h1>
578      <ul class="toc">
[1825]579         <li><a href="#rfc.section.1">1.</a>&nbsp;&nbsp;&nbsp;<a href="#caching">Introduction</a><ul>
[2239]580               <li><a href="#rfc.section.1.1">1.1</a>&nbsp;&nbsp;&nbsp;<a href="#conformance">Conformance and Error Handling</a></li>
581               <li><a href="#rfc.section.1.2">1.2</a>&nbsp;&nbsp;&nbsp;<a href="#notation">Syntax Notation</a><ul>
582                     <li><a href="#rfc.section.1.2.1">1.2.1</a>&nbsp;&nbsp;&nbsp;<a href="#delta-seconds">Delta Seconds</a></li>
[424]583                  </ul>
584               </li>
[52]585            </ul>
586         </li>
[1825]587         <li><a href="#rfc.section.2">2.</a>&nbsp;&nbsp;&nbsp;<a href="#caching.overview">Overview of Cache Operation</a></li>
588         <li><a href="#rfc.section.3">3.</a>&nbsp;&nbsp;&nbsp;<a href="#response.cacheability">Storing Responses in Caches</a><ul>
589               <li><a href="#rfc.section.3.1">3.1</a>&nbsp;&nbsp;&nbsp;<a href="#incomplete.responses">Storing Incomplete Responses</a></li>
590               <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>
[2238]591               <li><a href="#rfc.section.3.3">3.3</a>&nbsp;&nbsp;&nbsp;<a href="#combining.responses">Combining Partial Content</a></li>
[1751]592            </ul>
593         </li>
[1825]594         <li><a href="#rfc.section.4">4.</a>&nbsp;&nbsp;&nbsp;<a href="#constructing.responses.from.caches">Constructing Responses from Caches</a><ul>
[2234]595               <li><a href="#rfc.section.4.1">4.1</a>&nbsp;&nbsp;&nbsp;<a href="#expiration.model">Freshness</a><ul>
[1825]596                     <li><a href="#rfc.section.4.1.1">4.1.1</a>&nbsp;&nbsp;&nbsp;<a href="#calculating.freshness.lifetime">Calculating Freshness Lifetime</a></li>
597                     <li><a href="#rfc.section.4.1.2">4.1.2</a>&nbsp;&nbsp;&nbsp;<a href="#heuristic.freshness">Calculating Heuristic Freshness</a></li>
598                     <li><a href="#rfc.section.4.1.3">4.1.3</a>&nbsp;&nbsp;&nbsp;<a href="#age.calculations">Calculating Age</a></li>
599                     <li><a href="#rfc.section.4.1.4">4.1.4</a>&nbsp;&nbsp;&nbsp;<a href="#serving.stale.responses">Serving Stale Responses</a></li>
[538]600                  </ul>
601               </li>
[2234]602               <li><a href="#rfc.section.4.2">4.2</a>&nbsp;&nbsp;&nbsp;<a href="#validation.model">Validation</a><ul>
[2238]603                     <li><a href="#rfc.section.4.2.1">4.2.1</a>&nbsp;&nbsp;&nbsp;<a href="#freshening.responses">Freshening Stored Responses upon Validation</a></li>
[1419]604                  </ul>
605               </li>
[2237]606               <li><a href="#rfc.section.4.3">4.3</a>&nbsp;&nbsp;&nbsp;<a href="#caching.negotiated.responses">Calculating Secondary Keys with Vary</a></li>
[52]607            </ul>
608         </li>
[1825]609         <li><a href="#rfc.section.5">5.</a>&nbsp;&nbsp;&nbsp;<a href="#head.effects">Updating Caches with HEAD Responses</a></li>
610         <li><a href="#rfc.section.6">6.</a>&nbsp;&nbsp;&nbsp;<a href="#invalidation.after.updates.or.deletions">Request Methods that Invalidate</a></li>
611         <li><a href="#rfc.section.7">7.</a>&nbsp;&nbsp;&nbsp;<a href="#header.field.definitions">Header Field Definitions</a><ul>
612               <li><a href="#rfc.section.7.1">7.1</a>&nbsp;&nbsp;&nbsp;<a href="#header.age">Age</a></li>
613               <li><a href="#rfc.section.7.2">7.2</a>&nbsp;&nbsp;&nbsp;<a href="#header.cache-control">Cache-Control</a><ul>
614                     <li><a href="#rfc.section.7.2.1">7.2.1</a>&nbsp;&nbsp;&nbsp;<a href="#cache-request-directive">Request Cache-Control Directives</a><ul>
[2236]615                           <li><a href="#rfc.section.7.2.1.1">7.2.1.1</a>&nbsp;&nbsp;&nbsp;<a href="#cache-request-directive.max-age">max-age</a></li>
616                           <li><a href="#rfc.section.7.2.1.2">7.2.1.2</a>&nbsp;&nbsp;&nbsp;<a href="#cache-request-directive.max-stale">max-stale</a></li>
617                           <li><a href="#rfc.section.7.2.1.3">7.2.1.3</a>&nbsp;&nbsp;&nbsp;<a href="#cache-request-directive.min-fresh">min-fresh</a></li>
618                           <li><a href="#rfc.section.7.2.1.4">7.2.1.4</a>&nbsp;&nbsp;&nbsp;<a href="#cache-request-directive.no-cache">no-cache</a></li>
619                           <li><a href="#rfc.section.7.2.1.5">7.2.1.5</a>&nbsp;&nbsp;&nbsp;<a href="#cache-request-directive.no-store">no-store</a></li>
[1825]620                           <li><a href="#rfc.section.7.2.1.6">7.2.1.6</a>&nbsp;&nbsp;&nbsp;<a href="#cache-request-directive.no-transform">no-transform</a></li>
621                           <li><a href="#rfc.section.7.2.1.7">7.2.1.7</a>&nbsp;&nbsp;&nbsp;<a href="#cache-request-directive.only-if-cached">only-if-cached</a></li>
[1695]622                        </ul>
623                     </li>
[1825]624                     <li><a href="#rfc.section.7.2.2">7.2.2</a>&nbsp;&nbsp;&nbsp;<a href="#cache-response-directive">Response Cache-Control Directives</a><ul>
[2236]625                           <li><a href="#rfc.section.7.2.2.1">7.2.2.1</a>&nbsp;&nbsp;&nbsp;<a href="#cache-response-directive.must-revalidate">must-revalidate</a></li>
626                           <li><a href="#rfc.section.7.2.2.2">7.2.2.2</a>&nbsp;&nbsp;&nbsp;<a href="#cache-response-directive.no-cache">no-cache</a></li>
627                           <li><a href="#rfc.section.7.2.2.3">7.2.2.3</a>&nbsp;&nbsp;&nbsp;<a href="#cache-response-directive.no-store">no-store</a></li>
628                           <li><a href="#rfc.section.7.2.2.4">7.2.2.4</a>&nbsp;&nbsp;&nbsp;<a href="#cache-response-directive.no-transform">no-transform</a></li>
629                           <li><a href="#rfc.section.7.2.2.5">7.2.2.5</a>&nbsp;&nbsp;&nbsp;<a href="#cache-response-directive.public">public</a></li>
630                           <li><a href="#rfc.section.7.2.2.6">7.2.2.6</a>&nbsp;&nbsp;&nbsp;<a href="#cache-response-directive.private">private</a></li>
631                           <li><a href="#rfc.section.7.2.2.7">7.2.2.7</a>&nbsp;&nbsp;&nbsp;<a href="#cache-response-directive.proxy-revalidate">proxy-revalidate</a></li>
632                           <li><a href="#rfc.section.7.2.2.8">7.2.2.8</a>&nbsp;&nbsp;&nbsp;<a href="#cache-response-directive.max-age">max-age</a></li>
633                           <li><a href="#rfc.section.7.2.2.9">7.2.2.9</a>&nbsp;&nbsp;&nbsp;<a href="#cache-response-directive.s-maxage">s-maxage</a></li>
[1695]634                        </ul>
635                     </li>
[1825]636                     <li><a href="#rfc.section.7.2.3">7.2.3</a>&nbsp;&nbsp;&nbsp;<a href="#cache.control.extensions">Cache Control Extensions</a></li>
[52]637                  </ul>
638               </li>
[1825]639               <li><a href="#rfc.section.7.3">7.3</a>&nbsp;&nbsp;&nbsp;<a href="#header.expires">Expires</a></li>
640               <li><a href="#rfc.section.7.4">7.4</a>&nbsp;&nbsp;&nbsp;<a href="#header.pragma">Pragma</a></li>
[1860]641               <li><a href="#rfc.section.7.5">7.5</a>&nbsp;&nbsp;&nbsp;<a href="#header.warning">Warning</a><ul>
642                     <li><a href="#rfc.section.7.5.1">7.5.1</a>&nbsp;&nbsp;&nbsp;<a href="#warn.110">110 Response is Stale</a></li>
643                     <li><a href="#rfc.section.7.5.2">7.5.2</a>&nbsp;&nbsp;&nbsp;<a href="#warn.111">111 Revalidation Failed</a></li>
644                     <li><a href="#rfc.section.7.5.3">7.5.3</a>&nbsp;&nbsp;&nbsp;<a href="#warn.112">112 Disconnected Operation</a></li>
645                     <li><a href="#rfc.section.7.5.4">7.5.4</a>&nbsp;&nbsp;&nbsp;<a href="#warn.113">113 Heuristic Expiration</a></li>
646                     <li><a href="#rfc.section.7.5.5">7.5.5</a>&nbsp;&nbsp;&nbsp;<a href="#warn.199">199 Miscellaneous Warning</a></li>
647                     <li><a href="#rfc.section.7.5.6">7.5.6</a>&nbsp;&nbsp;&nbsp;<a href="#warn.214">214 Transformation Applied</a></li>
648                     <li><a href="#rfc.section.7.5.7">7.5.7</a>&nbsp;&nbsp;&nbsp;<a href="#warn.299">299 Miscellaneous Persistent Warning</a></li>
649                     <li><a href="#rfc.section.7.5.8">7.5.8</a>&nbsp;&nbsp;&nbsp;<a href="#warn.code.extensions">Warn Code Extensions</a></li>
[1485]650                  </ul>
651               </li>
[52]652            </ul>
653         </li>
[1825]654         <li><a href="#rfc.section.8">8.</a>&nbsp;&nbsp;&nbsp;<a href="#history.lists">History Lists</a></li>
[2243]655         <li><a href="#rfc.section.9">9.</a>&nbsp;&nbsp;&nbsp;<a href="#iana.considerations">IANA Considerations</a><ul>
656               <li><a href="#rfc.section.9.1">9.1</a>&nbsp;&nbsp;&nbsp;<a href="#cache.directive.registry">Cache Directive Registry</a><ul>
657                     <li><a href="#rfc.section.9.1.1">9.1.1</a>&nbsp;&nbsp;&nbsp;<a href="#cache.directive.registry.procedure">Procedure</a></li>
658                     <li><a href="#rfc.section.9.1.2">9.1.2</a>&nbsp;&nbsp;&nbsp;<a href="#cache.directive.registration">Registrations</a></li>
659                  </ul>
660               </li>
[2244]661               <li><a href="#rfc.section.9.2">9.2</a>&nbsp;&nbsp;&nbsp;<a href="#warn.code.registry">Warn Code Registry</a><ul>
662                     <li><a href="#rfc.section.9.2.1">9.2.1</a>&nbsp;&nbsp;&nbsp;<a href="#warn.code.registry.procedure">Procedure</a></li>
663                     <li><a href="#rfc.section.9.2.2">9.2.2</a>&nbsp;&nbsp;&nbsp;<a href="#warn.code.registration">Registrations</a></li>
664                  </ul>
665               </li>
[1825]666               <li><a href="#rfc.section.9.3">9.3</a>&nbsp;&nbsp;&nbsp;<a href="#header.field.registration">Header Field Registration</a></li>
[253]667            </ul>
668         </li>
[1825]669         <li><a href="#rfc.section.10">10.</a>&nbsp;&nbsp;&nbsp;<a href="#security.considerations">Security Considerations</a></li>
670         <li><a href="#rfc.section.11">11.</a>&nbsp;&nbsp;&nbsp;<a href="#acks">Acknowledgments</a></li>
671         <li><a href="#rfc.section.12">12.</a>&nbsp;&nbsp;&nbsp;<a href="#rfc.references">References</a><ul>
672               <li><a href="#rfc.section.12.1">12.1</a>&nbsp;&nbsp;&nbsp;<a href="#rfc.references.1">Normative References</a></li>
673               <li><a href="#rfc.section.12.2">12.2</a>&nbsp;&nbsp;&nbsp;<a href="#rfc.references.2">Informative References</a></li>
[1513]674            </ul>
675         </li>
[1072]676         <li><a href="#rfc.authors">Authors' Addresses</a></li>
[1825]677         <li><a href="#rfc.section.A">A.</a>&nbsp;&nbsp;&nbsp;<a href="#changes.from.rfc.2616">Changes from RFC 2616</a></li>
678         <li><a href="#rfc.section.B">B.</a>&nbsp;&nbsp;&nbsp;<a href="#imported.abnf">Imported ABNF</a></li>
679         <li><a href="#rfc.section.C">C.</a>&nbsp;&nbsp;&nbsp;<a href="#collected.abnf">Collected ABNF</a></li>
680         <li><a href="#rfc.section.D">D.</a>&nbsp;&nbsp;&nbsp;<a href="#change.log">Change Log (to be removed by RFC Editor before publication)</a><ul>
681               <li><a href="#rfc.section.D.1">D.1</a>&nbsp;&nbsp;&nbsp;<a href="#changes.since.19">Since draft-ietf-httpbis-p6-cache-19</a></li>
682               <li><a href="#rfc.section.D.2">D.2</a>&nbsp;&nbsp;&nbsp;<a href="#changes.since.20">Since draft-ietf-httpbis-p6-cache-20</a></li>
[1929]683               <li><a href="#rfc.section.D.3">D.3</a>&nbsp;&nbsp;&nbsp;<a href="#changes.since.21">Since draft-ietf-httpbis-p6-cache-21</a></li>
[2190]684               <li><a href="#rfc.section.D.4">D.4</a>&nbsp;&nbsp;&nbsp;<a href="#changes.since.22">Since draft-ietf-httpbis-p6-cache-22</a></li>
[115]685            </ul>
686         </li>
[1072]687         <li><a href="#rfc.index">Index</a></li>
[52]688      </ul>
[157]689      <h1 id="rfc.section.1" class="np"><a href="#rfc.section.1">1.</a>&nbsp;<a id="caching" href="#caching">Introduction</a></h1>
[538]690      <p id="rfc.section.1.p.1">HTTP is typically used for distributed information systems, where performance can be improved by the use of response caches.
691         This document defines aspects of HTTP/1.1 related to caching and reusing response messages.
[52]692      </p>
[157]693      <div id="rfc.iref.c.1"></div>
[2234]694      <p id="rfc.section.1.p.2">An HTTP <dfn>cache</dfn> is a local store of response messages and the subsystem that controls storage, retrieval, and deletion of messages in it.
695         A cache stores cacheable responses in order to reduce the response time and network bandwidth consumption on future, equivalent
696         requests. Any client or server <em class="bcp14">MAY</em> employ a cache, though a cache cannot be used by a server that is acting as a tunnel.
[52]697      </p>
[2239]698      <div id="rfc.iref.s.1"></div>
699      <div id="rfc.iref.p.1"></div>
700      <div id="shared.and.non-shared.caches">
701         <p id="rfc.section.1.p.3">A <dfn>shared cache</dfn> is a cache that stores responses to be reused by more than one user; shared caches are usually (but not always) deployed as
702            a part of an intermediary. A <dfn>private cache</dfn>, in contrast, is dedicated to a single user.
703         </p>
704      </div>
705      <p id="rfc.section.1.p.4">The goal of caching in HTTP/1.1 is to significantly improve performance by reusing a prior response message to satisfy a current
[2234]706         request. A stored response is considered "fresh", as defined in <a href="#expiration.model" title="Freshness">Section&nbsp;4.1</a>, if the response can be reused without "validation" (checking with the origin server to see if the cached response remains
707         valid for this request). A fresh response can therefore reduce both latency and network overhead each time it is reused. When
[2240]708         a cached response is not fresh, it might still be reusable if it can be freshened by validation (<a href="#validation.model" title="Validation">Section&nbsp;4.2</a>) or if the origin is unavailable (<a href="#serving.stale.responses" title="Serving Stale Responses">Section&nbsp;4.1.4</a>).
[96]709      </p>
[2239]710      <h2 id="rfc.section.1.1"><a href="#rfc.section.1.1">1.1</a>&nbsp;<a id="conformance" href="#conformance">Conformance and Error Handling</a></h2>
711      <p id="rfc.section.1.1.p.1">The key words "MUST", "MUST NOT", "REQUIRED", "SHALL", "SHALL NOT", "SHOULD", "SHOULD NOT", "RECOMMENDED", "MAY", and "OPTIONAL"
[157]712         in this document are to be interpreted as described in <a href="#RFC2119" id="rfc.xref.RFC2119.1"><cite title="Key words for use in RFCs to Indicate Requirement Levels">[RFC2119]</cite></a>.
[52]713      </p>
[2239]714      <p id="rfc.section.1.1.p.2">Conformance criteria and considerations regarding error handling are defined in <a href="p1-messaging.html#conformance" title="Conformance and Error Handling">Section 2.5</a> of <a href="#Part1" id="rfc.xref.Part1.1"><cite title="Hypertext Transfer Protocol (HTTP/1.1): Message Syntax and Routing">[Part1]</cite></a>.
[52]715      </p>
[2239]716      <h2 id="rfc.section.1.2"><a href="#rfc.section.1.2">1.2</a>&nbsp;<a id="notation" href="#notation">Syntax Notation</a></h2>
717      <p id="rfc.section.1.2.p.1">This specification uses the Augmented Backus-Naur Form (ABNF) notation of <a href="#RFC5234" id="rfc.xref.RFC5234.1"><cite title="Augmented BNF for Syntax Specifications: ABNF">[RFC5234]</cite></a> with the list rule extension defined in <a href="p1-messaging.html#notation" title="Syntax Notation">Section 1.2</a> of <a href="#Part1" id="rfc.xref.Part1.2"><cite title="Hypertext Transfer Protocol (HTTP/1.1): Message Syntax and Routing">[Part1]</cite></a>. <a href="#imported.abnf" title="Imported ABNF">Appendix&nbsp;B</a> describes rules imported from other documents. <a href="#collected.abnf" title="Collected ABNF">Appendix&nbsp;C</a> shows the collected ABNF with the list rule expanded.
[543]718      </p>
[2239]719      <h3 id="rfc.section.1.2.1"><a href="#rfc.section.1.2.1">1.2.1</a>&nbsp;<a id="delta-seconds" href="#delta-seconds">Delta Seconds</a></h3>
720      <p id="rfc.section.1.2.1.p.1">The delta-seconds rule specifies a non-negative integer, representing time in seconds.</p>
[1805]721      <div id="rfc.figure.u.1"></div><pre class="inline"><span id="rfc.iref.g.1"></span>  <a href="#delta-seconds" class="smpl">delta-seconds</a>  = 1*<a href="#imported.abnf" class="smpl">DIGIT</a>
[2247]722</pre><p id="rfc.section.1.2.1.p.3">If a cache receives a delta-seconds value larger than the largest positive integer it can represent, or if any of its subsequent
723         calculations overflows, it <em class="bcp14">MUST</em> consider the value to be 2147483648 (2<sup>31</sup>). Recipients parsing a delta-seconds value <em class="bcp14">MUST</em> use an arithmetic type of at least 31 bits of range, and senders <em class="bcp14">MUST NOT</em> generate delta-seconds with a value greater than 2147483648.
[1323]724      </p>
[2239]725      <div id="rfc.iref.c.2"></div>
726      <div id="rfc.iref.c.3"></div>
[1751]727      <h1 id="rfc.section.2"><a href="#rfc.section.2">2.</a>&nbsp;<a id="caching.overview" href="#caching.overview">Overview of Cache Operation</a></h1>
[1864]728      <p id="rfc.section.2.p.1">Proper cache operation preserves the semantics of HTTP transfers (<a href="#Part2" id="rfc.xref.Part2.1"><cite title="Hypertext Transfer Protocol (HTTP/1.1): Semantics and Content">[Part2]</cite></a>) while eliminating the transfer of information already held in the cache. Although caching is an entirely <em class="bcp14">OPTIONAL</em> feature of HTTP, we assume that reusing the cached response is desirable and that such reuse is the default behavior when
[2234]729         no requirement or local configuration prevents it. Therefore, HTTP cache requirements are focused on preventing a cache from
730         either storing a non-reusable response or reusing a stored response inappropriately, rather than mandating that caches always
731         store and reuse particular responses.
[1375]732      </p>
733      <p id="rfc.section.2.p.2">Each <dfn>cache entry</dfn> consists of a cache key and one or more HTTP responses corresponding to prior requests that used the same key. The most common
[2109]734         form of cache entry is a successful result of a retrieval request: i.e., a <a href="p2-semantics.html#status.200" class="smpl">200 (OK)</a> response to a GET request, which contains a representation of the resource identified by the request target (<a href="p2-semantics.html#GET" title="GET">Section 4.3.1</a> of <a href="#Part2" id="rfc.xref.Part2.2"><cite title="Hypertext Transfer Protocol (HTTP/1.1): Semantics and Content">[Part2]</cite></a>). However, it is also possible to cache permanent redirects, negative results (e.g., <a href="p2-semantics.html#status.404" class="smpl">404 (Not Found)</a>), incomplete results (e.g., <a href="p5-range.html#status.206" class="smpl">206 (Partial Content)</a>), and responses to methods other than GET if the method's definition allows such caching and defines something suitable for
[1754]735         use as a cache key.
[1375]736      </p>
[2239]737      <div id="rfc.iref.c.4"></div>
[2234]738      <p id="rfc.section.2.p.3">The primary <dfn>cache key</dfn> consists of the request method and target URI. However, since HTTP caches in common use today are typically limited to caching
[2247]739         responses to GET, many caches simply decline other methods and use only the URI as the primary cache key.
[1375]740      </p>
741      <p id="rfc.section.2.p.4">If a request target is subject to content negotiation, its cache entry might consist of multiple stored responses, each differentiated
[2237]742         by a secondary key for the values of the original request's selecting header fields (<a href="#caching.negotiated.responses" title="Calculating Secondary Keys with Vary">Section&nbsp;4.3</a>).
[1375]743      </p>
[1751]744      <h1 id="rfc.section.3"><a href="#rfc.section.3">3.</a>&nbsp;<a id="response.cacheability" href="#response.cacheability">Storing Responses in Caches</a></h1>
745      <p id="rfc.section.3.p.1">A cache <em class="bcp14">MUST NOT</em> store a response to any request, unless:
[205]746      </p>
[538]747      <ul>
[722]748         <li>The request method is understood by the cache and defined as being cacheable, and</li>
[737]749         <li>the response status code is understood by the cache, and</li>
[1751]750         <li>the "no-store" cache directive (see <a href="#header.cache-control" id="rfc.xref.header.cache-control.1" title="Cache-Control">Section&nbsp;7.2</a>) does not appear in request or response header fields, and
[52]751         </li>
[2236]752         <li>the "private" cache response directive (see <a href="#cache-response-directive.private" title="private">Section&nbsp;7.2.2.6</a>) does not appear in the response, if the cache is shared, and
[52]753         </li>
[1864]754         <li>the <a href="p7-auth.html#header.authorization" class="smpl">Authorization</a> header field (see <a href="p7-auth.html#header.authorization" title="Authorization">Section 4.1</a> of <a href="#Part7" id="rfc.xref.Part7.1"><cite title="Hypertext Transfer Protocol (HTTP/1.1): Authentication">[Part7]</cite></a>) does not appear in the request, if the cache is shared, unless the response explicitly allows it (see <a href="#caching.authenticated.responses" title="Storing Responses to Authenticated Requests">Section&nbsp;3.2</a>), and
[538]755         </li>
[737]756         <li>the response either:
757            <ul>
[1751]758               <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;7.3</a>), or
[737]759               </li>
[2236]760               <li>contains a max-age response cache directive (see <a href="#cache-response-directive.max-age" title="max-age">Section&nbsp;7.2.2.8</a>), or
[737]761               </li>
[2236]762               <li>contains a s-maxage response cache directive (see <a href="#cache-response-directive.s-maxage" title="s-maxage">Section&nbsp;7.2.2.9</a>) and the cache is shared, or
[2234]763               </li>
[1751]764               <li>contains a Cache Control Extension (see <a href="#cache.control.extensions" title="Cache Control Extensions">Section&nbsp;7.2.3</a>) that allows it to be cached, or
[737]765               </li>
[2180]766               <li>has a status code that is defined as cacheable (see <a href="#heuristic.freshness" title="Calculating Heuristic Freshness">Section&nbsp;4.1.2</a>), or
[737]767               </li>
[2236]768               <li>contains a public response cache directive (see <a href="#cache-response-directive.public" title="public">Section&nbsp;7.2.2.5</a>).
[2183]769               </li>
[737]770            </ul> 
[538]771         </li>
772      </ul>
[1751]773      <p id="rfc.section.3.p.2">Note that any of the requirements listed above can be overridden by a cache-control extension; see <a href="#cache.control.extensions" title="Cache Control Extensions">Section&nbsp;7.2.3</a>.
[1291]774      </p>
[2234]775      <p id="rfc.section.3.p.3">In this context, a cache has "understood" a request method or a response status code if it recognizes it and implements all
776         specified caching-related behavior.
[737]777      </p>
[2234]778      <p id="rfc.section.3.p.4">Note that, in normal operation, some caches will not store a response that has neither a cache validator nor an explicit expiration
[538]779         time, as such responses are not usually useful to store. However, caches are not prohibited from storing such responses.
[52]780      </p>
[1751]781      <h2 id="rfc.section.3.1"><a href="#rfc.section.3.1">3.1</a>&nbsp;<a id="incomplete.responses" href="#incomplete.responses">Storing Incomplete Responses</a></h2>
[1864]782      <p id="rfc.section.3.1.p.1">A response message is considered complete when all of the octets indicated by the message framing (<a href="#Part1" id="rfc.xref.Part1.3"><cite title="Hypertext Transfer Protocol (HTTP/1.1): Message Syntax and Routing">[Part1]</cite></a>) are received prior to the connection being closed. If the request is GET, the response status is <a href="p2-semantics.html#status.200" class="smpl">200
[1751]783            (OK)</a>, and the entire response header block has been received, a cache <em class="bcp14">MAY</em> store an incomplete response message body if the cache entry is recorded as incomplete. Likewise, a <a href="p5-range.html#status.206" class="smpl">206 (Partial Content)</a> response <em class="bcp14">MAY</em> be stored as if it were an incomplete <a href="p2-semantics.html#status.200" class="smpl">200
[2147]784            (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.
[52]785      </p>
[2238]786      <p id="rfc.section.3.1.p.2">A cache <em class="bcp14">MAY</em> complete a stored incomplete response by making a subsequent range request (<a href="#Part5" id="rfc.xref.Part5.1"><cite title="Hypertext Transfer Protocol (HTTP/1.1): Range Requests">[Part5]</cite></a>) and combining the successful response with the stored entry, as defined in <a href="#combining.responses" title="Combining Partial Content">Section&nbsp;3.3</a>. A cache <em class="bcp14">MUST NOT</em> use an incomplete response to answer requests unless the response has been made complete or the request is partial and specifies
[1708]787         a range that is wholly within the incomplete response. A cache <em class="bcp14">MUST NOT</em> send a partial response to a client without explicitly marking it as such using the <a href="p5-range.html#status.206" class="smpl">206 (Partial Content)</a> status code.
[52]788      </p>
[1751]789      <h2 id="rfc.section.3.2"><a href="#rfc.section.3.2">3.2</a>&nbsp;<a id="caching.authenticated.responses" href="#caching.authenticated.responses">Storing Responses to Authenticated Requests</a></h2>
[1864]790      <p id="rfc.section.3.2.p.1">A shared cache <em class="bcp14">MUST NOT</em> use a cached response to a request with an <a href="p7-auth.html#header.authorization" class="smpl">Authorization</a> header field (<a href="p7-auth.html#header.authorization" title="Authorization">Section 4.1</a> of <a href="#Part7" id="rfc.xref.Part7.2"><cite title="Hypertext Transfer Protocol (HTTP/1.1): Authentication">[Part7]</cite></a>) to satisfy any subsequent request unless a cache directive that allows such responses to be stored is present in the response.
[52]791      </p>
[1751]792      <p id="rfc.section.3.2.p.2">In this specification, the following <a href="#header.cache-control" class="smpl">Cache-Control</a> response directives (<a href="#cache-response-directive" title="Response Cache-Control Directives">Section&nbsp;7.2.2</a>) have such an effect: must-revalidate, public, s-maxage.
793      </p>
794      <p id="rfc.section.3.2.p.3">Note that cached responses that contain the "must-revalidate" and/or "s-maxage" response directives are not allowed to be
795         served stale (<a href="#serving.stale.responses" title="Serving Stale Responses">Section&nbsp;4.1.4</a>) by shared caches. In particular, a response with either "max-age=0, must-revalidate" or "s-maxage=0" cannot be used to satisfy
796         a subsequent request without revalidating it on the origin server.
797      </p>
[2238]798      <h2 id="rfc.section.3.3"><a href="#rfc.section.3.3">3.3</a>&nbsp;<a id="combining.responses" href="#combining.responses">Combining Partial Content</a></h2>
799      <p id="rfc.section.3.3.p.1">A response might transfer only a partial representation if the connection closed prematurely or if the request used one or
800         more Range specifiers (<a href="#Part5" id="rfc.xref.Part5.2"><cite title="Hypertext Transfer Protocol (HTTP/1.1): Range Requests">[Part5]</cite></a>). After several such transfers, a cache might have received several ranges of the same representation. A cache <em class="bcp14">MAY</em> combine these ranges into a single stored response, and reuse that response to satisfy later requests, if they all share the
801         same strong validator and the cache complies with the client requirements in <a href="p5-range.html#combining.byte.ranges" title="Combining Ranges">Section 4.3</a> of <a href="#Part5" id="rfc.xref.Part5.3"><cite title="Hypertext Transfer Protocol (HTTP/1.1): Range Requests">[Part5]</cite></a>.
802      </p>
803      <p id="rfc.section.3.3.p.2">When combining the new response with one or more stored responses, a cache <em class="bcp14">MUST</em>:
804      </p>
805      <ul>
806         <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;7.5</a>);
807         </li>
808         <li>retain any <a href="#header.warning" class="smpl">Warning</a> header fields in the stored response with warn-code 2xx; and,
809         </li>
810         <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.
811         </li>
812      </ul>
[1751]813      <h1 id="rfc.section.4"><a href="#rfc.section.4">4.</a>&nbsp;<a id="constructing.responses.from.caches" href="#constructing.responses.from.caches">Constructing Responses from Caches</a></h1>
[2234]814      <p id="rfc.section.4.p.1">When presented with a request, a cache <em class="bcp14">MUST NOT</em> reuse a stored response, unless:
[1751]815      </p>
[538]816      <ul>
[1864]817         <li>The presented effective request URI (<a href="p1-messaging.html#effective.request.uri" title="Effective Request URI">Section 5.5</a> of <a href="#Part1" id="rfc.xref.Part1.4"><cite title="Hypertext Transfer Protocol (HTTP/1.1): Message Syntax and Routing">[Part1]</cite></a>) and that of the stored response match, and
[538]818         </li>
819         <li>the request method associated with the stored response allows it to be used for the presented request, and</li>
[2237]820         <li>selecting header fields nominated by the stored response (if any) match those presented (see <a href="#caching.negotiated.responses" title="Calculating Secondary Keys with Vary">Section&nbsp;4.3</a>), and
[538]821         </li>
[2234]822         <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;7.4</a>), nor the no-cache cache directive (<a href="#cache-request-directive" title="Request Cache-Control Directives">Section&nbsp;7.2.1</a>), unless the stored response is successfully validated (<a href="#validation.model" title="Validation">Section&nbsp;4.2</a>), and
[538]823         </li>
[2236]824         <li>the stored response does not contain the no-cache cache directive (<a href="#cache-response-directive.no-cache" title="no-cache">Section&nbsp;7.2.2.2</a>), unless it is successfully validated (<a href="#validation.model" title="Validation">Section&nbsp;4.2</a>), and
[1483]825         </li>
[538]826         <li>the stored response is either:
827            <ul>
[2234]828               <li>fresh (see <a href="#expiration.model" title="Freshness">Section&nbsp;4.1</a>), or
[538]829               </li>
[1751]830               <li>allowed to be served stale (see <a href="#serving.stale.responses" title="Serving Stale Responses">Section&nbsp;4.1.4</a>), or
[538]831               </li>
[2234]832               <li>successfully validated (see <a href="#validation.model" title="Validation">Section&nbsp;4.2</a>).
[538]833               </li>
[540]834            </ul> 
[538]835         </li>
836      </ul>
[1751]837      <p id="rfc.section.4.p.2">Note that any of the requirements listed above can be overridden by a cache-control extension; see <a href="#cache.control.extensions" title="Cache Control Extensions">Section&nbsp;7.2.3</a>.
[540]838      </p>
[2234]839      <p id="rfc.section.4.p.3">When a stored response is used to satisfy a request without validation, a cache <em class="bcp14">MUST</em> generate an <a href="#header.age" class="smpl">Age</a> header field (<a href="#header.age" id="rfc.xref.header.age.1" title="Age">Section&nbsp;7.1</a>), replacing any present in the response with a value equal to the stored response's current_age; see <a href="#age.calculations" title="Calculating Age">Section&nbsp;4.1.3</a>.
[1291]840      </p>
[2088]841      <p id="rfc.section.4.p.4">A cache <em class="bcp14">MUST</em> write through requests with methods that are unsafe (<a href="p2-semantics.html#safe.methods" title="Safe Methods">Section 4.2.1</a> of <a href="#Part2" id="rfc.xref.Part2.3"><cite title="Hypertext Transfer Protocol (HTTP/1.1): Semantics and Content">[Part2]</cite></a>) to the origin server; i.e., a cache is not allowed to generate a reply to such a request before having forwarded the request
[1604]842         and having received a corresponding response.
[52]843      </p>
[1751]844      <p id="rfc.section.4.p.5">Also, note that unsafe requests might invalidate already stored responses; see <a href="#invalidation.after.updates.or.deletions" title="Request Methods that Invalidate">Section&nbsp;6</a>.
[52]845      </p>
[2234]846      <p id="rfc.section.4.p.6">When more than one suitable response is stored, a cache <em class="bcp14">MUST</em> use the most recent response (as determined by the <a href="p2-semantics.html#header.date" class="smpl">Date</a> header field). It can also forward the request with "Cache-Control: max-age=0" or "Cache-Control: no-cache" to disambiguate
[1740]847         which response to use.
[52]848      </p>
[2234]849      <p id="rfc.section.4.p.7">A cache that does not have a clock available <em class="bcp14">MUST NOT</em> use stored responses without revalidating them upon every use.
[1044]850      </p>
[2239]851      <div id="rfc.iref.f.1"></div>
852      <div id="rfc.iref.s.2"></div>
[2234]853      <h2 id="rfc.section.4.1"><a href="#rfc.section.4.1">4.1</a>&nbsp;<a id="expiration.model" href="#expiration.model">Freshness</a></h2>
[2239]854      <p id="rfc.section.4.1.p.1">A <dfn>fresh</dfn> response is one whose age has not yet exceeded its freshness lifetime. Conversely, a <dfn>stale</dfn> response is one where it has.
855      </p>
856      <div id="rfc.iref.f.2"></div>
857      <div id="rfc.iref.e.1"></div>
858      <div id="rfc.iref.h.1"></div>
859      <p id="rfc.section.4.1.p.2">A response's <dfn>freshness lifetime</dfn> is the length of time between its generation by the origin server and its expiration time. An <dfn>explicit expiration time</dfn> is the time at which the origin server intends that a stored response can no longer be used by a cache without further validation,
860         whereas a <dfn>heuristic expiration time</dfn> is assigned by a cache when no explicit expiriation time is available.
861      </p>
862      <div id="rfc.iref.a.1"></div>
863      <p id="rfc.section.4.1.p.3">A response's <dfn>age</dfn> is the time that has passed since it was generated by, or successfully validated with, the origin server.
864      </p>
865      <p id="rfc.section.4.1.p.4">When a response is "fresh" in the cache, it can be used to satisfy subsequent requests without contacting the origin server,
[538]866         thereby improving efficiency.
[52]867      </p>
[2239]868      <p id="rfc.section.4.1.p.5">The primary mechanism for determining freshness is for an origin server to provide an explicit expiration time in the future,
[2236]869         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;7.3</a>) or the max-age response cache directive (<a href="#cache-response-directive.max-age" title="max-age">Section&nbsp;7.2.2.8</a>). Generally, origin servers will assign future explicit expiration times to responses in the belief that the representation
[868]870         is not likely to change in a semantically significant way before the expiration time is reached.
[52]871      </p>
[2239]872      <p id="rfc.section.4.1.p.6">If an origin server wishes to force a cache to validate every request, it can assign an explicit expiration time in the past
[1991]873         to indicate that the response is already stale. Compliant caches will normally validate a stale cached response before reusing
[1751]874         it for subsequent requests (see <a href="#serving.stale.responses" title="Serving Stale Responses">Section&nbsp;4.1.4</a>).
[540]875      </p>
[2239]876      <p id="rfc.section.4.1.p.7">Since origin servers do not always provide explicit expiration times, caches are also allowed to use a heuristic to determine
[2180]877         an expiration time under certain circumstances (see <a href="#heuristic.freshness" title="Calculating Heuristic Freshness">Section&nbsp;4.1.2</a>).
[52]878      </p>
[2232]879      <div id="rfc.figure.u.2"></div>
880      <p>The calculation to determine if a response is fresh is:</p><pre class="text">   response_is_fresh = (freshness_lifetime &gt; current_age)
[2239]881</pre><p id="rfc.section.4.1.p.9">freshness_lifetime is defined in <a href="#calculating.freshness.lifetime" title="Calculating Freshness Lifetime">Section&nbsp;4.1.1</a>; current_age is defined in <a href="#age.calculations" title="Calculating Age">Section&nbsp;4.1.3</a>.
[52]882      </p>
[2239]883      <p id="rfc.section.4.1.p.10">Clients can send the max-age or min-fresh cache directives in a request to constrain or relax freshness calculations for the
[2002]884         corresponding response (<a href="#cache-request-directive" title="Request Cache-Control Directives">Section&nbsp;7.2.1</a>).
[52]885      </p>
[2239]886      <p id="rfc.section.4.1.p.11">When calculating freshness, to avoid common problems in date parsing:</p>
887      <p id="rfc.section.4.1.p.12"> </p>
[2235]888      <ul>
889         <li>Although all date formats are specified to be case-sensitive, cache recipients <em class="bcp14">SHOULD</em> match day, week and timezone names case-insensitively.
890         </li>
891         <li>If a cache recipient's internal implementation of time has less resolution than the value of an HTTP-date, the recipient <em class="bcp14">MUST</em> internally represent a parsed <a href="#header.expires" class="smpl">Expires</a> date as the nearest time equal to or earlier than the received value.
892         </li>
893         <li>Cache recipients <em class="bcp14">MUST NOT</em> allow local time zones to influence the calculation or comparison of an age or expiration time.
894         </li>
895         <li>Cache recipients <em class="bcp14">SHOULD</em> consider a date with a zone abbreviation other than "GMT" to be invalid for calculating expiration.
896         </li>
897      </ul>
[2239]898      <p id="rfc.section.4.1.p.13">Note that freshness applies only to cache operation; it cannot be used to force a user agent to refresh its display or reload
[1751]899         a resource. See <a href="#history.lists" title="History Lists">Section&nbsp;8</a> for an explanation of the difference between caches and history mechanisms.
[52]900      </p>
[1751]901      <h3 id="rfc.section.4.1.1"><a href="#rfc.section.4.1.1">4.1.1</a>&nbsp;<a id="calculating.freshness.lifetime" href="#calculating.freshness.lifetime">Calculating Freshness Lifetime</a></h3>
902      <p id="rfc.section.4.1.1.p.1">A cache can calculate the freshness lifetime (denoted as freshness_lifetime) of a response by using the first match of: </p>
[538]903      <ul>
[2236]904         <li>If the cache is shared and the s-maxage response cache directive (<a href="#cache-response-directive.s-maxage" title="s-maxage">Section&nbsp;7.2.2.9</a>) is present, use its value, or
[538]905         </li>
[2236]906         <li>If the max-age response cache directive (<a href="#cache-response-directive.max-age" title="max-age">Section&nbsp;7.2.2.8</a>) is present, use its value, or
[538]907         </li>
[1751]908         <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;7.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
[538]909         </li>
[1751]910         <li>Otherwise, no explicit expiration time is present in the response. A heuristic freshness lifetime might be applicable; see <a href="#heuristic.freshness" title="Calculating Heuristic Freshness">Section&nbsp;4.1.2</a>.
[538]911         </li>
912      </ul>
[1751]913      <p id="rfc.section.4.1.1.p.2">Note that this calculation is not vulnerable to clock skew, since all of the information comes from the origin server.</p>
[2234]914      <p id="rfc.section.4.1.1.p.3">When there is more than one value present for a given directive (e.g., two <a href="#header.expires" class="smpl">Expires</a> header fields, multiple Cache-Control: max-age directives), the directive's value is considered invalid. Caches are encouraged
915         to consider responses that have invalid freshness information to be stale.
[1731]916      </p>
[1751]917      <h3 id="rfc.section.4.1.2"><a href="#rfc.section.4.1.2">4.1.2</a>&nbsp;<a id="heuristic.freshness" href="#heuristic.freshness">Calculating Heuristic Freshness</a></h3>
[2180]918      <p id="rfc.section.4.1.2.p.1">Since origin servers do not always provide explicit expiration times, a cache <em class="bcp14">MAY</em> assign a heuristic expiration time when an explicit time is not specified, employing algorithms that use other header field
919         values (such as the <a href="p4-conditional.html#header.last-modified" class="smpl">Last-Modified</a> time) to estimate a plausible expiration time. This specification does not provide specific algorithms, but does impose worst-case
920         constraints on their results.
[52]921      </p>
[2180]922      <p id="rfc.section.4.1.2.p.2">A cache <em class="bcp14">MUST NOT</em> use heuristics to determine freshness when an explicit expiration time is present in the stored response. Because of the requirements
923         in <a href="#response.cacheability" title="Storing Responses in Caches">Section&nbsp;3</a>, this means that, effectively, heuristics can only be used on responses without explicit freshness whose status codes are
924         defined as cacheable, and responses without explicit freshness that have been marked as explicitly cacheable (e.g., with a
925         "public" response cache directive).
[52]926      </p>
[2239]927      <p id="rfc.section.4.1.2.p.3">If the response has a <a href="p4-conditional.html#header.last-modified" class="smpl">Last-Modified</a> header field (<a href="p4-conditional.html#header.last-modified" title="Last-Modified">Section 2.2</a> of <a href="#Part4" id="rfc.xref.Part4.1"><cite title="Hypertext Transfer Protocol (HTTP/1.1): Conditional Requests">[Part4]</cite></a>), caches are encouraged to use a heuristic expiration value that is no more than some fraction of the interval since that
[1434]928         time. A typical setting of this fraction might be 10%.
[52]929      </p>
[2180]930      <p id="rfc.section.4.1.2.p.4">When a heuristic is used to calculate freshness lifetime, a cache <em class="bcp14">SHOULD</em> attach a <a href="#header.warning" class="smpl">Warning</a> header field with a 113 warn-code to the response if its current_age is more than 24 hours and such a warning is not already
931         present.
932      </p>
933      <div class="note" id="rfc.section.4.1.2.p.5"> 
[1755]934         <p> <b>Note:</b>  <a href="http://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 (i.e., those containing '?'). In practice,
[2234]935            this has not been widely implemented. Therefore, origin servers are encouraged to send explicit directives (e.g., Cache-Control:
[828]936            no-cache) if they wish to preclude caching.
937         </p> 
938      </div>
[1751]939      <h3 id="rfc.section.4.1.3"><a href="#rfc.section.4.1.3">4.1.3</a>&nbsp;<a id="age.calculations" href="#age.calculations">Calculating Age</a></h3>
[2082]940      <p id="rfc.section.4.1.3.p.1">The <a href="#header.age" class="smpl">Age</a> header field is used to convey an estimated age of the response message when obtained from a cache. The Age field value is
941         the cache's estimate of the number of seconds since the response was generated or validated by the origin server. In essence,
942         the Age value is the sum of the time that the response has been resident in each of the caches along the path from the origin
943         server, plus the amount of time it has been in transit along network paths.
[52]944      </p>
[1751]945      <p id="rfc.section.4.1.3.p.2">The following data is used for the age calculation:</p>
946      <p id="rfc.section.4.1.3.p.3"> <dfn>age_value</dfn> 
[52]947      </p>
[779]948      <ul class="empty">
[1751]949         <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;7.1</a>), in a form appropriate for arithmetic operation; or 0, if not available.
[784]950         </li>
[779]951      </ul>
[1751]952      <p id="rfc.section.4.1.3.p.4"> <dfn>date_value</dfn> 
[52]953      </p>
[779]954      <ul class="empty">
[2180]955         <li>The term "date_value" denotes the value of the Date header field, in a form appropriate for arithmetic operations. See <a href="p2-semantics.html#header.date" title="Date">Section 7.1.1.2</a> of <a href="#Part2" id="rfc.xref.Part2.4"><cite title="Hypertext Transfer Protocol (HTTP/1.1): Semantics and Content">[Part2]</cite></a> for the definition of the Date header field, and for requirements regarding responses without it.
[779]956         </li>
957      </ul>
[1751]958      <p id="rfc.section.4.1.3.p.5"> <dfn>now</dfn> 
[779]959      </p>
960      <ul class="empty">
[2082]961         <li>The term "now" means "the current value of the clock at the host performing the calculation". A host ought to use NTP (<a href="#RFC1305" id="rfc.xref.RFC1305.1"><cite title="Network Time Protocol (Version 3) Specification, Implementation">[RFC1305]</cite></a>) or some similar protocol to synchronize its clocks to Coordinated Universal Time.
[779]962         </li>
963      </ul>
[1751]964      <p id="rfc.section.4.1.3.p.6"> <dfn>request_time</dfn> 
[779]965      </p>
966      <ul class="empty">
967         <li>The current value of the clock at the host at the time the request resulting in the stored response was made.</li>
968      </ul>
[1751]969      <p id="rfc.section.4.1.3.p.7"> <dfn>response_time</dfn> 
[779]970      </p>
971      <ul class="empty">
972         <li>The current value of the clock at the host at the time the response was received.</li>
973      </ul>
[1751]974      <p id="rfc.section.4.1.3.p.8">A response's age can be calculated in two entirely independent ways: </p>
[52]975      <ol>
[786]976         <li>the "apparent_age": response_time minus date_value, if the local clock is reasonably well synchronized to the origin server's
977            clock. If the result is negative, the result is replaced by zero.
[52]978         </li>
[1112]979         <li>the "corrected_age_value", if all of the caches along the response path implement HTTP/1.1. A cache <em class="bcp14">MUST</em> interpret this value relative to the time the request was initiated, not the time that the response was received.
[792]980         </li>
[52]981      </ol>
[2232]982      <div id="rfc.figure.u.3"></div><pre class="text">  apparent_age = max(0, response_time - date_value);
[792]983
984  response_delay = response_time - request_time;
985  corrected_age_value = age_value + response_delay; 
[2232]986</pre><div id="rfc.figure.u.4"></div>
[2250]987      <p>These are combined as</p><pre class="text">  corrected_initial_age = max(apparent_age, corrected_age_value);
[1751]988</pre><p id="rfc.section.4.1.3.p.11">unless the cache is confident in the value of the <a href="#header.age" class="smpl">Age</a> header field (e.g., because there are no HTTP/1.0 hops in the <a href="p1-messaging.html#header.via" class="smpl">Via</a> header field), in which case the corrected_age_value <em class="bcp14">MAY</em> be used as the corrected_initial_age.
[1484]989      </p>
[1751]990      <p id="rfc.section.4.1.3.p.12">The current_age of a stored response can then be calculated by adding the amount of time (in seconds) since the stored response
[538]991         was last validated by the origin server to the corrected_initial_age.
[52]992      </p>
[1805]993      <div id="rfc.figure.u.5"></div><pre class="text">  resident_time = now - response_time;
[786]994  current_age = corrected_initial_age + resident_time;
[2235]995</pre><h3 id="rfc.section.4.1.4"><a href="#rfc.section.4.1.4">4.1.4</a>&nbsp;<a id="serving.stale.responses" href="#serving.stale.responses">Serving Stale Responses</a></h3>
[1751]996      <p id="rfc.section.4.1.4.p.1">A "stale" response is one that either has explicit expiry information or is allowed to have heuristic expiry calculated, but
[2234]997         is not fresh according to the calculations in <a href="#expiration.model" title="Freshness">Section&nbsp;4.1</a>.
[52]998      </p>
[2247]999      <p id="rfc.section.4.1.4.p.2">A cache <em class="bcp14">MUST NOT</em> generate a stale response if it is prohibited by an explicit in-protocol directive (e.g., by a "no-store" or "no-cache" cache
[538]1000         directive, a "must-revalidate" cache-response-directive, or an applicable "s-maxage" or "proxy-revalidate" cache-response-directive;
[1751]1001         see <a href="#cache-response-directive" title="Response Cache-Control Directives">Section&nbsp;7.2.2</a>).
[52]1002      </p>
[2052]1003      <p id="rfc.section.4.1.4.p.3">A cache <em class="bcp14">MUST NOT</em> send stale responses unless it is disconnected (i.e., it cannot contact the origin server or otherwise find a forward path)
[1751]1004         or doing so is explicitly allowed (e.g., by the max-stale request directive; see <a href="#cache-request-directive" title="Request Cache-Control Directives">Section&nbsp;7.2.1</a>).
[52]1005      </p>
[2238]1006      <p id="rfc.section.4.1.4.p.4">A cache <em class="bcp14">SHOULD</em> append a <a href="#header.warning" class="smpl">Warning</a> header field with the 110 warn-code (see <a href="#header.warning" id="rfc.xref.header.warning.2" title="Warning">Section&nbsp;7.5</a>) to stale responses. Likewise, a cache <em class="bcp14">SHOULD</em> add the 112 warn-code to stale responses if the cache is disconnected.
[52]1007      </p>
[2239]1008      <div id="rfc.iref.f.3"></div>
[2250]1009      <p id="rfc.section.4.1.4.p.5">Note that if a cache receives a <dfn>first-hand</dfn> response (one where the freshness model is not in use; i.e., its age is 0, whether it is an entire response, or a <a href="p4-conditional.html#status.304" class="smpl">304 (Not Modified)</a> response) that it would normally forward to the requesting client, and the received response is no longer fresh, the cache <em class="bcp14">MAY</em> forward it to the requesting client without adding a new <a href="#header.warning" class="smpl">Warning</a> (but without removing any existing Warning header fields). A cache ought not attempt to validate a response simply because
[1737]1010         that response became stale in transit.
[52]1011      </p>
[2234]1012      <h2 id="rfc.section.4.2"><a href="#rfc.section.4.2">4.2</a>&nbsp;<a id="validation.model" href="#validation.model">Validation</a></h2>
[1751]1013      <p id="rfc.section.4.2.p.1">When a cache has one or more stored responses for a requested URI, but cannot serve any of them (e.g., because they are not
[2239]1014         fresh, or one cannot be selected; see <a href="#caching.negotiated.responses" title="Calculating Secondary Keys with Vary">Section&nbsp;4.3</a>), it can use the conditional request mechanism <a href="#Part4" id="rfc.xref.Part4.2"><cite title="Hypertext Transfer Protocol (HTTP/1.1): Conditional Requests">[Part4]</cite></a> in the forwarded request to give the origin server an opportunity to both select a valid stored response to be used, and to
[609]1015         update it. This process is known as "validating" or "revalidating" the stored response.
[52]1016      </p>
[2239]1017      <div id="rfc.iref.v.1"></div>
1018      <p id="rfc.section.4.2.p.2">When sending such a conditional request, a cache adds a <dfn>validator</dfn> (or more than one), that is used to find out whether a stored response is an equivalent copy of a current representation of
1019         the resource.
[52]1020      </p>
[2239]1021      <p id="rfc.section.4.2.p.3">One such validator is the <a href="p4-conditional.html#header.if-modified-since" class="smpl">If-Modified-Since</a> header field, whose value is that of the <a href="p4-conditional.html#header.last-modified" class="smpl">Last-Modified</a> header field from the selected (see <a href="#caching.negotiated.responses" title="Calculating Secondary Keys with Vary">Section&nbsp;4.3</a>) stored response, if available.
1022      </p>
1023      <p id="rfc.section.4.2.p.4">Another is the <a href="p4-conditional.html#header.if-none-match" class="smpl">If-None-Match</a> header field, whose value is that of the <a href="p4-conditional.html#header.etag" class="smpl">ETag</a> header field(s) from relevant responses stored for the primary cache key, if present. However, if any of the stored responses
[2250]1024         contains only partial content, the cache ought not include its entity-tag in the If-None-Match header field unless the request
[2234]1025         is for a range that would be fully satisfied by that stored response.
[52]1026      </p>
[2239]1027      <p id="rfc.section.4.2.p.5">Cache handling of a response to a conditional request is dependent upon its status code:</p>
1028      <p id="rfc.section.4.2.p.6"> </p>
[1419]1029      <ul>
[2238]1030         <li>A <a href="p4-conditional.html#status.304" class="smpl">304 (Not Modified)</a> response status code indicates that the stored response can be updated and reused; see <a href="#freshening.responses" title="Freshening Stored Responses upon Validation">Section&nbsp;4.2.1</a>.
[1419]1031         </li>
[1910]1032         <li>A full response (i.e., one with a payload body) indicates that none of the stored responses nominated in the conditional request
1033            is suitable. Instead, the cache can use the full response to satisfy the request and <em class="bcp14">MAY</em> replace the stored response(s).
[1419]1034         </li>
[1735]1035         <li>However, if a cache receives a <a href="p2-semantics.html#status.5xx" class="smpl">5xx (Server Error)</a> response while attempting to validate a response, it can either forward this response to the requesting client, or act as
[2052]1036            if the server failed to respond. In the latter case, it can send a previously stored response (see <a href="#serving.stale.responses" title="Serving Stale Responses">Section&nbsp;4.1.4</a>).
[1419]1037         </li>
1038      </ul>
[2238]1039      <h3 id="rfc.section.4.2.1"><a href="#rfc.section.4.2.1">4.2.1</a>&nbsp;<a id="freshening.responses" href="#freshening.responses">Freshening Stored Responses upon Validation</a></h3>
[1751]1040      <p id="rfc.section.4.2.1.p.1">When a cache receives a <a href="p4-conditional.html#status.304" class="smpl">304 (Not Modified)</a> response and already has one or more stored <a href="p2-semantics.html#status.200" class="smpl">200 (OK)</a> responses for the same cache key, the cache needs to identify which of the stored responses are updated by this new response
[2100]1041         and then update the stored response(s) with the new information provided in the <a href="p4-conditional.html#status.304" class="smpl">304</a> response.
[540]1042      </p>
[2239]1043      <div id="rfc.iref.s.3"></div>
[2100]1044      <p id="rfc.section.4.2.1.p.2">The stored response to update is identified by using the first match (if any) of: </p>
[1419]1045      <ul>
[2239]1046         <li>If the new response contains a <dfn>strong validator</dfn> (see <a href="p4-conditional.html#weak.and.strong.validators" title="Weak versus Strong">Section 2.1</a> of <a href="#Part4" id="rfc.xref.Part4.3"><cite title="Hypertext Transfer Protocol (HTTP/1.1): Conditional Requests">[Part4]</cite></a>), then that strong validator identifies the selected representation for update. All of the stored responses with the same
[2247]1047            strong validator are selected. If none of the stored responses contain the same strong validator, then the cache <em class="bcp14">MUST NOT</em> use the new response to update any stored responses.
[1419]1048         </li>
1049         <li>If the new response contains a weak validator and that validator corresponds to one of the cache's stored responses, then
[2234]1050            the most recent of those matching stored responses is selected for update.
[1419]1051         </li>
[2100]1052         <li>If the new response does not include any form of validator (such as in the case where a client generates an If-Modified-Since
1053            request from a source other than the Last-Modified response header field), and there is only one stored response, and that
[2234]1054            stored response also lacks a validator, then that stored response is selected for update.
[1419]1055         </li>
1056      </ul>
[2100]1057      <p id="rfc.section.4.2.1.p.3">If a stored response is selected for update, the cache <em class="bcp14">MUST</em>:
[52]1058      </p>
[1419]1059      <ul>
[2238]1060         <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;7.5</a>);
[1419]1061         </li>
[1737]1062         <li>retain any <a href="#header.warning" class="smpl">Warning</a> header fields in the stored response with warn-code 2xx; and,
1063         </li>
[1734]1064         <li>use other header fields provided in the <a href="p4-conditional.html#status.304" class="smpl">304 (Not Modified)</a> response to replace all instances of the corresponding header fields in the stored response.
[1419]1065         </li>
1066      </ul>
[2237]1067      <h2 id="rfc.section.4.3"><a href="#rfc.section.4.3">4.3</a>&nbsp;<a id="caching.negotiated.responses" href="#caching.negotiated.responses">Calculating Secondary Keys with Vary</a></h2>
[2180]1068      <p id="rfc.section.4.3.p.1">When a cache receives a request that can be satisfied by a stored response that has a <a href="p2-semantics.html#header.vary" class="smpl">Vary</a> header field (<a href="p2-semantics.html#header.vary" title="Vary">Section 7.1.4</a> of <a href="#Part2" id="rfc.xref.Part2.5"><cite title="Hypertext Transfer Protocol (HTTP/1.1): Semantics and Content">[Part2]</cite></a>), it <em class="bcp14">MUST NOT</em> use that response unless all of the selecting header fields nominated by the Vary header field match in both the original
[994]1069         request (i.e., that associated with the stored response), and the presented request.
[52]1070      </p>
[1751]1071      <p id="rfc.section.4.3.p.2">The selecting header fields from two requests are defined to match if and only if those in the first request can be transformed
[1164]1072         to those in the second request by applying any of the following:
[52]1073      </p>
[771]1074      <ul>
[994]1075         <li>adding or removing whitespace, where allowed in the header field's syntax</li>
[1864]1076         <li>combining multiple header fields with the same field name (see <a href="p1-messaging.html#header.fields" title="Header Fields">Section 3.2</a> of <a href="#Part1" id="rfc.xref.Part1.5"><cite title="Hypertext Transfer Protocol (HTTP/1.1): Message Syntax and Routing">[Part1]</cite></a>)
[771]1077         </li>
[994]1078         <li>normalizing both header field values in a way that is known to have identical semantics, according to the header field's specification
[771]1079            (e.g., re-ordering field values when order is not significant; case-normalization, where values are defined to be case-insensitive)
1080         </li>
1081      </ul>
[1751]1082      <p id="rfc.section.4.3.p.3">If (after any normalization that might take place) a header field is absent from a request, it can only match another request
[771]1083         if it is also absent there.
1084      </p>
[2248]1085      <p id="rfc.section.4.3.p.4">A <a href="p2-semantics.html#header.vary" class="smpl">Vary</a> header field-value of "*" always fails to match.
[52]1086      </p>
[1751]1087      <p id="rfc.section.4.3.p.5">The stored response with matching selecting header fields is known as the selected response.</p>
[2268]1088      <p id="rfc.section.4.3.p.6">If multiple selected responses are available (potentially including responses without a Vary header field), the cache will
1089         need to choose one to use. When a selecting header field has a known mechanism for doing so (e.g., qvalues on <a href="p2-semantics.html#header.accept" class="smpl">Accept</a> and similar request header fields), that mechanism <em class="bcp14">MAY</em> be used to select preferred responses; of the remainder, the most recent response (as determined by the <a href="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>.
[52]1090      </p>
[1996]1091      <p id="rfc.section.4.3.p.7">If no selected response is available, the cache cannot satisfy the presented request. Typically, it is forwarded to the origin
[2234]1092         server in a (possibly conditional; see <a href="#validation.model" title="Validation">Section&nbsp;4.2</a>) request.
[1289]1093      </p>
[1751]1094      <h1 id="rfc.section.5"><a href="#rfc.section.5">5.</a>&nbsp;<a id="head.effects" href="#head.effects">Updating Caches with HEAD Responses</a></h1>
1095      <p id="rfc.section.5.p.1">A response to the HEAD method is identical to what an equivalent request made with a GET would have been, except it lacks
1096         a body. This property of HEAD responses is used to both invalidate and update cached GET responses.
1097      </p>
[2237]1098      <p id="rfc.section.5.p.2">If one or more stored GET responses can be selected (as per <a href="#caching.negotiated.responses" title="Calculating Secondary Keys with Vary">Section&nbsp;4.3</a>) for a HEAD request, and the <a href="p1-messaging.html#header.content-length" class="smpl">Content-Length</a>, <a href="p4-conditional.html#header.etag" class="smpl">ETag</a> or <a href="p4-conditional.html#header.last-modified" class="smpl">Last-Modified</a> value of a HEAD response differs from that in a selected GET response, the cache <em class="bcp14">MUST</em> consider that selected response to be stale.
[1751]1099      </p>
[2237]1100      <p id="rfc.section.5.p.3">If the <a href="p1-messaging.html#header.content-length" class="smpl">Content-Length</a>, <a href="p4-conditional.html#header.etag" class="smpl">ETag</a> and <a href="p4-conditional.html#header.last-modified" class="smpl">Last-Modified</a> values of a HEAD response (when present) are the same as that in a selected GET response (as per <a href="#caching.negotiated.responses" title="Calculating Secondary Keys with Vary">Section&nbsp;4.3</a>), the cache <em class="bcp14">SHOULD</em> update the remaining header fields in the stored response using the following rules:
[1751]1101      </p>
1102      <ul>
[1860]1103         <li>delete any <a href="#header.warning" class="smpl">Warning</a> header fields in the stored response with warn-code 1xx (see <a href="#header.warning" id="rfc.xref.header.warning.4" title="Warning">Section&nbsp;7.5</a>);
[1751]1104         </li>
1105         <li>retain any <a href="#header.warning" class="smpl">Warning</a> header fields in the stored response with warn-code 2xx; and,
1106         </li>
1107         <li>use other header fields provided in the response to replace all instances of the corresponding header fields in the stored
1108            response.
1109         </li>
1110      </ul>
1111      <h1 id="rfc.section.6"><a href="#rfc.section.6">6.</a>&nbsp;<a id="invalidation.after.updates.or.deletions" href="#invalidation.after.updates.or.deletions">Request Methods that Invalidate</a></h1>
[2180]1112      <p id="rfc.section.6.p.1">Because unsafe request methods (<a href="p2-semantics.html#safe.methods" title="Safe Methods">Section 4.2.1</a> of <a href="#Part2" id="rfc.xref.Part2.6"><cite title="Hypertext Transfer Protocol (HTTP/1.1): Semantics and Content">[Part2]</cite></a>) such as PUT, POST or DELETE have the potential for changing state on the origin server, intervening caches can use them
[1751]1113         to keep their contents up-to-date.
1114      </p>
[1864]1115      <p id="rfc.section.6.p.2">A cache <em class="bcp14">MUST</em> invalidate the effective Request URI (<a href="p1-messaging.html#effective.request.uri" title="Effective Request URI">Section 5.5</a> of <a href="#Part1" id="rfc.xref.Part1.6"><cite title="Hypertext Transfer Protocol (HTTP/1.1): Message Syntax and Routing">[Part1]</cite></a>) as well as the URI(s) in the <a href="p2-semantics.html#header.location" class="smpl">Location</a> and <a href="p2-semantics.html#header.content-location" class="smpl">Content-Location</a> response header fields (if present) when a non-error response to a request with an unsafe method is received.
[1751]1116      </p>
[1864]1117      <p id="rfc.section.6.p.3">However, a cache <em class="bcp14">MUST NOT</em> invalidate a URI from a <a href="p2-semantics.html#header.location" class="smpl">Location</a> or <a href="p2-semantics.html#header.content-location" class="smpl">Content-Location</a> response header field if the host part of that URI differs from the host part in the effective request URI (<a href="p1-messaging.html#effective.request.uri" title="Effective Request URI">Section 5.5</a> of <a href="#Part1" id="rfc.xref.Part1.7"><cite title="Hypertext Transfer Protocol (HTTP/1.1): Message Syntax and Routing">[Part1]</cite></a>). This helps prevent denial of service attacks.
[1751]1118      </p>
[1864]1119      <p id="rfc.section.6.p.4">A cache <em class="bcp14">MUST</em> invalidate the effective request URI (<a href="p1-messaging.html#effective.request.uri" title="Effective Request URI">Section 5.5</a> of <a href="#Part1" id="rfc.xref.Part1.8"><cite title="Hypertext Transfer Protocol (HTTP/1.1): Message Syntax and Routing">[Part1]</cite></a>) when it receives a non-error response to a request with a method whose safety is unknown.
[1751]1120      </p>
1121      <p id="rfc.section.6.p.5">Here, a "non-error response" is one with a <a href="p2-semantics.html#status.2xx" class="smpl">2xx (Successful)</a> or <a href="p2-semantics.html#status.3xx" class="smpl">3xx (Redirection)</a> status code. "Invalidate" means that the cache will either remove all stored responses related to the effective request URI,
[2052]1122         or will mark these as "invalid" and in need of a mandatory validation before they can be sent in response to a subsequent
[1751]1123         request.
1124      </p>
[2234]1125      <p id="rfc.section.6.p.6">Note that this does not guarantee that all appropriate responses are invalidated. For example, a state-changing request might
1126         invalidate responses in the caches it travels through, but relevant responses still might be stored in other caches that it
1127         has not.
[1751]1128      </p>
1129      <h1 id="rfc.section.7"><a href="#rfc.section.7">7.</a>&nbsp;<a id="header.field.definitions" href="#header.field.definitions">Header Field Definitions</a></h1>
1130      <p id="rfc.section.7.p.1">This section defines the syntax and semantics of HTTP/1.1 header fields related to caching.</p>
[52]1131      <div id="rfc.iref.a.2"></div>
[1751]1132      <h2 id="rfc.section.7.1"><a href="#rfc.section.7.1">7.1</a>&nbsp;<a id="header.age" href="#header.age">Age</a></h2>
1133      <p id="rfc.section.7.1.p.1">The "Age" header field conveys the sender's estimate of the amount of time since the response was generated or successfully
1134         validated at the origin server. Age values are calculated as specified in <a href="#age.calculations" title="Calculating Age">Section&nbsp;4.1.3</a>.
[52]1135      </p>
[1805]1136      <div id="rfc.figure.u.6"></div><pre class="inline"><span id="rfc.iref.g.2"></span>  <a href="#header.age" class="smpl">Age</a> = <a href="#delta-seconds" class="smpl">delta-seconds</a>
[2239]1137</pre><p id="rfc.section.7.1.p.3">Age field-values are non-negative integers, representing time in seconds (see <a href="#delta-seconds" title="Delta Seconds">Section&nbsp;1.2.1</a>).
[52]1138      </p>
[1751]1139      <p id="rfc.section.7.1.p.4">The presence of an Age header field in a response implies that a response is not first-hand. However, the converse is not
[912]1140         true, since HTTP/1.0 caches might not implement the Age header field.
[538]1141      </p>
[2239]1142      <div id="rfc.iref.c.5"></div>
[1751]1143      <h2 id="rfc.section.7.2"><a href="#rfc.section.7.2">7.2</a>&nbsp;<a id="header.cache-control" href="#header.cache-control">Cache-Control</a></h2>
1144      <p id="rfc.section.7.2.p.1">The "Cache-Control" header field is used to specify directives for caches along the request/response chain. Such cache directives
[1164]1145         are unidirectional in that the presence of a directive in a request does not imply that the same directive is to be given
1146         in the response.
[52]1147      </p>
[1751]1148      <p id="rfc.section.7.2.p.2">A cache <em class="bcp14">MUST</em> obey the requirements of the Cache-Control directives defined in this section. See <a href="#cache.control.extensions" title="Cache Control Extensions">Section&nbsp;7.2.3</a> for information about how Cache-Control directives defined elsewhere are handled.
[827]1149      </p>
[1751]1150      <div class="note" id="rfc.section.7.2.p.3"> 
[2241]1151         <p> <b>Note:</b> Some HTTP/1.0 caches might not implement Cache-Control.
[540]1152         </p> 
1153      </div>
[1751]1154      <p id="rfc.section.7.2.p.4">A proxy, whether or not it implements a cache, <em class="bcp14">MUST</em> pass cache directives through in forwarded messages, regardless of their significance to that application, since the directives
[1174]1155         might be applicable to all recipients along the request/response chain. It is not possible to target a directive to a specific
1156         cache.
[52]1157      </p>
[1751]1158      <p id="rfc.section.7.2.p.5">Cache directives are identified by a token, to be compared case-insensitively, and have an optional argument, that can use
[1695]1159         both token and quoted-string syntax. For the directives defined below that define arguments, recipients ought to accept both
1160         forms, even if one is documented to be preferred. For any directive not defined by this specification, recipients <em class="bcp14">MUST</em> accept both forms.
1161      </p>
[1805]1162      <div id="rfc.figure.u.7"></div><pre class="inline"><span id="rfc.iref.g.3"></span><span id="rfc.iref.g.4"></span>  <a href="#header.cache-control" class="smpl">Cache-Control</a>   = 1#<a href="#header.cache-control" class="smpl">cache-directive</a>
[52]1163
[1805]1164  <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> ) ]
[2215]1165</pre><p id="rfc.section.7.2.p.7">For the cache directives defined below, no argument is defined (nor allowed) unless stated otherwise.</p>
[1751]1166      <h3 id="rfc.section.7.2.1"><a href="#rfc.section.7.2.1">7.2.1</a>&nbsp;<a id="cache-request-directive" href="#cache-request-directive">Request Cache-Control Directives</a></h3>
[1695]1167      <div id="rfc.iref.m.1"></div>
[2236]1168      <h4 id="rfc.section.7.2.1.1"><a href="#rfc.section.7.2.1.1">7.2.1.1</a>&nbsp;<a id="cache-request-directive.max-age" href="#cache-request-directive.max-age">max-age</a></h4>
1169      <p id="rfc.section.7.2.1.1.p.1">Argument syntax: </p>
[729]1170      <ul class="empty">
[2239]1171         <li> <a href="#delta-seconds" class="smpl">delta-seconds</a> (see <a href="#delta-seconds" title="Delta Seconds">Section&nbsp;1.2.1</a>)
[939]1172         </li>
[729]1173      </ul>
[2236]1174      <p id="rfc.section.7.2.1.1.p.2">The "max-age" request directive indicates that the client is unwilling to accept a response whose age is greater than the
[1779]1175         specified number of seconds. Unless the max-stale request directive is also present, the client is not willing to accept a
1176         stale response.
[52]1177      </p>
[2236]1178      <p id="rfc.section.7.2.1.1.p.3"> <b>Note:</b> This directive uses the token form of the argument syntax; e.g., 'max-age=5', not 'max-age="5"'. Senders <em class="bcp14">SHOULD NOT</em> use the quoted-string form.
[1695]1179      </p>
1180      <div id="rfc.iref.m.2"></div>
[2236]1181      <h4 id="rfc.section.7.2.1.2"><a href="#rfc.section.7.2.1.2">7.2.1.2</a>&nbsp;<a id="cache-request-directive.max-stale" href="#cache-request-directive.max-stale">max-stale</a></h4>
1182      <p id="rfc.section.7.2.1.2.p.1">Argument syntax: </p>
[729]1183      <ul class="empty">
[2239]1184         <li> <a href="#delta-seconds" class="smpl">delta-seconds</a> (see <a href="#delta-seconds" title="Delta Seconds">Section&nbsp;1.2.1</a>)
[729]1185         </li>
1186      </ul>
[2236]1187      <p id="rfc.section.7.2.1.2.p.2">The "max-stale" request directive indicates that the client is willing to accept a response that has exceeded its freshness
[2234]1188         lifetime. If max-stale is assigned a value, then the client is willing to accept a response that has exceeded its freshness
1189         lifetime by no more than the specified number of seconds. If no value is assigned to max-stale, then the client is willing
1190         to accept a stale response of any age.
[52]1191      </p>
[2236]1192      <p id="rfc.section.7.2.1.2.p.3"> <b>Note:</b> This directive uses the token form of the argument syntax; e.g., 'max-stale=10', not 'max-stale="10"'. Senders <em class="bcp14">SHOULD NOT</em> use the quoted-string form.
[1695]1193      </p>
1194      <div id="rfc.iref.m.3"></div>
[2236]1195      <h4 id="rfc.section.7.2.1.3"><a href="#rfc.section.7.2.1.3">7.2.1.3</a>&nbsp;<a id="cache-request-directive.min-fresh" href="#cache-request-directive.min-fresh">min-fresh</a></h4>
1196      <p id="rfc.section.7.2.1.3.p.1">Argument syntax: </p>
[729]1197      <ul class="empty">
[2239]1198         <li> <a href="#delta-seconds" class="smpl">delta-seconds</a> (see <a href="#delta-seconds" title="Delta Seconds">Section&nbsp;1.2.1</a>)
[729]1199         </li>
1200      </ul>
[2236]1201      <p id="rfc.section.7.2.1.3.p.2">The "min-fresh" request directive indicates that the client is willing to accept a response whose freshness lifetime is no
[1779]1202         less than its current age plus the specified time in seconds. That is, the client wants a response that will still be fresh
1203         for at least the specified number of seconds.
[52]1204      </p>
[2236]1205      <p id="rfc.section.7.2.1.3.p.3"> <b>Note:</b> This directive uses the token form of the argument syntax; e.g., 'min-fresh=20', not 'min-fresh="20"'. Senders <em class="bcp14">SHOULD NOT</em> use the quoted-string form.
[1695]1206      </p>
[2236]1207      <div id="rfc.iref.n.1"></div>
1208      <h4 id="rfc.section.7.2.1.4"><a href="#rfc.section.7.2.1.4">7.2.1.4</a>&nbsp;<a id="cache-request-directive.no-cache" href="#cache-request-directive.no-cache">no-cache</a></h4>
1209      <p id="rfc.section.7.2.1.4.p.1">The "no-cache" request directive indicates that a cache <em class="bcp14">MUST NOT</em> use a stored response to satisfy the request without successful validation on the origin server.
1210      </p>
1211      <div id="rfc.iref.n.2"></div>
1212      <h4 id="rfc.section.7.2.1.5"><a href="#rfc.section.7.2.1.5">7.2.1.5</a>&nbsp;<a id="cache-request-directive.no-store" href="#cache-request-directive.no-store">no-store</a></h4>
1213      <p id="rfc.section.7.2.1.5.p.1">The "no-store" request directive indicates that a cache <em class="bcp14">MUST NOT</em> store any part of either this request or any response to it. This directive applies to both private and shared caches. "<em class="bcp14">MUST NOT</em> store" in this context means that the cache <em class="bcp14">MUST NOT</em> intentionally store the information in non-volatile storage, and <em class="bcp14">MUST</em> make a best-effort attempt to remove the information from volatile storage as promptly as possible after forwarding it.
1214      </p>
1215      <p id="rfc.section.7.2.1.5.p.2">This directive is NOT a reliable or sufficient mechanism for ensuring privacy. In particular, malicious or compromised caches
1216         might not recognize or obey this directive, and communications networks might be vulnerable to eavesdropping.
1217      </p>
1218      <p id="rfc.section.7.2.1.5.p.3">Note that if a request containing this directive is satisfied from a cache, the no-store request directive does not apply
1219         to the already stored response.
1220      </p>
[1695]1221      <div id="rfc.iref.n.3"></div>
[1751]1222      <h4 id="rfc.section.7.2.1.6"><a href="#rfc.section.7.2.1.6">7.2.1.6</a>&nbsp;<a id="cache-request-directive.no-transform" href="#cache-request-directive.no-transform">no-transform</a></h4>
[2044]1223      <p id="rfc.section.7.2.1.6.p.1">The "no-transform" request directive indicates that an intermediary (whether or not it implements a cache) <em class="bcp14">MUST NOT</em> transform the payload, as defined in <a href="p1-messaging.html#message.transformations" title="Transformations">Section 5.7.2</a> of <a href="#Part1" id="rfc.xref.Part1.9"><cite title="Hypertext Transfer Protocol (HTTP/1.1): Message Syntax and Routing">[Part1]</cite></a>.
[1695]1224      </p>
1225      <div id="rfc.iref.o.1"></div>
[1751]1226      <h4 id="rfc.section.7.2.1.7"><a href="#rfc.section.7.2.1.7">7.2.1.7</a>&nbsp;<a id="cache-request-directive.only-if-cached" href="#cache-request-directive.only-if-cached">only-if-cached</a></h4>
[1779]1227      <p id="rfc.section.7.2.1.7.p.1">The "only-if-cached" request directive indicates that the client only wishes to obtain a stored response. If it receives this
[1775]1228         directive, a cache <em class="bcp14">SHOULD</em> either respond using a stored response that is consistent with the other constraints of the request, or respond with a <a href="p2-semantics.html#status.504" class="smpl">504 (Gateway
[1751]1229            Timeout)</a> status code. If a group of caches is being operated as a unified system with good internal connectivity, a member cache <em class="bcp14">MAY</em> forward such a request within that group of caches.
[1695]1230      </p>
[1751]1231      <h3 id="rfc.section.7.2.2"><a href="#rfc.section.7.2.2">7.2.2</a>&nbsp;<a id="cache-response-directive" href="#cache-response-directive">Response Cache-Control Directives</a></h3>
[2236]1232      <div id="rfc.iref.m.4"></div>
1233      <h4 id="rfc.section.7.2.2.1"><a href="#rfc.section.7.2.2.1">7.2.2.1</a>&nbsp;<a id="cache-response-directive.must-revalidate" href="#cache-response-directive.must-revalidate">must-revalidate</a></h4>
1234      <p id="rfc.section.7.2.2.1.p.1">The "must-revalidate" response directive indicates that once it has become stale, a cache <em class="bcp14">MUST NOT</em> use the response to satisfy subsequent requests without successful validation on the origin server.
[52]1235      </p>
[2236]1236      <p id="rfc.section.7.2.2.1.p.2">The must-revalidate directive is necessary to support reliable operation for certain protocol features. In all circumstances
1237         a cache <em class="bcp14">MUST</em> obey the must-revalidate directive; in particular, if a cache cannot reach the origin server for any reason, it <em class="bcp14">MUST</em> generate a <a href="p2-semantics.html#status.504" class="smpl">504 (Gateway Timeout)</a> response.
[52]1238      </p>
[2236]1239      <p id="rfc.section.7.2.2.1.p.3">The must-revalidate directive ought to be used by servers if and only if failure to validate a request on the representation
1240         could result in incorrect operation, such as a silently unexecuted financial transaction.
[52]1241      </p>
[1695]1242      <div id="rfc.iref.n.4"></div>
[2236]1243      <h4 id="rfc.section.7.2.2.2"><a href="#rfc.section.7.2.2.2">7.2.2.2</a>&nbsp;<a id="cache-response-directive.no-cache" href="#cache-response-directive.no-cache">no-cache</a></h4>
1244      <p id="rfc.section.7.2.2.2.p.1">Argument syntax: </p>
[729]1245      <ul class="empty">
[1805]1246         <li>#<a href="#imported.abnf" class="smpl">field-name</a> 
[729]1247         </li>
1248      </ul>
[2236]1249      <p id="rfc.section.7.2.2.2.p.2">The "no-cache" response directive indicates that the response <em class="bcp14">MUST NOT</em> be used to satisfy a subsequent request without successful validation on the origin server. This allows an origin server to
[2052]1250         prevent a cache from using it to satisfy a request without contacting it, even by caches that have been configured to send
[1695]1251         stale responses.
[52]1252      </p>
[2236]1253      <p id="rfc.section.7.2.2.2.p.3">If the no-cache response directive specifies one or more field-names, then a cache <em class="bcp14">MAY</em> use the response to satisfy a subsequent request, subject to any other restrictions on caching. However, any header fields
[1695]1254         in the response that have the field-name(s) listed <em class="bcp14">MUST NOT</em> be sent in the response to a subsequent request without successful revalidation with the origin server. This allows an origin
1255         server to prevent the re-use of certain header fields in a response, while still allowing caching of the rest of the response.
1256      </p>
[2236]1257      <p id="rfc.section.7.2.2.2.p.4">The field-names given are not limited to the set of header fields defined by this specification. Field names are case-insensitive.</p>
1258      <p id="rfc.section.7.2.2.2.p.5"> <b>Note:</b> Although it has been back-ported to many implementations, some HTTP/1.0 caches will not recognize or obey this directive.
[2247]1259         Also, no-cache response directives with field-names are often handled by caches as if an unqualified no-cache directive was
1260         received; i.e., the special handling for the qualified form is not widely implemented.
[1695]1261      </p>
[2236]1262      <p id="rfc.section.7.2.2.2.p.6"> <b>Note:</b> This directive uses the quoted-string form of the argument syntax. Senders <em class="bcp14">SHOULD NOT</em> use the token form (even if quoting appears not to be needed for single-entry lists).
[1695]1263      </p>
1264      <div id="rfc.iref.n.5"></div>
[2236]1265      <h4 id="rfc.section.7.2.2.3"><a href="#rfc.section.7.2.2.3">7.2.2.3</a>&nbsp;<a id="cache-response-directive.no-store" href="#cache-response-directive.no-store">no-store</a></h4>
1266      <p id="rfc.section.7.2.2.3.p.1">The "no-store" response directive indicates that a cache <em class="bcp14">MUST NOT</em> store any part of either the immediate request or response. This directive applies to both private and shared caches. "<em class="bcp14">MUST NOT</em> store" in this context means that the cache <em class="bcp14">MUST NOT</em> intentionally store the information in non-volatile storage, and <em class="bcp14">MUST</em> make a best-effort attempt to remove the information from volatile storage as promptly as possible after forwarding it.
[1695]1267      </p>
[2236]1268      <p id="rfc.section.7.2.2.3.p.2">This directive is NOT a reliable or sufficient mechanism for ensuring privacy. In particular, malicious or compromised caches
[1695]1269         might not recognize or obey this directive, and communications networks might be vulnerable to eavesdropping.
1270      </p>
[2236]1271      <div id="rfc.iref.n.6"></div>
1272      <h4 id="rfc.section.7.2.2.4"><a href="#rfc.section.7.2.2.4">7.2.2.4</a>&nbsp;<a id="cache-response-directive.no-transform" href="#cache-response-directive.no-transform">no-transform</a></h4>
1273      <p id="rfc.section.7.2.2.4.p.1">The "no-transform" response directive indicates that an intermediary (regardless of whether it implements a cache) <em class="bcp14">MUST NOT</em> transform the payload, as defined in <a href="p1-messaging.html#message.transformations" title="Transformations">Section 5.7.2</a> of <a href="#Part1" id="rfc.xref.Part1.10"><cite title="Hypertext Transfer Protocol (HTTP/1.1): Message Syntax and Routing">[Part1]</cite></a>.
[1695]1274      </p>
[2236]1275      <div id="rfc.iref.p.2"></div>
1276      <h4 id="rfc.section.7.2.2.5"><a href="#rfc.section.7.2.2.5">7.2.2.5</a>&nbsp;<a id="cache-response-directive.public" href="#cache-response-directive.public">public</a></h4>
1277      <p id="rfc.section.7.2.2.5.p.1">The "public" response directive indicates that any cache <em class="bcp14">MAY</em> store the response, even if the response would normally be non-cacheable or cacheable only within a non-shared cache. (See <a href="#caching.authenticated.responses" title="Storing Responses to Authenticated Requests">Section&nbsp;3.2</a> for additional details related to the use of public in response to a request containing <a href="p7-auth.html#header.authorization" class="smpl">Authorization</a>, and <a href="#response.cacheability" title="Storing Responses in Caches">Section&nbsp;3</a> for details of how public affects responses that would normally not be stored, due to their status codes not being defined
1278         as cacheable.)
[1695]1279      </p>
[2236]1280      <div id="rfc.iref.p.3"></div>
1281      <h4 id="rfc.section.7.2.2.6"><a href="#rfc.section.7.2.2.6">7.2.2.6</a>&nbsp;<a id="cache-response-directive.private" href="#cache-response-directive.private">private</a></h4>
1282      <p id="rfc.section.7.2.2.6.p.1">Argument syntax: </p>
1283      <ul class="empty">
1284         <li>#<a href="#imported.abnf" class="smpl">field-name</a> 
1285         </li>
1286      </ul>
1287      <p id="rfc.section.7.2.2.6.p.2">The "private" response directive indicates that the response message is intended for a single user and <em class="bcp14">MUST NOT</em> be stored by a shared cache. A private cache <em class="bcp14">MAY</em> store the response and reuse it for later requests, even if the response would normally be non-cacheable.
[1695]1288      </p>
[2236]1289      <p id="rfc.section.7.2.2.6.p.3">If the private response directive specifies one or more field-names, this requirement is limited to the field-values associated
1290         with the listed response header fields. That is, a shared cache <em class="bcp14">MUST NOT</em> store the specified field-names(s), whereas it <em class="bcp14">MAY</em> store the remainder of the response message.
1291      </p>
1292      <p id="rfc.section.7.2.2.6.p.4">The field-names given are not limited to the set of header fields defined by this specification. Field names are case-insensitive.</p>
1293      <p id="rfc.section.7.2.2.6.p.5"> <b>Note:</b> This usage of the word "private" only controls where the response can be stored; it cannot ensure the privacy of the message
[2247]1294         content. Also, private response directives with field-names are often handled by caches as if an unqualified private directive
1295         was received; i.e., the special handling for the qualified form is not widely implemented.
[2236]1296      </p>
1297      <p id="rfc.section.7.2.2.6.p.6"> <b>Note:</b> This directive uses the quoted-string form of the argument syntax. Senders <em class="bcp14">SHOULD NOT</em> use the token form (even if quoting appears not to be needed for single-entry lists).
1298      </p>
[1695]1299      <div id="rfc.iref.p.4"></div>
[2236]1300      <h4 id="rfc.section.7.2.2.7"><a href="#rfc.section.7.2.2.7">7.2.2.7</a>&nbsp;<a id="cache-response-directive.proxy-revalidate" href="#cache-response-directive.proxy-revalidate">proxy-revalidate</a></h4>
1301      <p id="rfc.section.7.2.2.7.p.1">The "proxy-revalidate" response directive has the same meaning as the must-revalidate response directive, except that it does
[1695]1302         not apply to private caches.
1303      </p>
1304      <div id="rfc.iref.m.5"></div>
[2236]1305      <h4 id="rfc.section.7.2.2.8"><a href="#rfc.section.7.2.2.8">7.2.2.8</a>&nbsp;<a id="cache-response-directive.max-age" href="#cache-response-directive.max-age">max-age</a></h4>
1306      <p id="rfc.section.7.2.2.8.p.1">Argument syntax: </p>
[729]1307      <ul class="empty">
[2239]1308         <li> <a href="#delta-seconds" class="smpl">delta-seconds</a> (see <a href="#delta-seconds" title="Delta Seconds">Section&nbsp;1.2.1</a>)
[729]1309         </li>
1310      </ul>
[2236]1311      <p id="rfc.section.7.2.2.8.p.2">The "max-age" response directive indicates that the response is to be considered stale after its age is greater than the specified
[1695]1312         number of seconds.
[52]1313      </p>
[2236]1314      <p id="rfc.section.7.2.2.8.p.3"> <b>Note:</b> This directive uses the token form of the argument syntax; e.g., 'max-age=5', not 'max-age="5"'. Senders <em class="bcp14">SHOULD NOT</em> use the quoted-string form.
[1695]1315      </p>
1316      <div id="rfc.iref.s.4"></div>
[2236]1317      <h4 id="rfc.section.7.2.2.9"><a href="#rfc.section.7.2.2.9">7.2.2.9</a>&nbsp;<a id="cache-response-directive.s-maxage" href="#cache-response-directive.s-maxage">s-maxage</a></h4>
1318      <p id="rfc.section.7.2.2.9.p.1">Argument syntax: </p>
[729]1319      <ul class="empty">
[2239]1320         <li> <a href="#delta-seconds" class="smpl">delta-seconds</a> (see <a href="#delta-seconds" title="Delta Seconds">Section&nbsp;1.2.1</a>)
[729]1321         </li>
1322      </ul>
[2236]1323      <p id="rfc.section.7.2.2.9.p.2">The "s-maxage" response directive indicates that, in shared caches, the maximum age specified by this directive overrides
[1779]1324         the maximum age specified by either the max-age directive or the <a href="#header.expires" class="smpl">Expires</a> header field. The s-maxage directive also implies the semantics of the proxy-revalidate response directive.
[52]1325      </p>
[2236]1326      <p id="rfc.section.7.2.2.9.p.3"> <b>Note:</b> This directive uses the token form of the argument syntax; e.g., 's-maxage=10', not 's-maxage="10"'. Senders <em class="bcp14">SHOULD NOT</em> use the quoted-string form.
[1695]1327      </p>
[1751]1328      <h3 id="rfc.section.7.2.3"><a href="#rfc.section.7.2.3">7.2.3</a>&nbsp;<a id="cache.control.extensions" href="#cache.control.extensions">Cache Control Extensions</a></h3>
1329      <p id="rfc.section.7.2.3.p.1">The Cache-Control header field can be extended through the use of one or more cache-extension tokens, each with an optional
[2234]1330         value.
1331      </p>
1332      <p id="rfc.section.7.2.3.p.2">Informational extensions (those that do not require a change in cache behavior) can be added without changing the semantics
[538]1333         of other directives. Behavioral extensions are designed to work by acting as modifiers to the existing base of cache directives.
[2234]1334      </p>
1335      <p id="rfc.section.7.2.3.p.3">Both the new directive and the standard directive are supplied, such that applications that do not understand the new directive
[538]1336         will default to the behavior specified by the standard directive, and those that understand the new directive will recognize
1337         it as modifying the requirements associated with the standard directive. In this way, extensions to the cache-control directives
1338         can be made without requiring changes to the base protocol.
[52]1339      </p>
[2234]1340      <p id="rfc.section.7.2.3.p.4">This extension mechanism depends on an HTTP cache obeying all of the cache-control directives defined for its native HTTP-version,
[52]1341         obeying certain extensions, and ignoring all directives that it does not understand.
1342      </p>
[2234]1343      <p id="rfc.section.7.2.3.p.5">For example, consider a hypothetical new response directive called "community" that acts as a modifier to the private directive.
[1112]1344         We define this new directive to mean that, in addition to any private cache, any cache that is shared only by members of the
[1707]1345         community named within its value is allowed to cache the response. An origin server wishing to allow the UCI community to
1346         use an otherwise private response in their shared cache(s) could do so by including
[52]1347      </p>
[1805]1348      <div id="rfc.figure.u.8"></div><pre class="text">  Cache-Control: private, community="UCI"
[2234]1349</pre><p id="rfc.section.7.2.3.p.7">A cache seeing this header field will act correctly even if the cache does not understand the community cache-extension, since
[52]1350         it will also see and understand the private directive and thus default to the safe behavior.
1351      </p>
[2234]1352      <p id="rfc.section.7.2.3.p.8">A cache <em class="bcp14">MUST</em> ignore unrecognized cache directives; it is assumed that any cache directive likely to be unrecognized by an HTTP/1.1 cache
[1112]1353         will be combined with standard directives (or the response's default cacheability) such that the cache behavior will remain
1354         minimally correct even if the cache does not understand the extension(s).
[52]1355      </p>
[2234]1356      <p id="rfc.section.7.2.3.p.9">New extension directives ought to consider defining:</p>
1357      <p id="rfc.section.7.2.3.p.10"> </p>
[1701]1358      <ul>
1359         <li>What it means for a directive to be specified multiple times,</li>
1360         <li>When the directive does not take an argument, what it means when an argument is present,</li>
[2234]1361         <li>When the directive requires an argument, what it means when it is missing,</li>
1362         <li>Whether the directive is specific to requests, responses, or able to be used in either.</li>
[1701]1363      </ul>
[52]1364      <div id="rfc.iref.e.2"></div>
[1751]1365      <h2 id="rfc.section.7.3"><a href="#rfc.section.7.3">7.3</a>&nbsp;<a id="header.expires" href="#header.expires">Expires</a></h2>
[2234]1366      <p id="rfc.section.7.3.p.1">The "Expires" header field gives the date/time after which the response is considered stale. See <a href="#expiration.model" title="Freshness">Section&nbsp;4.1</a> for further discussion of the freshness model.
[52]1367      </p>
[1751]1368      <p id="rfc.section.7.3.p.2">The presence of an Expires field does not imply that the original resource will change or cease to exist at, before, or after
[52]1369         that time.
1370      </p>
[2180]1371      <p id="rfc.section.7.3.p.3">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="#Part2" id="rfc.xref.Part2.7"><cite title="Hypertext Transfer Protocol (HTTP/1.1): Semantics and Content">[Part2]</cite></a>.
[52]1372      </p>
[1805]1373      <div id="rfc.figure.u.9"></div><pre class="inline"><span id="rfc.iref.g.5"></span>  <a href="#header.expires" class="smpl">Expires</a> = <a href="#imported.abnf" class="smpl">HTTP-date</a>
[2232]1374</pre><div id="rfc.figure.u.10"></div>
1375      <p>For example</p><pre class="text">  Expires: Thu, 01 Dec 1994 16:00:00 GMT
[2082]1376</pre><p id="rfc.section.7.3.p.6">A cache recipient <em class="bcp14">MUST</em> interpret invalid date formats, especially the value "0", as representing a time in the past (i.e., "already expired").
[1400]1377      </p>
[2236]1378      <p id="rfc.section.7.3.p.7">If a response includes a <a href="#header.cache-control" class="smpl">Cache-Control</a> field with the max-age directive (<a href="#cache-response-directive.max-age" title="max-age">Section&nbsp;7.2.2.8</a>), a recipient <em class="bcp14">MUST</em> ignore the Expires field. Likewise, if a response includes the s-maxage directive (<a href="#cache-response-directive.s-maxage" title="s-maxage">Section&nbsp;7.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 for recipients that have not yet implemented
[2082]1379         the Cache-Control field.
1380      </p>
1381      <p id="rfc.section.7.3.p.8">An origin server without a clock <em class="bcp14">MUST NOT</em> generate an Expires field unless its value represents a fixed time in the past (always expired) or its value has been associated
1382         with the resource by a system or user with a reliable clock.
1383      </p>
1384      <p id="rfc.section.7.3.p.9">Historically, HTTP required the Expires field-value to be no more than a year in the future. While longer freshness lifetimes
[1400]1385         are no longer prohibited, extremely large values have been demonstrated to cause problems (e.g., clock overflows due to use
[2030]1386         of 32-bit integers for time values), and many caches will evict a response far sooner than that.
[52]1387      </p>
[1112]1388      <div id="rfc.iref.p.5"></div>
[1751]1389      <h2 id="rfc.section.7.4"><a href="#rfc.section.7.4">7.4</a>&nbsp;<a id="header.pragma" href="#header.pragma">Pragma</a></h2>
1390      <p id="rfc.section.7.4.p.1">The "Pragma" header field allows backwards compatibility with HTTP/1.0 caches, so that clients can specify a "no-cache" request
[1737]1391         that they will understand (as <a href="#header.cache-control" class="smpl">Cache-Control</a> was not defined until HTTP/1.1). When the Cache-Control header field is also present and understood in a request, Pragma is
1392         ignored.
[52]1393      </p>
[1751]1394      <p id="rfc.section.7.4.p.2">In HTTP/1.0, Pragma was defined as an extensible field for implementation-specified directives for recipients. This specification
[1284]1395         deprecates such extensions to improve interoperability.
1396      </p>
[1805]1397      <div id="rfc.figure.u.11"></div><pre class="inline"><span id="rfc.iref.g.6"></span><span id="rfc.iref.g.7"></span><span id="rfc.iref.g.8"></span>  <a href="#header.pragma" class="smpl">Pragma</a>           = 1#<a href="#header.pragma" class="smpl">pragma-directive</a>
[1231]1398  <a href="#header.pragma" class="smpl">pragma-directive</a> = "no-cache" / <a href="#header.pragma" class="smpl">extension-pragma</a>
[1805]1399  <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> ) ]
[2247]1400</pre><p id="rfc.section.7.4.p.4">When the <a href="#header.cache-control" class="smpl">Cache-Control</a> header field is not present in a request, caches <em class="bcp14">MUST</em> consider the no-cache request pragma-directive as having the same effect as if "Cache-Control: no-cache" were present (see <a href="#cache-request-directive" title="Request Cache-Control Directives">Section&nbsp;7.2.1</a>).
[52]1401      </p>
[1751]1402      <p id="rfc.section.7.4.p.5">When sending a no-cache request, a client ought to include both the pragma and cache-control directives, unless Cache-Control:
[1737]1403         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:
[1284]1404      </p>
[2232]1405      <div id="rfc.figure.u.12"></div><pre class="text">GET / HTTP/1.1
[1284]1406Host: www.example.com
1407Cache-Control: max-age=30
1408Pragma: no-cache
[1287]1409
[2232]1410</pre><p id="rfc.section.7.4.p.7">will constrain HTTP/1.1 caches to serve a response no older than 30 seconds, while precluding implementations that do not
[1737]1411         understand <a href="#header.cache-control" class="smpl">Cache-Control</a> from serving a cached response.
[1284]1412      </p>
[1751]1413      <div class="note" id="rfc.section.7.4.p.8"> 
[1287]1414         <p> <b>Note:</b> Because the meaning of "Pragma: no-cache" in responses is not specified, it does not provide a reliable replacement for "Cache-Control:
1415            no-cache" in them.
[540]1416         </p> 
1417      </div>
[1860]1418      <div id="rfc.iref.w.1"></div>
1419      <h2 id="rfc.section.7.5"><a href="#rfc.section.7.5">7.5</a>&nbsp;<a id="header.warning" href="#header.warning">Warning</a></h2>
1420      <p id="rfc.section.7.5.p.1">The "Warning" header field is used to carry additional information about the status or transformation of a message that might
[1164]1421         not be reflected in the message. This information is typically used to warn about possible incorrectness introduced by caching
1422         operations or transformations applied to the payload of the message.
[52]1423      </p>
[1860]1424      <p id="rfc.section.7.5.p.2">Warnings can be used for other purposes, both cache-related and otherwise. The use of a warning, rather than an error status
[732]1425         code, distinguishes these responses from true failures.
[538]1426      </p>
[1860]1427      <p id="rfc.section.7.5.p.3">Warning header fields can in general be applied to any message, however some warn-codes are specific to caches and can only
[994]1428         be applied to response messages.
[538]1429      </p>
[1860]1430      <div id="rfc.figure.u.13"></div><pre class="inline"><span id="rfc.iref.g.9"></span><span id="rfc.iref.g.10"></span><span id="rfc.iref.g.11"></span><span id="rfc.iref.g.12"></span><span id="rfc.iref.g.13"></span><span id="rfc.iref.g.14"></span>  <a href="#header.warning" class="smpl">Warning</a>       = 1#<a href="#header.warning" class="smpl">warning-value</a>
[135]1431 
[1805]1432  <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>
1433                                        [<a href="#imported.abnf" class="smpl">SP</a> <a href="#header.warning" class="smpl">warn-date</a>]
[135]1434 
[1805]1435  <a href="#header.warning" class="smpl">warn-code</a>  = 3<a href="#imported.abnf" class="smpl">DIGIT</a>
1436  <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>
[135]1437                  ; the name or pseudonym of the server adding
[994]1438                  ; the Warning header field, for use in debugging
[1805]1439  <a href="#header.warning" class="smpl">warn-text</a>  = <a href="#imported.abnf" class="smpl">quoted-string</a>
1440  <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>
[1860]1441</pre><p id="rfc.section.7.5.p.5">Multiple warnings can be attached to a response (either by the origin server or by a cache), including multiple warnings with
[669]1442         the same code number, only differing in warn-text.
[52]1443      </p>
[1860]1444      <p id="rfc.section.7.5.p.6">When this occurs, the user agent <em class="bcp14">SHOULD</em> inform the user of as many of them as possible, in the order that they appear in the response.
[52]1445      </p>
[1860]1446      <p id="rfc.section.7.5.p.7">Systems that generate multiple Warning header fields are encouraged to order them with this user agent behavior in mind. New
[1772]1447         Warning header fields are added after any existing Warning header fields.
[52]1448      </p>
[1860]1449      <p id="rfc.section.7.5.p.8">Warnings are assigned three digit warn-codes. The first digit indicates whether the Warning is required to be deleted from
[538]1450         a stored response after validation:
[52]1451      </p>
[538]1452      <ul>
[1112]1453         <li>1xx Warnings describe the freshness or validation status of the response, and so <em class="bcp14">MUST</em> be deleted by a cache after validation. They can only be generated by a cache when validating a cached entry, and <em class="bcp14">MUST NOT</em> be generated in any other situation.
[538]1454         </li>
[868]1455         <li>2xx Warnings describe some aspect of the representation that is not rectified by a validation (for example, a lossy compression
[2052]1456            of the representation) and <em class="bcp14">MUST NOT</em> be deleted by a cache after validation, unless a full response is sent, in which case they <em class="bcp14">MUST</em> be.
[538]1457         </li>
1458      </ul>
[1860]1459      <p id="rfc.section.7.5.p.9">If an implementation sends a message with one or more Warning header fields to a receiver whose version is HTTP/1.0 or lower,
[1740]1460         then the sender <em class="bcp14">MUST</em> include in each warning-value a warn-date that matches the <a href="p2-semantics.html#header.date" class="smpl">Date</a> header field in the message.
[538]1461      </p>
[1860]1462      <p id="rfc.section.7.5.p.10">If a system receives a message with a warning-value that includes a warn-date, and that warn-date is different from the <a href="p2-semantics.html#header.date" class="smpl">Date</a> value in the response, then that warning-value <em class="bcp14">MUST</em> be deleted from the message before storing, forwarding, or using it. (preventing the consequences of naive caching of Warning
[994]1463         header fields.) If all of the warning-values are deleted for this reason, the Warning header field <em class="bcp14">MUST</em> be deleted as well.
[538]1464      </p>
[1860]1465      <p id="rfc.section.7.5.p.11">The following warn-codes are defined by this specification, each with a recommended warn-text in English, and a description
[538]1466         of its meaning.
1467      </p>
[2239]1468      <div id="rfc.iref.50"></div>
[1860]1469      <h3 id="rfc.section.7.5.1"><a href="#rfc.section.7.5.1">7.5.1</a>&nbsp;<a id="warn.110" href="#warn.110">110 Response is Stale</a></h3>
[2073]1470      <p id="rfc.section.7.5.1.p.1">A cache <em class="bcp14">SHOULD</em> generate this whenever the sent response is stale.
[1485]1471      </p>
[2239]1472      <div id="rfc.iref.50"></div>
[1860]1473      <h3 id="rfc.section.7.5.2"><a href="#rfc.section.7.5.2">7.5.2</a>&nbsp;<a id="warn.111" href="#warn.111">111 Revalidation Failed</a></h3>
[2073]1474      <p id="rfc.section.7.5.2.p.1">A cache <em class="bcp14">SHOULD</em> generate this when sending a stale response because an attempt to validate the response failed, due to an inability to reach
[1487]1475         the server.
1476      </p>
[2239]1477      <div id="rfc.iref.50"></div>
[1860]1478      <h3 id="rfc.section.7.5.3"><a href="#rfc.section.7.5.3">7.5.3</a>&nbsp;<a id="warn.112" href="#warn.112">112 Disconnected Operation</a></h3>
[2073]1479      <p id="rfc.section.7.5.3.p.1">A cache <em class="bcp14">SHOULD</em> generate this if it is intentionally disconnected from the rest of the network for a period of time.
[1487]1480      </p>
[2239]1481      <div id="rfc.iref.50"></div>
[1860]1482      <h3 id="rfc.section.7.5.4"><a href="#rfc.section.7.5.4">7.5.4</a>&nbsp;<a id="warn.113" href="#warn.113">113 Heuristic Expiration</a></h3>
[2073]1483      <p id="rfc.section.7.5.4.p.1">A cache <em class="bcp14">SHOULD</em> generate this if it heuristically chose a freshness lifetime greater than 24 hours and the response's age is greater than
1484         24 hours.
[1487]1485      </p>
[2239]1486      <div id="rfc.iref.50"></div>
[1860]1487      <h3 id="rfc.section.7.5.5"><a href="#rfc.section.7.5.5">7.5.5</a>&nbsp;<a id="warn.199" href="#warn.199">199 Miscellaneous Warning</a></h3>
1488      <p id="rfc.section.7.5.5.p.1">The warning text can include arbitrary information to be presented to a human user, or logged. A system receiving this warning <em class="bcp14">MUST NOT</em> take any automated action, besides presenting the warning to the user.
[1487]1489      </p>
[2239]1490      <div id="rfc.iref.50"></div>
[1860]1491      <h3 id="rfc.section.7.5.6"><a href="#rfc.section.7.5.6">7.5.6</a>&nbsp;<a id="warn.214" href="#warn.214">214 Transformation Applied</a></h3>
1492      <p id="rfc.section.7.5.6.p.1"> <em class="bcp14">MUST</em> be added by a proxy if it applies any transformation to the representation, such as changing the content-coding, media-type,
[1487]1493         or modifying the representation data, unless this Warning code already appears in the response.
1494      </p>
[2239]1495      <div id="rfc.iref.50"></div>
[1860]1496      <h3 id="rfc.section.7.5.7"><a href="#rfc.section.7.5.7">7.5.7</a>&nbsp;<a id="warn.299" href="#warn.299">299 Miscellaneous Persistent Warning</a></h3>
1497      <p id="rfc.section.7.5.7.p.1">The warning text can include arbitrary information to be presented to a human user, or logged. A system receiving this warning <em class="bcp14">MUST NOT</em> take any automated action.
[1487]1498      </p>
[1860]1499      <h3 id="rfc.section.7.5.8"><a href="#rfc.section.7.5.8">7.5.8</a>&nbsp;<a id="warn.code.extensions" href="#warn.code.extensions">Warn Code Extensions</a></h3>
[2244]1500      <p id="rfc.section.7.5.8.p.1">Extension warn codes can be defined; see <a href="#warn.code.registry.procedure" title="Procedure">Section&nbsp;9.2.1</a> for details.
[1487]1501      </p>
[1751]1502      <h1 id="rfc.section.8"><a href="#rfc.section.8">8.</a>&nbsp;<a id="history.lists" href="#history.lists">History Lists</a></h1>
1503      <p id="rfc.section.8.p.1">User agents often have history mechanisms, such as "Back" buttons and history lists, that can be used to redisplay a representation
[538]1504         retrieved earlier in a session.
[52]1505      </p>
[2234]1506      <p id="rfc.section.8.p.2">The freshness model (<a href="#expiration.model" title="Freshness">Section&nbsp;4.1</a>) does not necessarily apply to history mechanisms. I.e., a history mechanism can display a previous representation even if
[766]1507         it has expired.
[52]1508      </p>
[1751]1509      <p id="rfc.section.8.p.3">This does not prohibit the history mechanism from telling the user that a view might be stale, or from honoring cache directives
[766]1510         (e.g., Cache-Control: no-store).
[203]1511      </p>
[2243]1512      <h1 id="rfc.section.9"><a href="#rfc.section.9">9.</a>&nbsp;<a id="iana.considerations" href="#iana.considerations">IANA Considerations</a></h1>
1513      <h2 id="rfc.section.9.1"><a href="#rfc.section.9.1">9.1</a>&nbsp;<a id="cache.directive.registry" href="#cache.directive.registry">Cache Directive Registry</a></h2>
1514      <p id="rfc.section.9.1.p.1">The HTTP Cache Directive Registry defines the name space for the cache directives. It will be created and maintained at &lt;<a href="http://www.iana.org/assignments/http-cache-directives">http://www.iana.org/assignments/http-cache-directives</a>&gt;.
[538]1515      </p>
[2243]1516      <h3 id="rfc.section.9.1.1"><a href="#rfc.section.9.1.1">9.1.1</a>&nbsp;<a id="cache.directive.registry.procedure" href="#cache.directive.registry.procedure">Procedure</a></h3>
[2244]1517      <p id="rfc.section.9.1.1.p.1">A registration <em class="bcp14">MUST</em> include the following fields:
[817]1518      </p>
[2243]1519      <ul>
1520         <li>Cache Directive Name</li>
1521         <li>Pointer to specification text</li>
1522      </ul>
[2244]1523      <p id="rfc.section.9.1.1.p.2">Values to be added to this name space require IETF Review (see <a href="#RFC5226" id="rfc.xref.RFC5226.1"><cite title="Guidelines for Writing an IANA Considerations Section in RFCs">[RFC5226]</cite></a>, <a href="http://tools.ietf.org/html/rfc5226#section-4.1">Section 4.1</a>).
[2243]1524      </p>
1525      <h3 id="rfc.section.9.1.2"><a href="#rfc.section.9.1.2">9.1.2</a>&nbsp;<a id="cache.directive.registration" href="#cache.directive.registration">Registrations</a></h3>
[2244]1526      <p id="rfc.section.9.1.2.p.1">The HTTP Cache Directive Registry shall be populated with the registrations below:</p>
[290]1527      <div id="rfc.table.1">
[817]1528         <div id="iana.cache.directive.registration.table"></div>
1529         <table class="tt full left" cellpadding="3" cellspacing="0">
1530            <thead>
1531               <tr>
1532                  <th>Cache Directive</th>
1533                  <th>Reference</th>
1534               </tr>
1535            </thead>
1536            <tbody>
1537               <tr>
1538                  <td class="left">max-age</td>
[2236]1539                  <td class="left"> <a href="#cache-request-directive.max-age" title="max-age">Section&nbsp;7.2.1.1</a>, <a href="#cache-response-directive.max-age" title="max-age">Section&nbsp;7.2.2.8</a> 
[817]1540                  </td>
1541               </tr>
1542               <tr>
1543                  <td class="left">max-stale</td>
[2236]1544                  <td class="left"> <a href="#cache-request-directive.max-stale" title="max-stale">Section&nbsp;7.2.1.2</a> 
[817]1545                  </td>
1546               </tr>
1547               <tr>
1548                  <td class="left">min-fresh</td>
[2236]1549                  <td class="left"> <a href="#cache-request-directive.min-fresh" title="min-fresh">Section&nbsp;7.2.1.3</a> 
[817]1550                  </td>
1551               </tr>
1552               <tr>
1553                  <td class="left">must-revalidate</td>
[2236]1554                  <td class="left"> <a href="#cache-response-directive.must-revalidate" title="must-revalidate">Section&nbsp;7.2.2.1</a> 
[817]1555                  </td>
1556               </tr>
1557               <tr>
1558                  <td class="left">no-cache</td>
[2236]1559                  <td class="left"> <a href="#cache-request-directive.no-cache" title="no-cache">Section&nbsp;7.2.1.4</a>, <a href="#cache-response-directive.no-cache" title="no-cache">Section&nbsp;7.2.2.2</a> 
[817]1560                  </td>
1561               </tr>
1562               <tr>
1563                  <td class="left">no-store</td>
[2236]1564                  <td class="left"> <a href="#cache-request-directive.no-store" title="no-store">Section&nbsp;7.2.1.5</a>, <a href="#cache-response-directive.no-store" title="no-store">Section&nbsp;7.2.2.3</a> 
[817]1565                  </td>
1566               </tr>
1567               <tr>
1568                  <td class="left">no-transform</td>
[2236]1569                  <td class="left"> <a href="#cache-request-directive.no-transform" title="no-transform">Section&nbsp;7.2.1.6</a>, <a href="#cache-response-directive.no-transform" title="no-transform">Section&nbsp;7.2.2.4</a> 
[817]1570                  </td>
1571               </tr>
1572               <tr>
1573                  <td class="left">only-if-cached</td>
[1751]1574                  <td class="left"> <a href="#cache-request-directive.only-if-cached" title="only-if-cached">Section&nbsp;7.2.1.7</a> 
[817]1575                  </td>
1576               </tr>
1577               <tr>
1578                  <td class="left">private</td>
[2236]1579                  <td class="left"> <a href="#cache-response-directive.private" title="private">Section&nbsp;7.2.2.6</a> 
[817]1580                  </td>
1581               </tr>
1582               <tr>
1583                  <td class="left">proxy-revalidate</td>
[2236]1584                  <td class="left"> <a href="#cache-response-directive.proxy-revalidate" title="proxy-revalidate">Section&nbsp;7.2.2.7</a> 
[817]1585                  </td>
1586               </tr>
1587               <tr>
1588                  <td class="left">public</td>
[2236]1589                  <td class="left"> <a href="#cache-response-directive.public" title="public">Section&nbsp;7.2.2.5</a> 
[817]1590                  </td>
1591               </tr>
1592               <tr>
1593                  <td class="left">s-maxage</td>
[2236]1594                  <td class="left"> <a href="#cache-response-directive.s-maxage" title="s-maxage">Section&nbsp;7.2.2.9</a> 
[817]1595                  </td>
1596               </tr>
[825]1597               <tr>
1598                  <td class="left">stale-if-error</td>
1599                  <td class="left"> <a href="#RFC5861" id="rfc.xref.RFC5861.1"><cite title="HTTP Cache-Control Extensions for Stale Content">[RFC5861]</cite></a>, <a href="http://tools.ietf.org/html/rfc5861#section-4">Section 4</a> 
1600                  </td>
1601               </tr>
1602               <tr>
1603                  <td class="left">stale-while-revalidate</td>
1604                  <td class="left"> <a href="#RFC5861" id="rfc.xref.RFC5861.2"><cite title="HTTP Cache-Control Extensions for Stale Content">[RFC5861]</cite></a>, <a href="http://tools.ietf.org/html/rfc5861#section-3">Section 3</a> 
1605                  </td>
1606               </tr>
[817]1607            </tbody>
1608         </table>
1609      </div>
[2244]1610      <h2 id="rfc.section.9.2"><a href="#rfc.section.9.2">9.2</a>&nbsp;<a id="warn.code.registry" href="#warn.code.registry">Warn Code Registry</a></h2>
[2246]1611      <p id="rfc.section.9.2.p.1">The HTTP Warn Code Registry defines the name space for warn codes. It will be created and maintained at &lt;<a href="http://www.iana.org/assignments/http-warn-codes">http://www.iana.org/assignments/http-warn-codes</a>&gt;.
[817]1612      </p>
[2244]1613      <h3 id="rfc.section.9.2.1"><a href="#rfc.section.9.2.1">9.2.1</a>&nbsp;<a id="warn.code.registry.procedure" href="#warn.code.registry.procedure">Procedure</a></h3>
1614      <p id="rfc.section.9.2.1.p.1">A registration <em class="bcp14">MUST</em> include the following fields:
[1485]1615      </p>
[2244]1616      <ul>
1617         <li>Warn Code (3 digits)</li>
1618         <li>Short Description</li>
1619         <li>Pointer to specification text</li>
1620      </ul>
1621      <p id="rfc.section.9.2.1.p.2">Values to be added to this name space require IETF Review (see <a href="#RFC5226" id="rfc.xref.RFC5226.2"><cite title="Guidelines for Writing an IANA Considerations Section in RFCs">[RFC5226]</cite></a>, <a href="http://tools.ietf.org/html/rfc5226#section-4.1">Section 4.1</a>).
1622      </p>
1623      <h3 id="rfc.section.9.2.2"><a href="#rfc.section.9.2.2">9.2.2</a>&nbsp;<a id="warn.code.registration" href="#warn.code.registration">Registrations</a></h3>
1624      <p id="rfc.section.9.2.2.p.1">The HTTP Warn Code Registry shall be populated with the registrations below:</p>
[1487]1625      <div id="rfc.table.2">
1626         <div id="iana.warn.code.registration.table"></div>
[1485]1627         <table class="tt full left" cellpadding="3" cellspacing="0">
1628            <thead>
1629               <tr>
1630                  <th>Warn Code</th>
1631                  <th>Short Description</th>
1632                  <th>Reference</th>
1633               </tr>
1634            </thead>
1635            <tbody>
1636               <tr>
1637                  <td class="left">110</td>
[1487]1638                  <td class="left">Response is Stale</td>
[1860]1639                  <td class="left"> <a href="#warn.110" id="rfc.xref.warn.110.1" title="110 Response is Stale">Section&nbsp;7.5.1</a> 
[1487]1640                  </td>
[1485]1641               </tr>
1642               <tr>
1643                  <td class="left">111</td>
[1487]1644                  <td class="left">Revalidation Failed</td>
[1860]1645                  <td class="left"> <a href="#warn.111" id="rfc.xref.warn.111.1" title="111 Revalidation Failed">Section&nbsp;7.5.2</a> 
[1487]1646                  </td>
[1485]1647               </tr>
1648               <tr>
1649                  <td class="left">112</td>
[1487]1650                  <td class="left">Disconnected Operation</td>
[1860]1651                  <td class="left"> <a href="#warn.112" id="rfc.xref.warn.112.1" title="112 Disconnected Operation">Section&nbsp;7.5.3</a> 
[1487]1652                  </td>
[1485]1653               </tr>
1654               <tr>
1655                  <td class="left">113</td>
[1487]1656                  <td class="left">Heuristic Expiration</td>
[1860]1657                  <td class="left"> <a href="#warn.113" id="rfc.xref.warn.113.1" title="113 Heuristic Expiration">Section&nbsp;7.5.4</a> 
[1487]1658                  </td>
[1485]1659               </tr>
1660               <tr>
1661                  <td class="left">199</td>
[1487]1662                  <td class="left">Miscellaneous Warning</td>
[1860]1663                  <td class="left"> <a href="#warn.199" id="rfc.xref.warn.199.1" title="199 Miscellaneous Warning">Section&nbsp;7.5.5</a> 
[1487]1664                  </td>
[1485]1665               </tr>
1666               <tr>
1667                  <td class="left">214</td>
[1487]1668                  <td class="left">Transformation Applied</td>
[1860]1669                  <td class="left"> <a href="#warn.214" id="rfc.xref.warn.214.1" title="214 Transformation Applied">Section&nbsp;7.5.6</a> 
[1487]1670                  </td>
[1485]1671               </tr>
1672               <tr>
1673                  <td class="left">299</td>
[1487]1674                  <td class="left">Miscellaneous Persistent Warning</td>
[1860]1675                  <td class="left"> <a href="#warn.299" id="rfc.xref.warn.299.1" title="299 Miscellaneous Persistent Warning">Section&nbsp;7.5.7</a> 
[1487]1676                  </td>
[1485]1677               </tr>
1678            </tbody>
1679         </table>
1680      </div>
[1751]1681      <h2 id="rfc.section.9.3"><a href="#rfc.section.9.3">9.3</a>&nbsp;<a id="header.field.registration" href="#header.field.registration">Header Field Registration</a></h2>
[2246]1682      <p id="rfc.section.9.3.p.1">HTTP header fields are registered within the Message Header Field Registry maintained at &lt;<a href="http://www.iana.org/assignments/message-headers/message-header-index.html">http://www.iana.org/assignments/message-headers/message-header-index.html</a>&gt;.
[1485]1683      </p>
[2246]1684      <p id="rfc.section.9.3.p.2">This document defines the following HTTP header fields, so their associated registry entries shall be updated according to
1685         the permanent registrations below (see <a href="#BCP90" id="rfc.xref.BCP90.1"><cite title="Registration Procedures for Message Header Fields">[BCP90]</cite></a>):
1686      </p>
[1487]1687      <div id="rfc.table.3">
[290]1688         <div id="iana.header.registration.table"></div>
[669]1689         <table class="tt full left" cellpadding="3" cellspacing="0">
[253]1690            <thead>
1691               <tr>
1692                  <th>Header Field Name</th>
1693                  <th>Protocol</th>
1694                  <th>Status</th>
1695                  <th>Reference</th>
1696               </tr>
1697            </thead>
1698            <tbody>
1699               <tr>
[704]1700                  <td class="left">Age</td>
1701                  <td class="left">http</td>
1702                  <td class="left">standard</td>
[1751]1703                  <td class="left"> <a href="#header.age" id="rfc.xref.header.age.3" title="Age">Section&nbsp;7.1</a> 
[253]1704                  </td>
1705               </tr>
1706               <tr>
[704]1707                  <td class="left">Cache-Control</td>
1708                  <td class="left">http</td>
1709                  <td class="left">standard</td>
[1751]1710                  <td class="left"> <a href="#header.cache-control" id="rfc.xref.header.cache-control.2" title="Cache-Control">Section&nbsp;7.2</a> 
[253]1711                  </td>
1712               </tr>
1713               <tr>
[704]1714                  <td class="left">Expires</td>
1715                  <td class="left">http</td>
1716                  <td class="left">standard</td>
[1751]1717                  <td class="left"> <a href="#header.expires" id="rfc.xref.header.expires.4" title="Expires">Section&nbsp;7.3</a> 
[253]1718                  </td>
1719               </tr>
1720               <tr>
[704]1721                  <td class="left">Pragma</td>
1722                  <td class="left">http</td>
1723                  <td class="left">standard</td>
[2234]1724                  <td class="left"> <a href="#header.pragma" id="rfc.xref.header.pragma.2" title="Pragma">Section&nbsp;7.4</a> 
[253]1725                  </td>
1726               </tr>
1727               <tr>
[704]1728                  <td class="left">Warning</td>
1729                  <td class="left">http</td>
1730                  <td class="left">standard</td>
[1860]1731                  <td class="left"> <a href="#header.warning" id="rfc.xref.header.warning.5" title="Warning">Section&nbsp;7.5</a> 
[253]1732                  </td>
1733               </tr>
1734            </tbody>
1735         </table>
1736      </div>
[2246]1737      <p id="rfc.section.9.3.p.3">The change controller is: "IETF (iesg@ietf.org) - Internet Engineering Task Force".</p>
[1751]1738      <h1 id="rfc.section.10"><a href="#rfc.section.10">10.</a>&nbsp;<a id="security.considerations" href="#security.considerations">Security Considerations</a></h1>
[2069]1739      <p id="rfc.section.10.p.1">This section is meant to inform developers, information providers, and users of known security concerns specific to HTTP/1.1
[2180]1740         caching. More general security considerations are addressed in HTTP messaging <a href="#Part1" id="rfc.xref.Part1.11"><cite title="Hypertext Transfer Protocol (HTTP/1.1): Message Syntax and Routing">[Part1]</cite></a> and semantics <a href="#Part2" id="rfc.xref.Part2.8"><cite title="Hypertext Transfer Protocol (HTTP/1.1): Semantics and Content">[Part2]</cite></a>.
[2069]1741      </p>
1742      <p id="rfc.section.10.p.2">Caches expose additional potential vulnerabilities, since the contents of the cache represent an attractive target for malicious
[538]1743         exploitation. Because cache contents persist after an HTTP request is complete, an attack on the cache can reveal information
[970]1744         long after a user believes that the information has been removed from the network. Therefore, cache contents need to be protected
[538]1745         as sensitive information.
[52]1746      </p>
[2069]1747      <p id="rfc.section.10.p.3">Furthermore, the very use of a cache can bring about privacy concerns. For example, if two users share a cache, and the first
[1960]1748         one browses to a site, the second may be able to detect that the other has been to that site, because the resources from it
1749         load more quickly, thanks to the cache.
1750      </p>
[2069]1751      <p id="rfc.section.10.p.4">Implementation flaws might allow attackers to insert content into a cache ("cache poisoning"), leading to compromise of clients
[1865]1752         that trust that content. Because of their nature, these attacks are difficult to mitigate.
1753      </p>
[2069]1754      <p id="rfc.section.10.p.5">Likewise, implementation flaws (as well as misunderstanding of cache operation) might lead to caching of sensitive information
[1945]1755         (e.g., authentication credentials) that is thought to be private, exposing it to unauthorized parties.
[1865]1756      </p>
[2268]1757      <p id="rfc.section.10.p.6">Note that the Set-Cookie response header field <a href="#RFC6265" id="rfc.xref.RFC6265.1"><cite title="HTTP State Management Mechanism">[RFC6265]</cite></a> does not inhibit caching; a cacheable response with a Set-Cookie header field can be (and often is) used to satisfy subsequent
1758         requests to caches. Servers who wish to control caching of these responses are encouraged to emit appropriate Cache-Control
1759         response header fields.
[1865]1760      </p>
[1751]1761      <h1 id="rfc.section.11"><a href="#rfc.section.11">11.</a>&nbsp;<a id="acks" href="#acks">Acknowledgments</a></h1>
[2069]1762      <p id="rfc.section.11.p.1">See <a href="p1-messaging.html#acks" title="Acknowledgments">Section 9</a> of <a href="#Part1" id="rfc.xref.Part1.12"><cite title="Hypertext Transfer Protocol (HTTP/1.1): Message Syntax and Routing">[Part1]</cite></a>.
[52]1763      </p>
[1751]1764      <h1 id="rfc.references"><a id="rfc.section.12" href="#rfc.section.12">12.</a> References
[52]1765      </h1>
[1751]1766      <h2 id="rfc.references.1"><a href="#rfc.section.12.1" id="rfc.section.12.1">12.1</a> Normative References
[119]1767      </h2>
[2232]1768      <table>
[52]1769         <tr>
1770            <td class="reference"><b id="Part1">[Part1]</b></td>
[2232]1771            <td class="top"><a href="mailto:fielding@gbiv.com" title="Adobe Systems Incorporated">Fielding, R., Ed.</a> and <a href="mailto:julian.reschke@greenbytes.de" title="greenbytes GmbH">J. Reschke, Ed.</a>, “<a href="http://tools.ietf.org/html/draft-ietf-httpbis-p1-messaging-latest">Hypertext Transfer Protocol (HTTP/1.1): Message Syntax and Routing</a>”, Internet-Draft&nbsp;draft-ietf-httpbis-p1-messaging-latest (work in progress), May&nbsp;2013.
[52]1772            </td>
1773         </tr>
1774         <tr>
1775            <td class="reference"><b id="Part2">[Part2]</b></td>
[2232]1776            <td class="top"><a href="mailto:fielding@gbiv.com" title="Adobe Systems Incorporated">Fielding, R., Ed.</a> and <a href="mailto:julian.reschke@greenbytes.de" title="greenbytes GmbH">J. Reschke, Ed.</a>, “<a href="http://tools.ietf.org/html/draft-ietf-httpbis-p2-semantics-latest">Hypertext Transfer Protocol (HTTP/1.1): Semantics and Content</a>”, Internet-Draft&nbsp;draft-ietf-httpbis-p2-semantics-latest (work in progress), May&nbsp;2013.
[52]1777            </td>
1778         </tr>
1779         <tr>
1780            <td class="reference"><b id="Part4">[Part4]</b></td>
[2232]1781            <td class="top"><a href="mailto:fielding@gbiv.com" title="Adobe Systems Incorporated">Fielding, R., Ed.</a> and <a href="mailto:julian.reschke@greenbytes.de" title="greenbytes GmbH">J. Reschke, Ed.</a>, “<a href="http://tools.ietf.org/html/draft-ietf-httpbis-p4-conditional-latest">Hypertext Transfer Protocol (HTTP/1.1): Conditional Requests</a>”, Internet-Draft&nbsp;draft-ietf-httpbis-p4-conditional-latest (work in progress), May&nbsp;2013.
[52]1782            </td>
1783         </tr>
1784         <tr>
1785            <td class="reference"><b id="Part5">[Part5]</b></td>
[2232]1786            <td class="top"><a href="mailto:fielding@gbiv.com" title="Adobe Systems Incorporated">Fielding, R., Ed.</a>, <a href="mailto:ylafon@w3.org" title="World Wide Web Consortium">Lafon, Y., Ed.</a>, and <a href="mailto:julian.reschke@greenbytes.de" title="greenbytes GmbH">J. Reschke, Ed.</a>, “<a href="http://tools.ietf.org/html/draft-ietf-httpbis-p5-range-latest">Hypertext Transfer Protocol (HTTP/1.1): Range Requests</a>”, Internet-Draft&nbsp;draft-ietf-httpbis-p5-range-latest (work in progress), May&nbsp;2013.
[52]1787            </td>
1788         </tr>
1789         <tr>
1790            <td class="reference"><b id="Part7">[Part7]</b></td>
[2232]1791            <td class="top"><a href="mailto:fielding@gbiv.com" title="Adobe Systems Incorporated">Fielding, R., Ed.</a> and <a href="mailto:julian.reschke@greenbytes.de" title="greenbytes GmbH">J. Reschke, Ed.</a>, “<a href="http://tools.ietf.org/html/draft-ietf-httpbis-p7-auth-latest">Hypertext Transfer Protocol (HTTP/1.1): Authentication</a>”, Internet-Draft&nbsp;draft-ietf-httpbis-p7-auth-latest (work in progress), May&nbsp;2013.
[52]1792            </td>
1793         </tr>
1794         <tr>
[119]1795            <td class="reference"><b id="RFC2119">[RFC2119]</b></td>
[704]1796            <td class="top"><a href="mailto:sob@harvard.edu" title="Harvard University">Bradner, S.</a>, “<a href="http://tools.ietf.org/html/rfc2119">Key words for use in RFCs to Indicate Requirement Levels</a>”, BCP&nbsp;14, RFC&nbsp;2119, March&nbsp;1997.
[52]1797            </td>
1798         </tr>
[425]1799         <tr>
1800            <td class="reference"><b id="RFC5234">[RFC5234]</b></td>
[704]1801            <td class="top"><a href="mailto:dcrocker@bbiw.net" title="Brandenburg InternetWorking">Crocker, D., Ed.</a> and <a href="mailto:paul.overell@thus.net" title="THUS plc.">P. Overell</a>, “<a href="http://tools.ietf.org/html/rfc5234">Augmented BNF for Syntax Specifications: ABNF</a>”, STD&nbsp;68, RFC&nbsp;5234, January&nbsp;2008.
[425]1802            </td>
1803         </tr>
[119]1804      </table>
[1751]1805      <h2 id="rfc.references.2"><a href="#rfc.section.12.2" id="rfc.section.12.2">12.2</a> Informative References
[119]1806      </h2>
[2232]1807      <table>
[52]1808         <tr>
[2046]1809            <td class="reference"><b id="BCP90">[BCP90]</b></td>
1810            <td class="top"><a href="mailto:GK-IETF@ninebynine.org" title="Nine by Nine">Klyne, G.</a>, <a href="mailto:mnot@pobox.com" title="BEA Systems">Nottingham, M.</a>, and <a href="mailto:JeffMogul@acm.org" title="HP Labs">J. Mogul</a>, “<a href="http://tools.ietf.org/html/rfc3864">Registration Procedures for Message Header Fields</a>”, BCP&nbsp;90, RFC&nbsp;3864, September&nbsp;2004.
1811            </td>
1812         </tr>
1813         <tr>
[129]1814            <td class="reference"><b id="RFC1305">[RFC1305]</b></td>
[704]1815            <td class="top"><a href="mailto:mills@udel.edu" title="University of Delaware, Electrical Engineering Department">Mills, D.</a>, “<a href="http://tools.ietf.org/html/rfc1305">Network Time Protocol (Version 3) Specification, Implementation</a>”, RFC&nbsp;1305, March&nbsp;1992.
[129]1816            </td>
1817         </tr>
1818         <tr>
[119]1819            <td class="reference"><b id="RFC2616">[RFC2616]</b></td>
[704]1820            <td class="top"><a href="mailto:fielding@ics.uci.edu" title="University of California, Irvine">Fielding, R.</a>, <a href="mailto:jg@w3.org" title="W3C">Gettys, J.</a>, <a href="mailto:mogul@wrl.dec.com" title="Compaq Computer Corporation">Mogul, J.</a>, <a href="mailto:frystyk@w3.org" title="MIT Laboratory for Computer Science">Frystyk, H.</a>, <a href="mailto:masinter@parc.xerox.com" title="Xerox Corporation">Masinter, L.</a>, <a href="mailto:paulle@microsoft.com" title="Microsoft Corporation">Leach, P.</a>, and <a href="mailto:timbl@w3.org" title="W3C">T. Berners-Lee</a>, “<a href="http://tools.ietf.org/html/rfc2616">Hypertext Transfer Protocol -- HTTP/1.1</a>”, RFC&nbsp;2616, June&nbsp;1999.
[52]1821            </td>
1822         </tr>
[253]1823         <tr>
[817]1824            <td class="reference"><b id="RFC5226">[RFC5226]</b></td>
1825            <td class="top"><a href="mailto:narten@us.ibm.com" title="IBM">Narten, T.</a> and <a href="mailto:Harald@Alvestrand.no" title="Google">H. Alvestrand</a>, “<a href="http://tools.ietf.org/html/rfc5226">Guidelines for Writing an IANA Considerations Section in RFCs</a>”, BCP&nbsp;26, RFC&nbsp;5226, May&nbsp;2008.
1826            </td>
1827         </tr>
[825]1828         <tr>
1829            <td class="reference"><b id="RFC5861">[RFC5861]</b></td>
1830            <td class="top"><a href="mailto:mnot@yahoo-inc.com" title="Yahoo! Inc.">Nottingham, M.</a>, “<a href="http://tools.ietf.org/html/rfc5861">HTTP Cache-Control Extensions for Stale Content</a>”, RFC&nbsp;5861, April&nbsp;2010.
1831            </td>
1832         </tr>
[1865]1833         <tr>
1834            <td class="reference"><b id="RFC6265">[RFC6265]</b></td>
[1867]1835            <td class="top"><a href="mailto:abarth@eecs.berkeley.edu" title="&#xA;          University of California, Berkeley&#xA;        ">Barth, A.</a>, “<a href="http://tools.ietf.org/html/rfc6265">HTTP State Management Mechanism</a>”, RFC&nbsp;6265, April&nbsp;2011.
[1865]1836            </td>
1837         </tr>
[119]1838      </table>
[662]1839      <div class="avoidbreak">
1840         <h1 id="rfc.authors"><a href="#rfc.authors">Authors' Addresses</a></h1>
1841         <address class="vcard"><span class="vcardline"><span class="fn">Roy T. Fielding</span>
1842               (editor)
[1106]1843               <span class="n hidden"><span class="family-name">Fielding</span><span class="given-name">Roy T.</span></span></span><span class="org vcardline">Adobe Systems Incorporated</span><span class="adr"><span class="street-address vcardline">345 Park Ave</span><span class="vcardline"><span class="locality">San Jose</span>, <span class="region">CA</span>&nbsp;<span class="postal-code">95110</span></span><span class="country-name vcardline">USA</span></span><span class="vcardline">Email: <a href="mailto:fielding@gbiv.com"><span class="email">fielding@gbiv.com</span></a></span><span class="vcardline">URI: <a href="http://roy.gbiv.com/" class="url">http://roy.gbiv.com/</a></span></address>
[662]1844         <address class="vcard"><span class="vcardline"><span class="fn">Mark Nottingham</span>
1845               (editor)
[1914]1846               <span class="n hidden"><span class="family-name">Nottingham</span><span class="given-name">Mark</span></span></span><span class="org vcardline">Akamai</span><span class="vcardline">Email: <a href="mailto:mnot@mnot.net"><span class="email">mnot@mnot.net</span></a></span><span class="vcardline">URI: <a href="http://www.mnot.net/" class="url">http://www.mnot.net/</a></span></address>
[662]1847         <address class="vcard"><span class="vcardline"><span class="fn">Julian F. Reschke</span>
1848               (editor)
[1689]1849               <span class="n hidden"><span class="family-name">Reschke</span><span class="given-name">Julian F.</span></span></span><span class="org vcardline">greenbytes GmbH</span><span class="adr"><span class="street-address vcardline">Hafenweg 16</span><span class="vcardline"><span class="locality">Muenster</span>, <span class="region">NW</span>&nbsp;<span class="postal-code">48155</span></span><span class="country-name vcardline">Germany</span></span><span class="vcardline">Email: <a href="mailto:julian.reschke@greenbytes.de"><span class="email">julian.reschke@greenbytes.de</span></a></span><span class="vcardline">URI: <a href="http://greenbytes.de/tech/webdav/" class="url">http://greenbytes.de/tech/webdav/</a></span></address>
[662]1850      </div>
[912]1851      <h1 id="rfc.section.A" class="np"><a href="#rfc.section.A">A.</a>&nbsp;<a id="changes.from.rfc.2616" href="#changes.from.rfc.2616">Changes from RFC 2616</a></h1>
[2020]1852      <p id="rfc.section.A.p.1">Caching-related text has been substantially rewritten for clarity.</p>
1853      <p id="rfc.section.A.p.2">The algorithm for calculating age is now less conservative. (<a href="#age.calculations" title="Calculating Age">Section&nbsp;4.1.3</a>)
[139]1854      </p>
[2020]1855      <p id="rfc.section.A.p.3">Caches are now required to handle dates with timezones as if they're invalid, because it's not possible to accurately guess.
1856         (<a href="#age.calculations" title="Calculating Age">Section&nbsp;4.1.3</a>)
[106]1857      </p>
[2234]1858      <p id="rfc.section.A.p.4">The <a href="p2-semantics.html#header.content-location" class="smpl">Content-Location</a> response header field is no longer used to determine the appropriate response to use when validating. (<a href="#validation.model" title="Validation">Section&nbsp;4.2</a>)
[691]1859      </p>
[2020]1860      <p id="rfc.section.A.p.5">The algorithm for selecting a cached negotiated response to use has been clarified in several ways. In particular, it now
[2237]1861         explicitly allows header-specific canonicalization when processing selecting header fields. (<a href="#caching.negotiated.responses" title="Calculating Secondary Keys with Vary">Section&nbsp;4.3</a>)
[1231]1862      </p>
[2020]1863      <p id="rfc.section.A.p.6">Requirements regarding denial of service attack avoidance when performing invalidation have been clarified. (<a href="#invalidation.after.updates.or.deletions" title="Request Methods that Invalidate">Section&nbsp;6</a>)
[669]1864      </p>
[2020]1865      <p id="rfc.section.A.p.7">Cache invalidation only occurs when a successful response is received. (<a href="#invalidation.after.updates.or.deletions" title="Request Methods that Invalidate">Section&nbsp;6</a>)
1866      </p>
1867      <p id="rfc.section.A.p.8">The conditions under which an authenticated response can be cached have been clarified. (<a href="#caching.authenticated.responses" title="Storing Responses to Authenticated Requests">Section&nbsp;3.2</a>)
1868      </p>
1869      <p id="rfc.section.A.p.9">The one-year limit on Expires header field values has been removed; instead, the reasoning for using a sensible value is given.
1870         (<a href="#header.expires" id="rfc.xref.header.expires.5" title="Expires">Section&nbsp;7.3</a>)
1871      </p>
[2234]1872      <p id="rfc.section.A.p.10">The Pragma header field is now only defined for backwards compatibility; future pragmas are deprecated. (<a href="#header.pragma" id="rfc.xref.header.pragma.3" title="Pragma">Section&nbsp;7.4</a>)
[2020]1873      </p>
1874      <p id="rfc.section.A.p.11">Cache directives are explicitly defined to be case-insensitive. (<a href="#header.cache-control" id="rfc.xref.header.cache-control.3" title="Cache-Control">Section&nbsp;7.2</a>)
1875      </p>
1876      <p id="rfc.section.A.p.12">Handling of multiple instances of cache directives when only one is expected is now defined. (<a href="#header.cache-control" id="rfc.xref.header.cache-control.4" title="Cache-Control">Section&nbsp;7.2</a>)
1877      </p>
1878      <p id="rfc.section.A.p.13">The qualified forms of the private and no-cache cache directives are noted to not be widely implemented; e.g., "private=foo"
1879         is interpreted by many caches as simply "private". Additionally, the meaning of the qualified form of no-cache has been clarified.
1880         (<a href="#cache-response-directive" title="Response Cache-Control Directives">Section&nbsp;7.2.2</a>)
1881      </p>
1882      <p id="rfc.section.A.p.14">The "no-store" cache request directive doesn't apply to responses; i.e., a cache can satisfy a request with no-store on it,
[2236]1883         and does not invalidate it. (<a href="#cache-request-directive.no-store" title="no-store">Section&nbsp;7.2.1.5</a>)
[2020]1884      </p>
[2236]1885      <p id="rfc.section.A.p.15">The "no-cache" response cache directive's meaning has been clarified. (<a href="#cache-response-directive.no-cache" title="no-cache">Section&nbsp;7.2.2.2</a>)
[2020]1886      </p>
[2172]1887      <p id="rfc.section.A.p.16">New status codes can now define that caches are allowed to use heuristic freshness with them. (<a href="#heuristic.freshness" title="Calculating Heuristic Freshness">Section&nbsp;4.1.2</a>)
[2020]1888      </p>
[2172]1889      <p id="rfc.section.A.p.17">Caches are now allow to calculate heuristic freshness for URLs with query components. (<a href="#heuristic.freshness" title="Calculating Heuristic Freshness">Section&nbsp;4.1.2</a>)
[2020]1890      </p>
[2268]1891      <p id="rfc.section.A.p.18">Some requirements regarding production of the <a href="#header.warning" class="smpl">Warning</a> header fields have been relaxed, as it is not widely implemented. Furthermore, the <a href="#header.warning" class="smpl">Warning</a> header field no longer uses RFC 2047 encoding, nor allows multiple languages, as these aspects were not implemented. (<a href="#header.warning" id="rfc.xref.header.warning.6" title="Warning">Section&nbsp;7.5</a>)
[2020]1892      </p>
[2268]1893      <p id="rfc.section.A.p.19">This specification introduces the Cache Directive and Warn Code Registries, and defines considerations for new cache directives.
[2020]1894         (<a href="#cache.control.extensions" title="Cache Control Extensions">Section&nbsp;7.2.3</a> and <a href="#warn.code.extensions" title="Warn Code Extensions">Section&nbsp;7.5.8</a>)
1895      </p>
[1805]1896      <h1 id="rfc.section.B"><a href="#rfc.section.B">B.</a>&nbsp;<a id="imported.abnf" href="#imported.abnf">Imported ABNF</a></h1>
[1806]1897      <p id="rfc.section.B.p.1">The following core rules are included by reference, as defined in <a href="http://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 0-9), DQUOTE (double quote), HEXDIG
[1805]1898         (hexadecimal 0-9/A-F/a-f), LF (line feed), OCTET (any 8-bit sequence of data), SP (space), and VCHAR (any visible US-ASCII
1899         character).
1900      </p>
[2069]1901      <p id="rfc.section.B.p.2">The rules below are defined in <a href="#Part1" id="rfc.xref.Part1.13"><cite title="Hypertext Transfer Protocol (HTTP/1.1): Message Syntax and Routing">[Part1]</cite></a>:
[1805]1902      </p>
[2069]1903      <div id="rfc.figure.u.14"></div><pre class="inline">  <a href="#imported.abnf" class="smpl">OWS</a>           = &lt;OWS, defined in <a href="#Part1" id="rfc.xref.Part1.14"><cite title="Hypertext Transfer Protocol (HTTP/1.1): Message Syntax and Routing">[Part1]</cite></a>, <a href="p1-messaging.html#whitespace" title="Whitespace">Section 3.2.3</a>&gt;
1904  <a href="#imported.abnf" class="smpl">field-name</a>    = &lt;field-name, defined in <a href="#Part1" id="rfc.xref.Part1.15"><cite title="Hypertext Transfer Protocol (HTTP/1.1): Message Syntax and Routing">[Part1]</cite></a>, <a href="p1-messaging.html#header.fields" title="Header Fields">Section 3.2</a>&gt;
1905  <a href="#imported.abnf" class="smpl">quoted-string</a> = &lt;quoted-string, defined in <a href="#Part1" id="rfc.xref.Part1.16"><cite title="Hypertext Transfer Protocol (HTTP/1.1): Message Syntax and Routing">[Part1]</cite></a>, <a href="p1-messaging.html#field.components" title="Field value components">Section 3.2.6</a>&gt;
1906  <a href="#imported.abnf" class="smpl">token</a>         = &lt;token, defined in <a href="#Part1" id="rfc.xref.Part1.17"><cite title="Hypertext Transfer Protocol (HTTP/1.1): Message Syntax and Routing">[Part1]</cite></a>, <a href="p1-messaging.html#field.components" title="Field value components">Section 3.2.6</a>&gt;
[1805]1907
[2069]1908  <a href="#imported.abnf" class="smpl">port</a>          = &lt;port, defined in <a href="#Part1" id="rfc.xref.Part1.18"><cite title="Hypertext Transfer Protocol (HTTP/1.1): Message Syntax and Routing">[Part1]</cite></a>, <a href="p1-messaging.html#uri" title="Uniform Resource Identifiers">Section 2.7</a>&gt;
1909  <a href="#imported.abnf" class="smpl">pseudonym</a>     = &lt;pseudonym, defined in <a href="#Part1" id="rfc.xref.Part1.19"><cite title="Hypertext Transfer Protocol (HTTP/1.1): Message Syntax and Routing">[Part1]</cite></a>, <a href="p1-messaging.html#header.via" title="Via">Section 5.7.1</a>&gt; 
1910  <a href="#imported.abnf" class="smpl">uri-host</a>      = &lt;uri-host, defined in <a href="#Part1" id="rfc.xref.Part1.20"><cite title="Hypertext Transfer Protocol (HTTP/1.1): Message Syntax and Routing">[Part1]</cite></a>, <a href="p1-messaging.html#uri" title="Uniform Resource Identifiers">Section 2.7</a>&gt;
[1805]1911</pre><p id="rfc.section.B.p.4">The rules below are defined in other parts:</p>
[2180]1912      <div id="rfc.figure.u.15"></div><pre class="inline">  <a href="#imported.abnf" class="smpl">HTTP-date</a>     = &lt;HTTP-date, defined in <a href="#Part2" id="rfc.xref.Part2.9"><cite title="Hypertext Transfer Protocol (HTTP/1.1): Semantics and Content">[Part2]</cite></a>, <a href="p2-semantics.html#http.date" title="Date/Time Formats">Section 7.1.1.1</a>&gt;
[1805]1913</pre><h1 id="rfc.section.C"><a href="#rfc.section.C">C.</a>&nbsp;<a id="collected.abnf" href="#collected.abnf">Collected ABNF</a></h1>
[2206]1914      <p id="rfc.section.C.p.1">In the collected ABNF below, list rules are expanded as per <a href="p1-messaging.html#notation" title="Syntax Notation">Section 1.2</a> of <a href="#Part1" id="rfc.xref.Part1.21"><cite title="Hypertext Transfer Protocol (HTTP/1.1): Message Syntax and Routing">[Part1]</cite></a>.
1915      </p>