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

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

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

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