Ignore:
Timestamp:
14/06/14 11:20:37 (6 years ago)
Author:
julian.reschke@…
Message:

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

File:
1 edited

Legend:

Unmodified
Added
Removed
  • draft-ietf-httpbis/09/p6-cache.html

    r772 r2726  
    22  PUBLIC "-//W3C//DTD HTML 4.01//EN">
    33<html lang="en">
    4    <head profile="http://www.w3.org/2006/03/hcard http://dublincore.org/documents/2008/08/04/dc-html/">
     4   <head profile="http://dublincore.org/documents/2008/08/04/dc-html/">
    55      <meta http-equiv="Content-Type" content="text/html; charset=UTF-8">
    66      <title>HTTP/1.1, part 6: Caching</title><style type="text/css" title="Xml2Rfc (sans serif)">
     
    2424body {
    2525  color: black;
    26   font-family: verdana, helvetica, arial, sans-serif;
    27   font-size: 10pt;
     26  font-family: cambria, helvetica, arial, sans-serif;
     27  font-size: 11pt;
     28  margin-right: 2em;
    2829}
    2930cite {
     
    3334  margin-left: 2em;
    3435}
    35 dd {
    36   margin-right: 2em;
    37 }
    3836dl {
    3937  margin-left: 2em;
    4038}
    41 
    4239ul.empty {
    4340  list-style-type: none;
     
    5350}
    5451h1 {
    55   font-size: 14pt;
     52  font-size: 130%;
    5653  line-height: 21pt;
    5754  page-break-after: avoid;
     
    6057  page-break-before: always;
    6158}
    62 h1 a {
    63   color: #333333;
    64 }
    6559h2 {
    66   font-size: 12pt;
     60  font-size: 120%;
    6761  line-height: 15pt;
    6862  page-break-after: avoid;
    6963}
    70 h3, h4, h5, h6 {
    71   font-size: 10pt;
     64h3 {
     65  font-size: 110%;
    7266  page-break-after: avoid;
    7367}
    74 h2 a, h3 a, h4 a, h5 a, h6 a {
     68h4, h5, h6 {
     69  page-break-after: avoid;
     70}
     71h1 a, h2 a, h3 a, h4 a, h5 a, h6 a {
    7572  color: black;
    7673}
     
    8077li {
    8178  margin-left: 2em;
    82   margin-right: 2em;
    8379}
    8480ol {
    8581  margin-left: 2em;
    86   margin-right: 2em;
     82}
     83ol.la {
     84  list-style-type: lower-alpha;
     85}
     86ol.ua {
     87  list-style-type: upper-alpha;
    8788}
    8889ol p {
     
    9192p {
    9293  margin-left: 2em;
    93   margin-right: 2em;
    9494}
    9595pre {
     
    9797  background-color: lightyellow;
    9898  padding: .25em;
     99  page-break-inside: avoid;
    99100}
    100101pre.text2 {
     
    128129table.tt {
    129130  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;
    130142}
    131143table.full {
    132   border-style: outset;
    133   border-width: 1px;
    134 }
    135 table.headers {
    136   border-style: outset;
    137   border-width: 1px;
     144  border-style: solid;
     145  border-width: 2px;
    138146}
    139147table.tt td {
    140148  vertical-align: top;
    141149}
     150table.all td {
     151  border-style: solid;
     152  border-width: 1px;
     153}
    142154table.full td {
    143   border-style: inset;
     155  border-style: none solid;
    144156  border-width: 1px;
    145157}
     
    147159  vertical-align: top;
    148160}
     161table.all th {
     162  border-style: solid;
     163  border-width: 1px;
     164}
    149165table.full th {
    150   border-style: inset;
    151   border-width: 1px;
     166  border-style: solid;
     167  border-width: 1px 1px 2px 1px;
    152168}
    153169table.headers th {
    154   border-style: none none inset none;
    155   border-width: 1px;
     170  border-style: none none solid none;
     171  border-width: 2px;
    156172}
    157173table.left {
     
    168184  caption-side: bottom;
    169185  font-weight: bold;
    170   font-size: 9pt;
     186  font-size: 10pt;
    171187  margin-top: .5em;
    172188}
     
    175191  border-spacing: 1px;
    176192  width: 95%;
    177   font-size: 10pt;
     193  font-size: 11pt;
    178194  color: white;
    179195}
     
    183199td.topnowrap {
    184200  vertical-align: top;
    185   white-space: nowrap; 
     201  white-space: nowrap;
    186202}
    187203table.header td {
     
    200216  display:table-header-group;
    201217}
    202 ul.toc {
     218ul.toc, ul.toc ul {
    203219  list-style: none;
    204220  margin-left: 1.5em;
    205   margin-right: 0em;
    206221  padding-left: 0em;
    207222}
    208 li.tocline0 {
     223ul.toc li {
    209224  line-height: 150%;
    210225  font-weight: bold;
     226  margin-left: 0em;
     227}
     228ul.toc li li {
     229  line-height: normal;
     230  font-weight: normal;
    211231  font-size: 10pt;
    212232  margin-left: 0em;
    213   margin-right: 0em;
    214 }
    215 li.tocline1 {
    216   line-height: normal;
    217   font-weight: normal;
    218   font-size: 9pt;
    219   margin-left: 0em;
    220   margin-right: 0em;
    221 }
    222 li.tocline2 {
     233}
     234li.excluded {
    223235  font-size: 0pt;
    224236}
     
    226238  margin-left: 0em;
    227239}
    228 ul.ind {
     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 {
    229247  list-style: none;
    230248  margin-left: 1.5em;
    231   margin-right: 0em;
    232249  padding-left: 0em;
    233250  page-break-before: avoid;
    234251}
    235 li.indline0 {
     252ul.ind li {
    236253  font-weight: bold;
    237254  line-height: 200%;
    238255  margin-left: 0em;
    239   margin-right: 0em;
    240 }
    241 li.indline1 {
     256}
     257ul.ind li li {
    242258  font-weight: normal;
    243259  line-height: 150%;
    244260  margin-left: 0em;
    245   margin-right: 0em;
    246261}
    247262.avoidbreak {
     
    267282  font-weight: bold;
    268283  text-align: center;
    269   font-size: 9pt;
     284  font-size: 10pt;
    270285}
    271286.filename {
    272287  color: #333333;
     288  font-size: 75%;
    273289  font-weight: bold;
    274   font-size: 12pt;
    275290  line-height: 21pt;
    276291  text-align: center;
     
    279294  font-weight: bold;
    280295}
    281 .hidden {
    282   display: none;
    283 }
    284296.left {
    285297  text-align: left;
     
    289301}
    290302.title {
    291   color: #990000;
    292   font-size: 18pt;
     303  color: green;
     304  font-size: 150%;
    293305  line-height: 18pt;
    294306  font-weight: bold;
     
    296308  margin-top: 36pt;
    297309}
    298 .vcardline {
    299   display: block;
    300 }
    301310.warning {
    302   font-size: 14pt;
     311  font-size: 130%;
    303312  background-color: yellow;
    304313}
     
    309318    display: none;
    310319  }
    311  
     320
    312321  a {
    313322    color: black;
     
    324333    background-color: white;
    325334    vertical-align: top;
    326     font-size: 12pt;
     335    font-size: 110%;
    327336  }
    328337
    329   ul.toc a::after {
     338  ul.toc a:nth-child(2)::after {
    330339    content: leader('.') target-counter(attr(href), page);
    331340  }
    332  
    333   a.iref {
     341
     342  ul.ind li li a {
    334343    content: target-counter(attr(href), page);
    335344  }
    336  
     345
    337346  .print2col {
    338347    column-count: 2;
     
    344353@page {
    345354  @top-left {
    346        content: "Internet-Draft"; 
    347   } 
     355       content: "Internet-Draft";
     356  }
    348357  @top-right {
    349        content: "March 2010"; 
    350   } 
     358       content: "March 2010";
     359  }
    351360  @top-center {
    352        content: "HTTP/1.1, Part 6"; 
    353   } 
     361       content: "HTTP/1.1, Part 6";
     362  }
    354363  @bottom-left {
    355        content: "Fielding, et al."; 
    356   } 
     364       content: "Fielding, et al.";
     365  }
    357366  @bottom-center {
    358        content: "Standards Track";
    359   } 
     367       content: "Expires September 9, 2010";
     368  }
    360369  @bottom-right {
    361        content: "[Page " counter(page) "]"; 
    362   } 
    363 }
    364 
    365 @page:first { 
     370       content: "[Page " counter(page) "]";
     371  }
     372}
     373
     374@page:first {
    366375    @top-left {
    367376      content: normal;
     
    389398      <link rel="Appendix" title="B Collected ABNF" href="#rfc.section.B">
    390399      <link rel="Appendix" title="C Change Log (to be removed by RFC Editor before publication)" href="#rfc.section.C">
    391       <meta name="generator" content="http://greenbytes.de/tech/webdav/rfc2629.xslt, Revision 1.510, 2010-02-20 17:14:25, XSLT vendor: SAXON 8.9 from Saxonica http://www.saxonica.com/">
     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/">
    392401      <link rel="schema.dct" href="http://purl.org/dc/terms/">
    393402      <meta name="dct.creator" content="Fielding, R.">
     
    419428            </tr>
    420429            <tr>
    421                <td class="left">Obsoletes: <a href="http://tools.ietf.org/html/rfc2616">2616</a> (if approved)
     430               <td class="left">Obsoletes: <a href="https://tools.ietf.org/html/rfc2616">2616</a> (if approved)
    422431               </td>
    423432               <td class="right">J. Gettys</td>
     
    481490            <tr>
    482491               <td class="left"></td>
    483                <td class="right">J. F. Reschke, Editor</td>
     492               <td class="right">J. Reschke, Editor</td>
    484493            </tr>
    485494            <tr>
     
    494503      </table>
    495504      <p class="title">HTTP/1.1, part 6: Caching<br><span class="filename">draft-ietf-httpbis-p6-cache-09</span></p>
    496       <h1 id="rfc.abstract"><a href="#rfc.abstract">Abstract</a></h1> 
     505      <h1 id="rfc.abstract"><a href="#rfc.abstract">Abstract</a></h1>
    497506      <p>The Hypertext Transfer Protocol (HTTP) is an application-level protocol for distributed, collaborative, hypermedia information
    498507         systems. This document is Part 6 of the seven-part specification that defines the protocol referred to as "HTTP/1.1" and,
    499508         taken together, obsoletes RFC 2616. Part 6 defines requirements on HTTP caches and the associated header fields that control
    500509         cache behavior or indicate cacheable response messages.
    501       </p> 
    502       <h1 id="rfc.note.1"><a href="#rfc.note.1">Editorial Note (To be removed by RFC Editor)</a></h1> 
     510      </p>
     511      <h1 id="rfc.note.1"><a href="#rfc.note.1">Editorial Note (To be removed by RFC Editor)</a></h1>
    503512      <p>Discussion of this draft should take place on the HTTPBIS working group mailing list (ietf-http-wg@w3.org). The current issues
    504513         list is at &lt;<a href="http://tools.ietf.org/wg/httpbis/trac/report/11">http://tools.ietf.org/wg/httpbis/trac/report/11</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;.
    505       </p> 
     514      </p>
    506515      <p>The changes in this draft are summarized in <a href="#changes.since.08" title="Since draft-ietf-httpbis-p6-cache-08">Appendix&nbsp;C.10</a>.
    507       </p>
    508       <h1><a id="rfc.status" href="#rfc.status">Status of this Memo</a></h1>
    509       <p>This Internet-Draft is submitted to IETF in full conformance with the provisions of BCP 78 and BCP 79.</p>
    510       <p>Internet-Drafts are working documents of the Internet Engineering Task Force (IETF), its areas, and its working groups. Note
    511          that other groups may also distribute working documents as Internet-Drafts.
    512516      </p>
    513       <p>Internet-Drafts are draft documents valid for a maximum of six months and may be updated, replaced, or obsoleted by other
    514          documents at any time. It is inappropriate to use Internet-Drafts as reference material or to cite them other than as “work
    515          in progress”.
    516       </p>
    517       <p>The list of current Internet-Drafts can be accessed at <a href="http://www.ietf.org/ietf/1id-abstracts.txt">http://www.ietf.org/ietf/1id-abstracts.txt</a>.
    518       </p>
    519       <p>The list of Internet-Draft Shadow Directories can be accessed at <a href="http://www.ietf.org/shadow.html">http://www.ietf.org/shadow.html</a>.
    520       </p>
    521       <p>This Internet-Draft will expire in September 9, 2010.</p>
    522       <h1><a id="rfc.copyrightnotice" href="#rfc.copyrightnotice">Copyright Notice</a></h1>
    523       <p>Copyright © 2010 IETF Trust and the persons identified as the document authors. All rights reserved.</p>
    524       <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
    525          and restrictions with respect to this document. Code Components extracted from this document must include Simplified BSD License
    526          text as described in Section 4.e of the Trust Legal Provisions and are provided without warranty as described in the BSD License.
    527       </p>
    528       <p>This document may contain material from IETF Documents or IETF Contributions published or made publicly available before November
    529          10, 2008. The person(s) controlling the copyright in some of this material may not have granted the IETF Trust the right to
    530          allow modifications of such material outside the IETF Standards Process. Without obtaining an adequate license from the person(s)
    531          controlling the copyright in such materials, this document may not be modified outside the IETF Standards Process, and derivative
    532          works of it may not be created outside the IETF Standards Process, except to format it for publication as an RFC or to translate
    533          it into languages other than English.
    534       </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 to IETF 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), its areas, and its working groups. Note
     521            that other groups may also distribute working documents as Internet-Drafts.
     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>The list of current Internet-Drafts can be accessed at <a href="http://www.ietf.org/ietf/1id-abstracts.txt">http://www.ietf.org/ietf/1id-abstracts.txt</a>.
     528         </p>
     529         <p>The list of Internet-Draft Shadow Directories can be accessed at <a href="http://www.ietf.org/shadow.html">http://www.ietf.org/shadow.html</a>.
     530         </p>
     531         <p>This Internet-Draft will expire on September 9, 2010.</p>
     532      </div>
     533      <div id="rfc.copyrightnotice">
     534         <h1><a href="#rfc.copyrightnotice">Copyright Notice</a></h1>
     535         <p>Copyright © 2010 IETF Trust and the persons identified as the document authors. All rights reserved.</p>
     536         <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
     537            and restrictions with respect to this document. Code Components extracted from this document must include Simplified BSD License
     538            text as described in Section 4.e of the Trust Legal Provisions and are provided without warranty as described in the BSD License.
     539         </p>
     540         <p>This document may contain material from IETF Documents or IETF Contributions published or made publicly available before November
     541            10, 2008. The person(s) controlling the copyright in some of this material may not have granted the IETF Trust the right to
     542            allow modifications of such material outside the IETF Standards Process. Without obtaining an adequate license from the person(s)
     543            controlling the copyright in such materials, this document may not be modified outside the IETF Standards Process, and derivative
     544            works of it may not be created outside the IETF Standards Process, except to format it for publication as an RFC or to translate
     545            it into languages other than English.
     546         </p>
     547      </div>
    535548      <hr class="noprint">
    536549      <h1 class="np" id="rfc.toc"><a href="#rfc.toc">Table of Contents</a></h1>
    537550      <ul class="toc">
    538          <li class="tocline0">1.&nbsp;&nbsp;&nbsp;<a href="#caching">Introduction</a><ul class="toc">
    539                <li class="tocline1">1.1&nbsp;&nbsp;&nbsp;<a href="#intro.purpose">Purpose</a></li>
    540                <li class="tocline1">1.2&nbsp;&nbsp;&nbsp;<a href="#intro.terminology">Terminology</a></li>
    541                <li class="tocline1">1.3&nbsp;&nbsp;&nbsp;<a href="#intro.requirements">Requirements</a></li>
    542                <li class="tocline1">1.4&nbsp;&nbsp;&nbsp;<a href="#notation">Syntax Notation</a><ul class="toc">
    543                      <li class="tocline1">1.4.1&nbsp;&nbsp;&nbsp;<a href="#core.rules">Core Rules</a></li>
    544                      <li class="tocline1">1.4.2&nbsp;&nbsp;&nbsp;<a href="#abnf.dependencies">ABNF Rules defined in other Parts of the Specification</a></li>
     551         <li><a href="#rfc.section.1">1.</a>&nbsp;&nbsp;&nbsp;<a href="#caching">Introduction</a><ul>
     552               <li><a href="#rfc.section.1.1">1.1</a>&nbsp;&nbsp;&nbsp;<a href="#intro.purpose">Purpose</a></li>
     553               <li><a href="#rfc.section.1.2">1.2</a>&nbsp;&nbsp;&nbsp;<a href="#intro.terminology">Terminology</a></li>
     554               <li><a href="#rfc.section.1.3">1.3</a>&nbsp;&nbsp;&nbsp;<a href="#intro.requirements">Requirements</a></li>
     555               <li><a href="#rfc.section.1.4">1.4</a>&nbsp;&nbsp;&nbsp;<a href="#notation">Syntax Notation</a><ul>
     556                     <li><a href="#rfc.section.1.4.1">1.4.1</a>&nbsp;&nbsp;&nbsp;<a href="#core.rules">Core Rules</a></li>
     557                     <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>
    545558                  </ul>
    546559               </li>
    547560            </ul>
    548561         </li>
    549          <li class="tocline0">2.&nbsp;&nbsp;&nbsp;<a href="#caching.overview">Cache Operation</a><ul class="toc">
    550                <li class="tocline1">2.1&nbsp;&nbsp;&nbsp;<a href="#response.cacheability">Response Cacheability</a><ul class="toc">
    551                      <li class="tocline1">2.1.1&nbsp;&nbsp;&nbsp;<a href="#errors.or.incomplete.response.cache.behavior">Storing Partial and Incomplete Responses</a></li>
     562         <li><a href="#rfc.section.2">2.</a>&nbsp;&nbsp;&nbsp;<a href="#caching.overview">Cache Operation</a><ul>
     563               <li><a href="#rfc.section.2.1">2.1</a>&nbsp;&nbsp;&nbsp;<a href="#response.cacheability">Response Cacheability</a><ul>
     564                     <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>
    552565                  </ul>
    553566               </li>
    554                <li class="tocline1">2.2&nbsp;&nbsp;&nbsp;<a href="#constructing.responses.from.caches">Constructing Responses from Caches</a></li>
    555                <li class="tocline1">2.3&nbsp;&nbsp;&nbsp;<a href="#expiration.model">Freshness Model</a><ul class="toc">
    556                      <li class="tocline1">2.3.1&nbsp;&nbsp;&nbsp;<a href="#calculating.freshness.lifetime">Calculating Freshness Lifetime</a><ul class="toc">
    557                            <li class="tocline1">2.3.1.1&nbsp;&nbsp;&nbsp;<a href="#heuristic.freshness">Calculating Heuristic Freshness</a></li>
    558                         </ul>
    559                      </li>
    560                      <li class="tocline1">2.3.2&nbsp;&nbsp;&nbsp;<a href="#age.calculations">Calculating Age</a></li>
    561                      <li class="tocline1">2.3.3&nbsp;&nbsp;&nbsp;<a href="#serving.stale.responses">Serving Stale Responses</a></li>
     567               <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>
     568               <li><a href="#rfc.section.2.3">2.3</a>&nbsp;&nbsp;&nbsp;<a href="#expiration.model">Freshness Model</a><ul>
     569                     <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>
     570                     <li><a href="#rfc.section.2.3.2">2.3.2</a>&nbsp;&nbsp;&nbsp;<a href="#age.calculations">Calculating Age</a></li>
     571                     <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>
    562572                  </ul>
    563573               </li>
    564                <li class="tocline1">2.4&nbsp;&nbsp;&nbsp;<a href="#validation.model">Validation Model</a></li>
    565                <li class="tocline1">2.5&nbsp;&nbsp;&nbsp;<a href="#invalidation.after.updates.or.deletions">Request Methods that Invalidate</a></li>
    566                <li class="tocline1">2.6&nbsp;&nbsp;&nbsp;<a href="#caching.negotiated.responses">Caching Negotiated Responses</a></li>
    567                <li class="tocline1">2.7&nbsp;&nbsp;&nbsp;<a href="#combining.headers">Combining Responses</a></li>
     574               <li><a href="#rfc.section.2.4">2.4</a>&nbsp;&nbsp;&nbsp;<a href="#validation.model">Validation Model</a></li>
     575               <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>
     576               <li><a href="#rfc.section.2.6">2.6</a>&nbsp;&nbsp;&nbsp;<a href="#caching.negotiated.responses">Caching Negotiated Responses</a></li>
     577               <li><a href="#rfc.section.2.7">2.7</a>&nbsp;&nbsp;&nbsp;<a href="#combining.headers">Combining Responses</a></li>
    568578            </ul>
    569579         </li>
    570          <li class="tocline0">3.&nbsp;&nbsp;&nbsp;<a href="#header.fields">Header Field Definitions</a><ul class="toc">
    571                <li class="tocline1">3.1&nbsp;&nbsp;&nbsp;<a href="#header.age">Age</a></li>
    572                <li class="tocline1">3.2&nbsp;&nbsp;&nbsp;<a href="#header.cache-control">Cache-Control</a><ul class="toc">
    573                      <li class="tocline1">3.2.1&nbsp;&nbsp;&nbsp;<a href="#cache-request-directive">Request Cache-Control Directives</a></li>
    574                      <li class="tocline1">3.2.2&nbsp;&nbsp;&nbsp;<a href="#cache-response-directive">Response Cache-Control Directives</a></li>
    575                      <li class="tocline1">3.2.3&nbsp;&nbsp;&nbsp;<a href="#cache.control.extensions">Cache Control Extensions</a></li>
     580         <li><a href="#rfc.section.3">3.</a>&nbsp;&nbsp;&nbsp;<a href="#header.fields">Header Field Definitions</a><ul>
     581               <li><a href="#rfc.section.3.1">3.1</a>&nbsp;&nbsp;&nbsp;<a href="#header.age">Age</a></li>
     582               <li><a href="#rfc.section.3.2">3.2</a>&nbsp;&nbsp;&nbsp;<a href="#header.cache-control">Cache-Control</a><ul>
     583                     <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>
     584                     <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>
     585                     <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>
    576586                  </ul>
    577587               </li>
    578                <li class="tocline1">3.3&nbsp;&nbsp;&nbsp;<a href="#header.expires">Expires</a></li>
    579                <li class="tocline1">3.4&nbsp;&nbsp;&nbsp;<a href="#header.pragma">Pragma</a></li>
    580                <li class="tocline1">3.5&nbsp;&nbsp;&nbsp;<a href="#header.vary">Vary</a></li>
    581                <li class="tocline1">3.6&nbsp;&nbsp;&nbsp;<a href="#header.warning">Warning</a></li>
     588               <li><a href="#rfc.section.3.3">3.3</a>&nbsp;&nbsp;&nbsp;<a href="#header.expires">Expires</a></li>
     589               <li><a href="#rfc.section.3.4">3.4</a>&nbsp;&nbsp;&nbsp;<a href="#header.pragma">Pragma</a></li>
     590               <li><a href="#rfc.section.3.5">3.5</a>&nbsp;&nbsp;&nbsp;<a href="#header.vary">Vary</a></li>
     591               <li><a href="#rfc.section.3.6">3.6</a>&nbsp;&nbsp;&nbsp;<a href="#header.warning">Warning</a></li>
    582592            </ul>
    583593         </li>
    584          <li class="tocline0">4.&nbsp;&nbsp;&nbsp;<a href="#history.lists">History Lists</a></li>
    585          <li class="tocline0">5.&nbsp;&nbsp;&nbsp;<a href="#IANA.considerations">IANA Considerations</a><ul class="toc">
    586                <li class="tocline1">5.1&nbsp;&nbsp;&nbsp;<a href="#message.header.registration">Message Header Registration</a></li>
     594         <li><a href="#rfc.section.4">4.</a>&nbsp;&nbsp;&nbsp;<a href="#history.lists">History Lists</a></li>
     595         <li><a href="#rfc.section.5">5.</a>&nbsp;&nbsp;&nbsp;<a href="#IANA.considerations">IANA Considerations</a><ul>
     596               <li><a href="#rfc.section.5.1">5.1</a>&nbsp;&nbsp;&nbsp;<a href="#message.header.registration">Message Header Registration</a></li>
    587597            </ul>
    588598         </li>
    589          <li class="tocline0">6.&nbsp;&nbsp;&nbsp;<a href="#security.considerations">Security Considerations</a></li>
    590          <li class="tocline0">7.&nbsp;&nbsp;&nbsp;<a href="#ack">Acknowledgments</a></li>
    591          <li class="tocline0">8.&nbsp;&nbsp;&nbsp;<a href="#rfc.references">References</a><ul class="toc">
    592                <li class="tocline1">8.1&nbsp;&nbsp;&nbsp;<a href="#rfc.references.1">Normative References</a></li>
    593                <li class="tocline1">8.2&nbsp;&nbsp;&nbsp;<a href="#rfc.references.2">Informative References</a></li>
     599         <li><a href="#rfc.section.6">6.</a>&nbsp;&nbsp;&nbsp;<a href="#security.considerations">Security Considerations</a></li>
     600         <li><a href="#rfc.section.7">7.</a>&nbsp;&nbsp;&nbsp;<a href="#ack">Acknowledgments</a></li>
     601         <li><a href="#rfc.section.8">8.</a>&nbsp;&nbsp;&nbsp;<a href="#rfc.references">References</a><ul>
     602               <li><a href="#rfc.section.8.1">8.1</a>&nbsp;&nbsp;&nbsp;<a href="#rfc.references.1">Normative References</a></li>
     603               <li><a href="#rfc.section.8.2">8.2</a>&nbsp;&nbsp;&nbsp;<a href="#rfc.references.2">Informative References</a></li>
    594604            </ul>
    595605         </li>
    596          <li class="tocline0"><a href="#rfc.authors">Authors' Addresses</a></li>
    597          <li class="tocline0">A.&nbsp;&nbsp;&nbsp;<a href="#compatibility">Compatibility with Previous Versions</a><ul class="toc">
    598                <li class="tocline1">A.1&nbsp;&nbsp;&nbsp;<a href="#changes.from.rfc.2068">Changes from RFC 2068</a></li>
    599                <li class="tocline1">A.2&nbsp;&nbsp;&nbsp;<a href="#changes.from.rfc.2616">Changes from RFC 2616</a></li>
     606         <li><a href="#rfc.section.A">A.</a>&nbsp;&nbsp;&nbsp;<a href="#compatibility">Compatibility with Previous Versions</a><ul>
     607               <li><a href="#rfc.section.A.1">A.1</a>&nbsp;&nbsp;&nbsp;<a href="#changes.from.rfc.2068">Changes from RFC 2068</a></li>
     608               <li><a href="#rfc.section.A.2">A.2</a>&nbsp;&nbsp;&nbsp;<a href="#changes.from.rfc.2616">Changes from RFC 2616</a></li>
    600609            </ul>
    601610         </li>
    602          <li class="tocline0">B.&nbsp;&nbsp;&nbsp;<a href="#collected.abnf">Collected ABNF</a></li>
    603          <li class="tocline0">C.&nbsp;&nbsp;&nbsp;<a href="#change.log">Change Log (to be removed by RFC Editor before publication)</a><ul class="toc">
    604                <li class="tocline1">C.1&nbsp;&nbsp;&nbsp;<a href="#rfc.section.C.1">Since RFC2616</a></li>
    605                <li class="tocline1">C.2&nbsp;&nbsp;&nbsp;<a href="#rfc.section.C.2">Since draft-ietf-httpbis-p6-cache-00</a></li>
    606                <li class="tocline1">C.3&nbsp;&nbsp;&nbsp;<a href="#rfc.section.C.3">Since draft-ietf-httpbis-p6-cache-01</a></li>
    607                <li class="tocline1">C.4&nbsp;&nbsp;&nbsp;<a href="#changes.since.02">Since draft-ietf-httpbis-p6-cache-02</a></li>
    608                <li class="tocline1">C.5&nbsp;&nbsp;&nbsp;<a href="#changes.since.03">Since draft-ietf-httpbis-p6-cache-03</a></li>
    609                <li class="tocline1">C.6&nbsp;&nbsp;&nbsp;<a href="#changes.since.04">Since draft-ietf-httpbis-p6-cache-04</a></li>
    610                <li class="tocline1">C.7&nbsp;&nbsp;&nbsp;<a href="#changes.since.05">Since draft-ietf-httpbis-p6-cache-05</a></li>
    611                <li class="tocline1">C.8&nbsp;&nbsp;&nbsp;<a href="#changes.since.06">Since draft-ietf-httpbis-p6-cache-06</a></li>
    612                <li class="tocline1">C.9&nbsp;&nbsp;&nbsp;<a href="#changes.since.07">Since draft-ietf-httpbis-p6-cache-07</a></li>
    613                <li class="tocline1">C.10&nbsp;&nbsp;&nbsp;<a href="#changes.since.08">Since draft-ietf-httpbis-p6-cache-08</a></li>
     611         <li><a href="#rfc.section.B">B.</a>&nbsp;&nbsp;&nbsp;<a href="#collected.abnf">Collected ABNF</a></li>
     612         <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>
     613               <li><a href="#rfc.section.C.1">C.1</a>&nbsp;&nbsp;&nbsp;<a href="#rfc.section.C.1">Since RFC2616</a></li>
     614               <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>
     615               <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>
     616               <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>
     617               <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>
     618               <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>
     619               <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>
     620               <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>
     621               <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>
     622               <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>
    614623            </ul>
    615624         </li>
    616          <li class="tocline0"><a href="#rfc.index">Index</a></li>
     625         <li><a href="#rfc.index">Index</a></li>
     626         <li><a href="#rfc.authors">Authors' Addresses</a></li>
    617627      </ul>
    618       <h1 id="rfc.section.1" class="np"><a href="#rfc.section.1">1.</a>&nbsp;<a id="caching" href="#caching">Introduction</a></h1>
    619       <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.
    620          This document defines aspects of HTTP/1.1 related to caching and reusing response messages.
    621       </p>
    622       <div id="rfc.iref.c.1"></div>
    623       <h2 id="rfc.section.1.1"><a href="#rfc.section.1.1">1.1</a>&nbsp;<a id="intro.purpose" href="#intro.purpose">Purpose</a></h2>
    624       <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
    625          stores cacheable responses in order to reduce the response time and network bandwidth consumption on future, equivalent requests.
    626          Any client or server may include a cache, though a cache cannot be used by a server that is acting as a tunnel.
    627       </p>
    628       <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
    629          response message to satisfy a current request. In some cases, a stored response can be reused without the need for a network
    630          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
    631          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>).
    632       </p>
    633       <h2 id="rfc.section.1.2"><a href="#rfc.section.1.2">1.2</a>&nbsp;<a id="intro.terminology" href="#intro.terminology">Terminology</a></h2>
    634       <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>
    635       <p id="rfc.section.1.2.p.2"> <span id="rfc.iref.c.2"></span>  <dfn>cacheable</dfn> 
    636       </p>
    637       <ul class="empty">
    638          <li>A response is cacheable if a cache is allowed to store a copy of the response message for use in answering subsequent requests.
    639             Even when a response is cacheable, there may be additional constraints on whether a cache can use the cached copy to satisfy
    640             a particular request.
    641          </li>
    642       </ul>
    643       <p id="rfc.section.1.2.p.3"> <span id="rfc.iref.e.1"></span>  <dfn>explicit expiration time</dfn> 
    644       </p>
    645       <ul class="empty">
    646          <li>The time at which the origin server intends that an entity should no longer be returned by a cache without further validation.</li>
    647       </ul>
    648       <p id="rfc.section.1.2.p.4"> <span id="rfc.iref.h.1"></span>  <dfn>heuristic expiration time</dfn> 
    649       </p>
    650       <ul class="empty">
    651          <li>An expiration time assigned by a cache when no explicit expiration time is available.</li>
    652       </ul>
    653       <p id="rfc.section.1.2.p.5"> <span id="rfc.iref.a.1"></span>  <dfn>age</dfn> 
    654       </p>
    655       <ul class="empty">
    656          <li>The age of a response is the time since it was sent by, or successfully validated with, the origin server.</li>
    657       </ul>
    658       <p id="rfc.section.1.2.p.6"> <span id="rfc.iref.f.1"></span>  <dfn>first-hand</dfn> 
    659       </p>
    660       <ul class="empty">
    661          <li>A response is first-hand if the freshness model is not in use; i.e., its age is 0.</li>
    662       </ul>
    663       <p id="rfc.section.1.2.p.7"> <span id="rfc.iref.f.2"></span>  <dfn>freshness lifetime</dfn> 
    664       </p>
    665       <ul class="empty">
    666          <li>The length of time between the generation of a response and its expiration time.</li>
    667       </ul>
    668       <p id="rfc.section.1.2.p.8"> <span id="rfc.iref.f.3"></span>  <dfn>fresh</dfn> 
    669       </p>
    670       <ul class="empty">
    671          <li>A response is fresh if its age has not yet exceeded its freshness lifetime.</li>
    672       </ul>
    673       <p id="rfc.section.1.2.p.9"> <span id="rfc.iref.s.1"></span>  <dfn>stale</dfn> 
    674       </p>
    675       <ul class="empty">
    676          <li>A response is stale if its age has passed its freshness lifetime (either explicit or heuristic).</li>
    677       </ul>
    678       <p id="rfc.section.1.2.p.10"> <span id="rfc.iref.v.1"></span>  <dfn>validator</dfn> 
    679       </p>
    680       <ul class="empty">
    681          <li>A protocol element (e.g., an entity tag or a Last-Modified time) that is used to find out whether a stored response is an
    682             equivalent copy of an entity.
    683          </li>
    684       </ul>
    685       <div id="shared.and.non-shared.caches">
    686          <p id="rfc.section.1.2.p.11"> <span id="rfc.iref.v.2"></span>  <dfn>shared cache</dfn> 
     628      <div id="caching">
     629         <h1 id="rfc.section.1" class="np"><a href="#rfc.section.1">1.</a>&nbsp;<a href="#caching">Introduction</a></h1>
     630         <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.
     631            This document defines aspects of HTTP/1.1 related to caching and reusing response messages.
    687632         </p>
    688          <ul class="empty">
    689             <li>A cache that is accessible to more than one user. A non-shared cache is dedicated to a single user.</li>
    690          </ul>
    691       </div>
    692       <h2 id="rfc.section.1.3"><a href="#rfc.section.1.3">1.3</a>&nbsp;<a id="intro.requirements" href="#intro.requirements">Requirements</a></h2>
    693       <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"
    694          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>.
    695       </p>
    696       <p id="rfc.section.1.3.p.2">An implementation is not compliant if it fails to satisfy one or more of the <em class="bcp14">MUST</em> or <em class="bcp14">REQUIRED</em> level requirements for the protocols it implements. An implementation that satisfies all the <em class="bcp14">MUST</em> or <em class="bcp14">REQUIRED</em> level and all the <em class="bcp14">SHOULD</em> level requirements for its protocols is said to be "unconditionally compliant"; one that satisfies all the <em class="bcp14">MUST</em> level requirements but not all the <em class="bcp14">SHOULD</em> level requirements for its protocols is said to be "conditionally compliant."
    697       </p>
    698       <h2 id="rfc.section.1.4"><a href="#rfc.section.1.4">1.4</a>&nbsp;<a id="notation" href="#notation">Syntax Notation</a></h2>
    699       <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.
    700       </p>
    701       <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="http://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
    702          (hexadecimal 0-9/A-F/a-f), LF (line feed), OCTET (any 8-bit sequence of data), SP (space), VCHAR (any visible USASCII character),
    703          and WSP (whitespace).
    704       </p>
    705       <h3 id="rfc.section.1.4.1"><a href="#rfc.section.1.4.1">1.4.1</a>&nbsp;<a id="core.rules" href="#core.rules">Core Rules</a></h3>
    706       <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>:
    707       </p>
    708       <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;
     633         <div id="intro.purpose">
     634            <div id="rfc.iref.c.1"></div>
     635            <h2 id="rfc.section.1.1"><a href="#rfc.section.1.1">1.1</a>&nbsp;<a href="#intro.purpose">Purpose</a></h2>
     636            <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
     637               stores cacheable responses in order to reduce the response time and network bandwidth consumption on future, equivalent requests.
     638               Any client or server may include a cache, though a cache cannot be used by a server that is acting as a tunnel.
     639            </p>
     640            <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
     641               response message to satisfy a current request. In some cases, a stored response can be reused without the need for a network
     642               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
     643               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>).
     644            </p>
     645         </div>
     646         <div id="intro.terminology">
     647            <h2 id="rfc.section.1.2"><a href="#rfc.section.1.2">1.2</a>&nbsp;<a href="#intro.terminology">Terminology</a></h2>
     648            <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>
     649            <p id="rfc.section.1.2.p.2"><span id="rfc.iref.c.2"></span> <dfn>cacheable</dfn>
     650            </p>
     651            <ul class="empty">
     652               <li>A response is cacheable if a cache is allowed to store a copy of the response message for use in answering subsequent requests.
     653                  Even when a response is cacheable, there may be additional constraints on whether a cache can use the cached copy to satisfy
     654                  a particular request.
     655               </li>
     656            </ul>
     657            <p id="rfc.section.1.2.p.3"><span id="rfc.iref.e.1"></span> <dfn>explicit expiration time</dfn>
     658            </p>
     659            <ul class="empty">
     660               <li>The time at which the origin server intends that an entity should no longer be returned by a cache without further validation.</li>
     661            </ul>
     662            <p id="rfc.section.1.2.p.4"><span id="rfc.iref.h.1"></span> <dfn>heuristic expiration time</dfn>
     663            </p>
     664            <ul class="empty">
     665               <li>An expiration time assigned by a cache when no explicit expiration time is available.</li>
     666            </ul>
     667            <p id="rfc.section.1.2.p.5"><span id="rfc.iref.a.1"></span> <dfn>age</dfn>
     668            </p>
     669            <ul class="empty">
     670               <li>The age of a response is the time since it was sent by, or successfully validated with, the origin server.</li>
     671            </ul>
     672            <p id="rfc.section.1.2.p.6"><span id="rfc.iref.f.1"></span> <dfn>first-hand</dfn>
     673            </p>
     674            <ul class="empty">
     675               <li>A response is first-hand if the freshness model is not in use; i.e., its age is 0.</li>
     676            </ul>
     677            <p id="rfc.section.1.2.p.7"><span id="rfc.iref.f.2"></span> <dfn>freshness lifetime</dfn>
     678            </p>
     679            <ul class="empty">
     680               <li>The length of time between the generation of a response and its expiration time.</li>
     681            </ul>
     682            <p id="rfc.section.1.2.p.8"><span id="rfc.iref.f.3"></span> <dfn>fresh</dfn>
     683            </p>
     684            <ul class="empty">
     685               <li>A response is fresh if its age has not yet exceeded its freshness lifetime.</li>
     686            </ul>
     687            <p id="rfc.section.1.2.p.9"><span id="rfc.iref.s.1"></span> <dfn>stale</dfn>
     688            </p>
     689            <ul class="empty">
     690               <li>A response is stale if its age has passed its freshness lifetime (either explicit or heuristic).</li>
     691            </ul>
     692            <p id="rfc.section.1.2.p.10"><span id="rfc.iref.v.1"></span> <dfn>validator</dfn>
     693            </p>
     694            <ul class="empty">
     695               <li>A protocol element (e.g., an entity tag or a Last-Modified time) that is used to find out whether a stored response is an
     696                  equivalent copy of an entity.
     697               </li>
     698            </ul>
     699            <div id="shared.and.non-shared.caches">
     700               <p id="rfc.section.1.2.p.11"><span id="rfc.iref.v.2"></span> <dfn>shared cache</dfn>
     701               </p>
     702               <ul class="empty">
     703                  <li>A cache that is accessible to more than one user. A non-shared cache is dedicated to a single user.</li>
     704               </ul>
     705            </div>
     706         </div>
     707         <div id="intro.requirements">
     708            <h2 id="rfc.section.1.3"><a href="#rfc.section.1.3">1.3</a>&nbsp;<a href="#intro.requirements">Requirements</a></h2>
     709            <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"
     710               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>.
     711            </p>
     712            <p id="rfc.section.1.3.p.2">An implementation is not compliant if it fails to satisfy one or more of the <em class="bcp14">MUST</em> or <em class="bcp14">REQUIRED</em> level requirements for the protocols it implements. An implementation that satisfies all the <em class="bcp14">MUST</em> or <em class="bcp14">REQUIRED</em> level and all the <em class="bcp14">SHOULD</em> level requirements for its protocols is said to be "unconditionally compliant"; one that satisfies all the <em class="bcp14">MUST</em> level requirements but not all the <em class="bcp14">SHOULD</em> 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;
    709728  <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;
    710729  <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;
    711 </pre><h3 id="rfc.section.1.4.2"><a href="#rfc.section.1.4.2">1.4.2</a>&nbsp;<a id="abnf.dependencies" href="#abnf.dependencies">ABNF Rules defined in other Parts of the Specification</a></h3>
    712       <p id="rfc.section.1.4.2.p.1">The ABNF rules below are defined in other parts:</p>
    713       <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;
     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;
    714735  <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;
    715736  <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;
    716737  <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;
    717738  <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;
    718 </pre><h1 id="rfc.section.2"><a href="#rfc.section.2">2.</a>&nbsp;<a id="caching.overview" href="#caching.overview">Cache Operation</a></h1>
    719       <h2 id="rfc.section.2.1"><a href="#rfc.section.2.1">2.1</a>&nbsp;<a id="response.cacheability" href="#response.cacheability">Response Cacheability</a></h2>
    720       <p id="rfc.section.2.1.p.1">A cache <em class="bcp14">MUST NOT</em> store a response to any request, unless:
    721       </p>
    722       <ul>
    723          <li>The request method is understood by the cache and defined as being cacheable, and</li>
    724          <li>the response status code is understood by the cache, and</li>
    725          <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
    726          </li>
    727          <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
    728          </li>
    729          <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 "public" directive is present; see <a href="#header.cache-control" id="rfc.xref.header.cache-control.2" title="Cache-Control">Section&nbsp;3.2</a>), and
    730          </li>
    731          <li>the response either:
     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>
    732748            <ul>
    733                <li>contains an Expires header (see <a href="#header.expires" id="rfc.xref.header.expires.1" title="Expires">Section&nbsp;3.3</a>), or
    734                </li>
    735                <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
    736                </li>
    737                <li>contains a s-maxage response cache directive and the cache is shared, or</li>
    738                <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
    739                </li>
    740                <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>).
    741                </li>
    742             </ul>
    743          </li>
    744       </ul>
    745       <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
    746          cache-specific behaviour. In particular, 206 Partial Content responses cannot be cached by an implementation that does not
    747          handle partial content (see <a href="#errors.or.incomplete.response.cache.behavior" title="Storing Partial and Incomplete Responses">Section&nbsp;2.1.1</a>).
    748       </p>
    749       <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
    750          time, as such responses are not usually useful to store. However, caches are not prohibited from storing such responses.
    751       </p>
    752       <h3 id="rfc.section.2.1.1"><a href="#rfc.section.2.1.1">2.1.1</a>&nbsp;<a id="errors.or.incomplete.response.cache.behavior" href="#errors.or.incomplete.response.cache.behavior">Storing Partial and Incomplete Responses</a></h3>
    753       <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)
    754          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.
    755       </p>
    756       <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.
    757       </p>
    758       <h2 id="rfc.section.2.2"><a href="#rfc.section.2.2">2.2</a>&nbsp;<a id="constructing.responses.from.caches" href="#constructing.responses.from.caches">Constructing Responses from Caches</a></h2>
    759       <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:
    760       </p>
    761       <ul>
    762          <li>The presented Request-URI and that of the stored response match (<span class="comment" id="TODO-Request-URI">[<a href="#TODO-Request-URI" class="smpl">TODO-Request-URI</a>: Need to find a new term for this, as Part 1 doesn't define Request-URI anymore; the new term request-target does not work
    763                for this. (see &lt;<a href="http://tools.ietf.org/wg/httpbis/trac/ticket/196">http://tools.ietf.org/wg/httpbis/trac/ticket/196</a>&gt;)]</span>), and
    764          </li>
    765          <li>the request method associated with the stored response allows it to be used for the presented request, and</li>
    766          <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.6</a>), and
    767          </li>
    768          <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.3" 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
    769          </li>
    770          <li>the stored response is either:
     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 "public" directive is present; see <a href="#header.cache-control" id="rfc.xref.header.cache-control.2" title="Cache-Control">Section&nbsp;3.2</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>
    771791            <ul>
    772                <li>fresh (see <a href="#expiration.model" title="Freshness Model">Section&nbsp;2.3</a>), or
    773                </li>
    774                <li>allowed to be served stale (see <a href="#serving.stale.responses" title="Serving Stale Responses">Section&nbsp;2.3.3</a>), or
    775                </li>
    776                <li>successfully validated (see <a href="#validation.model" title="Validation Model">Section&nbsp;2.4</a>).
    777                </li>
    778             </ul>
    779          </li>
    780       </ul>
    781       <p id="rfc.section.2.2.p.2"> <span class="comment" id="TODO-method-cacheability">[<a href="#TODO-method-cacheability" class="smpl">TODO-method-cacheability</a>: define method cacheability for GET, HEAD and POST in p2-semantics.]</span>
    782       </p>
    783       <p id="rfc.section.2.2.p.3">When a stored response is used to satisfy a request, 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>. <span class="comment" id="DISCUSS-includes-validated">[<a href="#DISCUSS-includes-validated" class="smpl">DISCUSS-includes-validated</a>: this currently includes successfully validated responses.]</span>
    784       </p>
    785       <p id="rfc.section.2.2.p.4">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
    786          the request and having received a corresponding response.
    787       </p>
    788       <p id="rfc.section.2.2.p.5">Also, note that unsafe requests might invalidate already stored responses; see <a href="#invalidation.after.updates.or.deletions" title="Request Methods that Invalidate">Section&nbsp;2.5</a>.
    789       </p>
    790       <p id="rfc.section.2.2.p.6">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
    791          forward a request with "Cache-Control: max-age=0" or "Cache-Control: no-cache" to disambiguate which response to use.
    792       </p>
    793       <p id="rfc.section.2.2.p.7"> <span class="comment" id="TODO-header-properties">[<a href="#TODO-header-properties" class="smpl">TODO-header-properties</a>: end-to-end and hop-by-hop headers, non-modifiable headers removed; re-spec in p1]</span>
    794       </p>
    795       <h2 id="rfc.section.2.3"><a href="#rfc.section.2.3">2.3</a>&nbsp;<a id="expiration.model" href="#expiration.model">Freshness Model</a></h2>
    796       <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,
    797          thereby improving efficiency.
    798       </p>
    799       <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,
    800          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 entity is not
    801          likely to change in a semantically significant way before the expiration time is reached.
    802       </p>
    803       <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.
    804          This means that the response is always stale, so that caches should validate it before using it for subsequent requests. <span class="comment" id="TODO-response-stale">[<a href="#TODO-response-stale" class="smpl">TODO-response-stale</a>: This wording may cause confusion, because the response may still be served stale.]</span>
    805       </p>
    806       <p id="rfc.section.2.3.p.4">Since origin servers do not always provide explicit expiration times, HTTP caches may also assign heuristic expiration times
    807          when they are not specified, employing algorithms that use other header values (such as the Last-Modified time) to estimate
    808          a plausible expiration time. The HTTP/1.1 specification does not provide specific algorithms, but does impose worst-case constraints
    809          on their results.
    810       </p>
    811       <div id="rfc.figure.u.3"></div>
    812       <p>The calculation to determine if a response is fresh is:</p>  <pre class="text">   response_is_fresh = (freshness_lifetime &gt; current_age)
    813 </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>.
    814       </p>
    815       <p id="rfc.section.2.3.p.7">Additionally, clients may need to influence freshness calculation. They can do this using several request cache directives,
    816          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>.
    817       </p>
    818       <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>
    819       </p>
    820       <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
    821          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.
    822       </p>
    823       <h3 id="rfc.section.2.3.1"><a href="#rfc.section.2.3.1">2.3.1</a>&nbsp;<a id="calculating.freshness.lifetime" href="#calculating.freshness.lifetime">Calculating Freshness Lifetime</a></h3>
    824       <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>
    825       <ul>
    826          <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
    827          </li>
    828          <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
    829          </li>
    830          <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
    831          </li>
    832          <li>Otherwise, no explicit expiration time is present in the response, but a heuristic may be used; see <a href="#heuristic.freshness" title="Calculating Heuristic Freshness">Section&nbsp;2.3.1.1</a>.
    833          </li>
    834       </ul>
    835       <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>
    836       <h4 id="rfc.section.2.3.1.1"><a href="#rfc.section.2.3.1.1">2.3.1.1</a>&nbsp;<a id="heuristic.freshness" href="#heuristic.freshness">Calculating Heuristic Freshness</a></h4>
    837       <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 of 200, 203, 206, 300, 301 or 410, a
    838          heuristic expiration time can be calculated. Heuristics <em class="bcp14">MUST NOT</em> be used for other response status codes.
    839       </p>
    840       <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
    841          not already present.
    842       </p>
    843       <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%.
    844       </p>
    845       <p id="rfc.section.2.3.1.1.p.4"> <span class="comment" id="REVIEW-query-string-heuristics">[<a href="#REVIEW-query-string-heuristics" class="smpl">REVIEW-query-string-heuristics</a>: took away HTTP/1.0 query string heuristic uncacheability.]</span>
    846       </p>
    847       <h3 id="rfc.section.2.3.2"><a href="#rfc.section.2.3.2">2.3.2</a>&nbsp;<a id="age.calculations" href="#age.calculations">Calculating Age</a></h3>
    848       <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
    849          Age field value is the cache's estimate of the amount of time since the response was generated or validated by the origin
    850          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
    851          path from the origin server, plus the amount of time it has been in transit along network paths.
    852       </p>
    853       <p id="rfc.section.2.3.2.p.2">The term "age_value" denotes the value of the Age header, in a form appropriate for arithmetic operations.</p>
    854       <p id="rfc.section.2.3.2.p.3">HTTP/1.1 requires origin servers to send a Date header, if possible, with every response, giving the time at which the response
    855          was generated (see <a href="p1-messaging.html#header.date" title="Date">Section 9.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>). The term "date_value" denotes the value of the Date header, in a form appropriate for arithmetic operations.
    856       </p>
    857       <p id="rfc.section.2.3.2.p.4">The term "now" means "the current value of the clock at the host performing the calculation." Hosts that use HTTP, but especially
    858          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.
    859       </p>
    860       <p id="rfc.section.2.3.2.p.5">A response's age can be calculated in two entirely independent ways: </p>
    861       <ol>
    862          <li>now minus date_value, if the local clock is reasonably well synchronized to the origin server's clock. If the result is negative,
    863             the result is replaced by zero.
    864          </li>
    865          <li>age_value, if all of the caches along the response path implement HTTP/1.1.</li>
    866       </ol>
    867       <div id="rfc.figure.u.4"></div>
    868       <p>These are combined as</p>  <pre class="text">    corrected_received_age = max(now - date_value, age_value)
     792               <li>The presented Request-URI and that of the stored response match (<span class="comment" id="TODO-Request-URI">[<a href="#TODO-Request-URI" class="smpl">TODO-Request-URI</a>: Need to find a new term for this, as Part 1 doesn't define Request-URI anymore; the new term request-target does not work
     793                     for this. (see &lt;<a href="http://tools.ietf.org/wg/httpbis/trac/ticket/196">http://tools.ietf.org/wg/httpbis/trac/ticket/196</a>&gt;)]</span>), and
     794               </li>
     795               <li>the request method associated with the stored response allows it to be used for the presented request, and</li>
     796               <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.6</a>), and
     797               </li>
     798               <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.3" 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
     799               </li>
     800               <li>the stored response is either:
     801                  <ul>
     802                     <li>fresh (see <a href="#expiration.model" title="Freshness Model">Section&nbsp;2.3</a>), or
     803                     </li>
     804                     <li>allowed to be served stale (see <a href="#serving.stale.responses" title="Serving Stale Responses">Section&nbsp;2.3.3</a>), or
     805                     </li>
     806                     <li>successfully validated (see <a href="#validation.model" title="Validation Model">Section&nbsp;2.4</a>).
     807                     </li>
     808                  </ul>
     809               </li>
     810            </ul>
     811            <p id="rfc.section.2.2.p.2"><span class="comment" id="TODO-method-cacheability">[<a href="#TODO-method-cacheability" class="smpl">TODO-method-cacheability</a>: define method cacheability for GET, HEAD and POST in p2-semantics.]</span>
     812            </p>
     813            <p id="rfc.section.2.2.p.3">When a stored response is used to satisfy a request, 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>. <span class="comment" id="DISCUSS-includes-validated">[<a href="#DISCUSS-includes-validated" class="smpl">DISCUSS-includes-validated</a>: this currently includes successfully validated responses.]</span>
     814            </p>
     815            <p id="rfc.section.2.2.p.4">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
     816               the request and having received a corresponding response.
     817            </p>
     818            <p id="rfc.section.2.2.p.5">Also, note that unsafe requests might invalidate already stored responses; see <a href="#invalidation.after.updates.or.deletions" title="Request Methods that Invalidate">Section&nbsp;2.5</a>.
     819            </p>
     820            <p id="rfc.section.2.2.p.6">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
     821               forward a request with "Cache-Control: max-age=0" or "Cache-Control: no-cache" to disambiguate which response to use.
     822            </p>
     823            <p id="rfc.section.2.2.p.7"><span class="comment" id="TODO-header-properties">[<a href="#TODO-header-properties" class="smpl">TODO-header-properties</a>: end-to-end and hop-by-hop headers, non-modifiable headers removed; re-spec in p1]</span>
     824            </p>
     825         </div>
     826         <div id="expiration.model">
     827            <h2 id="rfc.section.2.3"><a href="#rfc.section.2.3">2.3</a>&nbsp;<a href="#expiration.model">Freshness Model</a></h2>
     828            <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,
     829               thereby improving efficiency.
     830            </p>
     831            <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,
     832               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 entity is not
     833               likely to change in a semantically significant way before the expiration time is reached.
     834            </p>
     835            <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.
     836               This means that the response is always stale, so that caches should validate it before using it for subsequent requests. <span class="comment" id="TODO-response-stale">[<a href="#TODO-response-stale" class="smpl">TODO-response-stale</a>: This wording may cause confusion, because the response may still be served stale.]</span>
     837            </p>
     838            <p id="rfc.section.2.3.p.4">Since origin servers do not always provide explicit expiration times, HTTP caches may also assign heuristic expiration times
     839               when they are not specified, employing algorithms that use other header values (such as the Last-Modified time) to estimate
     840               a plausible expiration time. The HTTP/1.1 specification does not provide specific algorithms, but does impose worst-case constraints
     841               on their results.
     842            </p>
     843            <div id="rfc.figure.u.3"></div>
     844            <p>The calculation to determine if a response is fresh is:</p><pre class="text">   response_is_fresh = (freshness_lifetime &gt; current_age)
     845</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>.
     846            </p>
     847            <p id="rfc.section.2.3.p.7">Additionally, clients may need to influence freshness calculation. They can do this using several request cache directives,
     848               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>.
     849            </p>
     850            <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>
     851            </p>
     852            <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
     853               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.
     854            </p>
     855            <div id="calculating.freshness.lifetime">
     856               <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>
     857               <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>
     858               <ul>
     859                  <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
     860                  </li>
     861                  <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
     862                  </li>
     863                  <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
     864                  </li>
     865                  <li>Otherwise, no explicit expiration time is present in the response, but a heuristic may be used; see <a href="#heuristic.freshness" title="Calculating Heuristic Freshness">Section&nbsp;2.3.1.1</a>.
     866                  </li>
     867               </ul>
     868               <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>
     869               <div id="heuristic.freshness">
     870                  <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>
     871                  <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 of 200, 203, 206, 300, 301 or 410, a
     872                     heuristic expiration time can be calculated. Heuristics <em class="bcp14">MUST NOT</em> be used for other response status codes.
     873                  </p>
     874                  <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
     875                     not already present.
     876                  </p>
     877                  <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%.
     878                  </p>
     879                  <p id="rfc.section.2.3.1.1.p.4"><span class="comment" id="REVIEW-query-string-heuristics">[<a href="#REVIEW-query-string-heuristics" class="smpl">REVIEW-query-string-heuristics</a>: took away HTTP/1.0 query string heuristic uncacheability.]</span>
     880                  </p>
     881               </div>
     882            </div>
     883            <div id="age.calculations">
     884               <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>
     885               <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
     886                  Age field value is the cache's estimate of the amount of time since the response was generated or validated by the origin
     887                  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
     888                  path from the origin server, plus the amount of time it has been in transit along network paths.
     889               </p>
     890               <p id="rfc.section.2.3.2.p.2">The term "age_value" denotes the value of the Age header, in a form appropriate for arithmetic operations.</p>
     891               <p id="rfc.section.2.3.2.p.3">HTTP/1.1 requires origin servers to send a Date header, if possible, with every response, giving the time at which the response
     892                  was generated (see <a href="p1-messaging.html#header.date" title="Date">Section 9.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>). The term "date_value" denotes the value of the Date header, in a form appropriate for arithmetic operations.
     893               </p>
     894               <p id="rfc.section.2.3.2.p.4">The term "now" means "the current value of the clock at the host performing the calculation." Hosts that use HTTP, but especially
     895                  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.
     896               </p>
     897               <p id="rfc.section.2.3.2.p.5">A response's age can be calculated in two entirely independent ways: </p>
     898               <ol>
     899                  <li>now minus date_value, if the local clock is reasonably well synchronized to the origin server's clock. If the result is negative,
     900                     the result is replaced by zero.
     901                  </li>
     902                  <li>age_value, if all of the caches along the response path implement HTTP/1.1.</li>
     903               </ol>
     904               <div id="rfc.figure.u.4"></div>
     905               <p>These are combined as</p><pre class="text">    corrected_received_age = max(now - date_value, age_value)
    869906</pre><p id="rfc.section.2.3.2.p.7">When an Age value is received, it <em class="bcp14">MUST</em> be interpreted relative to the time the request was initiated, not the time that the response was received.
    870       </p>
    871       <div id="rfc.figure.u.5"></div><pre class="text">   corrected_initial_age = corrected_received_age
     907               </p>
     908               <div id="rfc.figure.u.5"></div><pre class="text">   corrected_initial_age = corrected_received_age
    872909                         + (now - request_time)
    873910</pre><p id="rfc.section.2.3.2.p.9">where "request_time" is the time (according to the local clock) when the request that elicited this response was sent.</p>
    874       <p id="rfc.section.2.3.2.p.10">The current_age of a stored response can then be calculated by adding the amount of time (in seconds) since the stored response
    875          was last validated by the origin server to the corrected_initial_age.
    876       </p>
    877       <p id="rfc.section.2.3.2.p.11">In summary:</p>
    878       <div id="rfc.figure.u.6"></div><pre class="text">  age_value     - Age header field-value received with the response
     911               <p id="rfc.section.2.3.2.p.10">The current_age of a stored response can then be calculated by adding the amount of time (in seconds) since the stored response
     912                  was last validated by the origin server to the corrected_initial_age.
     913               </p>
     914               <p id="rfc.section.2.3.2.p.11">In summary:</p>
     915               <div id="rfc.figure.u.6"></div><pre class="text">  age_value     - Age header field-value received with the response
    879916  date_value    - Date header field-value received with the response
    880917  request_time  - local time when the cache made the request
     
    889926  resident_time = now - response_time;
    890927  current_age   = corrected_initial_age + resident_time;
    891 </pre><h3 id="rfc.section.2.3.3"><a href="#rfc.section.2.3.3">2.3.3</a>&nbsp;<a id="serving.stale.responses" href="#serving.stale.responses">Serving Stale Responses</a></h3>
    892       <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,
    893          but is not fresh according to the calculations in <a href="#expiration.model" title="Freshness Model">Section&nbsp;2.3</a>.
    894       </p>
    895       <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
    896          directive, a "must-revalidate" cache-response-directive, or an applicable "s-maxage" or "proxy-revalidate" cache-response-directive;
    897          see <a href="#cache-response-directive" title="Response Cache-Control Directives">Section&nbsp;3.2.2</a>).
    898       </p>
    899       <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
    900          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>).
    901       </p>
    902       <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.
    903       </p>
    904       <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
    905          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.
    906       </p>
    907       <h2 id="rfc.section.2.4"><a href="#rfc.section.2.4">2.4</a>&nbsp;<a id="validation.model" href="#validation.model">Validation Model</a></h2>
    908       <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
    909          fresh, or one cannot be selected; see <a href="#caching.negotiated.responses" title="Caching Negotiated Responses">Section&nbsp;2.6</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
    910          update it. This process is known as "validating" or "revalidating" the stored response.
    911       </p>
    912       <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.6</a>) stored response, if available.
    913       </p>
    914       <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
    915          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
    916          response.
    917       </p>
    918       <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.7</a>.
    919       </p>
    920       <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
    921          request is suitable. Instead, the full response is used both to satisfy the request and replace the stored response. <span class="comment" id="TODO-req-missing">[<a href="#TODO-req-missing" class="smpl">TODO-req-missing</a>: Should there be a requirement here?]</span>
    922       </p>
    923       <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>).
    924       </p>
    925       <h2 id="rfc.section.2.5"><a href="#rfc.section.2.5">2.5</a>&nbsp;<a id="invalidation.after.updates.or.deletions" href="#invalidation.after.updates.or.deletions">Request Methods that Invalidate</a></h2>
    926       <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.2"><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.
    927       </p>
    928       <p id="rfc.section.2.5.p.2">The following HTTP methods <em class="bcp14">MUST</em> cause a cache to invalidate the Request-URI as well as the URI(s) in the Location and Content-Location headers (if present):
    929       </p>
    930       <ul>
    931          <li>PUT</li>
    932          <li>DELETE</li>
    933          <li>POST</li>
    934       </ul>
    935       <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 Request-URI. This helps prevent denial of service
    936          attacks.
    937       </p>
    938       <p id="rfc.section.2.5.p.4"> <span class="comment" id="TODO-def-host-part">[<a href="#TODO-def-host-part" class="smpl">TODO-def-host-part</a>: "host part" needs to be specified better.]</span>
    939       </p>
    940       <p id="rfc.section.2.5.p.5">A cache that passes through requests for methods it does not understand <em class="bcp14">SHOULD</em> invalidate the Request-URI.
    941       </p>
    942       <p id="rfc.section.2.5.p.6">Here, "invalidate" means that the cache will either remove all stored responses related to the Request-URI, or will mark these
    943          as "invalid" and in need of a mandatory validation before they can be returned in response to a subsequent request.
    944       </p>
    945       <p id="rfc.section.2.5.p.7">Note that this does not guarantee that all appropriate responses are invalidated. For example, the request that caused the
    946          change at the origin server might not have gone through the cache where a response is stored.
    947       </p>
    948       <p id="rfc.section.2.5.p.8"> <span class="comment" id="TODO-spec-success-invalidate">[<a href="#TODO-spec-success-invalidate" class="smpl">TODO-spec-success-invalidate</a>: specify that only successful (2xx, 3xx?) responses invalidate.]</span>
    949       </p>
    950       <h2 id="rfc.section.2.6"><a href="#rfc.section.2.6">2.6</a>&nbsp;<a id="caching.negotiated.responses" href="#caching.negotiated.responses">Caching Negotiated Responses</a></h2>
    951       <p id="rfc.section.2.6.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
    952          (i.e., that associated with the stored response), and the presented request.
    953       </p>
    954       <p id="rfc.section.2.6.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
    955          to those in the second request by applying any of the following:
    956       </p>
    957       <ul>
    958          <li>adding or removing whitespace, where allowed in the header's syntax</li>
    959          <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.12"><cite title="HTTP/1.1, part 1: URIs, Connections, and Message Parsing">[Part1]</cite></a>)
    960          </li>
    961          <li>normalizing both header values in a way that is known to have identical semantics, according to the header's specification
    962             (e.g., re-ordering field values when order is not significant; case-normalization, where values are defined to be case-insensitive)
    963          </li>
    964       </ul>
    965       <p id="rfc.section.2.6.p.3">If (after any normalisation that may take place) a header field is absent from a request, it can only match another request
    966          if it is also absent there.
    967       </p>
    968       <p id="rfc.section.2.6.p.4">A Vary header field-value of "*" always fails to match, and subsequent requests to that resource can only be properly interpreted
    969          by the origin server.
    970       </p>
    971       <p id="rfc.section.2.6.p.5">The stored response with matching selecting request-headers is known as the selected response.</p>
    972       <p id="rfc.section.2.6.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>.
    973       </p>
    974       <h2 id="rfc.section.2.7"><a href="#rfc.section.2.7">2.7</a>&nbsp;<a id="combining.headers" href="#combining.headers">Combining Responses</a></h2>
    975       <p id="rfc.section.2.7.p.1">When a cache receives a 304 (Not Modified) response or a 206 (Partial Content) response (in this section, the "new" response"),
    976          it needs to created an updated response by combining the stored response with the new one, so that the updated response can
    977          be used to satisfy the request.
    978       </p>
    979       <p id="rfc.section.2.7.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>: may need language about Content-Location here]</span><span class="comment" id="TODO-inm-mult-etags">[<a href="#TODO-inm-mult-etags" class="smpl">TODO-inm-mult-etags</a>: cover case where INM with multiple etags was sent]</span>
    980       </p>
    981       <p id="rfc.section.2.7.p.3">If the 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.
    982       </p>
    983       <p id="rfc.section.2.7.p.4">The stored response headers are used as those of the updated response, except that </p>
    984       <ul>
    985          <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 from the stored response and the updated response.
    986          </li>
    987          <li>any stored Warning headers with warn-code 2xx <em class="bcp14">MUST</em> be retained in the stored response and the updated response.
    988          </li>
    989          <li>any headers provided in the new response <em class="bcp14">MUST</em> replace the corresponding headers from the stored response.
    990          </li>
    991       </ul>
    992       <p id="rfc.section.2.7.p.5">If a header field-name in the new response matches more than one header in the stored response, all such stored headers <em class="bcp14">MUST</em> be replaced.
    993       </p>
    994       <p id="rfc.section.2.7.p.6">The updated response can <span class="comment" id="TODO-is-req">[<a href="#TODO-is-req" class="smpl">TODO-is-req</a>: requirement?]</span> be used to replace the stored response in cache. In the case of a 206 response, the combined entity-body <em class="bcp14">MAY</em> be stored.
    995       </p>
    996       <p id="rfc.section.2.7.p.7"> <span class="comment" id="ISSUE-how-head">[<a href="#ISSUE-how-head" class="smpl">ISSUE-how-head</a>: discuss how to handle HEAD updates]</span>
    997       </p>
    998       <h1 id="rfc.section.3"><a href="#rfc.section.3">3.</a>&nbsp;<a id="header.fields" href="#header.fields">Header Field Definitions</a></h1>
    999       <p id="rfc.section.3.p.1">This section defines the syntax and semantics of HTTP/1.1 header fields related to caching.</p>
    1000       <p id="rfc.section.3.p.2">For entity-header fields, both sender and recipient refer to either the client or the server, depending on who sends and who
    1001          receives the entity.
    1002       </p>
    1003       <div id="rfc.iref.a.2"></div>
    1004       <div id="rfc.iref.h.2"></div>
    1005       <h2 id="rfc.section.3.1"><a href="#rfc.section.3.1">3.1</a>&nbsp;<a id="header.age" href="#header.age">Age</a></h2>
    1006       <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
    1007          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>.
    1008       </p>
    1009       <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>
     928</pre></div>
     929            <div id="serving.stale.responses">
     930               <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>
     931               <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,
     932                  but is not fresh according to the calculations in <a href="#expiration.model" title="Freshness Model">Section&nbsp;2.3</a>.
     933               </p>
     934               <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
     935                  directive, a "must-revalidate" cache-response-directive, or an applicable "s-maxage" or "proxy-revalidate" cache-response-directive;
     936                  see <a href="#cache-response-directive" title="Response Cache-Control Directives">Section&nbsp;3.2.2</a>).
     937               </p>
     938               <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
     939                  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>).
     940               </p>
     941               <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.
     942               </p>
     943               <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
     944                  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.
     945               </p>
     946            </div>
     947         </div>
     948         <div id="validation.model">
     949            <h2 id="rfc.section.2.4"><a href="#rfc.section.2.4">2.4</a>&nbsp;<a href="#validation.model">Validation Model</a></h2>
     950            <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
     951               fresh, or one cannot be selected; see <a href="#caching.negotiated.responses" title="Caching Negotiated Responses">Section&nbsp;2.6</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
     952               update it. This process is known as "validating" or "revalidating" the stored response.
     953            </p>
     954            <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.6</a>) stored response, if available.
     955            </p>
     956            <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
     957               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
     958               response.
     959            </p>
     960            <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.7</a>.
     961            </p>
     962            <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
     963               request is suitable. Instead, the full response is used both to satisfy the request and replace the stored response. <span class="comment" id="TODO-req-missing">[<a href="#TODO-req-missing" class="smpl">TODO-req-missing</a>: Should there be a requirement here?]</span>
     964            </p>
     965            <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>).
     966            </p>
     967         </div>
     968         <div id="invalidation.after.updates.or.deletions">
     969            <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>
     970            <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.2"><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.
     971            </p>
     972            <p id="rfc.section.2.5.p.2">The following HTTP methods <em class="bcp14">MUST</em> cause a cache to invalidate the Request-URI as well as the URI(s) in the Location and Content-Location headers (if present):
     973            </p>
     974            <ul>
     975               <li>PUT</li>
     976               <li>DELETE</li>
     977               <li>POST</li>
     978            </ul>
     979            <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 Request-URI. This helps prevent denial of service
     980               attacks.
     981            </p>
     982            <p id="rfc.section.2.5.p.4"><span class="comment" id="TODO-def-host-part">[<a href="#TODO-def-host-part" class="smpl">TODO-def-host-part</a>: "host part" needs to be specified better.]</span>
     983            </p>
     984            <p id="rfc.section.2.5.p.5">A cache that passes through requests for methods it does not understand <em class="bcp14">SHOULD</em> invalidate the Request-URI.
     985            </p>
     986            <p id="rfc.section.2.5.p.6">Here, "invalidate" means that the cache will either remove all stored responses related to the Request-URI, or will mark these
     987               as "invalid" and in need of a mandatory validation before they can be returned in response to a subsequent request.
     988            </p>
     989            <p id="rfc.section.2.5.p.7">Note that this does not guarantee that all appropriate responses are invalidated. For example, the request that caused the
     990               change at the origin server might not have gone through the cache where a response is stored.
     991            </p>
     992            <p id="rfc.section.2.5.p.8"><span class="comment" id="TODO-spec-success-invalidate">[<a href="#TODO-spec-success-invalidate" class="smpl">TODO-spec-success-invalidate</a>: specify that only successful (2xx, 3xx?) responses invalidate.]</span>
     993            </p>
     994         </div>
     995         <div id="caching.negotiated.responses">
     996            <h2 id="rfc.section.2.6"><a href="#rfc.section.2.6">2.6</a>&nbsp;<a href="#caching.negotiated.responses">Caching Negotiated Responses</a></h2>
     997            <p id="rfc.section.2.6.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
     998               (i.e., that associated with the stored response), and the presented request.
     999            </p>
     1000            <p id="rfc.section.2.6.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
     1001               to those in the second request by applying any of the following:
     1002            </p>
     1003            <ul>
     1004               <li>adding or removing whitespace, where allowed in the header's syntax</li>
     1005               <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.12"><cite title="HTTP/1.1, part 1: URIs, Connections, and Message Parsing">[Part1]</cite></a>)
     1006               </li>
     1007               <li>normalizing both header values in a way that is known to have identical semantics, according to the header's specification
     1008                  (e.g., re-ordering field values when order is not significant; case-normalization, where values are defined to be case-insensitive)
     1009               </li>
     1010            </ul>
     1011            <p id="rfc.section.2.6.p.3">If (after any normalisation that may take place) a header field is absent from a request, it can only match another request
     1012               if it is also absent there.
     1013            </p>
     1014            <p id="rfc.section.2.6.p.4">A Vary header field-value of "*" always fails to match, and subsequent requests to that resource can only be properly interpreted
     1015               by the origin server.
     1016            </p>
     1017            <p id="rfc.section.2.6.p.5">The stored response with matching selecting request-headers is known as the selected response.</p>
     1018            <p id="rfc.section.2.6.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>.
     1019            </p>
     1020         </div>
     1021         <div id="combining.headers">
     1022            <h2 id="rfc.section.2.7"><a href="#rfc.section.2.7">2.7</a>&nbsp;<a href="#combining.headers">Combining Responses</a></h2>
     1023            <p id="rfc.section.2.7.p.1">When a cache receives a 304 (Not Modified) response or a 206 (Partial Content) response (in this section, the "new" response"),
     1024               it needs to created an updated response by combining the stored response with the new one, so that the updated response can
     1025               be used to satisfy the request.
     1026            </p>
     1027            <p id="rfc.section.2.7.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>: may need language about Content-Location here]</span><span class="comment" id="TODO-inm-mult-etags">[<a href="#TODO-inm-mult-etags" class="smpl">TODO-inm-mult-etags</a>: cover case where INM with multiple etags was sent]</span>
     1028            </p>
     1029            <p id="rfc.section.2.7.p.3">If the 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.
     1030            </p>
     1031            <p id="rfc.section.2.7.p.4">The stored response headers are used as those of the updated response, except that </p>
     1032            <ul>
     1033               <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 from the stored response and the updated response.
     1034               </li>
     1035               <li>any stored Warning headers with warn-code 2xx <em class="bcp14">MUST</em> be retained in the stored response and the updated response.
     1036               </li>
     1037               <li>any headers provided in the new response <em class="bcp14">MUST</em> replace the corresponding headers from the stored response.
     1038               </li>
     1039            </ul>
     1040            <p id="rfc.section.2.7.p.5">If a header field-name in the new response matches more than one header in the stored response, all such stored headers <em class="bcp14">MUST</em> be replaced.
     1041            </p>
     1042            <p id="rfc.section.2.7.p.6">The updated response can <span class="comment" id="TODO-is-req">[<a href="#TODO-is-req" class="smpl">TODO-is-req</a>: requirement?]</span> be used to replace the stored response in cache. In the case of a 206 response, the combined entity-body <em class="bcp14">MAY</em> be stored.
     1043            </p>
     1044            <p id="rfc.section.2.7.p.7"><span class="comment" id="ISSUE-how-head">[<a href="#ISSUE-how-head" class="smpl">ISSUE-how-head</a>: discuss how to handle HEAD updates]</span>
     1045            </p>
     1046         </div>
     1047      </div>
     1048      <div id="header.fields">
     1049         <h1 id="rfc.section.3"><a href="#rfc.section.3">3.</a>&nbsp;<a href="#header.fields">Header Field Definitions</a></h1>
     1050         <p id="rfc.section.3.p.1">This section defines the syntax and semantics of HTTP/1.1 header fields related to caching.</p>
     1051         <p id="rfc.section.3.p.2">For entity-header fields, both sender and recipient refer to either the client or the server, depending on who sends and who
     1052            receives the entity.
     1053         </p>
     1054         <div id="header.age">
     1055            <div id="rfc.iref.a.2"></div>
     1056            <div id="rfc.iref.h.2"></div>
     1057            <h2 id="rfc.section.3.1"><a href="#rfc.section.3.1">3.1</a>&nbsp;<a href="#header.age">Age</a></h2>
     1058            <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
     1059               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>.
     1060            </p>
     1061            <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>
    10101062  <a href="#header.age" class="smpl">Age-v</a> = <a href="#rule.delta-seconds" class="smpl">delta-seconds</a>
    10111063</pre><div id="rule.delta-seconds">
    1012          <p id="rfc.section.3.1.p.3"> Age field-values are non-negative integers, representing time in seconds.</p>
    1013       </div>
    1014       <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>
     1064               <p id="rfc.section.3.1.p.3"> Age field-values are non-negative integers, representing time in seconds.</p>
     1065            </div>
     1066            <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>
    10151067</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,
    1016          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.
    1017       </p>
    1018       <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
    1019          true, since HTTP/1.0 caches may not implement the Age header field.
    1020       </p>
    1021       <div id="rfc.iref.c.3"></div>
    1022       <div id="rfc.iref.h.3"></div>
    1023       <h2 id="rfc.section.3.2"><a href="#rfc.section.3.2">3.2</a>&nbsp;<a id="header.cache-control" href="#header.cache-control">Cache-Control</a></h2>
    1024       <p id="rfc.section.3.2.p.1">The "Cache-Control" general-header field is used to specify directives that <em class="bcp14">MUST</em> be obeyed by all caches along the request/response chain. Such cache directives are unidirectional in that the presence of
    1025          a directive in a request does not imply that the same directive is to be given in the response.
    1026       </p>
    1027       <div class="note" id="rfc.section.3.2.p.2">
    1028          <p>Note that 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>).
    1029          </p>
    1030       </div>
    1031       <p id="rfc.section.3.2.p.3">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
    1032          might be applicable to all recipients along the request/response chain. It is not possible to target a directive to a specific
    1033          cache.
    1034       </p>
    1035       <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>
     1068               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.
     1069            </p>
     1070            <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
     1071               true, since HTTP/1.0 caches may not implement the Age header field.
     1072            </p>
     1073         </div>
     1074         <div id="header.cache-control">
     1075            <div id="rfc.iref.c.3"></div>
     1076            <div id="rfc.iref.h.3"></div>
     1077            <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>
     1078            <p id="rfc.section.3.2.p.1">The "Cache-Control" general-header field is used to specify directives that <em class="bcp14">MUST</em> be obeyed by all caches along the request/response chain. Such cache directives are unidirectional in that the presence of
     1079               a directive in a request does not imply that the same directive is to be given in the response.
     1080            </p>
     1081            <div class="note" id="rfc.section.3.2.p.2">
     1082               <p>Note that 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>).
     1083               </p>
     1084            </div>
     1085            <p id="rfc.section.3.2.p.3">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
     1086               might be applicable to all recipients along the request/response chain. It is not possible to target a directive to a specific
     1087               cache.
     1088            </p>
     1089            <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>
    10361090  <a href="#header.cache-control" class="smpl">Cache-Control-v</a> = 1#<a href="#header.cache-control" class="smpl">cache-directive</a>
    10371091
     
    10401094
    10411095  <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> ) ]
    1042 </pre><h3 id="rfc.section.3.2.1"><a href="#rfc.section.3.2.1">3.2.1</a>&nbsp;<a id="cache-request-directive" href="#cache-request-directive">Request Cache-Control Directives</a></h3>
    1043       <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> =
     1096</pre><div id="cache-request-directive">
     1097               <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>
     1098               <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> =
    10441099       "no-cache"
    10451100     / "no-store"
     
    10501105     / "only-if-cached"
    10511106     / <a href="#header.cache-control" class="smpl">cache-extension</a>
    1052 </pre><p id="rfc.section.3.2.1.p.2"> <span id="rfc.iref.c.4"></span>  <span id="rfc.iref.n.1"></span> no-cache
    1053       </p>
    1054       <ul class="empty">
    1055          <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.
    1056          </li>
    1057       </ul>
    1058       <p id="rfc.section.3.2.1.p.3"> <span id="rfc.iref.c.5"></span>  <span id="rfc.iref.n.2"></span> no-store
    1059       </p>
    1060       <ul class="empty">
    1061          <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.
    1062             "<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.
    1063          </li>
    1064          <li>This directive is NOT a reliable or sufficient mechanism for ensuring privacy. In particular, malicious or compromised caches
    1065             might not recognize or obey this directive, and communications networks may be vulnerable to eavesdropping.
    1066          </li>
    1067       </ul>
    1068       <p id="rfc.section.3.2.1.p.4"> <span id="rfc.iref.c.6"></span>  <span id="rfc.iref.m.1"></span> max-age
    1069       </p>
    1070       <ul class="empty">
    1071          <li>The max-age request directive indicates that the client is willing to accept a response whose age is no greater than the specified
    1072             time in seconds. Unless max-stale directive is also included, the client is not willing to accept a stale response.
    1073          </li>
    1074       </ul>
    1075       <p id="rfc.section.3.2.1.p.5"> <span id="rfc.iref.c.7"></span>  <span id="rfc.iref.m.2"></span> max-stale
    1076       </p>
    1077       <ul class="empty">
    1078          <li>The max-stale request directive indicates that the client is willing to accept a response that has exceeded its expiration
    1079             time. If max-stale is assigned a value, then the client is willing to accept a response that has exceeded its expiration time
    1080             by no more than the specified number of seconds. If no value is assigned to max-stale, then the client is willing to accept
    1081             a stale response of any age. <span class="comment" id="TODO-staleness">[<a href="#TODO-staleness" class="smpl">TODO-staleness</a>: of any staleness? --mnot]</span></li>
    1082       </ul>
    1083       <p id="rfc.section.3.2.1.p.6"> <span id="rfc.iref.c.8"></span>  <span id="rfc.iref.m.3"></span> min-fresh
    1084       </p>
    1085       <ul class="empty">
    1086          <li>The min-fresh request directive indicates that the client is willing to accept a response whose freshness lifetime is no less
    1087             than its current age plus the specified time in seconds. That is, the client wants a response that will still be fresh for
    1088             at least the specified number of seconds.
    1089          </li>
    1090       </ul>
    1091       <p id="rfc.section.3.2.1.p.7"> <span id="rfc.iref.c.9"></span>  <span id="rfc.iref.n.3"></span> no-transform
    1092       </p>
    1093       <ul class="empty">
    1094          <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 entity-body.
    1095          </li>
    1096       </ul>
    1097       <p id="rfc.section.3.2.1.p.8"> <span id="rfc.iref.c.10"></span>  <span id="rfc.iref.o.1"></span> only-if-cached
    1098       </p>
    1099       <ul class="empty">
    1100          <li>The only-if-cached request directive indicates that the client only wishes to return a stored response. If it receives this
    1101             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
    1102             (Gateway Timeout) status. If a group of caches is being operated as a unified system with good internal connectivity, such
    1103             a request <em class="bcp14">MAY</em> be forwarded within that group of caches.
    1104          </li>
    1105       </ul>
    1106       <h3 id="rfc.section.3.2.2"><a href="#rfc.section.3.2.2">3.2.2</a>&nbsp;<a id="cache-response-directive" href="#cache-response-directive">Response Cache-Control Directives</a></h3>
    1107       <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> =
     1107</pre><p id="rfc.section.3.2.1.p.2"><span id="rfc.iref.c.4"></span> <span id="rfc.iref.n.1"></span> no-cache
     1108               </p>
     1109               <ul class="empty">
     1110                  <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.
     1111                  </li>
     1112               </ul>
     1113               <p id="rfc.section.3.2.1.p.3"><span id="rfc.iref.c.5"></span> <span id="rfc.iref.n.2"></span> no-store
     1114               </p>
     1115               <ul class="empty">
     1116                  <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.
     1117                     "<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.
     1118                  </li>
     1119                  <li>This directive is NOT a reliable or sufficient mechanism for ensuring privacy. In particular, malicious or compromised caches
     1120                     might not recognize or obey this directive, and communications networks may be vulnerable to eavesdropping.
     1121                  </li>
     1122               </ul>
     1123               <p id="rfc.section.3.2.1.p.4"><span id="rfc.iref.c.6"></span> <span id="rfc.iref.m.1"></span> max-age
     1124               </p>
     1125               <ul class="empty">
     1126                  <li>The max-age request directive indicates that the client is willing to accept a response whose age is no greater than the specified
     1127                     time in seconds. Unless max-stale directive is also included, the client is not willing to accept a stale response.
     1128                  </li>
     1129               </ul>
     1130               <p id="rfc.section.3.2.1.p.5"><span id="rfc.iref.c.7"></span> <span id="rfc.iref.m.2"></span> max-stale
     1131               </p>
     1132               <ul class="empty">
     1133                  <li>The max-stale request directive indicates that the client is willing to accept a response that has exceeded its expiration
     1134                     time. If max-stale is assigned a value, then the client is willing to accept a response that has exceeded its expiration time
     1135                     by no more than the specified number of seconds. If no value is assigned to max-stale, then the client is willing to accept
     1136                     a stale response of any age. <span class="comment" id="TODO-staleness">[<a href="#TODO-staleness" class="smpl">TODO-staleness</a>: of any staleness? --mnot]</span></li>
     1137               </ul>
     1138               <p id="rfc.section.3.2.1.p.6"><span id="rfc.iref.c.8"></span> <span id="rfc.iref.m.3"></span> min-fresh
     1139               </p>
     1140               <ul class="empty">
     1141                  <li>The min-fresh request directive indicates that the client is willing to accept a response whose freshness lifetime is no less
     1142                     than its current age plus the specified time in seconds. That is, the client wants a response that will still be fresh for
     1143                     at least the specified number of seconds.
     1144                  </li>
     1145               </ul>
     1146               <p id="rfc.section.3.2.1.p.7"><span id="rfc.iref.c.9"></span> <span id="rfc.iref.n.3"></span> no-transform
     1147               </p>
     1148               <ul class="empty">
     1149                  <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 entity-body.
     1150                  </li>
     1151               </ul>
     1152               <p id="rfc.section.3.2.1.p.8"><span id="rfc.iref.c.10"></span> <span id="rfc.iref.o.1"></span> only-if-cached
     1153               </p>
     1154               <ul class="empty">
     1155                  <li>The only-if-cached request directive indicates that the client only wishes to return a stored response. If it receives this
     1156                     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
     1157                     (Gateway Timeout) status. If a group of caches is being operated as a unified system with good internal connectivity, such
     1158                     a request <em class="bcp14">MAY</em> be forwarded within that group of caches.
     1159                  </li>
     1160               </ul>
     1161            </div>
     1162            <div id="cache-response-directive">
     1163               <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>
     1164               <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> =
    11081165       "public"
    11091166     / "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> ]
     
    11161173     / "s-maxage" "=" <a href="#rule.delta-seconds" class="smpl">delta-seconds</a>
    11171174     / <a href="#header.cache-control" class="smpl">cache-extension</a>
    1118 </pre><p id="rfc.section.3.2.2.p.2"> <span id="rfc.iref.c.11"></span>  <span id="rfc.iref.p.1"></span> public
    1119       </p>
    1120       <ul class="empty">
    1121          <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.2"><cite title="HTTP/1.1, part 7: Authentication">[Part7]</cite></a>, for additional details.)
    1122          </li>
    1123       </ul>
    1124       <p id="rfc.section.3.2.2.p.3"> <span id="rfc.iref.c.12"></span>  <span id="rfc.iref.p.2"></span> private
    1125       </p>
    1126       <ul class="empty">
    1127          <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.
    1128          </li>
    1129          <li>If the private response directive specifies one or more field-names, this requirement is limited to the field-values associated
    1130             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.
    1131          </li>
    1132          <li> <b>Note:</b> This usage of the word private only controls where the response may be stored, and cannot ensure the privacy of the message
    1133             content. Also, private response directives with field-names are often handled by implementations as if an unqualified private
    1134             directive was received; i.e., the special handling for the qualified form is not widely implemented.
    1135          </li>
    1136       </ul>
    1137       <p id="rfc.section.3.2.2.p.4"> <span id="rfc.iref.c.13"></span>  <span id="rfc.iref.n.4"></span> no-cache
    1138       </p>
    1139       <ul class="empty">
    1140          <li>The no-cache response directive indicates that the response <em class="bcp14">MUST NOT</em> be used to satisfy a subsequent request without successful validation on the origin server. This allows an origin server to
    1141             prevent caching even by caches that have been configured to return stale responses.
    1142          </li>
    1143          <li>If the no-cache response directive specifies one or more field-names, this requirement is limited to the field-values associated
    1144             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
    1145             server to prevent the re-use of certain header fields in a response, while still allowing caching of the rest of the response.
    1146          </li>
    1147          <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
    1148             handled by implementations as if an unqualified no-cache directive was received; i.e., the special handling for the qualified
    1149             form is not widely implemented.
    1150          </li>
    1151       </ul>
    1152       <p id="rfc.section.3.2.2.p.5"> <span id="rfc.iref.c.14"></span>  <span id="rfc.iref.n.5"></span> no-store
    1153       </p>
    1154       <ul class="empty">
    1155          <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.
    1156          </li>
    1157          <li>This directive is NOT a reliable or sufficient mechanism for ensuring privacy. In particular, malicious or compromised caches
    1158             might not recognize or obey this directive, and communications networks may be vulnerable to eavesdropping.
    1159          </li>
    1160       </ul>
    1161       <p id="rfc.section.3.2.2.p.6"> <span id="rfc.iref.c.15"></span>  <span id="rfc.iref.m.4"></span> must-revalidate
    1162       </p>
    1163       <ul class="empty">
    1164          <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.
    1165          </li>
    1166          <li>The must-revalidate directive is necessary to support reliable operation for certain protocol features. In all circumstances
    1167             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.
    1168          </li>
    1169          <li>Servers <em class="bcp14">SHOULD</em> send the must-revalidate directive if and only if failure to validate a request on the entity could result in incorrect operation,
    1170             such as a silently unexecuted financial transaction.
    1171          </li>
    1172       </ul>
    1173       <p id="rfc.section.3.2.2.p.7"> <span id="rfc.iref.c.16"></span>  <span id="rfc.iref.p.3"></span> proxy-revalidate
    1174       </p>
    1175       <ul class="empty">
    1176          <li>The proxy-revalidate response directive has the same meaning as the must-revalidate response directive, except that it does
    1177             not apply to non-shared caches.
    1178          </li>
    1179       </ul>
    1180       <p id="rfc.section.3.2.2.p.8"> <span id="rfc.iref.c.17"></span>  <span id="rfc.iref.m.5"></span> max-age
    1181       </p>
    1182       <ul class="empty">
    1183          <li>The max-age response directive indicates that response is to be considered stale after its age is greater than the specified
    1184             number of seconds.
    1185          </li>
    1186       </ul>
    1187       <p id="rfc.section.3.2.2.p.9"> <span id="rfc.iref.c.18"></span>  <span id="rfc.iref.s.2"></span> s-maxage
    1188       </p>
    1189       <ul class="empty">
    1190          <li>The s-maxage response directive indicates that, in shared caches, the maximum age specified by this directive overrides the
    1191             maximum age specified by either the max-age directive or the Expires header. The s-maxage directive also implies the semantics
    1192             of the proxy-revalidate response directive.
    1193          </li>
    1194       </ul>
    1195       <p id="rfc.section.3.2.2.p.10"> <span id="rfc.iref.c.19"></span>  <span id="rfc.iref.n.6"></span> no-transform
    1196       </p>
    1197       <ul class="empty">
    1198          <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 entity-body.
    1199          </li>
    1200       </ul>
    1201       <h3 id="rfc.section.3.2.3"><a href="#rfc.section.3.2.3">3.2.3</a>&nbsp;<a id="cache.control.extensions" href="#cache.control.extensions">Cache Control Extensions</a></h3>
    1202       <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
    1203          value. Informational extensions (those that do not require a change in cache behavior) can be added without changing the semantics
    1204          of other directives. Behavioral extensions are designed to work by acting as modifiers to the existing base of cache directives.
    1205          Both the new directive and the standard directive are supplied, such that applications that do not understand the new directive
    1206          will default to the behavior specified by the standard directive, and those that understand the new directive will recognize
    1207          it as modifying the requirements associated with the standard directive. In this way, extensions to the cache-control directives
    1208          can be made without requiring changes to the base protocol.
    1209       </p>
    1210       <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,
    1211          obeying certain extensions, and ignoring all directives that it does not understand.
    1212       </p>
    1213       <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.
    1214          We define this new directive to mean that, in addition to any non-shared cache, any cache that is shared only by members of
    1215          the community named within its value may cache the response. An origin server wishing to allow the UCI community to use an
    1216          otherwise private response in their shared cache(s) could do so by including
    1217       </p>
    1218       <div id="rfc.figure.u.12"></div><pre class="text">  Cache-Control: private, community="UCI"
     1175</pre><p id="rfc.section.3.2.2.p.2"><span id="rfc.iref.c.11"></span> <span id="rfc.iref.p.1"></span> public
     1176               </p>
     1177               <ul class="empty">
     1178                  <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.2"><cite title="HTTP/1.1, part 7: Authentication">[Part7]</cite></a>, for additional details.)
     1179                  </li>
     1180               </ul>
     1181               <p id="rfc.section.3.2.2.p.3"><span id="rfc.iref.c.12"></span> <span id="rfc.iref.p.2"></span> private
     1182               </p>
     1183               <ul class="empty">
     1184                  <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.
     1185                  </li>
     1186                  <li>If the private response directive specifies one or more field-names, this requirement is limited to the field-values associated
     1187                     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.
     1188                  </li>
     1189                  <li><b>Note:</b> This usage of the word private only controls where the response may be stored, and cannot ensure the privacy of the message
     1190                     content. Also, private response directives with field-names are often handled by implementations as if an unqualified private
     1191                     directive was received; i.e., the special handling for the qualified form is not widely implemented.
     1192                  </li>
     1193               </ul>
     1194               <p id="rfc.section.3.2.2.p.4"><span id="rfc.iref.c.13"></span> <span id="rfc.iref.n.4"></span> no-cache
     1195               </p>
     1196               <ul class="empty">
     1197                  <li>The no-cache response directive indicates that the response <em class="bcp14">MUST NOT</em> be used to satisfy a subsequent request without successful validation on the origin server. This allows an origin server to
     1198                     prevent caching even by caches that have been configured to return stale responses.
     1199                  </li>
     1200                  <li>If the no-cache response directive specifies one or more field-names, this requirement is limited to the field-values associated
     1201                     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
     1202                     server to prevent the re-use of certain header fields in a response, while still allowing caching of the rest of the response.
     1203                  </li>
     1204                  <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
     1205                     handled by implementations as if an unqualified no-cache directive was received; i.e., the special handling for the qualified
     1206                     form is not widely implemented.
     1207                  </li>
     1208               </ul>
     1209               <p id="rfc.section.3.2.2.p.5"><span id="rfc.iref.c.14"></span> <span id="rfc.iref.n.5"></span> no-store
     1210               </p>
     1211               <ul class="empty">
     1212                  <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.
     1213                  </li>
     1214                  <li>This directive is NOT a reliable or sufficient mechanism for ensuring privacy. In particular, malicious or compromised caches
     1215                     might not recognize or obey this directive, and communications networks may be vulnerable to eavesdropping.
     1216                  </li>
     1217               </ul>
     1218               <p id="rfc.section.3.2.2.p.6"><span id="rfc.iref.c.15"></span> <span id="rfc.iref.m.4"></span> must-revalidate
     1219               </p>
     1220               <ul class="empty">
     1221                  <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.
     1222                  </li>
     1223                  <li>The must-revalidate directive is necessary to support reliable operation for certain protocol features. In all circumstances
     1224                     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.
     1225                  </li>
     1226                  <li>Servers <em class="bcp14">SHOULD</em> send the must-revalidate directive if and only if failure to validate a request on the entity could result in incorrect operation,
     1227                     such as a silently unexecuted financial transaction.
     1228                  </li>
     1229               </ul>
     1230               <p id="rfc.section.3.2.2.p.7"><span id="rfc.iref.c.16"></span> <span id="rfc.iref.p.3"></span> proxy-revalidate
     1231               </p>
     1232               <ul class="empty">
     1233                  <li>The proxy-revalidate response directive has the same meaning as the must-revalidate response directive, except that it does
     1234                     not apply to non-shared caches.
     1235                  </li>
     1236               </ul>
     1237               <p id="rfc.section.3.2.2.p.8"><span id="rfc.iref.c.17"></span> <span id="rfc.iref.m.5"></span> max-age
     1238               </p>
     1239               <ul class="empty">
     1240                  <li>The max-age response directive indicates that response is to be considered stale after its age is greater than the specified
     1241                     number of seconds.
     1242                  </li>
     1243               </ul>
     1244               <p id="rfc.section.3.2.2.p.9"><span id="rfc.iref.c.18"></span> <span id="rfc.iref.s.2"></span> s-maxage
     1245               </p>
     1246               <ul class="empty">
     1247                  <li>The s-maxage response directive indicates that, in shared caches, the maximum age specified by this directive overrides the
     1248                     maximum age specified by either the max-age directive or the Expires header. The s-maxage directive also implies the semantics
     1249                     of the proxy-revalidate response directive.
     1250                  </li>
     1251               </ul>
     1252               <p id="rfc.section.3.2.2.p.10"><span id="rfc.iref.c.19"></span> <span id="rfc.iref.n.6"></span> no-transform
     1253               </p>
     1254               <ul class="empty">
     1255                  <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 entity-body.
     1256                  </li>
     1257               </ul>
     1258            </div>
     1259            <div id="cache.control.extensions">
     1260               <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>
     1261               <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
     1262                  value. Informational extensions (those that do not require a change in cache behavior) can be added without changing the semantics
     1263                  of other directives. Behavioral extensions are designed to work by acting as modifiers to the existing base of cache directives.
     1264                  Both the new directive and the standard directive are supplied, such that applications that do not understand the new directive
     1265                  will default to the behavior specified by the standard directive, and those that understand the new directive will recognize
     1266                  it as modifying the requirements associated with the standard directive. In this way, extensions to the cache-control directives
     1267                  can be made without requiring changes to the base protocol.
     1268               </p>
     1269               <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,
     1270                  obeying certain extensions, and ignoring all directives that it does not understand.
     1271               </p>
     1272               <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.
     1273                  We define this new directive to mean that, in addition to any non-shared cache, any cache that is shared only by members of
     1274                  the community named within its value may cache the response. An origin server wishing to allow the UCI community to use an
     1275                  otherwise private response in their shared cache(s) could do so by including
     1276               </p>
     1277               <div id="rfc.figure.u.12"></div><pre class="text">  Cache-Control: private, community="UCI"
    12191278</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
    1220          it will also see and understand the private directive and thus default to the safe behavior.
    1221       </p>
    1222       <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
    1223          directives (or the response's default cacheability) such that the cache behavior will remain minimally correct even if the
    1224          cache does not understand the extension(s).
    1225       </p>
    1226       <div id="rfc.iref.e.2"></div>
    1227       <div id="rfc.iref.h.4"></div>
    1228       <h2 id="rfc.section.3.3"><a href="#rfc.section.3.3">3.3</a>&nbsp;<a id="header.expires" href="#header.expires">Expires</a></h2>
    1229       <p id="rfc.section.3.3.p.1">The "Expires" entity-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.
    1230       </p>
    1231       <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
    1232          that time.
    1233       </p>
    1234       <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.13"><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.
    1235       </p>
    1236       <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>
     1279                  it will also see and understand the private directive and thus default to the safe behavior.
     1280               </p>
     1281               <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
     1282                  directives (or the response's default cacheability) such that the cache behavior will remain minimally correct even if the
     1283                  cache does not understand the extension(s).
     1284               </p>
     1285            </div>
     1286         </div>
     1287         <div id="header.expires">
     1288            <div id="rfc.iref.e.2"></div>
     1289            <div id="rfc.iref.h.4"></div>
     1290            <h2 id="rfc.section.3.3"><a href="#rfc.section.3.3">3.3</a>&nbsp;<a href="#header.expires">Expires</a></h2>
     1291            <p id="rfc.section.3.3.p.1">The "Expires" entity-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.
     1292            </p>
     1293            <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
     1294               that time.
     1295            </p>
     1296            <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.13"><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.
     1297            </p>
     1298            <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>
    12371299  <a href="#header.expires" class="smpl">Expires-v</a> = <a href="#abnf.dependencies" class="smpl">HTTP-date</a>
    1238 </pre><div id="rfc.figure.u.14"></div>
    1239       <p>For example</p>  <pre class="text">  Expires: Thu, 01 Dec 1994 16:00:00 GMT
    1240 </pre><div class="note" id="rfc.section.3.3.p.6">
    1241          <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.
    1242          </p>
    1243       </div>
    1244       <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.
    1245       </p>
    1246       <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").
    1247       </p>
    1248       <div id="rfc.iref.p.4"></div>
    1249       <div id="rfc.iref.h.5"></div>
    1250       <h2 id="rfc.section.3.4"><a href="#rfc.section.3.4">3.4</a>&nbsp;<a id="header.pragma" href="#header.pragma">Pragma</a></h2>
    1251       <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
    1252          along the request/response chain. All pragma directives specify optional behavior from the viewpoint of the protocol; however,
    1253          some systems <em class="bcp14">MAY</em> require that behavior be consistent with the directives.
    1254       </p>
    1255       <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>
     1300</pre><div id="rfc.figure.u.14"></div>
     1301            <p>For example</p><pre class="text">  Expires: Thu, 01 Dec 1994 16:00:00 GMT
     1302</pre><div class="note" id="rfc.section.3.3.p.6">
     1303               <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.
     1304               </p>
     1305            </div>
     1306            <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.
     1307            </p>
     1308            <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").
     1309            </p>
     1310         </div>
     1311         <div id="header.pragma">
     1312            <div id="rfc.iref.p.4"></div>
     1313            <div id="rfc.iref.h.5"></div>
     1314            <h2 id="rfc.section.3.4"><a href="#rfc.section.3.4">3.4</a>&nbsp;<a href="#header.pragma">Pragma</a></h2>
     1315            <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
     1316               along the request/response chain. All pragma directives specify optional behavior from the viewpoint of the protocol; however,
     1317               some systems <em class="bcp14">MAY</em> require that behavior be consistent with the directives.
     1318            </p>
     1319            <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>
    12561320  <a href="#header.pragma" class="smpl">Pragma-v</a>          = 1#<a href="#header.pragma" class="smpl">pragma-directive</a>
    12571321  <a href="#header.pragma" class="smpl">pragma-directive</a>  = "no-cache" / <a href="#header.pragma" class="smpl">extension-pragma</a>
    12581322  <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> ) ]
    12591323</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
    1260          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".
    1261       </p>
    1262       <div class="note" id="rfc.section.3.4.p.4">
    1263          <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
    1264             replacement for "Cache-Control: no-cache" in a response.
    1265          </p>
    1266       </div>
    1267       <p id="rfc.section.3.4.p.5">This mechanism is deprecated; no new Pragma directives will be defined in HTTP.</p>
    1268       <div id="rfc.iref.v.3"></div>
    1269       <div id="rfc.iref.h.6"></div>
    1270       <h2 id="rfc.section.3.5"><a href="#rfc.section.3.5">3.5</a>&nbsp;<a id="header.vary" href="#header.vary">Vary</a></h2>
    1271       <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>
    1272       <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.6</a>. determines, while the response is fresh, whether a cache is permitted to use the response to reply to a subsequent request
    1273          without validation; see <a href="#caching.negotiated.responses" title="Caching Negotiated Responses">Section&nbsp;2.6</a>.
    1274       </p>
    1275       <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
    1276          the representation.
    1277       </p>
    1278       <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>
     1324               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".
     1325            </p>
     1326            <div class="note" id="rfc.section.3.4.p.4">
     1327               <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
     1328                  replacement for "Cache-Control: no-cache" in a response.
     1329               </p>
     1330            </div>
     1331            <p id="rfc.section.3.4.p.5">This mechanism is deprecated; no new Pragma directives will be defined in HTTP.</p>
     1332         </div>
     1333         <div id="header.vary">
     1334            <div id="rfc.iref.v.3"></div>
     1335            <div id="rfc.iref.h.6"></div>
     1336            <h2 id="rfc.section.3.5"><a href="#rfc.section.3.5">3.5</a>&nbsp;<a href="#header.vary">Vary</a></h2>
     1337            <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>
     1338            <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.6</a>. determines, while the response is fresh, whether a cache is permitted to use the response to reply to a subsequent request
     1339               without validation; see <a href="#caching.negotiated.responses" title="Caching Negotiated Responses">Section&nbsp;2.6</a>.
     1340            </p>
     1341            <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
     1342               the representation.
     1343            </p>
     1344            <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>
    12791345  <a href="#header.vary" class="smpl">Vary-v</a> = "*" / 1#<a href="#abnf.dependencies" class="smpl">field-name</a>
    12801346</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>
    1281       <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
    1282          to properly interpret future requests on that resource and informs the user agent about the presence of negotiation on that
    1283          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
    1284          the user agent with useful information about the dimensions over which the response varies at the time of the response.
    1285       </p>
    1286       <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
    1287          of the client), play a role in the selection of the response representation; therefore, a cache cannot determine whether this
    1288          response is appropriate. The "*" value <em class="bcp14">MUST NOT</em> be generated by a proxy server; it may only be generated by an origin server.
    1289       </p>
    1290       <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
    1291          are case-insensitive.
    1292       </p>
    1293       <div id="rfc.iref.w.1"></div>
    1294       <div id="rfc.iref.h.7"></div>
    1295       <h2 id="rfc.section.3.6"><a href="#rfc.section.3.6">3.6</a>&nbsp;<a id="header.warning" href="#header.warning">Warning</a></h2>
    1296       <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
    1297          that might not be reflected in the message. This information is typically used to warn about possible incorrectness introduced
    1298          by caching operations or transformations applied to the entity body of the message.
    1299       </p>
    1300       <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
    1301          code, distinguishes these responses from true failures.
    1302       </p>
    1303       <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
    1304          to response messages.
    1305       </p>
    1306       <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>
     1347            <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
     1348               to properly interpret future requests on that resource and informs the user agent about the presence of negotiation on that
     1349               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
     1350               the user agent with useful information about the dimensions over which the response varies at the time of the response.
     1351            </p>
     1352            <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
     1353               of the client), play a role in the selection of the response representation; therefore, a cache cannot determine whether this
     1354               response is appropriate. The "*" value <em class="bcp14">MUST NOT</em> be generated by a proxy server; it may only be generated by an origin server.
     1355            </p>
     1356            <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
     1357               are case-insensitive.
     1358            </p>
     1359         </div>
     1360         <div id="header.warning">
     1361            <div id="rfc.iref.w.1"></div>
     1362            <div id="rfc.iref.h.7"></div>
     1363            <h2 id="rfc.section.3.6"><a href="#rfc.section.3.6">3.6</a>&nbsp;<a href="#header.warning">Warning</a></h2>
     1364            <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
     1365               that might not be reflected in the message. This information is typically used to warn about possible incorrectness introduced
     1366               by caching operations or transformations applied to the entity body of the message.
     1367            </p>
     1368            <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
     1369               code, distinguishes these responses from true failures.
     1370            </p>
     1371            <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
     1372               to response messages.
     1373            </p>
     1374            <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>
    13071375  <a href="#header.warning" class="smpl">Warning-v</a>  = 1#<a href="#header.warning" class="smpl">warning-value</a>
    13081376 
     
    13171385  <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>
    13181386</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
    1319          the same code number, only differing in warn-text.
    1320       </p>
    1321       <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.
    1322       </p>
    1323       <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.
    1324       </p>
    1325       <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
    1326          a stored response after validation:
    1327       </p>
    1328       <ul>
    1329          <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.
    1330          </li>
    1331          <li>2xx Warnings describe some aspect of the entity body or entity headers that is not rectified by a validation (for example,
    1332             a lossy compression of the entity bodies) 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.
    1333          </li>
    1334       </ul>
    1335       <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
    1336          the sender <em class="bcp14">MUST</em> include in each warning-value a warn-date that matches the Date header in the message.
    1337       </p>
    1338       <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
    1339          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
    1340          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.
    1341       </p>
    1342       <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
    1343          of its meaning.
    1344       </p>
    1345       <p id="rfc.section.3.6.p.12"> 110 Response is stale </p>
    1346       <ul class="empty">
    1347          <li><em class="bcp14">SHOULD</em> be included whenever the returned response is stale.
    1348          </li>
    1349       </ul>
    1350       <p id="rfc.section.3.6.p.13"> 111 Revalidation failed </p>
    1351       <ul class="empty">
    1352          <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
    1353             reach the server.
    1354          </li>
    1355       </ul>
    1356       <p id="rfc.section.3.6.p.14"> 112 Disconnected operation </p>
    1357       <ul class="empty">
    1358          <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.
    1359          </li>
    1360       </ul>
    1361       <p id="rfc.section.3.6.p.15"> 113 Heuristic expiration </p>
    1362       <ul class="empty">
    1363          <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
    1364             than 24 hours.
    1365          </li>
    1366       </ul>
    1367       <p id="rfc.section.3.6.p.16"> 199 Miscellaneous warning </p>
    1368       <ul class="empty">
    1369          <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.
    1370          </li>
    1371       </ul>
    1372       <p id="rfc.section.3.6.p.17"> 214 Transformation applied </p>
    1373       <ul class="empty">
    1374          <li><em class="bcp14">MUST</em> be added by an intermediate cache or proxy if it applies any transformation changing the content-coding (as specified in the
    1375             Content-Encoding header) or media-type (as specified in the Content-Type header) of the response, or the entity-body of the
    1376             response, unless this Warning code already appears in the response.
    1377          </li>
    1378       </ul>
    1379       <p id="rfc.section.3.6.p.18"> 299 Miscellaneous persistent warning </p>
    1380       <ul class="empty">
    1381          <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.
    1382          </li>
    1383       </ul>
    1384       <h1 id="rfc.section.4"><a href="#rfc.section.4">4.</a>&nbsp;<a id="history.lists" href="#history.lists">History Lists</a></h1>
    1385       <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 an entity
    1386          retrieved earlier in a session.
    1387       </p>
    1388       <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
    1389          it has expired.
    1390       </p>
    1391       <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
    1392          (e.g., Cache-Control: no-store).
    1393       </p>
    1394       <h1 id="rfc.section.5"><a href="#rfc.section.5">5.</a>&nbsp;<a id="IANA.considerations" href="#IANA.considerations">IANA Considerations</a></h1>
    1395       <h2 id="rfc.section.5.1"><a href="#rfc.section.5.1">5.1</a>&nbsp;<a id="message.header.registration" href="#message.header.registration">Message Header Registration</a></h2>
    1396       <p id="rfc.section.5.1.p.1">The Message Header 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; should 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>):
    1397       </p>
    1398       <div id="rfc.table.1">
    1399          <div id="iana.header.registration.table"></div>
    1400          <table class="tt full left" cellpadding="3" cellspacing="0">
    1401             <thead>
    1402                <tr>
    1403                   <th>Header Field Name</th>
    1404                   <th>Protocol</th>
    1405                   <th>Status</th>
    1406                   <th>Reference</th>
    1407                </tr>
    1408             </thead>
    1409             <tbody>
    1410                <tr>
    1411                   <td class="left">Age</td>
    1412                   <td class="left">http</td>
    1413                   <td class="left">standard</td>
    1414                   <td class="left"> <a href="#header.age" id="rfc.xref.header.age.2" title="Age">Section&nbsp;3.1</a>
    1415                   </td>
    1416                </tr>
    1417                <tr>
    1418                   <td class="left">Cache-Control</td>
    1419                   <td class="left">http</td>
    1420                   <td class="left">standard</td>
    1421                   <td class="left"> <a href="#header.cache-control" id="rfc.xref.header.cache-control.4" title="Cache-Control">Section&nbsp;3.2</a>
    1422                   </td>
    1423                </tr>
    1424                <tr>
    1425                   <td class="left">Expires</td>
    1426                   <td class="left">http</td>
    1427                   <td class="left">standard</td>
    1428                   <td class="left"> <a href="#header.expires" id="rfc.xref.header.expires.4" title="Expires">Section&nbsp;3.3</a>
    1429                   </td>
    1430                </tr>
    1431                <tr>
    1432                   <td class="left">Pragma</td>
    1433                   <td class="left">http</td>
    1434                   <td class="left">standard</td>
    1435                   <td class="left"> <a href="#header.pragma" id="rfc.xref.header.pragma.3" title="Pragma">Section&nbsp;3.4</a>
    1436                   </td>
    1437                </tr>
    1438                <tr>
    1439                   <td class="left">Vary</td>
    1440                   <td class="left">http</td>
    1441                   <td class="left">standard</td>
    1442                   <td class="left"> <a href="#header.vary" id="rfc.xref.header.vary.2" title="Vary">Section&nbsp;3.5</a>
    1443                   </td>
    1444                </tr>
    1445                <tr>
    1446                   <td class="left">Warning</td>
    1447                   <td class="left">http</td>
    1448                   <td class="left">standard</td>
    1449                   <td class="left"> <a href="#header.warning" id="rfc.xref.header.warning.3" title="Warning">Section&nbsp;3.6</a>
    1450                   </td>
    1451                </tr>
    1452             </tbody>
    1453          </table>
     1387               the same code number, only differing in warn-text.
     1388            </p>
     1389            <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.
     1390            </p>
     1391            <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.
     1392            </p>
     1393            <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
     1394               a stored response after validation:
     1395            </p>
     1396            <ul>
     1397               <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.
     1398               </li>
     1399               <li>2xx Warnings describe some aspect of the entity body or entity headers that is not rectified by a validation (for example,
     1400                  a lossy compression of the entity bodies) 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.
     1401               </li>
     1402            </ul>
     1403            <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
     1404               the sender <em class="bcp14">MUST</em> include in each warning-value a warn-date that matches the Date header in the message.
     1405            </p>
     1406            <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
     1407               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
     1408               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.
     1409            </p>
     1410            <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
     1411               of its meaning.
     1412            </p>
     1413            <p id="rfc.section.3.6.p.12"> 110 Response is stale </p>
     1414            <ul class="empty">
     1415               <li><em class="bcp14">SHOULD</em> be included whenever the returned response is stale.
     1416               </li>
     1417            </ul>
     1418            <p id="rfc.section.3.6.p.13"> 111 Revalidation failed </p>
     1419            <ul class="empty">
     1420               <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
     1421                  reach the server.
     1422               </li>
     1423            </ul>
     1424            <p id="rfc.section.3.6.p.14"> 112 Disconnected operation </p>
     1425            <ul class="empty">
     1426               <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.
     1427               </li>
     1428            </ul>
     1429            <p id="rfc.section.3.6.p.15"> 113 Heuristic expiration </p>
     1430            <ul class="empty">
     1431               <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
     1432                  than 24 hours.
     1433               </li>
     1434            </ul>
     1435            <p id="rfc.section.3.6.p.16"> 199 Miscellaneous warning </p>
     1436            <ul class="empty">
     1437               <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.
     1438               </li>
     1439            </ul>
     1440            <p id="rfc.section.3.6.p.17"> 214 Transformation applied </p>
     1441            <ul class="empty">
     1442               <li><em class="bcp14">MUST</em> be added by an intermediate cache or proxy if it applies any transformation changing the content-coding (as specified in the
     1443                  Content-Encoding header) or media-type (as specified in the Content-Type header) of the response, or the entity-body of the
     1444                  response, unless this Warning code already appears in the response.
     1445               </li>
     1446            </ul>
     1447            <p id="rfc.section.3.6.p.18"> 299 Miscellaneous persistent warning </p>
     1448            <ul class="empty">
     1449               <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.
     1450               </li>
     1451            </ul>
     1452         </div>
    14541453      </div>
    1455       <p id="rfc.section.5.1.p.2">The change controller is: "IETF (iesg@ietf.org) - Internet Engineering Task Force".</p>
    1456       <h1 id="rfc.section.6"><a href="#rfc.section.6">6.</a>&nbsp;<a id="security.considerations" href="#security.considerations">Security Considerations</a></h1>
    1457       <p id="rfc.section.6.p.1">Caches expose additional potential vulnerabilities, since the contents of the cache represent an attractive target for malicious
    1458          exploitation. Because cache contents persist after an HTTP request is complete, an attack on the cache can reveal information
    1459          long after a user believes that the information has been removed from the network. Therefore, cache contents should be protected
    1460          as sensitive information.
    1461       </p>
    1462       <h1 id="rfc.section.7"><a href="#rfc.section.7">7.</a>&nbsp;<a id="ack" href="#ack">Acknowledgments</a></h1>
    1463       <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:
    1464          Shel Kaphan, Paul Leach, Koen Holtman, David Morris, and Larry Masinter.
    1465       </p>
     1454      <div id="history.lists">
     1455         <h1 id="rfc.section.4"><a href="#rfc.section.4">4.</a>&nbsp;<a href="#history.lists">History Lists</a></h1>
     1456         <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 an entity
     1457            retrieved earlier in a session.
     1458         </p>
     1459         <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
     1460            it has expired.
     1461         </p>
     1462         <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
     1463            (e.g., Cache-Control: no-store).
     1464         </p>
     1465      </div>
     1466      <div id="IANA.considerations">
     1467         <h1 id="rfc.section.5"><a href="#rfc.section.5">5.</a>&nbsp;<a href="#IANA.considerations">IANA Considerations</a></h1>
     1468         <div id="message.header.registration">
     1469            <h2 id="rfc.section.5.1"><a href="#rfc.section.5.1">5.1</a>&nbsp;<a href="#message.header.registration">Message Header Registration</a></h2>
     1470            <p id="rfc.section.5.1.p.1">The Message Header 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; should 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>):
     1471            </p>
     1472            <div id="rfc.table.1">
     1473               <div id="iana.header.registration.table"></div>
     1474               <table class="tt full left" cellpadding="3" cellspacing="0">
     1475                  <thead>
     1476                     <tr>
     1477                        <th>Header Field Name</th>
     1478                        <th>Protocol</th>
     1479                        <th>Status</th>
     1480                        <th>Reference</th>
     1481                     </tr>
     1482                  </thead>
     1483                  <tbody>
     1484                     <tr>
     1485                        <td class="left">Age</td>
     1486                        <td class="left">http</td>
     1487                        <td class="left">standard</td>
     1488                        <td class="left"><a href="#header.age" id="rfc.xref.header.age.2" title="Age">Section&nbsp;3.1</a>
     1489                        </td>
     1490                     </tr>
     1491                     <tr>
     1492                        <td class="left">Cache-Control</td>
     1493                        <td class="left">http</td>
     1494                        <td class="left">standard</td>
     1495                        <td class="left"><a href="#header.cache-control" id="rfc.xref.header.cache-control.4" title="Cache-Control">Section&nbsp;3.2</a>
     1496                        </td>
     1497                     </tr>
     1498                     <tr>
     1499                        <td class="left">Expires</td>
     1500                        <td class="left">http</td>
     1501                        <td class="left">standard</td>
     1502                        <td class="left"><a href="#header.expires" id="rfc.xref.header.expires.4" title="Expires">Section&nbsp;3.3</a>
     1503                        </td>
     1504                     </tr>
     1505                     <tr>
     1506                        <td class="left">Pragma</td>
     1507                        <td class="left">http</td>
     1508                        <td class="left">standard</td>
     1509                        <td class="left"><a href="#header.pragma" id="rfc.xref.header.pragma.3" title="Pragma">Section&nbsp;3.4</a>
     1510                        </td>
     1511                     </tr>
     1512                     <tr>
     1513                        <td class="left">Vary</td>
     1514                        <td class="left">http</td>
     1515                        <td class="left">standard</td>
     1516                        <td class="left"><a href="#header.vary" id="rfc.xref.header.vary.2" title="Vary">Section&nbsp;3.5</a>
     1517                        </td>
     1518                     </tr>
     1519                     <tr>
     1520                        <td class="left">Warning</td>
     1521                        <td class="left">http</td>
     1522                        <td class="left">standard</td>
     1523                        <td class="left"><a href="#header.warning" id="rfc.xref.header.warning.3" title="Warning">Section&nbsp;3.6</a>
     1524                        </td>
     1525                     </tr>
     1526                  </tbody>
     1527               </table>
     1528            </div>
     1529            <p id="rfc.section.5.1.p.2">The change controller is: "IETF (iesg@ietf.org) - Internet Engineering Task Force".</p>
     1530         </div>
     1531      </div>
     1532      <div id="security.considerations">
     1533         <h1 id="rfc.section.6"><a href="#rfc.section.6">6.</a>&nbsp;<a href="#security.considerations">Security Considerations</a></h1>
     1534         <p id="rfc.section.6.p.1">Caches expose additional potential vulnerabilities, since the contents of the cache represent an attractive target for malicious
     1535            exploitation. Because cache contents persist after an HTTP request is complete, an attack on the cache can reveal information
     1536            long after a user believes that the information has been removed from the network. Therefore, cache contents should be protected
     1537            as sensitive information.
     1538         </p>
     1539      </div>
     1540      <div id="ack">
     1541         <h1 id="rfc.section.7"><a href="#rfc.section.7">7.</a>&nbsp;<a href="#ack">Acknowledgments</a></h1>
     1542         <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:
     1543            Shel Kaphan, Paul Leach, Koen Holtman, David Morris, and Larry Masinter.
     1544         </p>
     1545      </div>
    14661546      <h1 id="rfc.references"><a id="rfc.section.8" href="#rfc.section.8">8.</a> References
    14671547      </h1>
    14681548      <h2 id="rfc.references.1"><a href="#rfc.section.8.1" id="rfc.section.8.1">8.1</a> Normative References
    14691549      </h2>
    1470       <table>             
     1550      <table>
    14711551         <tr>
    14721552            <td class="reference"><b id="Part1">[Part1]</b></td>
    1473             <td class="top"><a href="mailto:fielding@gbiv.com" title="Day Software">Fielding, R., Ed.</a>, <a href="mailto:jg@laptop.org" title="One Laptop per Child">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. F. Reschke, Ed.</a>, “<a href="http://tools.ietf.org/html/draft-ietf-httpbis-p1-messaging-09">HTTP/1.1, part 1: URIs, Connections, and Message Parsing</a>”, Internet-Draft&nbsp;draft-ietf-httpbis-p1-messaging-09 (work in progress), March&nbsp;2010.
     1553            <td class="top"><a href="mailto:fielding@gbiv.com" title="Day Software">Fielding, R., Ed.</a>, <a href="mailto:jg@laptop.org" title="One Laptop per Child">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-09">HTTP/1.1, part 1: URIs, Connections, and Message Parsing</a>”, Internet-Draft&nbsp;draft-ietf-httpbis-p1-messaging-09 (work in progress), March&nbsp;2010.
    14741554            </td>
    14751555         </tr>
    14761556         <tr>
    14771557            <td class="reference"><b id="Part2">[Part2]</b></td>
    1478             <td class="top"><a href="mailto:fielding@gbiv.com" title="Day Software">Fielding, R., Ed.</a>, <a href="mailto:jg@laptop.org" title="One Laptop per Child">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. F. Reschke, Ed.</a>, “<a href="http://tools.ietf.org/html/draft-ietf-httpbis-p2-semantics-09">HTTP/1.1, part 2: Message Semantics</a>”, Internet-Draft&nbsp;draft-ietf-httpbis-p2-semantics-09 (work in progress), March&nbsp;2010.
     1558            <td class="top"><a href="mailto:fielding@gbiv.com" title="Day Software">Fielding, R., Ed.</a>, <a href="mailto:jg@laptop.org" title="One Laptop per Child">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-09">HTTP/1.1, part 2: Message Semantics</a>”, Internet-Draft&nbsp;draft-ietf-httpbis-p2-semantics-09 (work in progress), March&nbsp;2010.
    14791559            </td>
    14801560         </tr>
    14811561         <tr>
    14821562            <td class="reference"><b id="Part4">[Part4]</b></td>
    1483             <td class="top"><a href="mailto:fielding@gbiv.com" title="Day Software">Fielding, R., Ed.</a>, <a href="mailto:jg@laptop.org" title="One Laptop per Child">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. F. Reschke, Ed.</a>, “<a href="http://tools.ietf.org/html/draft-ietf-httpbis-p4-conditional-09">HTTP/1.1, part 4: Conditional Requests</a>”, Internet-Draft&nbsp;draft-ietf-httpbis-p4-conditional-09 (work in progress), March&nbsp;2010.
     1563            <td class="top"><a href="mailto:fielding@gbiv.com" title="Day Software">Fielding, R., Ed.</a>, <a href="mailto:jg@laptop.org" title="One Laptop per Child">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-09">HTTP/1.1, part 4: Conditional Requests</a>”, Internet-Draft&nbsp;draft-ietf-httpbis-p4-conditional-09 (work in progress), March&nbsp;2010.
    14841564            </td>
    14851565         </tr>
    14861566         <tr>
    14871567            <td class="reference"><b id="Part5">[Part5]</b></td>
    1488             <td class="top"><a href="mailto:fielding@gbiv.com" title="Day Software">Fielding, R., Ed.</a>, <a href="mailto:jg@laptop.org" title="One Laptop per Child">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. F. Reschke, Ed.</a>, “<a href="http://tools.ietf.org/html/draft-ietf-httpbis-p5-range-09">HTTP/1.1, part 5: Range Requests and Partial Responses</a>”, Internet-Draft&nbsp;draft-ietf-httpbis-p5-range-09 (work in progress), March&nbsp;2010.
     1568            <td class="top"><a href="mailto:fielding@gbiv.com" title="Day Software">Fielding, R., Ed.</a>, <a href="mailto:jg@laptop.org" title="One Laptop per Child">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-09">HTTP/1.1, part 5: Range Requests and Partial Responses</a>”, Internet-Draft&nbsp;draft-ietf-httpbis-p5-range-09 (work in progress), March&nbsp;2010.
    14891569            </td>
    14901570         </tr>
    14911571         <tr>
    14921572            <td class="reference"><b id="Part7">[Part7]</b></td>
    1493             <td class="top"><a href="mailto:fielding@gbiv.com" title="Day Software">Fielding, R., Ed.</a>, <a href="mailto:jg@laptop.org" title="One Laptop per Child">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. F. Reschke, Ed.</a>, “<a href="http://tools.ietf.org/html/draft-ietf-httpbis-p7-auth-09">HTTP/1.1, part 7: Authentication</a>”, Internet-Draft&nbsp;draft-ietf-httpbis-p7-auth-09 (work in progress), March&nbsp;2010.
     1573            <td class="top"><a href="mailto:fielding@gbiv.com" title="Day Software">Fielding, R., Ed.</a>, <a href="mailto:jg@laptop.org" title="One Laptop per Child">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-09">HTTP/1.1, part 7: Authentication</a>”, Internet-Draft&nbsp;draft-ietf-httpbis-p7-auth-09 (work in progress), March&nbsp;2010.
    14941574            </td>
    14951575         </tr>
    14961576         <tr>
    14971577            <td class="reference"><b id="RFC2119">[RFC2119]</b></td>
    1498             <td class="top"><a href="mailto:sob@harvard.edu" title="Harvard University">Bradner, S.</a>, “<a href="http://tools.ietf.org/html/rfc2119">Key words for use in RFCs to Indicate Requirement Levels</a>”, BCP&nbsp;14, RFC&nbsp;2119, March&nbsp;1997.
     1578            <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.
    14991579            </td>
    15001580         </tr>
    15011581         <tr>
    15021582            <td class="reference"><b id="RFC5234">[RFC5234]</b></td>
    1503             <td class="top"><a href="mailto:dcrocker@bbiw.net" title="Brandenburg InternetWorking">Crocker, D., Ed.</a> and <a href="mailto:paul.overell@thus.net" title="THUS plc.">P. Overell</a>, “<a href="http://tools.ietf.org/html/rfc5234">Augmented BNF for Syntax Specifications: ABNF</a>”, STD&nbsp;68, RFC&nbsp;5234, January&nbsp;2008.
     1583            <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.
    15041584            </td>
    15051585         </tr>
     
    15071587      <h2 id="rfc.references.2"><a href="#rfc.section.8.2" id="rfc.section.8.2">8.2</a> Informative References
    15081588      </h2>
    1509       <table>     
     1589      <table>
    15101590         <tr>
    15111591            <td class="reference"><b id="RFC1305">[RFC1305]</b></td>
    1512             <td class="top"><a href="mailto:mills@udel.edu" title="University of Delaware, Electrical Engineering Department">Mills, D.</a>, “<a href="http://tools.ietf.org/html/rfc1305">Network Time Protocol (Version 3) Specification, Implementation</a>”, RFC&nbsp;1305, March&nbsp;1992.
     1592            <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.
    15131593            </td>
    15141594         </tr>
    15151595         <tr>
    15161596            <td class="reference"><b id="RFC2616">[RFC2616]</b></td>
    1517             <td class="top"><a href="mailto:fielding@ics.uci.edu" title="University of California, Irvine">Fielding, R.</a>, <a href="mailto:jg@w3.org" title="W3C">Gettys, J.</a>, <a href="mailto:mogul@wrl.dec.com" title="Compaq Computer Corporation">Mogul, J.</a>, <a href="mailto:frystyk@w3.org" title="MIT Laboratory for Computer Science">Frystyk, H.</a>, <a href="mailto:masinter@parc.xerox.com" title="Xerox Corporation">Masinter, L.</a>, <a href="mailto:paulle@microsoft.com" title="Microsoft Corporation">Leach, P.</a>, and <a href="mailto:timbl@w3.org" title="W3C">T. Berners-Lee</a>, “<a href="http://tools.ietf.org/html/rfc2616">Hypertext Transfer Protocol -- HTTP/1.1</a>”, RFC&nbsp;2616, June&nbsp;1999.
     1597            <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.
    15181598            </td>
    15191599         </tr>
    15201600         <tr>
    15211601            <td class="reference"><b id="RFC3864">[RFC3864]</b></td>
    1522             <td class="top"><a href="mailto:GK-IETF@ninebynine.org" title="Nine by Nine">Klyne, G.</a>, <a href="mailto:mnot@pobox.com" title="BEA Systems">Nottingham, M.</a>, and <a href="mailto:JeffMogul@acm.org" title="HP Labs">J. Mogul</a>, “<a href="http://tools.ietf.org/html/rfc3864">Registration Procedures for Message Header Fields</a>”, BCP&nbsp;90, RFC&nbsp;3864, September&nbsp;2004.
     1602            <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.
    15231603            </td>
    15241604         </tr>
    15251605      </table>
    1526       <div class="avoidbreak">
    1527          <h1 id="rfc.authors"><a href="#rfc.authors">Authors' Addresses</a></h1>
    1528          <address class="vcard"><span class="vcardline"><span class="fn">Roy T. Fielding</span>
    1529                (editor)
    1530                <span class="n hidden"><span class="family-name">Fielding</span><span class="given-name">Roy T.</span></span></span><span class="org vcardline">Day Software</span><span class="adr"><span class="street-address vcardline">23 Corporate Plaza DR, Suite 280</span><span class="vcardline"><span class="locality">Newport Beach</span>, <span class="region">CA</span>&nbsp;<span class="postal-code">92660</span></span><span class="country-name vcardline">USA</span></span><span class="vcardline tel">Phone: <a href="tel:+1-949-706-5300"><span class="value">+1-949-706-5300</span></a></span><span class="vcardline tel"><span class="type">Fax</span>: <a href="fax:+1-949-706-5305"><span class="value">+1-949-706-5305</span></a></span><span class="vcardline">EMail: <a href="mailto:fielding@gbiv.com"><span class="email">fielding@gbiv.com</span></a></span><span class="vcardline">URI: <a href="http://roy.gbiv.com/" class="url">http://roy.gbiv.com/</a></span></address>
    1531          <address class="vcard"><span class="vcardline"><span class="fn">Jim Gettys</span><span class="n hidden"><span class="family-name">Gettys</span><span class="given-name">Jim</span></span></span><span class="org vcardline">One Laptop per Child</span><span class="adr"><span class="street-address vcardline">21 Oak Knoll Road</span><span class="vcardline"><span class="locality">Carlisle</span>, <span class="region">MA</span>&nbsp;<span class="postal-code">01741</span></span><span class="country-name vcardline">USA</span></span><span class="vcardline">EMail: <a href="mailto:jg@laptop.org"><span class="email">jg@laptop.org</span></a></span><span class="vcardline">URI: <a href="http://www.laptop.org/" class="url">http://www.laptop.org/</a></span></address>
    1532          <address class="vcard"><span class="vcardline"><span class="fn">Jeffrey C. Mogul</span><span class="n hidden"><span class="family-name">Mogul</span><span class="given-name">Jeffrey C.</span></span></span><span class="org vcardline">Hewlett-Packard Company</span><span class="adr"><span class="street-address vcardline">HP Labs, Large Scale Systems Group</span><span class="street-address vcardline">1501 Page Mill Road, MS 1177</span><span class="vcardline"><span class="locality">Palo Alto</span>, <span class="region">CA</span>&nbsp;<span class="postal-code">94304</span></span><span class="country-name vcardline">USA</span></span><span class="vcardline">EMail: <a href="mailto:JeffMogul@acm.org"><span class="email">JeffMogul@acm.org</span></a></span></address>
    1533          <address class="vcard"><span class="vcardline"><span class="fn">Henrik Frystyk Nielsen</span><span class="n hidden"><span class="family-name">Frystyk</span></span></span><span class="org vcardline">Microsoft Corporation</span><span class="adr"><span class="street-address vcardline">1 Microsoft Way</span><span class="vcardline"><span class="locality">Redmond</span>, <span class="region">WA</span>&nbsp;<span class="postal-code">98052</span></span><span class="country-name vcardline">USA</span></span><span class="vcardline">EMail: <a href="mailto:henrikn@microsoft.com"><span class="email">henrikn@microsoft.com</span></a></span></address>
    1534          <address class="vcard"><span class="vcardline"><span class="fn">Larry Masinter</span><span class="n hidden"><span class="family-name">Masinter</span><span class="given-name">Larry</span></span></span><span class="org vcardline">Adobe Systems, Incorporated</span><span class="adr"><span class="street-address vcardline">345 Park Ave</span><span class="vcardline"><span class="locality">San Jose</span>, <span class="region">CA</span>&nbsp;<span class="postal-code">95110</span></span><span class="country-name vcardline">USA</span></span><span class="vcardline">EMail: <a href="mailto:LMM@acm.org"><span class="email">LMM@acm.org</span></a></span><span class="vcardline">URI: <a href="http://larry.masinter.net/" class="url">http://larry.masinter.net/</a></span></address>
    1535          <address class="vcard"><span class="vcardline"><span class="fn">Paul J. Leach</span><span class="n hidden"><span class="family-name">Leach</span><span class="given-name">Paul J.</span></span></span><span class="org vcardline">Microsoft Corporation</span><span class="adr"><span class="street-address vcardline">1 Microsoft Way</span><span class="vcardline"><span class="locality">Redmond</span>, <span class="region">WA</span>&nbsp;<span class="postal-code">98052</span></span></span><span class="vcardline">EMail: <a href="mailto:paulle@microsoft.com"><span class="email">paulle@microsoft.com</span></a></span></address>
    1536          <address class="vcard"><span class="vcardline"><span class="fn">Tim Berners-Lee</span><span class="n hidden"><span class="family-name">Berners-Lee</span><span class="given-name">Tim</span></span></span><span class="org vcardline">World Wide Web Consortium</span><span class="adr"><span class="street-address vcardline">MIT Computer Science and Artificial Intelligence Laboratory</span><span class="street-address vcardline">The Stata Center, Building 32</span><span class="street-address vcardline">32 Vassar Street</span><span class="vcardline"><span class="locality">Cambridge</span>, <span class="region">MA</span>&nbsp;<span class="postal-code">02139</span></span><span class="country-name vcardline">USA</span></span><span class="vcardline">EMail: <a href="mailto:timbl@w3.org"><span class="email">timbl@w3.org</span></a></span><span class="vcardline">URI: <a href="http://www.w3.org/People/Berners-Lee/" class="url">http://www.w3.org/People/Berners-Lee/</a></span></address>
    1537          <address class="vcard"><span class="vcardline"><span class="fn">Yves Lafon</span>
    1538                (editor)
    1539                <span class="n hidden"><span class="family-name">Lafon</span><span class="given-name">Yves</span></span></span><span class="org vcardline">World Wide Web Consortium</span><span class="adr"><span class="street-address vcardline">W3C / ERCIM</span><span class="street-address vcardline">2004, rte des Lucioles</span><span class="vcardline"><span class="locality">Sophia-Antipolis</span>, <span class="region">AM</span>&nbsp;<span class="postal-code">06902</span></span><span class="country-name vcardline">France</span></span><span class="vcardline">EMail: <a href="mailto:ylafon@w3.org"><span class="email">ylafon@w3.org</span></a></span><span class="vcardline">URI: <a href="http://www.raubacapeu.net/people/yves/" class="url">http://www.raubacapeu.net/people/yves/</a></span></address>
    1540          <address class="vcard"><span class="vcardline"><span class="fn">Mark Nottingham</span>
    1541                (editor)
    1542                <span class="n hidden"><span class="family-name">Nottingham</span><span class="given-name">Mark</span></span></span><span class="vcardline">EMail: <a href="mailto:mnot@mnot.net"><span class="email">mnot@mnot.net</span></a></span><span class="vcardline">URI: <a href="http://www.mnot.net/" class="url">http://www.mnot.net/</a></span></address>
    1543          <address class="vcard"><span class="vcardline"><span class="fn">Julian F. Reschke</span>
    1544                (editor)
    1545                <span class="n hidden"><span class="family-name">Reschke</span><span class="given-name">Julian F.</span></span></span><span class="org vcardline">greenbytes GmbH</span><span class="adr"><span class="street-address vcardline">Hafenweg 16</span><span class="vcardline"><span class="locality">Muenster</span>, <span class="region">NW</span>&nbsp;<span class="postal-code">48155</span></span><span class="country-name vcardline">Germany</span></span><span class="vcardline tel">Phone: <a href="tel:+492512807760"><span class="value">+49 251 2807760</span></a></span><span class="vcardline tel"><span class="type">Fax</span>: <a href="fax:+492512807761"><span class="value">+49 251 2807761</span></a></span><span class="vcardline">EMail: <a href="mailto:julian.reschke@greenbytes.de"><span class="email">julian.reschke@greenbytes.de</span></a></span><span class="vcardline">URI: <a href="http://greenbytes.de/tech/webdav/" class="url">http://greenbytes.de/tech/webdav/</a></span></address>
     1606      <div id="compatibility">
     1607         <h1 id="rfc.section.A" class="np"><a href="#rfc.section.A">A.</a>&nbsp;<a href="#compatibility">Compatibility with Previous Versions</a></h1>
     1608         <div id="changes.from.rfc.2068">
     1609            <h2 id="rfc.section.A.1"><a href="#rfc.section.A.1">A.1</a>&nbsp;<a href="#changes.from.rfc.2068">Changes from RFC 2068</a></h2>
     1610            <p id="rfc.section.A.1.p.1">A case was missed in the Cache-Control model of HTTP/1.1; s-maxage was introduced to add this missing case. (Sections <a href="#response.cacheability" title="Response Cacheability">2.1</a>, <a href="#header.cache-control" id="rfc.xref.header.cache-control.5" title="Cache-Control">3.2</a>).
     1611            </p>
     1612            <p id="rfc.section.A.1.p.2">Range request responses would become very verbose if all meta-data were always returned; by allowing the server to only send
     1613               needed headers in a 206 response, this problem can be avoided. (<a href="#combining.headers" title="Combining Responses">Section&nbsp;2.7</a>)
     1614            </p>
     1615            <p id="rfc.section.A.1.p.3">The Cache-Control: max-age directive was not properly defined for responses. (<a href="#cache-response-directive" title="Response Cache-Control Directives">Section&nbsp;3.2.2</a>)
     1616            </p>
     1617            <p id="rfc.section.A.1.p.4">Warnings could be cached incorrectly, or not updated appropriately. (Section <a href="#expiration.model" title="Freshness Model">2.3</a>, <a href="#combining.headers" title="Combining Responses">2.7</a>, <a href="#header.cache-control" id="rfc.xref.header.cache-control.6" title="Cache-Control">3.2</a>, and <a href="#header.warning" id="rfc.xref.header.warning.4" title="Warning">3.6</a>) Warning also needed to be a general header, as PUT or other methods may have need for it in requests.
     1618            </p>
     1619         </div>
     1620         <div id="changes.from.rfc.2616">
     1621            <h2 id="rfc.section.A.2"><a href="#rfc.section.A.2">A.2</a>&nbsp;<a href="#changes.from.rfc.2616">Changes from RFC 2616</a></h2>
     1622            <p id="rfc.section.A.2.p.1">Remove requirement to consider Content-Location in successful responses in order to determine the appropriate response to
     1623               use. (<a href="#validation.model" title="Validation Model">Section&nbsp;2.4</a>)
     1624            </p>
     1625            <p id="rfc.section.A.2.p.2">Clarify denial of service attack avoidance requirement. (<a href="#invalidation.after.updates.or.deletions" title="Request Methods that Invalidate">Section&nbsp;2.5</a>)
     1626            </p>
     1627            <p id="rfc.section.A.2.p.3">Do not mention RFC 2047 encoding and multiple languages in Warning headers anymore, as these aspects never were implemented.
     1628               (<a href="#header.warning" id="rfc.xref.header.warning.5" title="Warning">Section&nbsp;3.6</a>)
     1629            </p>
     1630         </div>
    15461631      </div>
    1547       <h1 id="rfc.section.A" class="np"><a href="#rfc.section.A">A.</a>&nbsp;<a id="compatibility" href="#compatibility">Compatibility with Previous Versions</a></h1>
    1548       <h2 id="rfc.section.A.1"><a href="#rfc.section.A.1">A.1</a>&nbsp;<a id="changes.from.rfc.2068" href="#changes.from.rfc.2068">Changes from RFC 2068</a></h2>
    1549       <p id="rfc.section.A.1.p.1">A case was missed in the Cache-Control model of HTTP/1.1; s-maxage was introduced to add this missing case. (Sections <a href="#response.cacheability" title="Response Cacheability">2.1</a>, <a href="#header.cache-control" id="rfc.xref.header.cache-control.5" title="Cache-Control">3.2</a>).
    1550       </p>
    1551       <p id="rfc.section.A.1.p.2">Range request responses would become very verbose if all meta-data were always returned; by allowing the server to only send
    1552          needed headers in a 206 response, this problem can be avoided. (<a href="#combining.headers" title="Combining Responses">Section&nbsp;2.7</a>)
    1553       </p>
    1554       <p id="rfc.section.A.1.p.3">The Cache-Control: max-age directive was not properly defined for responses. (<a href="#cache-response-directive" title="Response Cache-Control Directives">Section&nbsp;3.2.2</a>)
    1555       </p>
    1556       <p id="rfc.section.A.1.p.4">Warnings could be cached incorrectly, or not updated appropriately. (Section <a href="#expiration.model" title="Freshness Model">2.3</a>, <a href="#combining.headers" title="Combining Responses">2.7</a>, <a href="#header.cache-control" id="rfc.xref.header.cache-control.6" title="Cache-Control">3.2</a>, and <a href="#header.warning" id="rfc.xref.header.warning.4" title="Warning">3.6</a>) Warning also needed to be a general header, as PUT or other methods may have need for it in requests.
    1557       </p>
    1558       <h2 id="rfc.section.A.2"><a href="#rfc.section.A.2">A.2</a>&nbsp;<a id="changes.from.rfc.2616" href="#changes.from.rfc.2616">Changes from RFC 2616</a></h2>
    1559       <p id="rfc.section.A.2.p.1">Remove requirement to consider Content-Location in successful responses in order to determine the appropriate response to
    1560          use. (<a href="#validation.model" title="Validation Model">Section&nbsp;2.4</a>)
    1561       </p>
    1562       <p id="rfc.section.A.2.p.2">Clarify denial of service attack avoidance requirement. (<a href="#invalidation.after.updates.or.deletions" title="Request Methods that Invalidate">Section&nbsp;2.5</a>)
    1563       </p>
    1564       <p id="rfc.section.A.2.p.3">Do not mention RFC 2047 encoding and multiple languages in Warning headers anymore, as these aspects never were implemented.
    1565          (<a href="#header.warning" id="rfc.xref.header.warning.5" title="Warning">Section&nbsp;3.6</a>)
    1566       </p>
    1567       <h1 id="rfc.section.B"><a href="#rfc.section.B">B.</a>&nbsp;<a id="collected.abnf" href="#collected.abnf">Collected ABNF</a></h1>
    1568       <div id="rfc.figure.u.18"></div> <pre class="inline"><a href="#header.age" class="smpl">Age</a> = "Age:" OWS Age-v
     1632      <div id="collected.abnf">
     1633         <h1 id="rfc.section.B"><a href="#rfc.section.B">B.</a>&nbsp;<a href="#collected.abnf">Collected ABNF</a></h1>
     1634         <div id="rfc.figure.u.18"></div><pre class="inline"><a href="#header.age" class="smpl">Age</a> = "Age:" OWS Age-v
    15691635<a href="#header.age" class="smpl">Age-v</a> = delta-seconds
    15701636
     
    16271693<a href="#header.warning" class="smpl">warning-value</a> = warn-code SP warn-agent SP warn-text [ SP warn-date
    16281694 ]
    1629 </pre> <div id="rfc.figure.u.19"></div>
    1630       <p>ABNF diagnostics:</p><pre class="inline">; Age defined but not used
     1695</pre><div id="rfc.figure.u.19"></div>
     1696         <p>ABNF diagnostics:</p><pre class="inline">; Age defined but not used
    16311697; Cache-Control defined but not used
    16321698; Expires defined but not used
     
    16341700; Vary defined but not used
    16351701; Warning defined but not used
    1636 </pre><h1 id="rfc.section.C"><a href="#rfc.section.C">C.</a>&nbsp;<a id="change.log" href="#change.log">Change Log (to be removed by RFC Editor before publication)</a></h1>
    1637       <h2 id="rfc.section.C.1"><a href="#rfc.section.C.1">C.1</a>&nbsp;Since RFC2616
    1638       </h2>
    1639       <p id="rfc.section.C.1.p.1">Extracted relevant partitions from <a href="#RFC2616" id="rfc.xref.RFC2616.1"><cite title="Hypertext Transfer Protocol -- HTTP/1.1">[RFC2616]</cite></a>.
    1640       </p>
    1641       <h2 id="rfc.section.C.2"><a href="#rfc.section.C.2">C.2</a>&nbsp;Since draft-ietf-httpbis-p6-cache-00
    1642       </h2>
    1643       <p id="rfc.section.C.2.p.1">Closed issues: </p>
    1644       <ul>
    1645          <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;)
    1646          </li>
    1647          <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;)
    1648          </li>
    1649          <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"
    1650          </li>
    1651          <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"
    1652          </li>
    1653          <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"
    1654          </li>
    1655          <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"
    1656          </li>
    1657          <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"
    1658          </li>
    1659          <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"
    1660          </li>
    1661          <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"
    1662          </li>
    1663       </ul>
    1664       <p id="rfc.section.C.2.p.2">Other changes: </p>
    1665       <ul>
    1666          <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;)
    1667          </li>
    1668       </ul>
    1669       <h2 id="rfc.section.C.3"><a href="#rfc.section.C.3">C.3</a>&nbsp;Since draft-ietf-httpbis-p6-cache-01
    1670       </h2>
    1671       <p id="rfc.section.C.3.p.1">Closed issues: </p>
    1672       <ul>
    1673          <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"
    1674          </li>
    1675       </ul>
    1676       <p id="rfc.section.C.3.p.2">Other changes: </p>
    1677       <ul>
    1678          <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;)
    1679          </li>
    1680          <li>Add explicit references to BNF syntax and rules imported from other parts of the specification.</li>
    1681       </ul>
    1682       <h2 id="rfc.section.C.4"><a href="#rfc.section.C.4">C.4</a>&nbsp;<a id="changes.since.02" href="#changes.since.02">Since draft-ietf-httpbis-p6-cache-02</a></h2>
    1683       <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;):
    1684       </p>
    1685       <ul>
    1686          <li>Reference RFC 3984, and update header registrations for headers defined in this document.</li>
    1687       </ul>
    1688       <h2 id="rfc.section.C.5"><a href="#rfc.section.C.5">C.5</a>&nbsp;<a id="changes.since.03" href="#changes.since.03">Since draft-ietf-httpbis-p6-cache-03</a></h2>
    1689       <p id="rfc.section.C.5.p.1">Closed issues: </p>
    1690       <ul>
    1691          <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"
    1692          </li>
    1693       </ul>
    1694       <h2 id="rfc.section.C.6"><a href="#rfc.section.C.6">C.6</a>&nbsp;<a id="changes.since.04" href="#changes.since.04">Since draft-ietf-httpbis-p6-cache-04</a></h2>
    1695       <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;):
    1696       </p>
    1697       <ul>
    1698          <li>Use "/" instead of "|" for alternatives.</li>
    1699          <li>Introduce new ABNF rules for "bad" whitespace ("BWS"), optional whitespace ("OWS") and required whitespace ("RWS").</li>
    1700          <li>Rewrite ABNFs to spell out whitespace rules, factor out header value format definitions.</li>
    1701       </ul>
    1702       <h2 id="rfc.section.C.7"><a href="#rfc.section.C.7">C.7</a>&nbsp;<a id="changes.since.05" href="#changes.since.05">Since draft-ietf-httpbis-p6-cache-05</a></h2>
    1703       <p id="rfc.section.C.7.p.1">This is a total rewrite of this part of the specification.</p>
    1704       <p id="rfc.section.C.7.p.2">Affected issues: </p>
    1705       <ul>
    1706          <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"
    1707          </li>
    1708          <li> &lt;<a href="http://trac.tools.ietf.org/wg/httpbis/trac/ticket/60">http://trac.tools.ietf.org/wg/httpbis/trac/ticket/60</a>&gt;: "Placement of 13.5.1 and 13.5.2"
    1709          </li>
    1710          <li> &lt;<a href="http://trac.tools.ietf.org/wg/httpbis/trac/ticket/138">http://trac.tools.ietf.org/wg/httpbis/trac/ticket/138</a>&gt;: "The role of Warning and Semantic Transparency in Caching"
    1711          </li>
    1712          <li> &lt;<a href="http://trac.tools.ietf.org/wg/httpbis/trac/ticket/139">http://trac.tools.ietf.org/wg/httpbis/trac/ticket/139</a>&gt;: "Methods and Caching"
    1713          </li>
    1714       </ul>
    1715       <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;):
    1716       </p>
    1717       <ul>
    1718          <li>Add appendix containing collected and expanded ABNF, reorganize ABNF introduction.</li>
    1719       </ul>
    1720       <h2 id="rfc.section.C.8"><a href="#rfc.section.C.8">C.8</a>&nbsp;<a id="changes.since.06" href="#changes.since.06">Since draft-ietf-httpbis-p6-cache-06</a></h2>
    1721       <p id="rfc.section.C.8.p.1">Closed issues: </p>
    1722       <ul>
    1723          <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"
    1724          </li>
    1725       </ul>
    1726       <p id="rfc.section.C.8.p.2">Affected issues: </p>
    1727       <ul>
    1728          <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
    1729          </li>
    1730       </ul>
    1731       <h2 id="rfc.section.C.9"><a href="#rfc.section.C.9">C.9</a>&nbsp;<a id="changes.since.07" href="#changes.since.07">Since draft-ietf-httpbis-p6-cache-07</a></h2>
    1732       <p id="rfc.section.C.9.p.1">Closed issues: </p>
    1733       <ul>
    1734          <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"
    1735          </li>
    1736          <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"
    1737          </li>
    1738          <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"
    1739          </li>
    1740          <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"
    1741          </li>
    1742       </ul>
    1743       <h2 id="rfc.section.C.10"><a href="#rfc.section.C.10">C.10</a>&nbsp;<a id="changes.since.08" href="#changes.since.08">Since draft-ietf-httpbis-p6-cache-08</a></h2>
    1744       <p id="rfc.section.C.10.p.1">Closed issues: </p>
    1745       <ul>
    1746          <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"
    1747          </li>
    1748          <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"
    1749          </li>
    1750       </ul>
    1751       <p id="rfc.section.C.10.p.2">Affected issues: </p>
    1752       <ul>
    1753          <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
    1754          </li>
    1755       </ul>
    1756       <p id="rfc.section.C.10.p.3">Partly resolved issues: </p>
    1757       <ul>
    1758          <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"
    1759          </li>
    1760       </ul>
     1702</pre></div>
     1703      <div id="change.log">
     1704         <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>
     1705         <div>
     1706            <h2 id="rfc.section.C.1"><a href="#rfc.section.C.1">C.1</a>&nbsp;Since RFC2616
     1707            </h2>
     1708            <p id="rfc.section.C.1.p.1">Extracted relevant partitions from <a href="#RFC2616" id="rfc.xref.RFC2616.1"><cite title="Hypertext Transfer Protocol -- HTTP/1.1">[RFC2616]</cite></a>.
     1709            </p>
     1710         </div>
     1711         <div>
     1712            <h2 id="rfc.section.C.2"><a href="#rfc.section.C.2">C.2</a>&nbsp;Since draft-ietf-httpbis-p6-cache-00
     1713            </h2>
     1714            <p id="rfc.section.C.2.p.1">Closed issues: </p>
     1715            <ul>
     1716               <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;)
     1717               </li>
     1718               <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;)
     1719               </li>
     1720               <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"
     1721               </li>
     1722               <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"
     1723               </li>
     1724               <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"
     1725               </li>
     1726               <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"
     1727               </li>
     1728               <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"
     1729               </li>
     1730               <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"
     1731               </li>
     1732               <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"
     1733               </li>
     1734            </ul>
     1735            <p id="rfc.section.C.2.p.2">Other changes: </p>
     1736            <ul>
     1737               <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;)
     1738               </li>
     1739            </ul>
     1740         </div>
     1741         <div>
     1742            <h2 id="rfc.section.C.3"><a href="#rfc.section.C.3">C.3</a>&nbsp;Since draft-ietf-httpbis-p6-cache-01
     1743            </h2>
     1744            <p id="rfc.section.C.3.p.1">Closed issues: </p>
     1745            <ul>
     1746               <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"
     1747               </li>
     1748            </ul>
     1749            <p id="rfc.section.C.3.p.2">Other changes: </p>
     1750            <ul>
     1751               <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;)
     1752               </li>
     1753               <li>Add explicit references to BNF syntax and rules imported from other parts of the specification.</li>
     1754            </ul>
     1755         </div>
     1756         <div id="changes.since.02">
     1757            <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>
     1758            <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;):
     1759            </p>
     1760            <ul>
     1761               <li>Reference RFC 3984, and update header registrations for headers defined in this document.</li>
     1762            </ul>
     1763         </div>
     1764         <div id="changes.since.03">
     1765            <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>
     1766            <p id="rfc.section.C.5.p.1">Closed issues: </p>
     1767            <ul>
     1768               <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"
     1769               </li>
     1770            </ul>
     1771         </div>
     1772         <div id="changes.since.04">
     1773            <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>
     1774            <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;):
     1775            </p>
     1776            <ul>
     1777               <li>Use "/" instead of "|" for alternatives.</li>
     1778               <li>Introduce new ABNF rules for "bad" whitespace ("BWS"), optional whitespace ("OWS") and required whitespace ("RWS").</li>
     1779               <li>Rewrite ABNFs to spell out whitespace rules, factor out header value format definitions.</li>
     1780            </ul>
     1781         </div>
     1782         <div id="changes.since.05">
     1783            <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>
     1784            <p id="rfc.section.C.7.p.1">This is a total rewrite of this part of the specification.</p>
     1785            <p id="rfc.section.C.7.p.2">Affected issues: </p>
     1786            <ul>
     1787               <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"
     1788               </li>
     1789               <li>&lt;<a href="http://trac.tools.ietf.org/wg/httpbis/trac/ticket/60">http://trac.tools.ietf.org/wg/httpbis/trac/ticket/60</a>&gt;: "Placement of 13.5.1 and 13.5.2"
     1790               </li>
     1791               <li>&lt;<a href="http://trac.tools.ietf.org/wg/httpbis/trac/ticket/138">http://trac.tools.ietf.org/wg/httpbis/trac/ticket/138</a>&gt;: "The role of Warning and Semantic Transparency in Caching"
     1792               </li>
     1793               <li>&lt;<a href="http://trac.tools.ietf.org/wg/httpbis/trac/ticket/139">http://trac.tools.ietf.org/wg/httpbis/trac/ticket/139</a>&gt;: "Methods and Caching"
     1794               </li>
     1795            </ul>
     1796            <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;):
     1797            </p>
     1798            <ul>
     1799               <li>Add appendix containing collected and expanded ABNF, reorganize ABNF introduction.</li>
     1800            </ul>
     1801         </div>
     1802         <div id="changes.since.06">
     1803            <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>
     1804            <p id="rfc.section.C.8.p.1">Closed issues: </p>
     1805            <ul>
     1806               <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"
     1807               </li>
     1808            </ul>
     1809            <p id="rfc.section.C.8.p.2">Affected issues: </p>
     1810            <ul>
     1811               <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
     1812               </li>
     1813            </ul>
     1814         </div>
     1815         <div id="changes.since.07">
     1816            <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>
     1817            <p id="rfc.section.C.9.p.1">Closed issues: </p>
     1818            <ul>
     1819               <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"
     1820               </li>
     1821               <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"
     1822               </li>
     1823               <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"
     1824               </li>
     1825               <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"
     1826               </li>
     1827            </ul>
     1828         </div>
     1829         <div id="changes.since.08">
     1830            <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>
     1831            <p id="rfc.section.C.10.p.1">Closed issues: </p>
     1832            <ul>
     1833               <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"
     1834               </li>
     1835               <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"
     1836               </li>
     1837            </ul>
     1838            <p id="rfc.section.C.10.p.2">Affected issues: </p>
     1839            <ul>
     1840               <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
     1841               </li>
     1842            </ul>
     1843            <p id="rfc.section.C.10.p.3">Partly resolved issues: </p>
     1844            <ul>
     1845               <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"
     1846               </li>
     1847            </ul>
     1848         </div>
     1849      </div>
    17611850      <h1 id="rfc.index"><a href="#rfc.index">Index</a></h1>
    17621851      <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>
     
    17641853      <div class="print2col">
    17651854         <ul class="ind">
    1766             <li class="indline0"><a id="rfc.index.A" href="#rfc.index.A"><b>A</b></a><ul class="ind">
    1767                   <li class="indline1">age&nbsp;&nbsp;<a class="iref" href="#rfc.iref.a.1">1.2</a></li>
    1768                   <li class="indline1">Age header&nbsp;&nbsp;<a class="iref" href="#rfc.xref.header.age.1">2.2</a>, <a class="iref" href="#rfc.iref.a.2"><b>3.1</b></a>, <a class="iref" href="#rfc.xref.header.age.2">5.1</a></li>
     1855            <li><a id="rfc.index.A" href="#rfc.index.A"><b>A</b></a><ul>
     1856                  <li>age&nbsp;&nbsp;<a href="#rfc.iref.a.1">1.2</a></li>
     1857                  <li>Age header&nbsp;&nbsp;<a href="#rfc.xref.header.age.1">2.2</a>, <a href="#rfc.iref.a.2"><b>3.1</b></a>, <a href="#rfc.xref.header.age.2">5.1</a></li>
    17691858               </ul>
    17701859            </li>
    1771             <li class="indline0"><a id="rfc.index.C" href="#rfc.index.C"><b>C</b></a><ul class="ind">
    1772                   <li class="indline1">cache&nbsp;&nbsp;<a class="iref" href="#rfc.iref.c.1">1.1</a></li>
    1773                   <li class="indline1">Cache Directives&nbsp;&nbsp;
    1774                      <ul class="ind">
    1775                         <li class="indline1">max-age&nbsp;&nbsp;<a class="iref" href="#rfc.iref.c.6"><b>3.2.1</b></a>, <a class="iref" href="#rfc.iref.c.17"><b>3.2.2</b></a></li>
    1776                         <li class="indline1">max-stale&nbsp;&nbsp;<a class="iref" href="#rfc.iref.c.7"><b>3.2.1</b></a></li>
    1777                         <li class="indline1">min-fresh&nbsp;&nbsp;<a class="iref" href="#rfc.iref.c.8"><b>3.2.1</b></a></li>
    1778                         <li class="indline1">must-revalidate&nbsp;&nbsp;<a class="iref" href="#rfc.iref.c.15"><b>3.2.2</b></a></li>
    1779                         <li class="indline1">no-cache&nbsp;&nbsp;<a class="iref" href="#rfc.iref.c.4"><b>3.2.1</b></a>, <a class="iref" href="#rfc.iref.c.13"><b>3.2.2</b></a></li>
    1780                         <li class="indline1">no-store&nbsp;&nbsp;<a class="iref" href="#rfc.iref.c.5"><b>3.2.1</b></a>, <a class="iref" href="#rfc.iref.c.14"><b>3.2.2</b></a></li>
    1781                         <li class="indline1">no-transform&nbsp;&nbsp;<a class="iref" href="#rfc.iref.c.9"><b>3.2.1</b></a>, <a class="iref" href="#rfc.iref.c.19"><b>3.2.2</b></a></li>
    1782                         <li class="indline1">only-if-cached&nbsp;&nbsp;<a class="iref" href="#rfc.iref.c.10"><b>3.2.1</b></a></li>
    1783                         <li class="indline1">private&nbsp;&nbsp;<a class="iref" href="#rfc.iref.c.12"><b>3.2.2</b></a></li>
    1784                         <li class="indline1">proxy-revalidate&nbsp;&nbsp;<a class="iref" href="#rfc.iref.c.16"><b>3.2.2</b></a></li>
    1785                         <li class="indline1">public&nbsp;&nbsp;<a class="iref" href="#rfc.iref.c.11"><b>3.2.2</b></a></li>
    1786                         <li class="indline1">s-maxage&nbsp;&nbsp;<a class="iref" href="#rfc.iref.c.18"><b>3.2.2</b></a></li>
     1860            <li><a id="rfc.index.C" href="#rfc.index.C"><b>C</b></a><ul>
     1861                  <li>cache&nbsp;&nbsp;<a href="#rfc.iref.c.1">1.1</a></li>
     1862                  <li>Cache Directives&nbsp;&nbsp;
     1863                     <ul>
     1864                        <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>
     1865                        <li>max-stale&nbsp;&nbsp;<a href="#rfc.iref.c.7"><b>3.2.1</b></a></li>
     1866                        <li>min-fresh&nbsp;&nbsp;<a href="#rfc.iref.c.8"><b>3.2.1</b></a></li>
     1867                        <li>must-revalidate&nbsp;&nbsp;<a href="#rfc.iref.c.15"><b>3.2.2</b></a></li>
     1868                        <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>
     1869                        <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>
     1870                        <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>
     1871                        <li>only-if-cached&nbsp;&nbsp;<a href="#rfc.iref.c.10"><b>3.2.1</b></a></li>
     1872                        <li>private&nbsp;&nbsp;<a href="#rfc.iref.c.12"><b>3.2.2</b></a></li>
     1873                        <li>proxy-revalidate&nbsp;&nbsp;<a href="#rfc.iref.c.16"><b>3.2.2</b></a></li>
     1874                        <li>public&nbsp;&nbsp;<a href="#rfc.iref.c.11"><b>3.2.2</b></a></li>
     1875                        <li>s-maxage&nbsp;&nbsp;<a href="#rfc.iref.c.18"><b>3.2.2</b></a></li>
    17871876                     </ul>
    17881877                  </li>
    1789                   <li class="indline1">Cache-Control header&nbsp;&nbsp;<a class="iref" href="#rfc.xref.header.cache-control.1">2.1</a>, <a class="iref" href="#rfc.xref.header.cache-control.2">2.1</a>, <a class="iref" href="#rfc.xref.header.cache-control.3">2.2</a>, <a class="iref" href="#rfc.iref.c.3"><b>3.2</b></a>, <a class="iref" href="#rfc.xref.header.cache-control.4">5.1</a>, <a class="iref" href="#rfc.xref.header.cache-control.5">A.1</a>, <a class="iref" href="#rfc.xref.header.cache-control.6">A.1</a></li>
    1790                   <li class="indline1">cacheable&nbsp;&nbsp;<a class="iref" href="#rfc.iref.c.2">1.2</a></li>
     1878                  <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.1</a>, <a href="#rfc.xref.header.cache-control.3">2.2</a>, <a href="#rfc.iref.c.3"><b>3.2</b></a>, <a href="#rfc.xref.header.cache-control.4">5.1</a>, <a href="#rfc.xref.header.cache-control.5">A.1</a>, <a href="#rfc.xref.header.cache-control.6">A.1</a></li>
     1879                  <li>cacheable&nbsp;&nbsp;<a href="#rfc.iref.c.2">1.2</a></li>
    17911880               </ul>
    17921881            </li>
    1793             <li class="indline0"><a id="rfc.index.E" href="#rfc.index.E"><b>E</b></a><ul class="ind">
    1794                   <li class="indline1">Expires header&nbsp;&nbsp;<a class="iref" href="#rfc.xref.header.expires.1">2.1</a>, <a class="iref" href="#rfc.xref.header.expires.2">2.3</a>, <a class="iref" href="#rfc.xref.header.expires.3">2.3.1</a>, <a class="iref" href="#rfc.iref.e.2"><b>3.3</b></a>, <a class="iref" href="#rfc.xref.header.expires.4">5.1</a></li>
    1795                   <li class="indline1">explicit expiration time&nbsp;&nbsp;<a class="iref" href="#rfc.iref.e.1">1.2</a></li>
     1882            <li><a id="rfc.index.E" href="#rfc.index.E"><b>E</b></a><ul>
     1883                  <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.1</a></li>
     1884                  <li>explicit expiration time&nbsp;&nbsp;<a href="#rfc.iref.e.1">1.2</a></li>
    17961885               </ul>
    17971886            </li>
    1798             <li class="indline0"><a id="rfc.index.F" href="#rfc.index.F"><b>F</b></a><ul class="ind">
    1799                   <li class="indline1">first-hand&nbsp;&nbsp;<a class="iref" href="#rfc.iref.f.1">1.2</a></li>
    1800                   <li class="indline1">fresh&nbsp;&nbsp;<a class="iref" href="#rfc.iref.f.3">1.2</a></li>
    1801                   <li class="indline1">freshness lifetime&nbsp;&nbsp;<a class="iref" href="#rfc.iref.f.2">1.2</a></li>
     1887            <li><a id="rfc.index.F" href="#rfc.index.F"><b>F</b></a><ul>
     1888                  <li>first-hand&nbsp;&nbsp;<a href="#rfc.iref.f.1">1.2</a></li>
     1889                  <li>fresh&nbsp;&nbsp;<a href="#rfc.iref.f.3">1.2</a></li>
     1890                  <li>freshness lifetime&nbsp;&nbsp;<a href="#rfc.iref.f.2">1.2</a></li>
    18021891               </ul>
    18031892            </li>
    1804             <li class="indline0"><a id="rfc.index.G" href="#rfc.index.G"><b>G</b></a><ul class="ind">
    1805                   <li class="indline1"><tt>Grammar</tt>&nbsp;&nbsp;
    1806                      <ul class="ind">
    1807                         <li class="indline1"><tt>Age</tt>&nbsp;&nbsp;<a class="iref" href="#rfc.iref.g.1"><b>3.1</b></a></li>
    1808                         <li class="indline1"><tt>Age-v</tt>&nbsp;&nbsp;<a class="iref" href="#rfc.iref.g.2"><b>3.1</b></a></li>
    1809                         <li class="indline1"><tt>Cache-Control</tt>&nbsp;&nbsp;<a class="iref" href="#rfc.iref.g.4"><b>3.2</b></a></li>
    1810                         <li class="indline1"><tt>Cache-Control-v</tt>&nbsp;&nbsp;<a class="iref" href="#rfc.iref.g.5"><b>3.2</b></a></li>
    1811                         <li class="indline1"><tt>cache-extension</tt>&nbsp;&nbsp;<a class="iref" href="#rfc.iref.g.6"><b>3.2</b></a></li>
    1812                         <li class="indline1"><tt>cache-request-directive</tt>&nbsp;&nbsp;<a class="iref" href="#rfc.iref.g.7"><b>3.2.1</b></a></li>
    1813                         <li class="indline1"><tt>cache-response-directive</tt>&nbsp;&nbsp;<a class="iref" href="#rfc.iref.g.8"><b>3.2.2</b></a></li>
    1814                         <li class="indline1"><tt>delta-seconds</tt>&nbsp;&nbsp;<a class="iref" href="#rfc.iref.g.3"><b>3.1</b></a></li>
    1815                         <li class="indline1"><tt>Expires</tt>&nbsp;&nbsp;<a class="iref" href="#rfc.iref.g.9"><b>3.3</b></a></li>
    1816                         <li class="indline1"><tt>Expires-v</tt>&nbsp;&nbsp;<a class="iref" href="#rfc.iref.g.10"><b>3.3</b></a></li>
    1817                         <li class="indline1"><tt>extension-pragma</tt>&nbsp;&nbsp;<a class="iref" href="#rfc.iref.g.14"><b>3.4</b></a></li>
    1818                         <li class="indline1"><tt>Pragma</tt>&nbsp;&nbsp;<a class="iref" href="#rfc.iref.g.11"><b>3.4</b></a></li>
    1819                         <li class="indline1"><tt>pragma-directive</tt>&nbsp;&nbsp;<a class="iref" href="#rfc.iref.g.13"><b>3.4</b></a></li>
    1820                         <li class="indline1"><tt>Pragma-v</tt>&nbsp;&nbsp;<a class="iref" href="#rfc.iref.g.12"><b>3.4</b></a></li>
    1821                         <li class="indline1"><tt>Vary</tt>&nbsp;&nbsp;<a class="iref" href="#rfc.iref.g.15"><b>3.5</b></a></li>
    1822                         <li class="indline1"><tt>Vary-v</tt>&nbsp;&nbsp;<a class="iref" href="#rfc.iref.g.16"><b>3.5</b></a></li>
    1823                         <li class="indline1"><tt>warn-agent</tt>&nbsp;&nbsp;<a class="iref" href="#rfc.iref.g.21"><b>3.6</b></a></li>
    1824                         <li class="indline1"><tt>warn-code</tt>&nbsp;&nbsp;<a class="iref" href="#rfc.iref.g.20"><b>3.6</b></a></li>
    1825                         <li class="indline1"><tt>warn-date</tt>&nbsp;&nbsp;<a class="iref" href="#rfc.iref.g.23"><b>3.6</b></a></li>
    1826                         <li class="indline1"><tt>warn-text</tt>&nbsp;&nbsp;<a class="iref" href="#rfc.iref.g.22"><b>3.6</b></a></li>
    1827                         <li class="indline1"><tt>Warning</tt>&nbsp;&nbsp;<a class="iref" href="#rfc.iref.g.17"><b>3.6</b></a></li>
    1828                         <li class="indline1"><tt>Warning-v</tt>&nbsp;&nbsp;<a class="iref" href="#rfc.iref.g.18"><b>3.6</b></a></li>
    1829                         <li class="indline1"><tt>warning-value</tt>&nbsp;&nbsp;<a class="iref" href="#rfc.iref.g.19"><b>3.6</b></a></li>
     1893            <li><a id="rfc.index.G" href="#rfc.index.G"><b>G</b></a><ul>
     1894                  <li><tt>Grammar</tt>&nbsp;&nbsp;
     1895                     <ul>
     1896                        <li><tt>Age</tt>&nbsp;&nbsp;<a href="#rfc.iref.g.1"><b>3.1</b></a></li>
     1897                        <li><tt>Age-v</tt>&nbsp;&nbsp;<a href="#rfc.iref.g.2"><b>3.1</b></a></li>
     1898                        <li><tt>Cache-Control</tt>&nbsp;&nbsp;<a href="#rfc.iref.g.4"><b>3.2</b></a></li>
     1899                        <li><tt>Cache-Control-v</tt>&nbsp;&nbsp;<a href="#rfc.iref.g.5"><b>3.2</b></a></li>
     1900                        <li><tt>cache-extension</tt>&nbsp;&nbsp;<a href="#rfc.iref.g.6"><b>3.2</b></a></li>
     1901                        <li><tt>cache-request-directive</tt>&nbsp;&nbsp;<a href="#rfc.iref.g.7"><b>3.2.1</b></a></li>
     1902                        <li><tt>cache-response-directive</tt>&nbsp;&nbsp;<a href="#rfc.iref.g.8"><b>3.2.2</b></a></li>
     1903                        <li><tt>delta-seconds</tt>&nbsp;&nbsp;<a href="#rfc.iref.g.3"><b>3.1</b></a></li>
     1904                        <li><tt>Expires</tt>&nbsp;&nbsp;<a href="#rfc.iref.g.9"><b>3.3</b></a></li>
     1905                        <li><tt>Expires-v</tt>&nbsp;&nbsp;<a href="#rfc.iref.g.10"><b>3.3</b></a></li>
     1906                        <li><tt>extension-pragma</tt>&nbsp;&nbsp;<a href="#rfc.iref.g.14"><b>3.4</b></a></li>
     1907                        <li><tt>Pragma</tt>&nbsp;&nbsp;<a href="#rfc.iref.g.11"><b>3.4</b></a></li>
     1908                        <li><tt>pragma-directive</tt>&nbsp;&nbsp;<a href="#rfc.iref.g.13"><b>3.4</b></a></li>
     1909                        <li><tt>Pragma-v</tt>&nbsp;&nbsp;<a href="#rfc.iref.g.12"><b>3.4</b></a></li>
     1910                        <li><tt>Vary</tt>&nbsp;&nbsp;<a href="#rfc.iref.g.15"><b>3.5</b></a></li>
     1911                        <li><tt>Vary-v</tt>&nbsp;&nbsp;<a href="#rfc.iref.g.16"><b>3.5</b></a></li>
     1912                        <li><tt>warn-agent</tt>&nbsp;&nbsp;<a href="#rfc.iref.g.21"><b>3.6</b></a></li>
     1913                        <li><tt>warn-code</tt>&nbsp;&nbsp;<a href="#rfc.iref.g.20"><b>3.6</b></a></li>
     1914                        <li><tt>warn-date</tt>&nbsp;&nbsp;<a href="#rfc.iref.g.23"><b>3.6</b></a></li>
     1915                        <li><tt>warn-text</tt>&nbsp;&nbsp;<a href="#rfc.iref.g.22"><b>3.6</b></a></li>
     1916                        <li><tt>Warning</tt>&nbsp;&nbsp;<a href="#rfc.iref.g.17"><b>3.6</b></a></li>
     1917                        <li><tt>Warning-v</tt>&nbsp;&nbsp;<a href="#rfc.iref.g.18"><b>3.6</b></a></li>
     1918                        <li><tt>warning-value</tt>&nbsp;&nbsp;<a href="#rfc.iref.g.19"><b>3.6</b></a></li>
    18301919                     </ul>
    18311920                  </li>
    18321921               </ul>
    18331922            </li>
    1834             <li class="indline0"><a id="rfc.index.H" href="#rfc.index.H"><b>H</b></a><ul class="ind">
    1835                   <li class="indline1">Headers&nbsp;&nbsp;
    1836                      <ul class="ind">
    1837                         <li class="indline1">Age&nbsp;&nbsp;<a class="iref" href="#rfc.xref.header.age.1">2.2</a>, <a class="iref" href="#rfc.iref.h.2"><b>3.1</b></a>, <a class="iref" href="#rfc.xref.header.age.2">5.1</a></li>
    1838                         <li class="indline1">Cache-Control&nbsp;&nbsp;<a class="iref" href="#rfc.xref.header.cache-control.1">2.1</a>, <a class="iref" href="#rfc.xref.header.cache-control.2">2.1</a>, <a class="iref" href="#rfc.xref.header.cache-control.3">2.2</a>, <a class="iref" href="#rfc.iref.h.3"><b>3.2</b></a>, <a class="iref" href="#rfc.xref.header.cache-control.4">5.1</a>, <a class="iref" href="#rfc.xref.header.cache-control.5">A.1</a>, <a class="iref" href="#rfc.xref.header.cache-control.6">A.1</a></li>
    1839                         <li class="indline1">Expires&nbsp;&nbsp;<a class="iref" href="#rfc.xref.header.expires.1">2.1</a>, <a class="iref" href="#rfc.xref.header.expires.2">2.3</a>, <a class="iref" href="#rfc.xref.header.expires.3">2.3.1</a>, <a class="iref" href="#rfc.iref.h.4"><b>3.3</b></a>, <a class="iref" href="#rfc.xref.header.expires.4">5.1</a></li>
    1840                         <li class="indline1">Pragma&nbsp;&nbsp;<a class="iref" href="#rfc.xref.header.pragma.1">2.2</a>, <a class="iref" href="#rfc.xref.header.pragma.2">3.2</a>, <a class="iref" href="#rfc.iref.h.5"><b>3.4</b></a>, <a class="iref" href="#rfc.xref.header.pragma.3">5.1</a></li>
    1841                         <li class="indline1">Vary&nbsp;&nbsp;<a class="iref" href="#rfc.xref.header.vary.1">2.6</a>, <a class="iref" href="#rfc.iref.h.6"><b>3.5</b></a>, <a class="iref" href="#rfc.xref.header.vary.2">5.1</a></li>
    1842                         <li class="indline1">Warning&nbsp;&nbsp;<a class="iref" href="#rfc.xref.header.warning.1">2.3.3</a>, <a class="iref" href="#rfc.xref.header.warning.2">2.7</a>, <a class="iref" href="#rfc.iref.h.7"><b>3.6</b></a>, <a class="iref" href="#rfc.xref.header.warning.3">5.1</a>, <a class="iref" href="#rfc.xref.header.warning.4">A.1</a>, <a class="iref" href="#rfc.xref.header.warning.5">A.2</a></li>
     1923            <li><a id="rfc.index.H" href="#rfc.index.H"><b>H</b></a><ul>
     1924                  <li>Headers&nbsp;&nbsp;
     1925                     <ul>
     1926                        <li>Age&nbsp;&nbsp;<a href="#rfc.xref.header.age.1">2.2</a>, <a href="#rfc.iref.h.2"><b>3.1</b></a>, <a href="#rfc.xref.header.age.2">5.1</a></li>
     1927                        <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.1</a>, <a href="#rfc.xref.header.cache-control.3">2.2</a>, <a href="#rfc.iref.h.3"><b>3.2</b></a>, <a href="#rfc.xref.header.cache-control.4">5.1</a>, <a href="#rfc.xref.header.cache-control.5">A.1</a>, <a href="#rfc.xref.header.cache-control.6">A.1</a></li>
     1928                        <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.1</a></li>
     1929                        <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.1</a></li>
     1930                        <li>Vary&nbsp;&nbsp;<a href="#rfc.xref.header.vary.1">2.6</a>, <a href="#rfc.iref.h.6"><b>3.5</b></a>, <a href="#rfc.xref.header.vary.2">5.1</a></li>
     1931                        <li>Warning&nbsp;&nbsp;<a href="#rfc.xref.header.warning.1">2.3.3</a>, <a href="#rfc.xref.header.warning.2">2.7</a>, <a href="#rfc.iref.h.7"><b>3.6</b></a>, <a href="#rfc.xref.header.warning.3">5.1</a>, <a href="#rfc.xref.header.warning.4">A.1</a>, <a href="#rfc.xref.header.warning.5">A.2</a></li>
    18431932                     </ul>
    18441933                  </li>
    1845                   <li class="indline1">heuristic expiration time&nbsp;&nbsp;<a class="iref" href="#rfc.iref.h.1">1.2</a></li>
     1934                  <li>heuristic expiration time&nbsp;&nbsp;<a href="#rfc.iref.h.1">1.2</a></li>
    18461935               </ul>
    18471936            </li>
    1848             <li class="indline0"><a id="rfc.index.M" href="#rfc.index.M"><b>M</b></a><ul class="ind">
    1849                   <li class="indline1">max-age&nbsp;&nbsp;
    1850                      <ul class="ind">
    1851                         <li class="indline1">Cache Directive&nbsp;&nbsp;<a class="iref" href="#rfc.iref.m.1"><b>3.2.1</b></a>, <a class="iref" href="#rfc.iref.m.5"><b>3.2.2</b></a></li>
     1937            <li><a id="rfc.index.M" href="#rfc.index.M"><b>M</b></a><ul>
     1938                  <li>max-age&nbsp;&nbsp;
     1939                     <ul>
     1940                        <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>
    18521941                     </ul>
    18531942                  </li>
    1854                   <li class="indline1">max-stale&nbsp;&nbsp;
    1855                      <ul class="ind">
    1856                         <li class="indline1">Cache Directive&nbsp;&nbsp;<a class="iref" href="#rfc.iref.m.2"><b>3.2.1</b></a></li>
     1943                  <li>max-stale&nbsp;&nbsp;
     1944                     <ul>
     1945                        <li>Cache Directive&nbsp;&nbsp;<a href="#rfc.iref.m.2"><b>3.2.1</b></a></li>
    18571946                     </ul>
    18581947                  </li>
    1859                   <li class="indline1">min-fresh&nbsp;&nbsp;
    1860                      <ul class="ind">
    1861                         <li class="indline1">Cache Directive&nbsp;&nbsp;<a class="iref" href="#rfc.iref.m.3"><b>3.2.1</b></a></li>
     1948                  <li>min-fresh&nbsp;&nbsp;
     1949                     <ul>
     1950                        <li>Cache Directive&nbsp;&nbsp;<a href="#rfc.iref.m.3"><b>3.2.1</b></a></li>
    18621951                     </ul>
    18631952                  </li>
    1864                   <li class="indline1">must-revalidate&nbsp;&nbsp;
    1865                      <ul class="ind">
    1866                         <li class="indline1">Cache Directive&nbsp;&nbsp;<a class="iref" href="#rfc.iref.m.4"><b>3.2.2</b></a></li>
     1953                  <li>must-revalidate&nbsp;&nbsp;
     1954                     <ul>
     1955                        <li>Cache Directive&nbsp;&nbsp;<a href="#rfc.iref.m.4"><b>3.2.2</b></a></li>
    18671956                     </ul>
    18681957                  </li>
    18691958               </ul>
    18701959            </li>
    1871             <li class="indline0"><a id="rfc.index.N" href="#rfc.index.N"><b>N</b></a><ul class="ind">
    1872                   <li class="indline1">no-cache&nbsp;&nbsp;
    1873                      <ul class="ind">
    1874                         <li class="indline1">Cache Directive&nbsp;&nbsp;<a class="iref" href="#rfc.iref.n.1"><b>3.2.1</b></a>, <a class="iref" href="#rfc.iref.n.4"><b>3.2.2</b></a></li>
     1960            <li><a id="rfc.index.N" href="#rfc.index.N"><b>N</b></a><ul>
     1961                  <li>no-cache&nbsp;&nbsp;
     1962                     <ul>
     1963                        <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>
    18751964                     </ul>
    18761965                  </li>
    1877                   <li class="indline1">no-store&nbsp;&nbsp;
    1878                      <ul class="ind">
    1879                         <li class="indline1">Cache Directive&nbsp;&nbsp;<a class="iref" href="#rfc.iref.n.2"><b>3.2.1</b></a>, <a class="iref" href="#rfc.iref.n.5"><b>3.2.2</b></a></li>
     1966                  <li>no-store&nbsp;&nbsp;
     1967                     <ul>
     1968                        <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>
    18801969                     </ul>
    18811970                  </li>
    1882                   <li class="indline1">no-transform&nbsp;&nbsp;
    1883                      <ul class="ind">
    1884                         <li class="indline1">Cache Directive&nbsp;&nbsp;<a class="iref" href="#rfc.iref.n.3"><b>3.2.1</b></a>, <a class="iref" href="#rfc.iref.n.6"><b>3.2.2</b></a></li>
     1971                  <li>no-transform&nbsp;&nbsp;
     1972                     <ul>
     1973                        <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>
    18851974                     </ul>
    18861975                  </li>
    18871976               </ul>
    18881977            </li>
    1889             <li class="indline0"><a id="rfc.index.O" href="#rfc.index.O"><b>O</b></a><ul class="ind">
    1890                   <li class="indline1">only-if-cached&nbsp;&nbsp;
    1891                      <ul class="ind">
    1892                         <li class="indline1">Cache Directive&nbsp;&nbsp;<a class="iref" href="#rfc.iref.o.1"><b>3.2.1</b></a></li>
     1978            <li><a id="rfc.index.O" href="#rfc.index.O"><b>O</b></a><ul>
     1979                  <li>only-if-cached&nbsp;&nbsp;
     1980                     <ul>
     1981                        <li>Cache Directive&nbsp;&nbsp;<a href="#rfc.iref.o.1"><b>3.2.1</b></a></li>
    18931982                     </ul>
    18941983                  </li>
    18951984               </ul>
    18961985            </li>
    1897             <li class="indline0"><a id="rfc.index.P" href="#rfc.index.P"><b>P</b></a><ul class="ind">
    1898                   <li class="indline1"><em>Part1</em>&nbsp;&nbsp;<a class="iref" href="#rfc.xref.Part1.1">1.4</a>, <a class="iref" href="#rfc.xref.Part1.2">1.4.1</a>, <a class="iref" href="#rfc.xref.Part1.3">1.4.1</a>, <a class="iref" href="#rfc.xref.Part1.4">1.4.1</a>, <a class="iref" href="#rfc.xref.Part1.5">1.4.1</a>, <a class="iref" href="#rfc.xref.Part1.6">1.4.2</a>, <a class="iref" href="#rfc.xref.Part1.7">1.4.2</a>, <a class="iref" href="#rfc.xref.Part1.8">1.4.2</a>, <a class="iref" href="#rfc.xref.Part1.9">1.4.2</a>, <a class="iref" href="#rfc.xref.Part1.10">1.4.2</a>, <a class="iref" href="#rfc.xref.Part1.11">2.3.2</a>, <a class="iref" href="#rfc.xref.Part1.12">2.6</a>, <a class="iref" href="#rfc.xref.Part1.13">3.3</a>, <a class="iref" href="#Part1"><b>8.1</b></a><ul class="ind">
    1899                         <li class="indline1"><em>Section 1.2</em>&nbsp;&nbsp;<a class="iref" href="#rfc.xref.Part1.1">1.4</a></li>
    1900                         <li class="indline1"><em>Section 1.2.2</em>&nbsp;&nbsp;<a class="iref" href="#rfc.xref.Part1.2">1.4.1</a>, <a class="iref" href="#rfc.xref.Part1.3">1.4.1</a>, <a class="iref" href="#rfc.xref.Part1.4">1.4.1</a>, <a class="iref" href="#rfc.xref.Part1.5">1.4.1</a></li>
    1901                         <li class="indline1"><em>Section 2.6</em>&nbsp;&nbsp;<a class="iref" href="#rfc.xref.Part1.8">1.4.2</a>, <a class="iref" href="#rfc.xref.Part1.10">1.4.2</a></li>
    1902                         <li class="indline1"><em>Section 3.2</em>&nbsp;&nbsp;<a class="iref" href="#rfc.xref.Part1.6">1.4.2</a>, <a class="iref" href="#rfc.xref.Part1.12">2.6</a></li>
    1903                         <li class="indline1"><em>Section 6.1</em>&nbsp;&nbsp;<a class="iref" href="#rfc.xref.Part1.7">1.4.2</a>, <a class="iref" href="#rfc.xref.Part1.13">3.3</a></li>
    1904                         <li class="indline1"><em>Section 9.3</em>&nbsp;&nbsp;<a class="iref" href="#rfc.xref.Part1.11">2.3.2</a></li>
    1905                         <li class="indline1"><em>Section 9.9</em>&nbsp;&nbsp;<a class="iref" href="#rfc.xref.Part1.9">1.4.2</a></li>
     1986            <li><a id="rfc.index.P" href="#rfc.index.P"><b>P</b></a><ul>
     1987                  <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.3.2</a>, <a href="#rfc.xref.Part1.12">2.6</a>, <a href="#rfc.xref.Part1.13">3.3</a>, <a href="#Part1"><b>8.1</b></a><ul>
     1988                        <li><em>Section 1.2</em>&nbsp;&nbsp;<a href="#rfc.xref.Part1.1">1.4</a></li>
     1989                        <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>
     1990                        <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>
     1991                        <li><em>Section 3.2</em>&nbsp;&nbsp;<a href="#rfc.xref.Part1.6">1.4.2</a>, <a href="#rfc.xref.Part1.12">2.6</a></li>
     1992                        <li><em>Section 6.1</em>&nbsp;&nbsp;<a href="#rfc.xref.Part1.7">1.4.2</a>, <a href="#rfc.xref.Part1.13">3.3</a></li>
     1993                        <li><em>Section 9.3</em>&nbsp;&nbsp;<a href="#rfc.xref.Part1.11">2.3.2</a></li>
     1994                        <li><em>Section 9.9</em>&nbsp;&nbsp;<a href="#rfc.xref.Part1.9">1.4.2</a></li>
    19061995                     </ul>
    19071996                  </li>
    1908                   <li class="indline1"><em>Part2</em>&nbsp;&nbsp;<a class="iref" href="#rfc.xref.Part2.1">2.2</a>, <a class="iref" href="#rfc.xref.Part2.2">2.5</a>, <a class="iref" href="#Part2"><b>8.1</b></a><ul class="ind">
    1909                         <li class="indline1"><em>Section 7.1.1</em>&nbsp;&nbsp;<a class="iref" href="#rfc.xref.Part2.1">2.2</a>, <a class="iref" href="#rfc.xref.Part2.2">2.5</a></li>
     1997                  <li><em>Part2</em>&nbsp;&nbsp;<a href="#rfc.xref.Part2.1">2.2</a>, <a href="#rfc.xref.Part2.2">2.5</a>, <a href="#Part2"><b>8.1</b></a><ul>
     1998                        <li><em>Section 7.1.1</em>&nbsp;&nbsp;<a href="#rfc.xref.Part2.1">2.2</a>, <a href="#rfc.xref.Part2.2">2.5</a></li>
    19101999                     </ul>
    19112000                  </li>
    1912                   <li class="indline1"><em>Part4</em>&nbsp;&nbsp;<a class="iref" href="#rfc.xref.Part4.1">2.3.1.1</a>, <a class="iref" href="#rfc.xref.Part4.2">2.4</a>, <a class="iref" href="#rfc.xref.Part4.3">2.7</a>, <a class="iref" href="#Part4"><b>8.1</b></a><ul class="ind">
    1913                         <li class="indline1"><em>Section 4</em>&nbsp;&nbsp;<a class="iref" href="#rfc.xref.Part4.3">2.7</a></li>
    1914                         <li class="indline1"><em>Section 6.6</em>&nbsp;&nbsp;<a class="iref" href="#rfc.xref.Part4.1">2.3.1.1</a></li>
     2001                  <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.7</a>, <a href="#Part4"><b>8.1</b></a><ul>
     2002                        <li><em>Section 4</em>&nbsp;&nbsp;<a href="#rfc.xref.Part4.3">2.7</a></li>
     2003                        <li><em>Section 6.6</em>&nbsp;&nbsp;<a href="#rfc.xref.Part4.1">2.3.1.1</a></li>
    19152004                     </ul>
    19162005                  </li>
    1917                   <li class="indline1"><em>Part5</em>&nbsp;&nbsp;<a class="iref" href="#rfc.xref.Part5.1">2.1.1</a>, <a class="iref" href="#rfc.xref.Part5.2">2.1.1</a>, <a class="iref" href="#Part5"><b>8.1</b></a><ul class="ind">
    1918                         <li class="indline1"><em>Section 4</em>&nbsp;&nbsp;<a class="iref" href="#rfc.xref.Part5.2">2.1.1</a></li>
     2006                  <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>
     2007                        <li><em>Section 4</em>&nbsp;&nbsp;<a href="#rfc.xref.Part5.2">2.1.1</a></li>
    19192008                     </ul>
    19202009                  </li>
    1921                   <li class="indline1"><em>Part7</em>&nbsp;&nbsp;<a class="iref" href="#rfc.xref.Part7.1">2.1</a>, <a class="iref" href="#rfc.xref.Part7.2">3.2.2</a>, <a class="iref" href="#Part7"><b>8.1</b></a><ul class="ind">
    1922                         <li class="indline1"><em>Section 3.1</em>&nbsp;&nbsp;<a class="iref" href="#rfc.xref.Part7.1">2.1</a>, <a class="iref" href="#rfc.xref.Part7.2">3.2.2</a></li>
     2010                  <li><em>Part7</em>&nbsp;&nbsp;<a href="#rfc.xref.Part7.1">2.1</a>, <a href="#rfc.xref.Part7.2">3.2.2</a>, <a href="#Part7"><b>8.1</b></a><ul>
     2011                        <li><em>Section 3.1</em>&nbsp;&nbsp;<a href="#rfc.xref.Part7.1">2.1</a>, <a href="#rfc.xref.Part7.2">3.2.2</a></li>
    19232012                     </ul>
    19242013                  </li>
    1925                   <li class="indline1">Pragma header&nbsp;&nbsp;<a class="iref" href="#rfc.xref.header.pragma.1">2.2</a>, <a class="iref" href="#rfc.xref.header.pragma.2">3.2</a>, <a class="iref" href="#rfc.iref.p.4"><b>3.4</b></a>, <a class="iref" href="#rfc.xref.header.pragma.3">5.1</a></li>
    1926                   <li class="indline1">private&nbsp;&nbsp;
    1927                      <ul class="ind">
    1928                         <li class="indline1">Cache Directive&nbsp;&nbsp;<a class="iref" href="#rfc.iref.p.2"><b>3.2.2</b></a></li>
     2014                  <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.1</a></li>
     2015                  <li>private&nbsp;&nbsp;
     2016                     <ul>
     2017                        <li>Cache Directive&nbsp;&nbsp;<a href="#rfc.iref.p.2"><b>3.2.2</b></a></li>
    19292018                     </ul>
    19302019                  </li>
    1931                   <li class="indline1">proxy-revalidate&nbsp;&nbsp;
    1932                      <ul class="ind">
    1933                         <li class="indline1">Cache Directive&nbsp;&nbsp;<a class="iref" href="#rfc.iref.p.3"><b>3.2.2</b></a></li>
     2020                  <li>proxy-revalidate&nbsp;&nbsp;
     2021                     <ul>
     2022                        <li>Cache Directive&nbsp;&nbsp;<a href="#rfc.iref.p.3"><b>3.2.2</b></a></li>
    19342023                     </ul>
    19352024                  </li>
    1936                   <li class="indline1">public&nbsp;&nbsp;
    1937                      <ul class="ind">
    1938                         <li class="indline1">Cache Directive&nbsp;&nbsp;<a class="iref" href="#rfc.iref.p.1"><b>3.2.2</b></a></li>
     2025                  <li>public&nbsp;&nbsp;
     2026                     <ul>
     2027                        <li>Cache Directive&nbsp;&nbsp;<a href="#rfc.iref.p.1"><b>3.2.2</b></a></li>
    19392028                     </ul>
    19402029                  </li>
    19412030               </ul>
    19422031            </li>
    1943             <li class="indline0"><a id="rfc.index.R" href="#rfc.index.R"><b>R</b></a><ul class="ind">
    1944                   <li class="indline1"><em>RFC1305</em>&nbsp;&nbsp;<a class="iref" href="#rfc.xref.RFC1305.1">2.3.2</a>, <a class="iref" href="#RFC1305"><b>8.2</b></a></li>
    1945                   <li class="indline1"><em>RFC2119</em>&nbsp;&nbsp;<a class="iref" href="#rfc.xref.RFC2119.1">1.3</a>, <a class="iref" href="#RFC2119"><b>8.1</b></a></li>
    1946                   <li class="indline1"><em>RFC2616</em>&nbsp;&nbsp;<a class="iref" href="#RFC2616"><b>8.2</b></a>, <a class="iref" href="#rfc.xref.RFC2616.1">C.1</a></li>
    1947                   <li class="indline1"><em>RFC3864</em>&nbsp;&nbsp;<a class="iref" href="#rfc.xref.RFC3864.1">5.1</a>, <a class="iref" href="#RFC3864"><b>8.2</b></a></li>
    1948                   <li class="indline1"><em>RFC5234</em>&nbsp;&nbsp;<a class="iref" href="#rfc.xref.RFC5234.1">1.4</a>, <a class="iref" href="#rfc.xref.RFC5234.2">1.4</a>, <a class="iref" href="#RFC5234"><b>8.1</b></a><ul class="ind">
    1949                         <li class="indline1"><em>Appendix B.1</em>&nbsp;&nbsp;<a class="iref" href="#rfc.xref.RFC5234.2">1.4</a></li>
     2032            <li><a id="rfc.index.R" href="#rfc.index.R"><b>R</b></a><ul>
     2033                  <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>
     2034                  <li><em>RFC2119</em>&nbsp;&nbsp;<a href="#rfc.xref.RFC2119.1">1.3</a>, <a href="#RFC2119"><b>8.1</b></a></li>
     2035                  <li><em>RFC2616</em>&nbsp;&nbsp;<a href="#RFC2616"><b>8.2</b></a>, <a href="#rfc.xref.RFC2616.1">C.1</a></li>
     2036                  <li><em>RFC3864</em>&nbsp;&nbsp;<a href="#rfc.xref.RFC3864.1">5.1</a>, <a href="#RFC3864"><b>8.2</b></a></li>
     2037                  <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>
     2038                        <li><em>Appendix B.1</em>&nbsp;&nbsp;<a href="#rfc.xref.RFC5234.2">1.4</a></li>
    19502039                     </ul>
    19512040                  </li>
    19522041               </ul>
    19532042            </li>
    1954             <li class="indline0"><a id="rfc.index.S" href="#rfc.index.S"><b>S</b></a><ul class="ind">
    1955                   <li class="indline1">s-maxage&nbsp;&nbsp;
    1956                      <ul class="ind">
    1957                         <li class="indline1">Cache Directive&nbsp;&nbsp;<a class="iref" href="#rfc.iref.s.2"><b>3.2.2</b></a></li>
     2043            <li><a id="rfc.index.S" href="#rfc.index.S"><b>S</b></a><ul>
     2044                  <li>s-maxage&nbsp;&nbsp;
     2045                     <ul>
     2046                        <li>Cache Directive&nbsp;&nbsp;<a href="#rfc.iref.s.2"><b>3.2.2</b></a></li>
    19582047                     </ul>
    19592048                  </li>
    1960                   <li class="indline1">stale&nbsp;&nbsp;<a class="iref" href="#rfc.iref.s.1">1.2</a></li>
     2049                  <li>stale&nbsp;&nbsp;<a href="#rfc.iref.s.1">1.2</a></li>
    19612050               </ul>
    19622051            </li>
    1963             <li class="indline0"><a id="rfc.index.V" href="#rfc.index.V"><b>V</b></a><ul class="ind">
    1964                   <li class="indline1">validator&nbsp;&nbsp;<a class="iref" href="#rfc.iref.v.1">1.2</a>, <a class="iref" href="#rfc.iref.v.2">1.2</a></li>
    1965                   <li class="indline1">Vary header&nbsp;&nbsp;<a class="iref" href="#rfc.xref.header.vary.1">2.6</a>, <a class="iref" href="#rfc.iref.v.3"><b>3.5</b></a>, <a class="iref" href="#rfc.xref.header.vary.2">5.1</a></li>
     2052            <li><a id="rfc.index.V" href="#rfc.index.V"><b>V</b></a><ul>
     2053                  <li>validator&nbsp;&nbsp;<a href="#rfc.iref.v.1">1.2</a>, <a href="#rfc.iref.v.2">1.2</a></li>
     2054                  <li>Vary header&nbsp;&nbsp;<a href="#rfc.xref.header.vary.1">2.6</a>, <a href="#rfc.iref.v.3"><b>3.5</b></a>, <a href="#rfc.xref.header.vary.2">5.1</a></li>
    19662055               </ul>
    19672056            </li>
    1968             <li class="indline0"><a id="rfc.index.W" href="#rfc.index.W"><b>W</b></a><ul class="ind">
    1969                   <li class="indline1">Warning header&nbsp;&nbsp;<a class="iref" href="#rfc.xref.header.warning.1">2.3.3</a>, <a class="iref" href="#rfc.xref.header.warning.2">2.7</a>, <a class="iref" href="#rfc.iref.w.1"><b>3.6</b></a>, <a class="iref" href="#rfc.xref.header.warning.3">5.1</a>, <a class="iref" href="#rfc.xref.header.warning.4">A.1</a>, <a class="iref" href="#rfc.xref.header.warning.5">A.2</a></li>
     2057            <li><a id="rfc.index.W" href="#rfc.index.W"><b>W</b></a><ul>
     2058                  <li>Warning header&nbsp;&nbsp;<a href="#rfc.xref.header.warning.1">2.3.3</a>, <a href="#rfc.xref.header.warning.2">2.7</a>, <a href="#rfc.iref.w.1"><b>3.6</b></a>, <a href="#rfc.xref.header.warning.3">5.1</a>, <a href="#rfc.xref.header.warning.4">A.1</a>, <a href="#rfc.xref.header.warning.5">A.2</a></li>
    19702059               </ul>
    19712060            </li>
    19722061         </ul>
    19732062      </div>
     2063      <div class="avoidbreak">
     2064         <h1 id="rfc.authors"><a href="#rfc.authors">Authors' Addresses</a></h1>
     2065         <p><b>Roy T. Fielding</b>
     2066            (editor)
     2067            <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>
     2068         <p><b>Jim Gettys</b><br>One Laptop per Child<br>21 Oak Knoll Road<br>Carlisle, MA&nbsp;01741<br>USA<br>EMail: <a href="mailto:jg@laptop.org">jg@laptop.org</a><br>URI: <a href="http://www.laptop.org/">http://www.laptop.org/</a></p>
     2069         <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>
     2070         <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>
     2071         <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>
     2072         <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>
     2073         <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>
     2074         <p><b>Yves Lafon</b>
     2075            (editor)
     2076            <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>
     2077         <p><b>Mark Nottingham</b>
     2078            (editor)
     2079            <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>
     2080         <p><b>Julian F. Reschke</b>
     2081            (editor)
     2082            <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>
     2083      </div>
    19742084   </body>
    19752085</html>
Note: See TracChangeset for help on using the changeset viewer.