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/15/p6-cache.html

    r1326 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;
    8782}
    8883ol.la {
     
    9792p {
    9893  margin-left: 2em;
    99   margin-right: 2em;
    10094}
    10195pre {
     
    10397  background-color: lightyellow;
    10498  padding: .25em;
     99  page-break-inside: avoid;
    105100}
    106101pre.text2 {
     
    134129table.tt {
    135130  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;
    136142}
    137143table.full {
    138   border-style: outset;
    139   border-width: 1px;
    140 }
    141 table.headers {
    142   border-style: outset;
    143   border-width: 1px;
     144  border-style: solid;
     145  border-width: 2px;
    144146}
    145147table.tt td {
    146148  vertical-align: top;
    147149}
     150table.all td {
     151  border-style: solid;
     152  border-width: 1px;
     153}
    148154table.full td {
    149   border-style: inset;
     155  border-style: none solid;
    150156  border-width: 1px;
    151157}
     
    153159  vertical-align: top;
    154160}
     161table.all th {
     162  border-style: solid;
     163  border-width: 1px;
     164}
    155165table.full th {
    156   border-style: inset;
    157   border-width: 1px;
     166  border-style: solid;
     167  border-width: 1px 1px 2px 1px;
    158168}
    159169table.headers th {
    160   border-style: none none inset none;
    161   border-width: 1px;
     170  border-style: none none solid none;
     171  border-width: 2px;
    162172}
    163173table.left {
     
    174184  caption-side: bottom;
    175185  font-weight: bold;
    176   font-size: 9pt;
     186  font-size: 10pt;
    177187  margin-top: .5em;
    178188}
     
    181191  border-spacing: 1px;
    182192  width: 95%;
    183   font-size: 10pt;
     193  font-size: 11pt;
    184194  color: white;
    185195}
     
    189199td.topnowrap {
    190200  vertical-align: top;
    191   white-space: nowrap; 
     201  white-space: nowrap;
    192202}
    193203table.header td {
     
    209219  list-style: none;
    210220  margin-left: 1.5em;
    211   margin-right: 0em;
    212221  padding-left: 0em;
    213222}
     
    215224  line-height: 150%;
    216225  font-weight: bold;
    217   font-size: 10pt;
    218226  margin-left: 0em;
    219   margin-right: 0em;
    220227}
    221228ul.toc li li {
    222229  line-height: normal;
    223230  font-weight: normal;
    224   font-size: 9pt;
     231  font-size: 10pt;
    225232  margin-left: 0em;
    226   margin-right: 0em;
    227233}
    228234li.excluded {
     
    231237ul p {
    232238  margin-left: 0em;
     239}
     240.title, .filename, h1, h2, h3, h4 {
     241  font-family: candara, helvetica, arial, sans-serif;
     242}
     243samp, tt, code, pre {
     244  font: consolas, monospace;
    233245}
    234246ul.ind, ul.ind ul {
    235247  list-style: none;
    236248  margin-left: 1.5em;
    237   margin-right: 0em;
    238249  padding-left: 0em;
    239250  page-break-before: avoid;
     
    243254  line-height: 200%;
    244255  margin-left: 0em;
    245   margin-right: 0em;
    246256}
    247257ul.ind li li {
     
    249259  line-height: 150%;
    250260  margin-left: 0em;
    251   margin-right: 0em;
    252261}
    253262.avoidbreak {
     
    273282  font-weight: bold;
    274283  text-align: center;
    275   font-size: 9pt;
     284  font-size: 10pt;
    276285}
    277286.filename {
    278287  color: #333333;
     288  font-size: 75%;
    279289  font-weight: bold;
    280   font-size: 12pt;
    281290  line-height: 21pt;
    282291  text-align: center;
     
    285294  font-weight: bold;
    286295}
    287 .hidden {
    288   display: none;
    289 }
    290296.left {
    291297  text-align: left;
     
    295301}
    296302.title {
    297   color: #990000;
    298   font-size: 18pt;
     303  color: green;
     304  font-size: 150%;
    299305  line-height: 18pt;
    300306  font-weight: bold;
     
    302308  margin-top: 36pt;
    303309}
    304 .vcardline {
    305   display: block;
    306 }
    307310.warning {
    308   font-size: 14pt;
     311  font-size: 130%;
    309312  background-color: yellow;
    310313}
     
    315318    display: none;
    316319  }
    317  
     320
    318321  a {
    319322    color: black;
     
    330333    background-color: white;
    331334    vertical-align: top;
    332     font-size: 12pt;
     335    font-size: 110%;
    333336  }
    334337
    335   ul.toc a::after {
     338  ul.toc a:nth-child(2)::after {
    336339    content: leader('.') target-counter(attr(href), page);
    337340  }
    338  
     341
    339342  ul.ind li li a {
    340343    content: target-counter(attr(href), page);
    341344  }
    342  
     345
    343346  .print2col {
    344347    column-count: 2;
     
    350353@page {
    351354  @top-left {
    352        content: "Internet-Draft"; 
    353   } 
     355       content: "Internet-Draft";
     356  }
    354357  @top-right {
    355        content: "July 2011"; 
    356   } 
     358       content: "July 2011";
     359  }
    357360  @top-center {
    358        content: "HTTP/1.1, Part 6"; 
    359   } 
     361       content: "HTTP/1.1, Part 6";
     362  }
    360363  @bottom-left {
    361        content: "Fielding, et al."; 
    362   } 
     364       content: "Fielding, et al.";
     365  }
    363366  @bottom-center {
    364        content: "Expires January 12, 2012"; 
    365   } 
     367       content: "Expires January 12, 2012";
     368  }
    366369  @bottom-right {
    367        content: "[Page " counter(page) "]"; 
    368   } 
    369 }
    370 
    371 @page:first { 
     370       content: "[Page " counter(page) "]";
     371  }
     372}
     373
     374@page:first {
    372375    @top-left {
    373376      content: normal;
     
    395398      <link rel="Appendix" title="B Collected ABNF" href="#rfc.section.B">
    396399      <link rel="Appendix" title="C Change Log (to be removed by RFC Editor before publication)" href="#rfc.section.C">
    397       <meta name="generator" content="http://greenbytes.de/tech/webdav/rfc2629.xslt, Revision 1.550, 2011-05-30 14:02:12, 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/">
    398401      <link rel="schema.dct" href="http://purl.org/dc/terms/">
    399402      <meta name="dct.creator" content="Fielding, R.">
     
    425428            </tr>
    426429            <tr>
    427                <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)
    428431               </td>
    429432               <td class="right">J. Gettys</td>
     
    500503      </table>
    501504      <p class="title">HTTP/1.1, part 6: Caching<br><span class="filename">draft-ietf-httpbis-p6-cache-15</span></p>
    502       <h1 id="rfc.abstract"><a href="#rfc.abstract">Abstract</a></h1> 
     505      <h1 id="rfc.abstract"><a href="#rfc.abstract">Abstract</a></h1>
    503506      <p>The Hypertext Transfer Protocol (HTTP) is an application-level protocol for distributed, collaborative, hypermedia information
    504507         systems. This document is Part 6 of the seven-part specification that defines the protocol referred to as "HTTP/1.1" and,
    505508         taken together, obsoletes RFC 2616. Part 6 defines requirements on HTTP caches and the associated header fields that control
    506509         cache behavior or indicate cacheable response messages.
    507       </p> 
    508       <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>
    509512      <p>Discussion of this draft should take place on the HTTPBIS working group mailing list (ietf-http-wg@w3.org), which is archived
    510513         at &lt;<a href="http://lists.w3.org/Archives/Public/ietf-http-wg/">http://lists.w3.org/Archives/Public/ietf-http-wg/</a>&gt;.
    511       </p> 
     514      </p>
    512515      <p>The current issues list is at &lt;<a href="http://tools.ietf.org/wg/httpbis/trac/report/3">http://tools.ietf.org/wg/httpbis/trac/report/3</a>&gt; and related documents (including fancy diffs) can be found at &lt;<a href="http://tools.ietf.org/wg/httpbis/">http://tools.ietf.org/wg/httpbis/</a>&gt;.
    513       </p> 
     516      </p>
    514517      <p>The changes in this draft are summarized in <a href="#changes.since.14" title="Since draft-ietf-httpbis-p6-cache-14">Appendix&nbsp;C.16</a>.
    515       </p>
    516       <h1><a id="rfc.status" href="#rfc.status">Status of This Memo</a></h1>
    517       <p>This Internet-Draft is submitted in full conformance with the provisions of BCP 78 and BCP 79.</p>
    518       <p>Internet-Drafts are working documents of the Internet Engineering Task Force (IETF). Note that other groups may also distribute
    519          working documents as Internet-Drafts. The list of current Internet-Drafts is at <a href="http://datatracker.ietf.org/drafts/current/">http://datatracker.ietf.org/drafts/current/</a>.
    520518      </p>
    521       <p>Internet-Drafts are draft documents valid for a maximum of six months and may be updated, replaced, or obsoleted by other
    522          documents at any time. It is inappropriate to use Internet-Drafts as reference material or to cite them other than as “work
    523          in progress”.
    524       </p>
    525       <p>This Internet-Draft will expire on January 12, 2012.</p>
    526       <h1><a id="rfc.copyrightnotice" href="#rfc.copyrightnotice">Copyright Notice</a></h1>
    527       <p>Copyright © 2011 IETF Trust and the persons identified as the document authors. All rights reserved.</p>
    528       <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
    529          and restrictions with respect to this document. Code Components extracted from this document must include Simplified BSD License
    530          text as described in Section 4.e of the Trust Legal Provisions and are provided without warranty as described in the Simplified
    531          BSD License.
    532       </p>
    533       <p>This document may contain material from IETF Documents or IETF Contributions published or made publicly available before November
    534          10, 2008. The person(s) controlling the copyright in some of this material may not have granted the IETF Trust the right to
    535          allow modifications of such material outside the IETF Standards Process. Without obtaining an adequate license from the person(s)
    536          controlling the copyright in such materials, this document may not be modified outside the IETF Standards Process, and derivative
    537          works of it may not be created outside the IETF Standards Process, except to format it for publication as an RFC or to translate
    538          it into languages other than English.
    539       </p>
     519      <div id="rfc.status">
     520         <h1><a href="#rfc.status">Status of This Memo</a></h1>
     521         <p>This Internet-Draft is submitted in full conformance with the provisions of BCP 78 and BCP 79.</p>
     522         <p>Internet-Drafts are working documents of the Internet Engineering Task Force (IETF). Note that other groups may also distribute
     523            working documents as Internet-Drafts. The list of current Internet-Drafts is at <a href="http://datatracker.ietf.org/drafts/current/">http://datatracker.ietf.org/drafts/current/</a>.
     524         </p>
     525         <p>Internet-Drafts are draft documents valid for a maximum of six months and may be updated, replaced, or obsoleted by other
     526            documents at any time. It is inappropriate to use Internet-Drafts as reference material or to cite them other than as “work
     527            in progress”.
     528         </p>
     529         <p>This Internet-Draft will expire on January 12, 2012.</p>
     530      </div>
     531      <div id="rfc.copyrightnotice">
     532         <h1><a href="#rfc.copyrightnotice">Copyright Notice</a></h1>
     533         <p>Copyright © 2011 IETF Trust and the persons identified as the document authors. All rights reserved.</p>
     534         <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
     535            and restrictions with respect to this document. Code Components extracted from this document must include Simplified BSD License
     536            text as described in Section 4.e of the Trust Legal Provisions and are provided without warranty as described in the Simplified
     537            BSD License.
     538         </p>
     539         <p>This document may contain material from IETF Documents or IETF Contributions published or made publicly available before November
     540            10, 2008. The person(s) controlling the copyright in some of this material may not have granted the IETF Trust the right to
     541            allow modifications of such material outside the IETF Standards Process. Without obtaining an adequate license from the person(s)
     542            controlling the copyright in such materials, this document may not be modified outside the IETF Standards Process, and derivative
     543            works of it may not be created outside the IETF Standards Process, except to format it for publication as an RFC or to translate
     544            it into languages other than English.
     545         </p>
     546      </div>
    540547      <hr class="noprint">
    541548      <h1 class="np" id="rfc.toc"><a href="#rfc.toc">Table of Contents</a></h1>
    542549      <ul class="toc">
    543          <li>1.&nbsp;&nbsp;&nbsp;<a href="#caching">Introduction</a><ul>
    544                <li>1.1&nbsp;&nbsp;&nbsp;<a href="#intro.purpose">Purpose</a></li>
    545                <li>1.2&nbsp;&nbsp;&nbsp;<a href="#intro.terminology">Terminology</a></li>
    546                <li>1.3&nbsp;&nbsp;&nbsp;<a href="#intro.requirements">Requirements</a></li>
    547                <li>1.4&nbsp;&nbsp;&nbsp;<a href="#notation">Syntax Notation</a><ul>
    548                      <li>1.4.1&nbsp;&nbsp;&nbsp;<a href="#core.rules">Core Rules</a></li>
    549                      <li>1.4.2&nbsp;&nbsp;&nbsp;<a href="#abnf.dependencies">ABNF Rules defined in other Parts of the Specification</a></li>
     550         <li><a href="#rfc.section.1">1.</a>&nbsp;&nbsp;&nbsp;<a href="#caching">Introduction</a><ul>
     551               <li><a href="#rfc.section.1.1">1.1</a>&nbsp;&nbsp;&nbsp;<a href="#intro.purpose">Purpose</a></li>
     552               <li><a href="#rfc.section.1.2">1.2</a>&nbsp;&nbsp;&nbsp;<a href="#intro.terminology">Terminology</a></li>
     553               <li><a href="#rfc.section.1.3">1.3</a>&nbsp;&nbsp;&nbsp;<a href="#intro.requirements">Requirements</a></li>
     554               <li><a href="#rfc.section.1.4">1.4</a>&nbsp;&nbsp;&nbsp;<a href="#notation">Syntax Notation</a><ul>
     555                     <li><a href="#rfc.section.1.4.1">1.4.1</a>&nbsp;&nbsp;&nbsp;<a href="#core.rules">Core Rules</a></li>
     556                     <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>
    550557                  </ul>
    551558               </li>
    552                <li>1.5&nbsp;&nbsp;&nbsp;<a href="#delta-seconds">Delta Seconds</a></li>
     559               <li><a href="#rfc.section.1.5">1.5</a>&nbsp;&nbsp;&nbsp;<a href="#delta-seconds">Delta Seconds</a></li>
    553560            </ul>
    554561         </li>
    555          <li>2.&nbsp;&nbsp;&nbsp;<a href="#caching.overview">Cache Operation</a><ul>
    556                <li>2.1&nbsp;&nbsp;&nbsp;<a href="#response.cacheability">Response Cacheability</a><ul>
    557                      <li>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>
    558565                  </ul>
    559566               </li>
    560                <li>2.2&nbsp;&nbsp;&nbsp;<a href="#constructing.responses.from.caches">Constructing Responses from Caches</a></li>
    561                <li>2.3&nbsp;&nbsp;&nbsp;<a href="#expiration.model">Freshness Model</a><ul>
    562                      <li>2.3.1&nbsp;&nbsp;&nbsp;<a href="#calculating.freshness.lifetime">Calculating Freshness Lifetime</a><ul>
    563                            <li>2.3.1.1&nbsp;&nbsp;&nbsp;<a href="#heuristic.freshness">Calculating Heuristic Freshness</a></li>
    564                         </ul>
    565                      </li>
    566                      <li>2.3.2&nbsp;&nbsp;&nbsp;<a href="#age.calculations">Calculating Age</a></li>
    567                      <li>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>
    568572                  </ul>
    569573               </li>
    570                <li>2.4&nbsp;&nbsp;&nbsp;<a href="#validation.model">Validation Model</a></li>
    571                <li>2.5&nbsp;&nbsp;&nbsp;<a href="#invalidation.after.updates.or.deletions">Request Methods that Invalidate</a></li>
    572                <li>2.6&nbsp;&nbsp;&nbsp;<a href="#caching.authenticated.responses">Shared Caching of Authenticated Responses</a></li>
    573                <li>2.7&nbsp;&nbsp;&nbsp;<a href="#caching.negotiated.responses">Caching Negotiated Responses</a></li>
    574                <li>2.8&nbsp;&nbsp;&nbsp;<a href="#combining.responses">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.authenticated.responses">Shared Caching of Authenticated Responses</a></li>
     577               <li><a href="#rfc.section.2.7">2.7</a>&nbsp;&nbsp;&nbsp;<a href="#caching.negotiated.responses">Caching Negotiated Responses</a></li>
     578               <li><a href="#rfc.section.2.8">2.8</a>&nbsp;&nbsp;&nbsp;<a href="#combining.responses">Combining Responses</a></li>
    575579            </ul>
    576580         </li>
    577          <li>3.&nbsp;&nbsp;&nbsp;<a href="#header.fields">Header Field Definitions</a><ul>
    578                <li>3.1&nbsp;&nbsp;&nbsp;<a href="#header.age">Age</a></li>
    579                <li>3.2&nbsp;&nbsp;&nbsp;<a href="#header.cache-control">Cache-Control</a><ul>
    580                      <li>3.2.1&nbsp;&nbsp;&nbsp;<a href="#cache-request-directive">Request Cache-Control Directives</a></li>
    581                      <li>3.2.2&nbsp;&nbsp;&nbsp;<a href="#cache-response-directive">Response Cache-Control Directives</a></li>
    582                      <li>3.2.3&nbsp;&nbsp;&nbsp;<a href="#cache.control.extensions">Cache Control Extensions</a></li>
     581         <li><a href="#rfc.section.3">3.</a>&nbsp;&nbsp;&nbsp;<a href="#header.fields">Header Field Definitions</a><ul>
     582               <li><a href="#rfc.section.3.1">3.1</a>&nbsp;&nbsp;&nbsp;<a href="#header.age">Age</a></li>
     583               <li><a href="#rfc.section.3.2">3.2</a>&nbsp;&nbsp;&nbsp;<a href="#header.cache-control">Cache-Control</a><ul>
     584                     <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>
     585                     <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>
     586                     <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>
    583587                  </ul>
    584588               </li>
    585                <li>3.3&nbsp;&nbsp;&nbsp;<a href="#header.expires">Expires</a></li>
    586                <li>3.4&nbsp;&nbsp;&nbsp;<a href="#header.pragma">Pragma</a></li>
    587                <li>3.5&nbsp;&nbsp;&nbsp;<a href="#header.vary">Vary</a></li>
    588                <li>3.6&nbsp;&nbsp;&nbsp;<a href="#header.warning">Warning</a></li>
     589               <li><a href="#rfc.section.3.3">3.3</a>&nbsp;&nbsp;&nbsp;<a href="#header.expires">Expires</a></li>
     590               <li><a href="#rfc.section.3.4">3.4</a>&nbsp;&nbsp;&nbsp;<a href="#header.pragma">Pragma</a></li>
     591               <li><a href="#rfc.section.3.5">3.5</a>&nbsp;&nbsp;&nbsp;<a href="#header.vary">Vary</a></li>
     592               <li><a href="#rfc.section.3.6">3.6</a>&nbsp;&nbsp;&nbsp;<a href="#header.warning">Warning</a></li>
    589593            </ul>
    590594         </li>
    591          <li>4.&nbsp;&nbsp;&nbsp;<a href="#history.lists">History Lists</a></li>
    592          <li>5.&nbsp;&nbsp;&nbsp;<a href="#IANA.considerations">IANA Considerations</a><ul>
    593                <li>5.1&nbsp;&nbsp;&nbsp;<a href="#cache.directive.registration">Cache Directive Registry</a></li>
    594                <li>5.2&nbsp;&nbsp;&nbsp;<a href="#header.field.registration">Header Field Registration</a></li>
     595         <li><a href="#rfc.section.4">4.</a>&nbsp;&nbsp;&nbsp;<a href="#history.lists">History Lists</a></li>
     596         <li><a href="#rfc.section.5">5.</a>&nbsp;&nbsp;&nbsp;<a href="#IANA.considerations">IANA Considerations</a><ul>
     597               <li><a href="#rfc.section.5.1">5.1</a>&nbsp;&nbsp;&nbsp;<a href="#cache.directive.registration">Cache Directive Registry</a></li>
     598               <li><a href="#rfc.section.5.2">5.2</a>&nbsp;&nbsp;&nbsp;<a href="#header.field.registration">Header Field Registration</a></li>
    595599            </ul>
    596600         </li>
    597          <li>6.&nbsp;&nbsp;&nbsp;<a href="#security.considerations">Security Considerations</a></li>
    598          <li>7.&nbsp;&nbsp;&nbsp;<a href="#ack">Acknowledgments</a></li>
    599          <li>8.&nbsp;&nbsp;&nbsp;<a href="#rfc.references">References</a><ul>
    600                <li>8.1&nbsp;&nbsp;&nbsp;<a href="#rfc.references.1">Normative References</a></li>
    601                <li>8.2&nbsp;&nbsp;&nbsp;<a href="#rfc.references.2">Informative References</a></li>
     601         <li><a href="#rfc.section.6">6.</a>&nbsp;&nbsp;&nbsp;<a href="#security.considerations">Security Considerations</a></li>
     602         <li><a href="#rfc.section.7">7.</a>&nbsp;&nbsp;&nbsp;<a href="#ack">Acknowledgments</a></li>
     603         <li><a href="#rfc.section.8">8.</a>&nbsp;&nbsp;&nbsp;<a href="#rfc.references">References</a><ul>
     604               <li><a href="#rfc.section.8.1">8.1</a>&nbsp;&nbsp;&nbsp;<a href="#rfc.references.1">Normative References</a></li>
     605               <li><a href="#rfc.section.8.2">8.2</a>&nbsp;&nbsp;&nbsp;<a href="#rfc.references.2">Informative References</a></li>
    602606            </ul>
    603607         </li>
    604          <li><a href="#rfc.authors">Authors' Addresses</a></li>
    605          <li>A.&nbsp;&nbsp;&nbsp;<a href="#changes.from.rfc.2616">Changes from RFC 2616</a></li>
    606          <li>B.&nbsp;&nbsp;&nbsp;<a href="#collected.abnf">Collected ABNF</a></li>
    607          <li>C.&nbsp;&nbsp;&nbsp;<a href="#change.log">Change Log (to be removed by RFC Editor before publication)</a><ul>
    608                <li>C.1&nbsp;&nbsp;&nbsp;<a href="#rfc.section.C.1">Since RFC 2616</a></li>
    609                <li>C.2&nbsp;&nbsp;&nbsp;<a href="#rfc.section.C.2">Since draft-ietf-httpbis-p6-cache-00</a></li>
    610                <li>C.3&nbsp;&nbsp;&nbsp;<a href="#rfc.section.C.3">Since draft-ietf-httpbis-p6-cache-01</a></li>
    611                <li>C.4&nbsp;&nbsp;&nbsp;<a href="#changes.since.02">Since draft-ietf-httpbis-p6-cache-02</a></li>
    612                <li>C.5&nbsp;&nbsp;&nbsp;<a href="#changes.since.03">Since draft-ietf-httpbis-p6-cache-03</a></li>
    613                <li>C.6&nbsp;&nbsp;&nbsp;<a href="#changes.since.04">Since draft-ietf-httpbis-p6-cache-04</a></li>
    614                <li>C.7&nbsp;&nbsp;&nbsp;<a href="#changes.since.05">Since draft-ietf-httpbis-p6-cache-05</a></li>
    615                <li>C.8&nbsp;&nbsp;&nbsp;<a href="#changes.since.06">Since draft-ietf-httpbis-p6-cache-06</a></li>
    616                <li>C.9&nbsp;&nbsp;&nbsp;<a href="#changes.since.07">Since draft-ietf-httpbis-p6-cache-07</a></li>
    617                <li>C.10&nbsp;&nbsp;&nbsp;<a href="#changes.since.08">Since draft-ietf-httpbis-p6-cache-08</a></li>
    618                <li>C.11&nbsp;&nbsp;&nbsp;<a href="#changes.since.09">Since draft-ietf-httpbis-p6-cache-09</a></li>
    619                <li>C.12&nbsp;&nbsp;&nbsp;<a href="#changes.since.10">Since draft-ietf-httpbis-p6-cache-10</a></li>
    620                <li>C.13&nbsp;&nbsp;&nbsp;<a href="#changes.since.11">Since draft-ietf-httpbis-p6-cache-11</a></li>
    621                <li>C.14&nbsp;&nbsp;&nbsp;<a href="#changes.since.12">Since draft-ietf-httpbis-p6-cache-12</a></li>
    622                <li>C.15&nbsp;&nbsp;&nbsp;<a href="#changes.since.13">Since draft-ietf-httpbis-p6-cache-13</a></li>
    623                <li>C.16&nbsp;&nbsp;&nbsp;<a href="#changes.since.14">Since draft-ietf-httpbis-p6-cache-14</a></li>
     608         <li><a href="#rfc.section.A">A.</a>&nbsp;&nbsp;&nbsp;<a href="#changes.from.rfc.2616">Changes from RFC 2616</a></li>
     609         <li><a href="#rfc.section.B">B.</a>&nbsp;&nbsp;&nbsp;<a href="#collected.abnf">Collected ABNF</a></li>
     610         <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>
     611               <li><a href="#rfc.section.C.1">C.1</a>&nbsp;&nbsp;&nbsp;<a href="#rfc.section.C.1">Since RFC 2616</a></li>
     612               <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>
     613               <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>
     614               <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>
     615               <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>
     616               <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>
     617               <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>
     618               <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>
     619               <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>
     620               <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>
     621               <li><a href="#rfc.section.C.11">C.11</a>&nbsp;&nbsp;&nbsp;<a href="#changes.since.09">Since draft-ietf-httpbis-p6-cache-09</a></li>
     622               <li><a href="#rfc.section.C.12">C.12</a>&nbsp;&nbsp;&nbsp;<a href="#changes.since.10">Since draft-ietf-httpbis-p6-cache-10</a></li>
     623               <li><a href="#rfc.section.C.13">C.13</a>&nbsp;&nbsp;&nbsp;<a href="#changes.since.11">Since draft-ietf-httpbis-p6-cache-11</a></li>
     624               <li><a href="#rfc.section.C.14">C.14</a>&nbsp;&nbsp;&nbsp;<a href="#changes.since.12">Since draft-ietf-httpbis-p6-cache-12</a></li>
     625               <li><a href="#rfc.section.C.15">C.15</a>&nbsp;&nbsp;&nbsp;<a href="#changes.since.13">Since draft-ietf-httpbis-p6-cache-13</a></li>
     626               <li><a href="#rfc.section.C.16">C.16</a>&nbsp;&nbsp;&nbsp;<a href="#changes.since.14">Since draft-ietf-httpbis-p6-cache-14</a></li>
    624627            </ul>
    625628         </li>
    626629         <li><a href="#rfc.index">Index</a></li>
     630         <li><a href="#rfc.authors">Authors' Addresses</a></li>
    627631      </ul>
    628       <h1 id="rfc.section.1" class="np"><a href="#rfc.section.1">1.</a>&nbsp;<a id="caching" href="#caching">Introduction</a></h1>
    629       <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.
    630          This document defines aspects of HTTP/1.1 related to caching and reusing response messages.
    631       </p>
    632       <div id="rfc.iref.c.1"></div>
    633       <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>
    634       <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
    635          stores cacheable responses in order to reduce the response time and network bandwidth consumption on future, equivalent requests.
    636          Any client or server <em class="bcp14">MAY</em> employ a cache, though a cache cannot be used by a server that is acting as a tunnel.
    637       </p>
    638       <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
    639          response message to satisfy a current request. In some cases, a stored response can be reused without the need for a network
    640          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
    641          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>).
    642       </p>
    643       <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>
    644       <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>
    645       <p id="rfc.section.1.2.p.2"> <span id="rfc.iref.c.2"></span>  <dfn>cache</dfn> 
    646       </p>
    647       <ul class="empty">
    648          <li>A conformant implementation of a HTTP cache. Note that this implies an HTTP/1.1 cache; this specification does not define
    649             conformance for HTTP/1.0 caches.
    650          </li>
    651       </ul>
    652       <div id="shared.and.non-shared.caches">
    653          <p id="rfc.section.1.2.p.3"> <span id="rfc.iref.s.1"></span>  <dfn>shared cache</dfn> 
     632      <div id="caching">
     633         <h1 id="rfc.section.1" class="np"><a href="#rfc.section.1">1.</a>&nbsp;<a href="#caching">Introduction</a></h1>
     634         <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.
     635            This document defines aspects of HTTP/1.1 related to caching and reusing response messages.
    654636         </p>
    655          <ul class="empty">
    656             <li>A cache that is accessible to more than one user; usually (but not always) deployed as part of an intermediary.</li>
    657          </ul>
    658       </div>
    659       <p id="rfc.section.1.2.p.4"> <span id="rfc.iref.p.1"></span>  <dfn>private cache</dfn> 
    660       </p>
    661       <ul class="empty">
    662          <li>A cache that is dedicated to a single user.</li>
    663       </ul>
    664       <p id="rfc.section.1.2.p.5"> <span id="rfc.iref.c.3"></span>  <dfn>cacheable</dfn> 
    665       </p>
    666       <ul class="empty">
    667          <li>A response is cacheable if a cache is allowed to store a copy of the response message for use in answering subsequent requests.
    668             Even when a response is cacheable, there might be additional constraints on whether a cache can use the stored copy to satisfy
    669             a particular request.
    670          </li>
    671       </ul>
    672       <p id="rfc.section.1.2.p.6"> <span id="rfc.iref.e.1"></span>  <dfn>explicit expiration time</dfn> 
    673       </p>
    674       <ul class="empty">
    675          <li>The time at which the origin server intends that a representation no longer be returned by a cache without further validation.</li>
    676       </ul>
    677       <p id="rfc.section.1.2.p.7"> <span id="rfc.iref.h.1"></span>  <dfn>heuristic expiration time</dfn> 
    678       </p>
    679       <ul class="empty">
    680          <li>An expiration time assigned by a cache when no explicit expiration time is available.</li>
    681       </ul>
    682       <p id="rfc.section.1.2.p.8"> <span id="rfc.iref.a.1"></span>  <dfn>age</dfn> 
    683       </p>
    684       <ul class="empty">
    685          <li>The age of a response is the time since it was sent by, or successfully validated with, the origin server.</li>
    686       </ul>
    687       <p id="rfc.section.1.2.p.9"> <span id="rfc.iref.f.1"></span>  <dfn>first-hand</dfn> 
    688       </p>
    689       <ul class="empty">
    690          <li>A response is first-hand if the freshness model is not in use; i.e., its age is 0.</li>
    691       </ul>
    692       <p id="rfc.section.1.2.p.10"> <span id="rfc.iref.f.2"></span>  <dfn>freshness lifetime</dfn> 
    693       </p>
    694       <ul class="empty">
    695          <li>The length of time between the generation of a response and its expiration time.</li>
    696       </ul>
    697       <p id="rfc.section.1.2.p.11"> <span id="rfc.iref.f.3"></span>  <dfn>fresh</dfn> 
    698       </p>
    699       <ul class="empty">
    700          <li>A response is fresh if its age has not yet exceeded its freshness lifetime.</li>
    701       </ul>
    702       <p id="rfc.section.1.2.p.12"> <span id="rfc.iref.s.2"></span>  <dfn>stale</dfn> 
    703       </p>
    704       <ul class="empty">
    705          <li>A response is stale if its age has passed its freshness lifetime (either explicit or heuristic).</li>
    706       </ul>
    707       <p id="rfc.section.1.2.p.13"> <span id="rfc.iref.v.1"></span>  <dfn>validator</dfn> 
    708       </p>
    709       <ul class="empty">
    710          <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
    711             equivalent copy of a representation.
    712          </li>
    713       </ul>
    714       <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>
    715       <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"
    716          in this document are to be interpreted as described in <a href="#RFC2119" id="rfc.xref.RFC2119.1"><cite title="Key words for use in RFCs to Indicate Requirement Levels">[RFC2119]</cite></a>.
    717       </p>
    718       <p id="rfc.section.1.3.p.2">An implementation is not compliant if it fails to satisfy one or more of the "MUST" or "REQUIRED" level requirements for the
    719          protocols it implements. An implementation that satisfies all the "MUST" or "REQUIRED" level and all the "SHOULD" level requirements
    720          for its protocols is said to be "unconditionally compliant"; one that satisfies all the "MUST" level requirements but not
    721          all the "SHOULD" level requirements for its protocols is said to be "conditionally compliant".
    722       </p>
    723       <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>
    724       <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.
    725       </p>
    726       <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
    727          (hexadecimal 0-9/A-F/a-f), LF (line feed), OCTET (any 8-bit sequence of data), SP (space), VCHAR (any visible USASCII character),
    728          and WSP (whitespace).
    729       </p>
    730       <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>
    731       <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>:
    732       </p>
    733       <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;
     637         <div id="intro.purpose">
     638            <div id="rfc.iref.c.1"></div>
     639            <h2 id="rfc.section.1.1"><a href="#rfc.section.1.1">1.1</a>&nbsp;<a href="#intro.purpose">Purpose</a></h2>
     640            <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
     641               stores cacheable responses in order to reduce the response time and network bandwidth consumption on future, equivalent requests.
     642               Any client or server <em class="bcp14">MAY</em> employ a cache, though a cache cannot be used by a server that is acting as a tunnel.
     643            </p>
     644            <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
     645               response message to satisfy a current request. In some cases, a stored response can be reused without the need for a network
     646               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
     647               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>).
     648            </p>
     649         </div>
     650         <div id="intro.terminology">
     651            <h2 id="rfc.section.1.2"><a href="#rfc.section.1.2">1.2</a>&nbsp;<a href="#intro.terminology">Terminology</a></h2>
     652            <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>
     653            <p id="rfc.section.1.2.p.2"><span id="rfc.iref.c.2"></span> <dfn>cache</dfn>
     654            </p>
     655            <ul class="empty">
     656               <li>A conformant implementation of a HTTP cache. Note that this implies an HTTP/1.1 cache; this specification does not define
     657                  conformance for HTTP/1.0 caches.
     658               </li>
     659            </ul>
     660            <div id="shared.and.non-shared.caches">
     661               <p id="rfc.section.1.2.p.3"><span id="rfc.iref.s.1"></span> <dfn>shared cache</dfn>
     662               </p>
     663               <ul class="empty">
     664                  <li>A cache that is accessible to more than one user; usually (but not always) deployed as part of an intermediary.</li>
     665               </ul>
     666            </div>
     667            <p id="rfc.section.1.2.p.4"><span id="rfc.iref.p.1"></span> <dfn>private cache</dfn>
     668            </p>
     669            <ul class="empty">
     670               <li>A cache that is dedicated to a single user.</li>
     671            </ul>
     672            <p id="rfc.section.1.2.p.5"><span id="rfc.iref.c.3"></span> <dfn>cacheable</dfn>
     673            </p>
     674            <ul class="empty">
     675               <li>A response is cacheable if a cache is allowed to store a copy of the response message for use in answering subsequent requests.
     676                  Even when a response is cacheable, there might be additional constraints on whether a cache can use the stored copy to satisfy
     677                  a particular request.
     678               </li>
     679            </ul>
     680            <p id="rfc.section.1.2.p.6"><span id="rfc.iref.e.1"></span> <dfn>explicit expiration time</dfn>
     681            </p>
     682            <ul class="empty">
     683               <li>The time at which the origin server intends that a representation no longer be returned by a cache without further validation.</li>
     684            </ul>
     685            <p id="rfc.section.1.2.p.7"><span id="rfc.iref.h.1"></span> <dfn>heuristic expiration time</dfn>
     686            </p>
     687            <ul class="empty">
     688               <li>An expiration time assigned by a cache when no explicit expiration time is available.</li>
     689            </ul>
     690            <p id="rfc.section.1.2.p.8"><span id="rfc.iref.a.1"></span> <dfn>age</dfn>
     691            </p>
     692            <ul class="empty">
     693               <li>The age of a response is the time since it was sent by, or successfully validated with, the origin server.</li>
     694            </ul>
     695            <p id="rfc.section.1.2.p.9"><span id="rfc.iref.f.1"></span> <dfn>first-hand</dfn>
     696            </p>
     697            <ul class="empty">
     698               <li>A response is first-hand if the freshness model is not in use; i.e., its age is 0.</li>
     699            </ul>
     700            <p id="rfc.section.1.2.p.10"><span id="rfc.iref.f.2"></span> <dfn>freshness lifetime</dfn>
     701            </p>
     702            <ul class="empty">
     703               <li>The length of time between the generation of a response and its expiration time.</li>
     704            </ul>
     705            <p id="rfc.section.1.2.p.11"><span id="rfc.iref.f.3"></span> <dfn>fresh</dfn>
     706            </p>
     707            <ul class="empty">
     708               <li>A response is fresh if its age has not yet exceeded its freshness lifetime.</li>
     709            </ul>
     710            <p id="rfc.section.1.2.p.12"><span id="rfc.iref.s.2"></span> <dfn>stale</dfn>
     711            </p>
     712            <ul class="empty">
     713               <li>A response is stale if its age has passed its freshness lifetime (either explicit or heuristic).</li>
     714            </ul>
     715            <p id="rfc.section.1.2.p.13"><span id="rfc.iref.v.1"></span> <dfn>validator</dfn>
     716            </p>
     717            <ul class="empty">
     718               <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
     719                  equivalent copy of a representation.
     720               </li>
     721            </ul>
     722         </div>
     723         <div id="intro.requirements">
     724            <h2 id="rfc.section.1.3"><a href="#rfc.section.1.3">1.3</a>&nbsp;<a href="#intro.requirements">Requirements</a></h2>
     725            <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"
     726               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>.
     727            </p>
     728            <p id="rfc.section.1.3.p.2">An implementation is not compliant if it fails to satisfy one or more of the "MUST" or "REQUIRED" level requirements for the
     729               protocols it implements. An implementation that satisfies all the "MUST" or "REQUIRED" level and all the "SHOULD" level requirements
     730               for its protocols is said to be "unconditionally compliant"; one that satisfies all the "MUST" level requirements but not
     731               all the "SHOULD" level requirements for its protocols is said to be "conditionally compliant".
     732            </p>
     733         </div>
     734         <div id="notation">
     735            <h2 id="rfc.section.1.4"><a href="#rfc.section.1.4">1.4</a>&nbsp;<a href="#notation">Syntax Notation</a></h2>
     736            <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.
     737            </p>
     738            <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
     739               (hexadecimal 0-9/A-F/a-f), LF (line feed), OCTET (any 8-bit sequence of data), SP (space), VCHAR (any visible USASCII character),
     740               and WSP (whitespace).
     741            </p>
     742            <div id="core.rules">
     743               <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>
     744               <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>:
     745               </p>
     746               <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;
    734747  <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;
    735748  <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;
    736 </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>
    737       <p id="rfc.section.1.4.2.p.1">The ABNF rules below are defined in other parts:</p>
    738       <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;
     749</pre></div>
     750            <div id="abnf.dependencies">
     751               <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>
     752               <p id="rfc.section.1.4.2.p.1">The ABNF rules below are defined in other parts:</p>
     753               <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;
    739754  <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;
    740755  <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.7</a>&gt;
    741756  <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;
    742757  <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.7</a>&gt;
    743 </pre><h2 id="rfc.section.1.5"><a href="#rfc.section.1.5">1.5</a>&nbsp;<a id="delta-seconds" href="#delta-seconds">Delta Seconds</a></h2>
    744       <p id="rfc.section.1.5.p.1">The delta-seconds rule specifies a non-negative integer, representing time in seconds.</p>
    745       <div id="rfc.figure.u.3"></div><pre class="inline"><span id="rfc.iref.g.1"></span>  <a href="#delta-seconds" class="smpl">delta-seconds</a>  = 1*<a href="#notation" class="smpl">DIGIT</a>
     758</pre></div>
     759         </div>
     760         <div id="delta-seconds">
     761            <h2 id="rfc.section.1.5"><a href="#rfc.section.1.5">1.5</a>&nbsp;<a href="#delta-seconds">Delta Seconds</a></h2>
     762            <p id="rfc.section.1.5.p.1">The delta-seconds rule specifies a non-negative integer, representing time in seconds.</p>
     763            <div id="rfc.figure.u.3"></div><pre class="inline"><span id="rfc.iref.g.1"></span>  <a href="#delta-seconds" class="smpl">delta-seconds</a>  = 1*<a href="#notation" class="smpl">DIGIT</a>
    746764</pre><p id="rfc.section.1.5.p.3">If an implementation receives a delta-seconds value larger than the largest positive integer it can represent, or if any of
    747          its subsequent calculations overflows, it <em class="bcp14">MUST</em> consider the value to be 2147483648 (2<sup>31</sup>). Recipients parsing a delta-seconds value <em class="bcp14">SHOULD</em> use an arithmetic type of at least 31 bits of range, and senders <em class="bcp14">MUST NOT</em> send delta-seconds with a value greater than 2147483648.
    748       </p>
    749       <h1 id="rfc.section.2"><a href="#rfc.section.2">2.</a>&nbsp;<a id="caching.overview" href="#caching.overview">Cache Operation</a></h1>
    750       <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>
    751       <p id="rfc.section.2.1.p.1">A cache <em class="bcp14">MUST NOT</em> store a response to any request, unless:
    752       </p>
    753       <ul>
    754          <li>The request method is understood by the cache and defined as being cacheable, and</li>
    755          <li>the response status code is understood by the cache, and</li>
    756          <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 header fields, and
    757          </li>
    758          <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
    759          </li>
    760          <li>the "Authorization" header field (see <a href="p7-auth.html#header.authorization" title="Authorization">Section 4.1</a> of <a href="#Part7" id="rfc.xref.Part7.1"><cite title="HTTP/1.1, part 7: Authentication">[Part7]</cite></a>) does not appear in the request, if the cache is shared, unless the response explicitly allows it (see <a href="#caching.authenticated.responses" title="Shared Caching of Authenticated Responses">Section&nbsp;2.6</a>), and
    761          </li>
    762          <li>the response either:
    763             <ul>
    764                <li>contains an Expires header field (see <a href="#header.expires" id="rfc.xref.header.expires.1" title="Expires">Section&nbsp;3.3</a>), or
    765                </li>
    766                <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
    767                </li>
    768                <li>contains a s-maxage response cache directive and the cache is shared, or</li>
    769                <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
    770                </li>
    771                <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>).
    772                </li>
    773             </ul>
    774          </li>
    775       </ul>
    776       <p id="rfc.section.2.1.p.2">Note that any of the requirements listed above can be overridden by a cache-control extension; see <a href="#cache.control.extensions" title="Cache Control Extensions">Section&nbsp;3.2.3</a>.
    777       </p>
    778       <p id="rfc.section.2.1.p.3">In this context, a cache has "understood" a request method or a response status code if it recognises it and implements any
    779          cache-specific behavior. In particular, 206 Partial Content responses cannot be cached by an implementation that does not
    780          handle partial content (see <a href="#errors.or.incomplete.response.cache.behavior" title="Storing Partial and Incomplete Responses">Section&nbsp;2.1.1</a>).
    781       </p>
    782       <p id="rfc.section.2.1.p.4">Note that in normal operation, most caches will not store a response that has neither a cache validator nor an explicit expiration
    783          time, as such responses are not usually useful to store. However, caches are not prohibited from storing such responses.
    784       </p>
    785       <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>
    786       <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
    787          field) 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.
    788       </p>
    789       <p id="rfc.section.2.1.1.p.2">A cache that does not support the Range and Content-Range header fields <em class="bcp14">MUST NOT</em> store incomplete or partial responses.
    790       </p>
    791       <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>
    792       <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:
    793       </p>
    794       <ul>
    795          <li>The presented effective request URI (<a href="p1-messaging.html#effective.request.uri" title="Effective Request URI">Section 4.3</a> of <a href="#Part1" id="rfc.xref.Part1.11"><cite title="HTTP/1.1, part 1: URIs, Connections, and Message Parsing">[Part1]</cite></a>) and that of the stored response match, and
    796          </li>
    797          <li>the request method associated with the stored response allows it to be used for the presented request, and</li>
    798          <li>selecting header fields nominated by the stored response (if any) match those presented (see <a href="#caching.negotiated.responses" title="Caching Negotiated Responses">Section&nbsp;2.7</a>), and
    799          </li>
    800          <li>the presented request and stored response are free from directives that would prevent its use (see <a href="#header.cache-control" id="rfc.xref.header.cache-control.2" title="Cache-Control">Section&nbsp;3.2</a> and <a href="#header.pragma" id="rfc.xref.header.pragma.1" title="Pragma">Section&nbsp;3.4</a>), and
    801          </li>
    802          <li>the stored response is either:
    803             <ul>
    804                <li>fresh (see <a href="#expiration.model" title="Freshness Model">Section&nbsp;2.3</a>), or
    805                </li>
    806                <li>allowed to be served stale (see <a href="#serving.stale.responses" title="Serving Stale Responses">Section&nbsp;2.3.3</a>), or
    807                </li>
    808                <li>successfully validated (see <a href="#validation.model" title="Validation Model">Section&nbsp;2.4</a>).
    809                </li>
    810             </ul>
    811          </li>
    812       </ul>
    813       <p id="rfc.section.2.2.p.2">Note that any of the requirements listed above can be overridden by a cache-control extension; see <a href="#cache.control.extensions" title="Cache Control Extensions">Section&nbsp;3.2.3</a>.
    814       </p>
    815       <p id="rfc.section.2.2.p.3">When a stored response is used to satisfy a request without validation, a cache <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>.
    816       </p>
    817       <p id="rfc.section.2.2.p.4">A cache <em class="bcp14">MUST</em> write through requests with methods that are unsafe (<a href="p2-semantics.html#safe.methods" title="Safe Methods">Section 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>) to the origin server; i.e., a cache must not generate a reply to such a request before having forwarded the request and
    818          having received a corresponding response.
    819       </p>
    820       <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>.
    821       </p>
    822       <p id="rfc.section.2.2.p.6">When more than one suitable response is stored, a cache <em class="bcp14">MUST</em> use the most recent response (as determined by the Date header field). It can also forward a request with "Cache-Control:
    823          max-age=0" or "Cache-Control: no-cache" to disambiguate which response to use.
    824       </p>
    825       <p id="rfc.section.2.2.p.7">A cache that does not have a clock available <em class="bcp14">MUST NOT</em> use stored responses without revalidating them on every use. A cache, especially a shared cache, <em class="bcp14">SHOULD</em> use a mechanism, such as NTP <a href="#RFC1305" id="rfc.xref.RFC1305.1"><cite title="Network Time Protocol (Version 3) Specification, Implementation">[RFC1305]</cite></a>, to synchronize its clock with a reliable external standard.
    826       </p>
    827       <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>
    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 field (<a href="#header.expires" id="rfc.xref.header.expires.2" title="Expires">Section&nbsp;3.3</a>) or the max-age response cache directive (<a href="#cache-response-directive" title="Response Cache-Control Directives">Section&nbsp;3.2.2</a>). Generally, origin servers will assign future explicit expiration times to responses in the belief that the representation
    833          is not 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          to indicate that the response is already stale. Compliant caches will normally validate the cached response before reusing
    837          it for subsequent requests (see <a href="#serving.stale.responses" title="Serving Stale Responses">Section&nbsp;2.3.3</a>).
    838       </p>
    839       <p id="rfc.section.2.3.p.4">Since origin servers do not always provide explicit expiration times, a cache <em class="bcp14">MAY</em> assign a heuristic expiration time when an explicit time is not specified, employing algorithms that use other header field
    840          values (such as the Last-Modified time) to estimate a plausible expiration time. This specification does not provide specific
    841          algorithms, but does impose worst-case constraints on their results.
    842       </p>
    843       <div id="rfc.figure.u.4"></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 might 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">Note that freshness applies only to cache operation; it cannot be used to force a user agent to refresh its display or reload
    851          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.
    852       </p>
    853       <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>
    854       <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>
    855       <ul>
    856          <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
    857          </li>
    858          <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
    859          </li>
    860          <li>If the Expires response header field (<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 field, or
    861          </li>
    862          <li>Otherwise, no explicit expiration time is present in the response. A heuristic freshness lifetime might be applicable; see <a href="#heuristic.freshness" title="Calculating Heuristic Freshness">Section&nbsp;2.3.1.1</a>.
    863          </li>
    864       </ul>
    865       <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>
    866       <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>
    867       <p id="rfc.section.2.3.1.1.p.1">If no explicit expiration time is present in a stored response that has a status code whose definition allows heuristic freshness
    868          to be used (including the following in <a href="p2-semantics.html#status.codes" title="Status Code Definitions">Section 8</a> of <a href="#Part2" id="rfc.xref.Part2.2"><cite title="HTTP/1.1, part 2: Message Semantics">[Part2]</cite></a>: 200, 203, 206, 300, 301 and 410), a cache <em class="bcp14">MAY</em> calculate a heuristic expiration time. A cache <em class="bcp14">MUST NOT</em> use heuristics to determine freshness for responses with status codes that do not explicitly allow it.
    869       </p>
    870       <p id="rfc.section.2.3.1.1.p.2">When a heuristic is used to calculate freshness lifetime, a cache <em class="bcp14">SHOULD</em> attach a Warning header field with a 113 warn-code to the response if its current_age is more than 24 hours and such a warning
    871          is not already present.
    872       </p>
    873       <p id="rfc.section.2.3.1.1.p.3">Also, if the response has a Last-Modified header field (<a href="p4-conditional.html#header.last-modified" title="Last-Modified">Section 2.1</a> of <a href="#Part4" id="rfc.xref.Part4.1"><cite title="HTTP/1.1, part 4: Conditional Requests">[Part4]</cite></a>), a cache <em class="bcp14">SHOULD NOT</em> use a heuristic expiration value that is more than some fraction of the interval since that time. A typical setting of this
    874          fraction might be 10%.
    875       </p>
    876       <div class="note" id="rfc.section.2.3.1.1.p.4">
    877          <p> <b>Note:</b> RFC 2616 (<a href="#RFC2616" id="rfc.xref.RFC2616.1"><cite title="Hypertext Transfer Protocol -- HTTP/1.1">[RFC2616]</cite></a>, <a href="http://tools.ietf.org/html/rfc2616#section-13.9">Section 13.9</a>) required that caches do not calculate heuristic freshness for URIs with query components (i.e., those containing '?'). In
    878             practice, this has not been widely implemented. Therefore, servers are encouraged to send explicit directives (e.g., Cache-Control:
    879             no-cache) if they wish to preclude caching.
    880          </p>
     765               its subsequent calculations overflows, it <em class="bcp14">MUST</em> consider the value to be 2147483648 (2<sup>31</sup>). Recipients parsing a delta-seconds value <em class="bcp14">SHOULD</em> use an arithmetic type of at least 31 bits of range, and senders <em class="bcp14">MUST NOT</em> send delta-seconds with a value greater than 2147483648.
     766            </p>
     767         </div>
    881768      </div>
    882       <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>
    883       <p id="rfc.section.2.3.2.p.1">HTTP/1.1 uses the Age header field to convey the estimated age of the response message when obtained from a cache. The Age
    884          field value is the cache's estimate of the amount of time since the response was generated or validated by the origin server.
    885          In essence, the Age value is the sum of the time that the response has been resident in each of the caches along the path
    886          from the origin server, plus the amount of time it has been in transit along network paths.
    887       </p>
    888       <p id="rfc.section.2.3.2.p.2">The following data is used for the age calculation:</p>
    889       <p id="rfc.section.2.3.2.p.3"> <dfn>age_value</dfn> 
    890       </p>
    891       <ul class="empty">
    892          <li>The term "age_value" denotes the value of the Age header field (<a href="#header.age" id="rfc.xref.header.age.2" title="Age">Section&nbsp;3.1</a>), in a form appropriate for arithmetic operation; or 0, if not available.
    893          </li>
    894       </ul>
    895       <p id="rfc.section.2.3.2.p.4"> <dfn>date_value</dfn> 
    896       </p>
    897       <ul class="empty">
    898          <li>HTTP/1.1 requires origin servers to send a Date header field, if possible, with every response, giving the time at which the
    899             response was generated. The term "date_value" denotes the value of the Date header field, in a form appropriate for arithmetic
    900             operations. See <a href="p1-messaging.html#header.date" title="Date">Section 9.3</a> of <a href="#Part1" id="rfc.xref.Part1.12"><cite title="HTTP/1.1, part 1: URIs, Connections, and Message Parsing">[Part1]</cite></a> for the definition of the Date header field, and for requirements regarding responses without it.
    901          </li>
    902       </ul>
    903       <p id="rfc.section.2.3.2.p.5"> <dfn>now</dfn> 
    904       </p>
    905       <ul class="empty">
    906          <li>The term "now" means "the current value of the clock at the host performing the calculation". A cache <em class="bcp14">SHOULD</em> use NTP (<a href="#RFC1305" id="rfc.xref.RFC1305.2"><cite title="Network Time Protocol (Version 3) Specification, Implementation">[RFC1305]</cite></a>) or some similar protocol to synchronize its clocks to a globally accurate time standard.
    907          </li>
    908       </ul>
    909       <p id="rfc.section.2.3.2.p.6"> <dfn>request_time</dfn> 
    910       </p>
    911       <ul class="empty">
    912          <li>The current value of the clock at the host at the time the request resulting in the stored response was made.</li>
    913       </ul>
    914       <p id="rfc.section.2.3.2.p.7"> <dfn>response_time</dfn> 
    915       </p>
    916       <ul class="empty">
    917          <li>The current value of the clock at the host at the time the response was received.</li>
    918       </ul>
    919       <p id="rfc.section.2.3.2.p.8">A response's age can be calculated in two entirely independent ways: </p>
    920       <ol>
    921          <li>the "apparent_age": response_time minus date_value, if the local clock is reasonably well synchronized to the origin server's
    922             clock. If the result is negative, the result is replaced by zero.
    923          </li>
    924          <li>the "corrected_age_value", if all of the caches along the response path implement HTTP/1.1. A cache <em class="bcp14">MUST</em> interpret this value relative to the time the request was initiated, not the time that the response was received.
    925          </li>
    926       </ol>
    927       <div id="rfc.figure.u.5"></div> <pre class="text">  apparent_age = max(0, response_time - date_value);
     769      <div id="caching.overview">
     770         <h1 id="rfc.section.2"><a href="#rfc.section.2">2.</a>&nbsp;<a href="#caching.overview">Cache Operation</a></h1>
     771         <div id="response.cacheability">
     772            <h2 id="rfc.section.2.1"><a href="#rfc.section.2.1">2.1</a>&nbsp;<a href="#response.cacheability">Response Cacheability</a></h2>
     773            <p id="rfc.section.2.1.p.1">A cache <em class="bcp14">MUST NOT</em> store a response to any request, unless:
     774            </p>
     775            <ul>
     776               <li>The request method is understood by the cache and defined as being cacheable, and</li>
     777               <li>the response status code is understood by the cache, and</li>
     778               <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 header fields, and
     779               </li>
     780               <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
     781               </li>
     782               <li>the "Authorization" header field (see <a href="p7-auth.html#header.authorization" title="Authorization">Section 4.1</a> of <a href="#Part7" id="rfc.xref.Part7.1"><cite title="HTTP/1.1, part 7: Authentication">[Part7]</cite></a>) does not appear in the request, if the cache is shared, unless the response explicitly allows it (see <a href="#caching.authenticated.responses" title="Shared Caching of Authenticated Responses">Section&nbsp;2.6</a>), and
     783               </li>
     784               <li>the response either:
     785                  <ul>
     786                     <li>contains an Expires header field (see <a href="#header.expires" id="rfc.xref.header.expires.1" title="Expires">Section&nbsp;3.3</a>), or
     787                     </li>
     788                     <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
     789                     </li>
     790                     <li>contains a s-maxage response cache directive and the cache is shared, or</li>
     791                     <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
     792                     </li>
     793                     <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>).
     794                     </li>
     795                  </ul>
     796               </li>
     797            </ul>
     798            <p id="rfc.section.2.1.p.2">Note that any of the requirements listed above can be overridden by a cache-control extension; see <a href="#cache.control.extensions" title="Cache Control Extensions">Section&nbsp;3.2.3</a>.
     799            </p>
     800            <p id="rfc.section.2.1.p.3">In this context, a cache has "understood" a request method or a response status code if it recognises it and implements any
     801               cache-specific behavior. In particular, 206 Partial Content responses cannot be cached by an implementation that does not
     802               handle partial content (see <a href="#errors.or.incomplete.response.cache.behavior" title="Storing Partial and Incomplete Responses">Section&nbsp;2.1.1</a>).
     803            </p>
     804            <p id="rfc.section.2.1.p.4">Note that in normal operation, most caches will not store a response that has neither a cache validator nor an explicit expiration
     805               time, as such responses are not usually useful to store. However, caches are not prohibited from storing such responses.
     806            </p>
     807            <div id="errors.or.incomplete.response.cache.behavior">
     808               <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>
     809               <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
     810                  field) 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.
     811               </p>
     812               <p id="rfc.section.2.1.1.p.2">A cache that does not support the Range and Content-Range header fields <em class="bcp14">MUST NOT</em> store incomplete or partial responses.
     813               </p>
     814            </div>
     815         </div>
     816         <div id="constructing.responses.from.caches">
     817            <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>
     818            <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:
     819            </p>
     820            <ul>
     821               <li>The presented effective request URI (<a href="p1-messaging.html#effective.request.uri" title="Effective Request URI">Section 4.3</a> of <a href="#Part1" id="rfc.xref.Part1.11"><cite title="HTTP/1.1, part 1: URIs, Connections, and Message Parsing">[Part1]</cite></a>) and that of the stored response match, and
     822               </li>
     823               <li>the request method associated with the stored response allows it to be used for the presented request, and</li>
     824               <li>selecting header fields nominated by the stored response (if any) match those presented (see <a href="#caching.negotiated.responses" title="Caching Negotiated Responses">Section&nbsp;2.7</a>), and
     825               </li>
     826               <li>the presented request and stored response are free from directives that would prevent its use (see <a href="#header.cache-control" id="rfc.xref.header.cache-control.2" title="Cache-Control">Section&nbsp;3.2</a> and <a href="#header.pragma" id="rfc.xref.header.pragma.1" title="Pragma">Section&nbsp;3.4</a>), and
     827               </li>
     828               <li>the stored response is either:
     829                  <ul>
     830                     <li>fresh (see <a href="#expiration.model" title="Freshness Model">Section&nbsp;2.3</a>), or
     831                     </li>
     832                     <li>allowed to be served stale (see <a href="#serving.stale.responses" title="Serving Stale Responses">Section&nbsp;2.3.3</a>), or
     833                     </li>
     834                     <li>successfully validated (see <a href="#validation.model" title="Validation Model">Section&nbsp;2.4</a>).
     835                     </li>
     836                  </ul>
     837               </li>
     838            </ul>
     839            <p id="rfc.section.2.2.p.2">Note that any of the requirements listed above can be overridden by a cache-control extension; see <a href="#cache.control.extensions" title="Cache Control Extensions">Section&nbsp;3.2.3</a>.
     840            </p>
     841            <p id="rfc.section.2.2.p.3">When a stored response is used to satisfy a request without validation, a cache <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>.
     842            </p>
     843            <p id="rfc.section.2.2.p.4">A cache <em class="bcp14">MUST</em> write through requests with methods that are unsafe (<a href="p2-semantics.html#safe.methods" title="Safe Methods">Section 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>) to the origin server; i.e., a cache must not generate a reply to such a request before having forwarded the request and
     844               having received a corresponding response.
     845            </p>
     846            <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>.
     847            </p>
     848            <p id="rfc.section.2.2.p.6">When more than one suitable response is stored, a cache <em class="bcp14">MUST</em> use the most recent response (as determined by the Date header field). It can also forward a request with "Cache-Control:
     849               max-age=0" or "Cache-Control: no-cache" to disambiguate which response to use.
     850            </p>
     851            <p id="rfc.section.2.2.p.7">A cache that does not have a clock available <em class="bcp14">MUST NOT</em> use stored responses without revalidating them on every use. A cache, especially a shared cache, <em class="bcp14">SHOULD</em> use a mechanism, such as NTP <a href="#RFC1305" id="rfc.xref.RFC1305.1"><cite title="Network Time Protocol (Version 3) Specification, Implementation">[RFC1305]</cite></a>, to synchronize its clock with a reliable external standard.
     852            </p>
     853         </div>
     854         <div id="expiration.model">
     855            <h2 id="rfc.section.2.3"><a href="#rfc.section.2.3">2.3</a>&nbsp;<a href="#expiration.model">Freshness Model</a></h2>
     856            <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,
     857               thereby improving efficiency.
     858            </p>
     859            <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,
     860               using either the Expires header field (<a href="#header.expires" id="rfc.xref.header.expires.2" title="Expires">Section&nbsp;3.3</a>) or the max-age response cache directive (<a href="#cache-response-directive" title="Response Cache-Control Directives">Section&nbsp;3.2.2</a>). Generally, origin servers will assign future explicit expiration times to responses in the belief that the representation
     861               is not likely to change in a semantically significant way before the expiration time is reached.
     862            </p>
     863            <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
     864               to indicate that the response is already stale. Compliant caches will normally validate the cached response before reusing
     865               it for subsequent requests (see <a href="#serving.stale.responses" title="Serving Stale Responses">Section&nbsp;2.3.3</a>).
     866            </p>
     867            <p id="rfc.section.2.3.p.4">Since origin servers do not always provide explicit expiration times, a cache <em class="bcp14">MAY</em> assign a heuristic expiration time when an explicit time is not specified, employing algorithms that use other header field
     868               values (such as the Last-Modified time) to estimate a plausible expiration time. This specification does not provide specific
     869               algorithms, but does impose worst-case constraints on their results.
     870            </p>
     871            <div id="rfc.figure.u.4"></div>
     872            <p>The calculation to determine if a response is fresh is:</p><pre class="text">   response_is_fresh = (freshness_lifetime &gt; current_age)
     873</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>.
     874            </p>
     875            <p id="rfc.section.2.3.p.7">Additionally, clients might need to influence freshness calculation. They can do this using several request cache directives,
     876               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>.
     877            </p>
     878            <p id="rfc.section.2.3.p.8">Note that freshness applies only to cache operation; it cannot be used to force a user agent to refresh its display or reload
     879               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.
     880            </p>
     881            <div id="calculating.freshness.lifetime">
     882               <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>
     883               <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>
     884               <ul>
     885                  <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
     886                  </li>
     887                  <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
     888                  </li>
     889                  <li>If the Expires response header field (<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 field, or
     890                  </li>
     891                  <li>Otherwise, no explicit expiration time is present in the response. A heuristic freshness lifetime might be applicable; see <a href="#heuristic.freshness" title="Calculating Heuristic Freshness">Section&nbsp;2.3.1.1</a>.
     892                  </li>
     893               </ul>
     894               <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>
     895               <div id="heuristic.freshness">
     896                  <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>
     897                  <p id="rfc.section.2.3.1.1.p.1">If no explicit expiration time is present in a stored response that has a status code whose definition allows heuristic freshness
     898                     to be used (including the following in <a href="p2-semantics.html#status.codes" title="Status Code Definitions">Section 8</a> of <a href="#Part2" id="rfc.xref.Part2.2"><cite title="HTTP/1.1, part 2: Message Semantics">[Part2]</cite></a>: 200, 203, 206, 300, 301 and 410), a cache <em class="bcp14">MAY</em> calculate a heuristic expiration time. A cache <em class="bcp14">MUST NOT</em> use heuristics to determine freshness for responses with status codes that do not explicitly allow it.
     899                  </p>
     900                  <p id="rfc.section.2.3.1.1.p.2">When a heuristic is used to calculate freshness lifetime, a cache <em class="bcp14">SHOULD</em> attach a Warning header field with a 113 warn-code to the response if its current_age is more than 24 hours and such a warning
     901                     is not already present.
     902                  </p>
     903                  <p id="rfc.section.2.3.1.1.p.3">Also, if the response has a Last-Modified header field (<a href="p4-conditional.html#header.last-modified" title="Last-Modified">Section 2.1</a> of <a href="#Part4" id="rfc.xref.Part4.1"><cite title="HTTP/1.1, part 4: Conditional Requests">[Part4]</cite></a>), a cache <em class="bcp14">SHOULD NOT</em> use a heuristic expiration value that is more than some fraction of the interval since that time. A typical setting of this
     904                     fraction might be 10%.
     905                  </p>
     906                  <div class="note" id="rfc.section.2.3.1.1.p.4">
     907                     <p><b>Note:</b> RFC 2616 (<a href="#RFC2616" id="rfc.xref.RFC2616.1"><cite title="Hypertext Transfer Protocol -- HTTP/1.1">[RFC2616]</cite></a>, <a href="https://tools.ietf.org/html/rfc2616#section-13.9">Section 13.9</a>) required that caches do not calculate heuristic freshness for URIs with query components (i.e., those containing '?'). In
     908                        practice, this has not been widely implemented. Therefore, servers are encouraged to send explicit directives (e.g., Cache-Control:
     909                        no-cache) if they wish to preclude caching.
     910                     </p>
     911                  </div>
     912               </div>
     913            </div>
     914            <div id="age.calculations">
     915               <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>
     916               <p id="rfc.section.2.3.2.p.1">HTTP/1.1 uses the Age header field to convey the estimated age of the response message when obtained from a cache. The Age
     917                  field value is the cache's estimate of the amount of time since the response was generated or validated by the origin server.
     918                  In essence, the Age value is the sum of the time that the response has been resident in each of the caches along the path
     919                  from the origin server, plus the amount of time it has been in transit along network paths.
     920               </p>
     921               <p id="rfc.section.2.3.2.p.2">The following data is used for the age calculation:</p>
     922               <p id="rfc.section.2.3.2.p.3"><dfn>age_value</dfn>
     923               </p>
     924               <ul class="empty">
     925                  <li>The term "age_value" denotes the value of the Age header field (<a href="#header.age" id="rfc.xref.header.age.2" title="Age">Section&nbsp;3.1</a>), in a form appropriate for arithmetic operation; or 0, if not available.
     926                  </li>
     927               </ul>
     928               <p id="rfc.section.2.3.2.p.4"><dfn>date_value</dfn>
     929               </p>
     930               <ul class="empty">
     931                  <li>HTTP/1.1 requires origin servers to send a Date header field, if possible, with every response, giving the time at which the
     932                     response was generated. The term "date_value" denotes the value of the Date header field, in a form appropriate for arithmetic
     933                     operations. See <a href="p1-messaging.html#header.date" title="Date">Section 9.3</a> of <a href="#Part1" id="rfc.xref.Part1.12"><cite title="HTTP/1.1, part 1: URIs, Connections, and Message Parsing">[Part1]</cite></a> for the definition of the Date header field, and for requirements regarding responses without it.
     934                  </li>
     935               </ul>
     936               <p id="rfc.section.2.3.2.p.5"><dfn>now</dfn>
     937               </p>
     938               <ul class="empty">
     939                  <li>The term "now" means "the current value of the clock at the host performing the calculation". A cache <em class="bcp14">SHOULD</em> use NTP (<a href="#RFC1305" id="rfc.xref.RFC1305.2"><cite title="Network Time Protocol (Version 3) Specification, Implementation">[RFC1305]</cite></a>) or some similar protocol to synchronize its clocks to a globally accurate time standard.
     940                  </li>
     941               </ul>
     942               <p id="rfc.section.2.3.2.p.6"><dfn>request_time</dfn>
     943               </p>
     944               <ul class="empty">
     945                  <li>The current value of the clock at the host at the time the request resulting in the stored response was made.</li>
     946               </ul>
     947               <p id="rfc.section.2.3.2.p.7"><dfn>response_time</dfn>
     948               </p>
     949               <ul class="empty">
     950                  <li>The current value of the clock at the host at the time the response was received.</li>
     951               </ul>
     952               <p id="rfc.section.2.3.2.p.8">A response's age can be calculated in two entirely independent ways: </p>
     953               <ol>
     954                  <li>the "apparent_age": response_time minus date_value, if the local clock is reasonably well synchronized to the origin server's
     955                     clock. If the result is negative, the result is replaced by zero.
     956                  </li>
     957                  <li>the "corrected_age_value", if all of the caches along the response path implement HTTP/1.1. A cache <em class="bcp14">MUST</em> interpret this value relative to the time the request was initiated, not the time that the response was received.
     958                  </li>
     959               </ol>
     960               <div id="rfc.figure.u.5"></div><pre class="text">  apparent_age = max(0, response_time - date_value);
    928961
    929962  response_delay = response_time - request_time;
    930963  corrected_age_value = age_value + response_delay; 
    931 </pre> <div id="rfc.figure.u.6"></div>
    932       <p>These are combined as</p>  <pre class="text">  corrected_initial_age = max(apparent_age, corrected_age_value);
     964</pre><div id="rfc.figure.u.6"></div>
     965               <p>These are combined as</p><pre class="text">  corrected_initial_age = max(apparent_age, corrected_age_value);
    933966</pre><p id="rfc.section.2.3.2.p.11">The current_age of a stored response can then be calculated by adding the amount of time (in seconds) since the stored response
    934          was last validated by the origin server to the corrected_initial_age.
    935       </p>
    936       <div id="rfc.figure.u.7"></div><pre class="text">  resident_time = now - response_time;
     967                  was last validated by the origin server to the corrected_initial_age.
     968               </p>
     969               <div id="rfc.figure.u.7"></div><pre class="text">  resident_time = now - response_time;
    937970  current_age = corrected_initial_age + resident_time;
    938 </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>
    939       <p id="rfc.section.2.3.3.p.1">A "stale" response is one that either has explicit expiry information or is allowed to have heuristic expiry calculated, but
    940          is not fresh according to the calculations in <a href="#expiration.model" title="Freshness Model">Section&nbsp;2.3</a>.
    941       </p>
    942       <p id="rfc.section.2.3.3.p.2">A cache <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
    943          directive, a "must-revalidate" cache-response-directive, or an applicable "s-maxage" or "proxy-revalidate" cache-response-directive;
    944          see <a href="#cache-response-directive" title="Response Cache-Control Directives">Section&nbsp;3.2.2</a>).
    945       </p>
    946       <p id="rfc.section.2.3.3.p.3">A cache <em class="bcp14">SHOULD NOT</em> return stale responses unless it is disconnected (i.e., it cannot contact the origin server or otherwise find a forward path)
    947          or doing so is explicitly allowed (e.g., by the max-stale request directive; see <a href="#cache-request-directive" title="Request Cache-Control Directives">Section&nbsp;3.2.1</a>).
    948       </p>
    949       <p id="rfc.section.2.3.3.p.4">A cache <em class="bcp14">SHOULD</em> append a Warning header field with the 110 warn-code (see <a href="#header.warning" id="rfc.xref.header.warning.1" title="Warning">Section&nbsp;3.6</a>) to stale responses. Likewise, a cache <em class="bcp14">SHOULD</em> add the 112 warn-code to stale responses if the cache is disconnected.
    950       </p>
    951       <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
    952          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 header fields).
    953          A cache <em class="bcp14">SHOULD NOT</em> attempt to validate a response simply because that response became stale in transit.
    954       </p>
    955       <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>
    956       <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
    957          fresh, or one cannot be selected; see <a href="#caching.negotiated.responses" title="Caching Negotiated Responses">Section&nbsp;2.7</a>), it can use the conditional request mechanism <a href="#Part4" id="rfc.xref.Part4.2"><cite title="HTTP/1.1, part 4: Conditional Requests">[Part4]</cite></a> in the forwarded request to give the origin server an opportunity to both select a valid stored response to be used, and to
    958          update it. This process is known as "validating" or "revalidating" the stored response.
    959       </p>
    960       <p id="rfc.section.2.4.p.2">When sending such a conditional request, a cache <em class="bcp14">SHOULD</em> add an If-Modified-Since header field whose value is that of the Last-Modified header field from the selected (see <a href="#caching.negotiated.responses" title="Caching Negotiated Responses">Section&nbsp;2.7</a>) stored response, if available.
    961       </p>
    962       <p id="rfc.section.2.4.p.3">Additionally, a cache <em class="bcp14">SHOULD</em> add an If-None-Match header field whose value is that of the ETag header field(s) from all responses stored for the requested
    963          URI, if present. However, if any of the stored responses contains only partial content, the cache <em class="bcp14">SHOULD NOT</em> include its entity-tag in the If-None-Match header field unless the request is for a range that would be fully satisfied by
    964          that stored response.
    965       </p>
    966       <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.responses" title="Combining Responses">Section&nbsp;2.8</a>.
    967       </p>
    968       <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
    969          request is suitable. Instead, a cache <em class="bcp14">SHOULD</em> use the full response to satisfy the request and <em class="bcp14">MAY</em> replace the stored response.
    970       </p>
    971       <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>).
    972       </p>
    973       <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>
    974       <p id="rfc.section.2.5.p.1">Because unsafe request methods (<a href="p2-semantics.html#safe.methods" title="Safe Methods">Section 7.1.1</a> of <a href="#Part2" id="rfc.xref.Part2.3"><cite title="HTTP/1.1, part 2: Message Semantics">[Part2]</cite></a>) such as PUT, POST or DELETE have the potential for changing state on the origin server, intervening caches can use them
    975          to keep their contents up-to-date.
    976       </p>
    977       <p id="rfc.section.2.5.p.2">A cache <em class="bcp14">MUST</em> invalidate the effective Request URI (<a href="p1-messaging.html#effective.request.uri" title="Effective Request URI">Section 4.3</a> of <a href="#Part1" id="rfc.xref.Part1.13"><cite title="HTTP/1.1, part 1: URIs, Connections, and Message Parsing">[Part1]</cite></a>) as well as the URI(s) in the Location and Content-Location header fields (if present) when a non-error response to a request
    978          with an unsafe method is received.
    979       </p>
    980       <p id="rfc.section.2.5.p.3">However, a cache <em class="bcp14">MUST NOT</em> invalidate a URI from a Location or Content-Location header field if the host part of that URI differs from the host part
    981          in the effective request URI (<a href="p1-messaging.html#effective.request.uri" title="Effective Request URI">Section 4.3</a> of <a href="#Part1" id="rfc.xref.Part1.14"><cite title="HTTP/1.1, part 1: URIs, Connections, and Message Parsing">[Part1]</cite></a>). This helps prevent denial of service attacks.
    982       </p>
    983       <p id="rfc.section.2.5.p.4">A cache <em class="bcp14">SHOULD</em> invalidate the effective request URI (<a href="p1-messaging.html#effective.request.uri" title="Effective Request URI">Section 4.3</a> of <a href="#Part1" id="rfc.xref.Part1.15"><cite title="HTTP/1.1, part 1: URIs, Connections, and Message Parsing">[Part1]</cite></a>) when it receives a non-error response to a request with a method whose safety is unknown.
    984       </p>
    985       <p id="rfc.section.2.5.p.5">Here, a "non-error response" is one with a 2xx or 3xx status code. "Invalidate" means that the cache will either remove all
    986          stored responses related to the effective request URI, or will mark these as "invalid" and in need of a mandatory validation
    987          before they can be returned in response to a subsequent request.
    988       </p>
    989       <p id="rfc.section.2.5.p.6">Note that this does not guarantee that all appropriate responses are invalidated. For example, the request that caused the
    990          change at the origin server might not have gone through the cache where a response is stored.
    991       </p>
    992       <h2 id="rfc.section.2.6"><a href="#rfc.section.2.6">2.6</a>&nbsp;<a id="caching.authenticated.responses" href="#caching.authenticated.responses">Shared Caching of Authenticated Responses</a></h2>
    993       <p id="rfc.section.2.6.p.1">A shared cache <em class="bcp14">MUST NOT</em> use a cached response to a request with an Authorization header field (<a href="p7-auth.html#header.authorization" title="Authorization">Section 4.1</a> of <a href="#Part7" id="rfc.xref.Part7.2"><cite title="HTTP/1.1, part 7: Authentication">[Part7]</cite></a>) to satisfy any subsequent request unless a cache directive that allows such responses to be stored is present in the response.
    994       </p>
    995       <p id="rfc.section.2.6.p.2">In this specification, the following Cache-Control response directives (<a href="#cache-response-directive" title="Response Cache-Control Directives">Section&nbsp;3.2.2</a>) have such an effect: must-revalidate, public, s-maxage.
    996       </p>
    997       <p id="rfc.section.2.6.p.3">Note that cached responses that contain the "must-revalidate" and/or "s-maxage" response directives are not allowed to be
    998          served stale (<a href="#serving.stale.responses" title="Serving Stale Responses">Section&nbsp;2.3.3</a>) by shared caches. In particular, a response with either "max-age=0, must-revalidate" or "s-maxage=0" cannot be used to satisfy
    999          a subsequent request without revalidating it on the origin server.
    1000       </p>
    1001       <h2 id="rfc.section.2.7"><a href="#rfc.section.2.7">2.7</a>&nbsp;<a id="caching.negotiated.responses" href="#caching.negotiated.responses">Caching Negotiated Responses</a></h2>
    1002       <p id="rfc.section.2.7.p.1">When a cache receives a request that can be satisfied by a stored response that has a Vary header field (<a href="#header.vary" id="rfc.xref.header.vary.1" title="Vary">Section&nbsp;3.5</a>), it <em class="bcp14">MUST NOT</em> use that response unless all of the selecting header fields nominated by the Vary header field match in both the original
    1003          request (i.e., that associated with the stored response), and the presented request.
    1004       </p>
    1005       <p id="rfc.section.2.7.p.2">The selecting header fields from two requests are defined to match if and only if those in the first request can be transformed
    1006          to those in the second request by applying any of the following:
    1007       </p>
    1008       <ul>
    1009          <li>adding or removing whitespace, where allowed in the header field's syntax</li>
    1010          <li>combining multiple header fields with the same field name (see <a href="p1-messaging.html#header.fields" title="Header Fields">Section 3.2</a> of <a href="#Part1" id="rfc.xref.Part1.16"><cite title="HTTP/1.1, part 1: URIs, Connections, and Message Parsing">[Part1]</cite></a>)
    1011          </li>
    1012          <li>normalizing both header field values in a way that is known to have identical semantics, according to the header field's specification
    1013             (e.g., re-ordering field values when order is not significant; case-normalization, where values are defined to be case-insensitive)
    1014          </li>
    1015       </ul>
    1016       <p id="rfc.section.2.7.p.3">If (after any normalization that might take place) a header field is absent from a request, it can only match another request
    1017          if it is also absent there.
    1018       </p>
    1019       <p id="rfc.section.2.7.p.4">A Vary header field-value of "*" always fails to match, and subsequent requests to that resource can only be properly interpreted
    1020          by the origin server.
    1021       </p>
    1022       <p id="rfc.section.2.7.p.5">The stored response with matching selecting header fields is known as the selected response.</p>
    1023       <p id="rfc.section.2.7.p.6">If multiple selected responses are available, the most recent response (as determined by the Date header field) is used; see <a href="#constructing.responses.from.caches" title="Constructing Responses from Caches">Section&nbsp;2.2</a>.
    1024       </p>
    1025       <p id="rfc.section.2.7.p.7">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>.
    1026       </p>
    1027       <h2 id="rfc.section.2.8"><a href="#rfc.section.2.8">2.8</a>&nbsp;<a id="combining.responses" href="#combining.responses">Combining Responses</a></h2>
    1028       <p id="rfc.section.2.8.p.1">When a cache receives a 304 (Not Modified) response or a 206 (Partial Content) response (in this section, the "new" response"),
    1029          it needs to create an updated response by combining the stored response with the new one, so that the updated response can
    1030          be used to satisfy the request, and potentially update the cached response.
    1031       </p>
    1032       <p id="rfc.section.2.8.p.2">If the new response contains an ETag, it identifies the stored response to use. <span class="comment" id="TODO-mention-CL">[<a href="#TODO-mention-CL" class="smpl">TODO-mention-CL</a>: might need language about Content-Location here]</span><span class="comment" id="TODO-select-for-combine">[<a href="#TODO-select-for-combine" class="smpl">TODO-select-for-combine</a>: Shouldn't this be the selected response?]</span>
    1033       </p>
    1034       <p id="rfc.section.2.8.p.3">When the new response's status code is 206 (partial content), a cache <em class="bcp14">MUST NOT</em> combine it with the old response if either response does not have a validator, and <em class="bcp14">MUST NOT</em> combine it with the old response when those validators do not match with the strong comparison function (see <a href="p4-conditional.html#weak.and.strong.validators" title="Weak versus Strong">Section 2.2.2</a> of <a href="#Part4" id="rfc.xref.Part4.3"><cite title="HTTP/1.1, part 4: Conditional Requests">[Part4]</cite></a>).
    1035       </p>
    1036       <p id="rfc.section.2.8.p.4">The stored response header fields are used as those of the updated response, except that </p>
    1037       <ul>
    1038          <li>a cache <em class="bcp14">MUST</em> delete any stored Warning header fields with warn-code 1xx (see <a href="#header.warning" id="rfc.xref.header.warning.2" title="Warning">Section&nbsp;3.6</a>).
    1039          </li>
    1040          <li>a cache <em class="bcp14">MUST</em> retain any stored Warning header fields with warn-code 2xx.
    1041          </li>
    1042          <li>a cache <em class="bcp14">MUST</em> use other header fields provided in the new response to replace all instances of the corresponding header fields from the
    1043             stored response.
    1044          </li>
    1045       </ul>
    1046       <p id="rfc.section.2.8.p.5">A cache <em class="bcp14">MUST</em> use the updated response header fields to replace those of the stored response (unless the stored response is removed). In
    1047          the case of a 206 response, a cache <em class="bcp14">MAY</em> store the combined representation.
    1048       </p>
    1049       <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>
    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       <div id="rfc.iref.a.2"></div>
    1052       <div id="rfc.iref.h.2"></div>
    1053       <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>
    1054       <p id="rfc.section.3.1.p.1">The "Age" header field conveys the sender's estimate of the amount of time since the response was generated or successfully
    1055          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>.
    1056       </p>
    1057       <div id="rfc.figure.u.8"></div><pre class="inline"><span id="rfc.iref.g.2"></span>  <a href="#header.age" class="smpl">Age</a> = <a href="#delta-seconds" class="smpl">delta-seconds</a>
     971</pre></div>
     972            <div id="serving.stale.responses">
     973               <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>
     974               <p id="rfc.section.2.3.3.p.1">A "stale" response is one that either has explicit expiry information or is allowed to have heuristic expiry calculated, but
     975                  is not fresh according to the calculations in <a href="#expiration.model" title="Freshness Model">Section&nbsp;2.3</a>.
     976               </p>
     977               <p id="rfc.section.2.3.3.p.2">A cache <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
     978                  directive, a "must-revalidate" cache-response-directive, or an applicable "s-maxage" or "proxy-revalidate" cache-response-directive;
     979                  see <a href="#cache-response-directive" title="Response Cache-Control Directives">Section&nbsp;3.2.2</a>).
     980               </p>
     981               <p id="rfc.section.2.3.3.p.3">A cache <em class="bcp14">SHOULD NOT</em> return stale responses unless it is disconnected (i.e., it cannot contact the origin server or otherwise find a forward path)
     982                  or doing so is explicitly allowed (e.g., by the max-stale request directive; see <a href="#cache-request-directive" title="Request Cache-Control Directives">Section&nbsp;3.2.1</a>).
     983               </p>
     984               <p id="rfc.section.2.3.3.p.4">A cache <em class="bcp14">SHOULD</em> append a Warning header field with the 110 warn-code (see <a href="#header.warning" id="rfc.xref.header.warning.1" title="Warning">Section&nbsp;3.6</a>) to stale responses. Likewise, a cache <em class="bcp14">SHOULD</em> add the 112 warn-code to stale responses if the cache is disconnected.
     985               </p>
     986               <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
     987                  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 header fields).
     988                  A cache <em class="bcp14">SHOULD NOT</em> attempt to validate a response simply because that response became stale in transit.
     989               </p>
     990            </div>
     991         </div>
     992         <div id="validation.model">
     993            <h2 id="rfc.section.2.4"><a href="#rfc.section.2.4">2.4</a>&nbsp;<a href="#validation.model">Validation Model</a></h2>
     994            <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
     995               fresh, or one cannot be selected; see <a href="#caching.negotiated.responses" title="Caching Negotiated Responses">Section&nbsp;2.7</a>), it can use the conditional request mechanism <a href="#Part4" id="rfc.xref.Part4.2"><cite title="HTTP/1.1, part 4: Conditional Requests">[Part4]</cite></a> in the forwarded request to give the origin server an opportunity to both select a valid stored response to be used, and to
     996               update it. This process is known as "validating" or "revalidating" the stored response.
     997            </p>
     998            <p id="rfc.section.2.4.p.2">When sending such a conditional request, a cache <em class="bcp14">SHOULD</em> add an If-Modified-Since header field whose value is that of the Last-Modified header field from the selected (see <a href="#caching.negotiated.responses" title="Caching Negotiated Responses">Section&nbsp;2.7</a>) stored response, if available.
     999            </p>
     1000            <p id="rfc.section.2.4.p.3">Additionally, a cache <em class="bcp14">SHOULD</em> add an If-None-Match header field whose value is that of the ETag header field(s) from all responses stored for the requested
     1001               URI, if present. However, if any of the stored responses contains only partial content, the cache <em class="bcp14">SHOULD NOT</em> include its entity-tag in the If-None-Match header field unless the request is for a range that would be fully satisfied by
     1002               that stored response.
     1003            </p>
     1004            <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.responses" title="Combining Responses">Section&nbsp;2.8</a>.
     1005            </p>
     1006            <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
     1007               request is suitable. Instead, a cache <em class="bcp14">SHOULD</em> use the full response to satisfy the request and <em class="bcp14">MAY</em> replace the stored response.
     1008            </p>
     1009            <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>).
     1010            </p>
     1011         </div>
     1012         <div id="invalidation.after.updates.or.deletions">
     1013            <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>
     1014            <p id="rfc.section.2.5.p.1">Because unsafe request methods (<a href="p2-semantics.html#safe.methods" title="Safe Methods">Section 7.1.1</a> of <a href="#Part2" id="rfc.xref.Part2.3"><cite title="HTTP/1.1, part 2: Message Semantics">[Part2]</cite></a>) such as PUT, POST or DELETE have the potential for changing state on the origin server, intervening caches can use them
     1015               to keep their contents up-to-date.
     1016            </p>
     1017            <p id="rfc.section.2.5.p.2">A cache <em class="bcp14">MUST</em> invalidate the effective Request URI (<a href="p1-messaging.html#effective.request.uri" title="Effective Request URI">Section 4.3</a> of <a href="#Part1" id="rfc.xref.Part1.13"><cite title="HTTP/1.1, part 1: URIs, Connections, and Message Parsing">[Part1]</cite></a>) as well as the URI(s) in the Location and Content-Location header fields (if present) when a non-error response to a request
     1018               with an unsafe method is received.
     1019            </p>
     1020            <p id="rfc.section.2.5.p.3">However, a cache <em class="bcp14">MUST NOT</em> invalidate a URI from a Location or Content-Location header field if the host part of that URI differs from the host part
     1021               in the effective request URI (<a href="p1-messaging.html#effective.request.uri" title="Effective Request URI">Section 4.3</a> of <a href="#Part1" id="rfc.xref.Part1.14"><cite title="HTTP/1.1, part 1: URIs, Connections, and Message Parsing">[Part1]</cite></a>). This helps prevent denial of service attacks.
     1022            </p>
     1023            <p id="rfc.section.2.5.p.4">A cache <em class="bcp14">SHOULD</em> invalidate the effective request URI (<a href="p1-messaging.html#effective.request.uri" title="Effective Request URI">Section 4.3</a> of <a href="#Part1" id="rfc.xref.Part1.15"><cite title="HTTP/1.1, part 1: URIs, Connections, and Message Parsing">[Part1]</cite></a>) when it receives a non-error response to a request with a method whose safety is unknown.
     1024            </p>
     1025            <p id="rfc.section.2.5.p.5">Here, a "non-error response" is one with a 2xx or 3xx status code. "Invalidate" means that the cache will either remove all
     1026               stored responses related to the effective request URI, or will mark these as "invalid" and in need of a mandatory validation
     1027               before they can be returned in response to a subsequent request.
     1028            </p>
     1029            <p id="rfc.section.2.5.p.6">Note that this does not guarantee that all appropriate responses are invalidated. For example, the request that caused the
     1030               change at the origin server might not have gone through the cache where a response is stored.
     1031            </p>
     1032         </div>
     1033         <div id="caching.authenticated.responses">
     1034            <h2 id="rfc.section.2.6"><a href="#rfc.section.2.6">2.6</a>&nbsp;<a href="#caching.authenticated.responses">Shared Caching of Authenticated Responses</a></h2>
     1035            <p id="rfc.section.2.6.p.1">A shared cache <em class="bcp14">MUST NOT</em> use a cached response to a request with an Authorization header field (<a href="p7-auth.html#header.authorization" title="Authorization">Section 4.1</a> of <a href="#Part7" id="rfc.xref.Part7.2"><cite title="HTTP/1.1, part 7: Authentication">[Part7]</cite></a>) to satisfy any subsequent request unless a cache directive that allows such responses to be stored is present in the response.
     1036            </p>
     1037            <p id="rfc.section.2.6.p.2">In this specification, the following Cache-Control response directives (<a href="#cache-response-directive" title="Response Cache-Control Directives">Section&nbsp;3.2.2</a>) have such an effect: must-revalidate, public, s-maxage.
     1038            </p>
     1039            <p id="rfc.section.2.6.p.3">Note that cached responses that contain the "must-revalidate" and/or "s-maxage" response directives are not allowed to be
     1040               served stale (<a href="#serving.stale.responses" title="Serving Stale Responses">Section&nbsp;2.3.3</a>) by shared caches. In particular, a response with either "max-age=0, must-revalidate" or "s-maxage=0" cannot be used to satisfy
     1041               a subsequent request without revalidating it on the origin server.
     1042            </p>
     1043         </div>
     1044         <div id="caching.negotiated.responses">
     1045            <h2 id="rfc.section.2.7"><a href="#rfc.section.2.7">2.7</a>&nbsp;<a href="#caching.negotiated.responses">Caching Negotiated Responses</a></h2>
     1046            <p id="rfc.section.2.7.p.1">When a cache receives a request that can be satisfied by a stored response that has a Vary header field (<a href="#header.vary" id="rfc.xref.header.vary.1" title="Vary">Section&nbsp;3.5</a>), it <em class="bcp14">MUST NOT</em> use that response unless all of the selecting header fields nominated by the Vary header field match in both the original
     1047               request (i.e., that associated with the stored response), and the presented request.
     1048            </p>
     1049            <p id="rfc.section.2.7.p.2">The selecting header fields from two requests are defined to match if and only if those in the first request can be transformed
     1050               to those in the second request by applying any of the following:
     1051            </p>
     1052            <ul>
     1053               <li>adding or removing whitespace, where allowed in the header field's syntax</li>
     1054               <li>combining multiple header fields with the same field name (see <a href="p1-messaging.html#header.fields" title="Header Fields">Section 3.2</a> of <a href="#Part1" id="rfc.xref.Part1.16"><cite title="HTTP/1.1, part 1: URIs, Connections, and Message Parsing">[Part1]</cite></a>)
     1055               </li>
     1056               <li>normalizing both header field values in a way that is known to have identical semantics, according to the header field's specification
     1057                  (e.g., re-ordering field values when order is not significant; case-normalization, where values are defined to be case-insensitive)
     1058               </li>
     1059            </ul>
     1060            <p id="rfc.section.2.7.p.3">If (after any normalization that might take place) a header field is absent from a request, it can only match another request
     1061               if it is also absent there.
     1062            </p>
     1063            <p id="rfc.section.2.7.p.4">A Vary header field-value of "*" always fails to match, and subsequent requests to that resource can only be properly interpreted
     1064               by the origin server.
     1065            </p>
     1066            <p id="rfc.section.2.7.p.5">The stored response with matching selecting header fields is known as the selected response.</p>
     1067            <p id="rfc.section.2.7.p.6">If multiple selected responses are available, the most recent response (as determined by the Date header field) is used; see <a href="#constructing.responses.from.caches" title="Constructing Responses from Caches">Section&nbsp;2.2</a>.
     1068            </p>
     1069            <p id="rfc.section.2.7.p.7">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>.
     1070            </p>
     1071         </div>
     1072         <div id="combining.responses">
     1073            <h2 id="rfc.section.2.8"><a href="#rfc.section.2.8">2.8</a>&nbsp;<a href="#combining.responses">Combining Responses</a></h2>
     1074            <p id="rfc.section.2.8.p.1">When a cache receives a 304 (Not Modified) response or a 206 (Partial Content) response (in this section, the "new" response"),
     1075               it needs to create an updated response by combining the stored response with the new one, so that the updated response can
     1076               be used to satisfy the request, and potentially update the cached response.
     1077            </p>
     1078            <p id="rfc.section.2.8.p.2">If the new response contains an ETag, it identifies the stored response to use. <span class="comment" id="TODO-mention-CL">[<a href="#TODO-mention-CL" class="smpl">TODO-mention-CL</a>: might need language about Content-Location here]</span><span class="comment" id="TODO-select-for-combine">[<a href="#TODO-select-for-combine" class="smpl">TODO-select-for-combine</a>: Shouldn't this be the selected response?]</span>
     1079            </p>
     1080            <p id="rfc.section.2.8.p.3">When the new response's status code is 206 (partial content), a cache <em class="bcp14">MUST NOT</em> combine it with the old response if either response does not have a validator, and <em class="bcp14">MUST NOT</em> combine it with the old response when those validators do not match with the strong comparison function (see <a href="p4-conditional.html#weak.and.strong.validators" title="Weak versus Strong">Section 2.2.2</a> of <a href="#Part4" id="rfc.xref.Part4.3"><cite title="HTTP/1.1, part 4: Conditional Requests">[Part4]</cite></a>).
     1081            </p>
     1082            <p id="rfc.section.2.8.p.4">The stored response header fields are used as those of the updated response, except that </p>
     1083            <ul>
     1084               <li>a cache <em class="bcp14">MUST</em> delete any stored Warning header fields with warn-code 1xx (see <a href="#header.warning" id="rfc.xref.header.warning.2" title="Warning">Section&nbsp;3.6</a>).
     1085               </li>
     1086               <li>a cache <em class="bcp14">MUST</em> retain any stored Warning header fields with warn-code 2xx.
     1087               </li>
     1088               <li>a cache <em class="bcp14">MUST</em> use other header fields provided in the new response to replace all instances of the corresponding header fields from the
     1089                  stored response.
     1090               </li>
     1091            </ul>
     1092            <p id="rfc.section.2.8.p.5">A cache <em class="bcp14">MUST</em> use the updated response header fields to replace those of the stored response (unless the stored response is removed). In
     1093               the case of a 206 response, a cache <em class="bcp14">MAY</em> store the combined representation.
     1094            </p>
     1095         </div>
     1096      </div>
     1097      <div id="header.fields">
     1098         <h1 id="rfc.section.3"><a href="#rfc.section.3">3.</a>&nbsp;<a href="#header.fields">Header Field Definitions</a></h1>
     1099         <p id="rfc.section.3.p.1">This section defines the syntax and semantics of HTTP/1.1 header fields related to caching.</p>
     1100         <div id="header.age">
     1101            <div id="rfc.iref.a.2"></div>
     1102            <div id="rfc.iref.h.2"></div>
     1103            <h2 id="rfc.section.3.1"><a href="#rfc.section.3.1">3.1</a>&nbsp;<a href="#header.age">Age</a></h2>
     1104            <p id="rfc.section.3.1.p.1">The "Age" header field conveys the sender's estimate of the amount of time since the response was generated or successfully
     1105               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>.
     1106            </p>
     1107            <div id="rfc.figure.u.8"></div><pre class="inline"><span id="rfc.iref.g.2"></span>  <a href="#header.age" class="smpl">Age</a> = <a href="#delta-seconds" class="smpl">delta-seconds</a>
    10581108</pre><p id="rfc.section.3.1.p.3">Age field-values are non-negative integers, representing time in seconds (see <a href="#delta-seconds" title="Delta Seconds">Section&nbsp;1.5</a>).
    1059       </p>
    1060       <p id="rfc.section.3.1.p.4">The presence of an Age header field in a response implies that a response is not first-hand. However, the converse is not
    1061          true, since HTTP/1.0 caches might not implement the Age header field.
    1062       </p>
    1063       <div id="rfc.iref.c.4"></div>
    1064       <div id="rfc.iref.h.3"></div>
    1065       <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>
    1066       <p id="rfc.section.3.2.p.1">The "Cache-Control" header field is used to specify directives for caches along the request/response chain. Such cache directives
    1067          are unidirectional in that the presence of a directive in a request does not imply that the same directive is to be given
    1068          in the response.
    1069       </p>
    1070       <p id="rfc.section.3.2.p.2">A cache <em class="bcp14">MUST</em> obey the requirements of the Cache-Control directives defined in this section. See <a href="#cache.control.extensions" title="Cache Control Extensions">Section&nbsp;3.2.3</a> for information about how Cache-Control directives defined elsewhere are handled.
    1071       </p>
    1072       <div class="note" id="rfc.section.3.2.p.3">
    1073          <p> <b>Note:</b> HTTP/1.0 caches might not implement Cache-Control and might only implement Pragma: no-cache (see <a href="#header.pragma" id="rfc.xref.header.pragma.2" title="Pragma">Section&nbsp;3.4</a>).
    1074          </p>
    1075       </div>
    1076       <p id="rfc.section.3.2.p.4">A proxy, whether or not it implements a cache, <em class="bcp14">MUST</em> pass cache directives through in forwarded messages, regardless of their significance to that application, since the directives
    1077          might be applicable to all recipients along the request/response chain. It is not possible to target a directive to a specific
    1078          cache.
    1079       </p>
    1080       <div id="rfc.figure.u.9"></div><pre class="inline"><span id="rfc.iref.g.3"></span><span id="rfc.iref.g.4"></span>  <a href="#header.cache-control" class="smpl">Cache-Control</a>   = 1#<a href="#header.cache-control" class="smpl">cache-directive</a>
     1109            </p>
     1110            <p id="rfc.section.3.1.p.4">The presence of an Age header field in a response implies that a response is not first-hand. However, the converse is not
     1111               true, since HTTP/1.0 caches might not implement the Age header field.
     1112            </p>
     1113         </div>
     1114         <div id="header.cache-control">
     1115            <div id="rfc.iref.c.4"></div>
     1116            <div id="rfc.iref.h.3"></div>
     1117            <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>
     1118            <p id="rfc.section.3.2.p.1">The "Cache-Control" header field is used to specify directives for caches along the request/response chain. Such cache directives
     1119               are unidirectional in that the presence of a directive in a request does not imply that the same directive is to be given
     1120               in the response.
     1121            </p>
     1122            <p id="rfc.section.3.2.p.2">A cache <em class="bcp14">MUST</em> obey the requirements of the Cache-Control directives defined in this section. See <a href="#cache.control.extensions" title="Cache Control Extensions">Section&nbsp;3.2.3</a> for information about how Cache-Control directives defined elsewhere are handled.
     1123            </p>
     1124            <div class="note" id="rfc.section.3.2.p.3">
     1125               <p><b>Note:</b> HTTP/1.0 caches might not implement Cache-Control and might only implement Pragma: no-cache (see <a href="#header.pragma" id="rfc.xref.header.pragma.2" title="Pragma">Section&nbsp;3.4</a>).
     1126               </p>
     1127            </div>
     1128            <p id="rfc.section.3.2.p.4">A proxy, whether or not it implements a cache, <em class="bcp14">MUST</em> pass cache directives through in forwarded messages, regardless of their significance to that application, since the directives
     1129               might be applicable to all recipients along the request/response chain. It is not possible to target a directive to a specific
     1130               cache.
     1131            </p>
     1132            <div id="rfc.figure.u.9"></div><pre class="inline"><span id="rfc.iref.g.3"></span><span id="rfc.iref.g.4"></span>  <a href="#header.cache-control" class="smpl">Cache-Control</a>   = 1#<a href="#header.cache-control" class="smpl">cache-directive</a>
    10811133
    10821134  <a href="#header.cache-control" class="smpl">cache-directive</a> = <a href="#header.cache-control" class="smpl">cache-request-directive</a>
     
    10841136
    10851137  <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> ) ]
    1086 </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>
    1087       <div id="rfc.figure.u.10"></div><pre class="inline"><span id="rfc.iref.g.5"></span>  <a href="#header.cache-control" class="smpl">cache-request-directive</a> =
     1138</pre><div id="cache-request-directive">
     1139               <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>
     1140               <div id="rfc.figure.u.10"></div><pre class="inline"><span id="rfc.iref.g.5"></span>  <a href="#header.cache-control" class="smpl">cache-request-directive</a> =
    10881141       "no-cache"
    10891142     / "no-store"
     
    10941147     / "only-if-cached"
    10951148     / <a href="#header.cache-control" class="smpl">cache-extension</a>
    1096 </pre><p id="rfc.section.3.2.1.p.2"> <dfn>no-cache</dfn>  <span id="rfc.iref.c.5"></span>  <span id="rfc.iref.n.1"></span> 
    1097       </p>
    1098       <ul class="empty">
    1099          <li>The no-cache request directive indicates that a cache <em class="bcp14">MUST NOT</em> use a stored response to satisfy the request without successful validation on the origin server.
    1100          </li>
    1101       </ul>
    1102       <p id="rfc.section.3.2.1.p.3"> <dfn>no-store</dfn>  <span id="rfc.iref.c.6"></span>  <span id="rfc.iref.n.2"></span> 
    1103       </p>
    1104       <ul class="empty">
    1105          <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 private and shared caches. "<em class="bcp14">MUST NOT</em> store" in this context means that the cache <em class="bcp14">MUST NOT</em> intentionally store the information in non-volatile storage, and <em class="bcp14">MUST</em> make a best-effort attempt to remove the information from volatile storage as promptly as possible after forwarding it.
    1106          </li>
    1107          <li>This directive is NOT a reliable or sufficient mechanism for ensuring privacy. In particular, malicious or compromised caches
    1108             might not recognize or obey this directive, and communications networks might be vulnerable to eavesdropping.
    1109          </li>
    1110          <li>Note that if a request containing this directive is satisfied from a cache, the no-store request directive does not apply
    1111             to the already stored response.
    1112          </li>
    1113       </ul>
    1114       <p id="rfc.section.3.2.1.p.4"> <dfn>max-age</dfn>  <span id="rfc.iref.c.7"></span>  <span id="rfc.iref.m.1"></span> 
    1115       </p>
    1116       <ul class="empty">
    1117          <li>The max-age request directive indicates that the client is unwilling to accept a response whose age is greater than the specified
    1118             number of seconds. Unless the max-stale request directive is also present, the client is not willing to accept a stale response.
    1119          </li>
    1120       </ul>
    1121       <p id="rfc.section.3.2.1.p.5"> <dfn>max-stale</dfn>  <span id="rfc.iref.c.8"></span>  <span id="rfc.iref.m.2"></span> 
    1122       </p>
    1123       <ul class="empty">
    1124          <li>The max-stale request directive indicates that the client is willing to accept a response that has exceeded its expiration
    1125             time. If max-stale is assigned a value, then the client is willing to accept a response that has exceeded its expiration time
    1126             by no more than the specified number of seconds. If no value is assigned to max-stale, then the client is willing to accept
    1127             a stale response of any age.
    1128          </li>
    1129       </ul>
    1130       <p id="rfc.section.3.2.1.p.6"> <dfn>min-fresh</dfn>  <span id="rfc.iref.c.9"></span>  <span id="rfc.iref.m.3"></span> 
    1131       </p>
    1132       <ul class="empty">
    1133          <li>The min-fresh request directive indicates that the client is willing to accept a response whose freshness lifetime is no less
    1134             than its current age plus the specified time in seconds. That is, the client wants a response that will still be fresh for
    1135             at least the specified number of seconds.
    1136          </li>
    1137       </ul>
    1138       <p id="rfc.section.3.2.1.p.7"> <dfn>no-transform</dfn>  <span id="rfc.iref.c.10"></span>  <span id="rfc.iref.n.3"></span> 
    1139       </p>
    1140       <ul class="empty">
    1141          <li>The no-transform request directive indicates that an intermediary (whether or not it implements a cache) <em class="bcp14">MUST NOT</em> change the Content-Encoding, Content-Range or Content-Type request header fields, nor the request representation.
    1142          </li>
    1143       </ul>
    1144       <p id="rfc.section.3.2.1.p.8"> <dfn>only-if-cached</dfn>  <span id="rfc.iref.c.11"></span>  <span id="rfc.iref.o.1"></span> 
    1145       </p>
    1146       <ul class="empty">
    1147          <li>The only-if-cached request directive indicates that the client only wishes to obtain a stored response. If it receives this
    1148             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
    1149             (Gateway Timeout) status code. If a group of caches is being operated as a unified system with good internal connectivity,
    1150             a member cache <em class="bcp14">MAY</em> forward such a request within that group of caches.
    1151          </li>
    1152       </ul>
    1153       <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>
    1154       <div id="rfc.figure.u.11"></div><pre class="inline"><span id="rfc.iref.g.6"></span>  <a href="#header.cache-control" class="smpl">cache-response-directive</a> =
     1149</pre><p id="rfc.section.3.2.1.p.2"><dfn>no-cache</dfn> <span id="rfc.iref.c.5"></span> <span id="rfc.iref.n.1"></span>
     1150               </p>
     1151               <ul class="empty">
     1152                  <li>The no-cache request directive indicates that a cache <em class="bcp14">MUST NOT</em> use a stored response to satisfy the request without successful validation on the origin server.
     1153                  </li>
     1154               </ul>
     1155               <p id="rfc.section.3.2.1.p.3"><dfn>no-store</dfn> <span id="rfc.iref.c.6"></span> <span id="rfc.iref.n.2"></span>
     1156               </p>
     1157               <ul class="empty">
     1158                  <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 private and shared caches. "<em class="bcp14">MUST NOT</em> store" in this context means that the cache <em class="bcp14">MUST NOT</em> intentionally store the information in non-volatile storage, and <em class="bcp14">MUST</em> make a best-effort attempt to remove the information from volatile storage as promptly as possible after forwarding it.
     1159                  </li>
     1160                  <li>This directive is NOT a reliable or sufficient mechanism for ensuring privacy. In particular, malicious or compromised caches
     1161                     might not recognize or obey this directive, and communications networks might be vulnerable to eavesdropping.
     1162                  </li>
     1163                  <li>Note that if a request containing this directive is satisfied from a cache, the no-store request directive does not apply
     1164                     to the already stored response.
     1165                  </li>
     1166               </ul>
     1167               <p id="rfc.section.3.2.1.p.4"><dfn>max-age</dfn> <span id="rfc.iref.c.7"></span> <span id="rfc.iref.m.1"></span>
     1168               </p>
     1169               <ul class="empty">
     1170                  <li>The max-age request directive indicates that the client is unwilling to accept a response whose age is greater than the specified
     1171                     number of seconds. Unless the max-stale request directive is also present, the client is not willing to accept a stale response.
     1172                  </li>
     1173               </ul>
     1174               <p id="rfc.section.3.2.1.p.5"><dfn>max-stale</dfn> <span id="rfc.iref.c.8"></span> <span id="rfc.iref.m.2"></span>
     1175               </p>
     1176               <ul class="empty">
     1177                  <li>The max-stale request directive indicates that the client is willing to accept a response that has exceeded its expiration
     1178                     time. If max-stale is assigned a value, then the client is willing to accept a response that has exceeded its expiration time
     1179                     by no more than the specified number of seconds. If no value is assigned to max-stale, then the client is willing to accept
     1180                     a stale response of any age.
     1181                  </li>
     1182               </ul>
     1183               <p id="rfc.section.3.2.1.p.6"><dfn>min-fresh</dfn> <span id="rfc.iref.c.9"></span> <span id="rfc.iref.m.3"></span>
     1184               </p>
     1185               <ul class="empty">
     1186                  <li>The min-fresh request directive indicates that the client is willing to accept a response whose freshness lifetime is no less
     1187                     than its current age plus the specified time in seconds. That is, the client wants a response that will still be fresh for
     1188                     at least the specified number of seconds.
     1189                  </li>
     1190               </ul>
     1191               <p id="rfc.section.3.2.1.p.7"><dfn>no-transform</dfn> <span id="rfc.iref.c.10"></span> <span id="rfc.iref.n.3"></span>
     1192               </p>
     1193               <ul class="empty">
     1194                  <li>The no-transform request directive indicates that an intermediary (whether or not it implements a cache) <em class="bcp14">MUST NOT</em> change the Content-Encoding, Content-Range or Content-Type request header fields, nor the request representation.
     1195                  </li>
     1196               </ul>
     1197               <p id="rfc.section.3.2.1.p.8"><dfn>only-if-cached</dfn> <span id="rfc.iref.c.11"></span> <span id="rfc.iref.o.1"></span>
     1198               </p>
     1199               <ul class="empty">
     1200                  <li>The only-if-cached request directive indicates that the client only wishes to obtain a stored response. If it receives this
     1201                     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
     1202                     (Gateway Timeout) status code. If a group of caches is being operated as a unified system with good internal connectivity,
     1203                     a member cache <em class="bcp14">MAY</em> forward such a request within that group of caches.
     1204                  </li>
     1205               </ul>
     1206            </div>
     1207            <div id="cache-response-directive">
     1208               <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>
     1209               <div id="rfc.figure.u.11"></div><pre class="inline"><span id="rfc.iref.g.6"></span>  <a href="#header.cache-control" class="smpl">cache-response-directive</a> =
    11551210       "public"
    11561211     / "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> ]
     
    11631218     / "s-maxage" "=" <a href="#delta-seconds" class="smpl">delta-seconds</a>
    11641219     / <a href="#header.cache-control" class="smpl">cache-extension</a>
    1165 </pre><p id="rfc.section.3.2.2.p.2"> <dfn>public</dfn>  <span id="rfc.iref.c.12"></span>  <span id="rfc.iref.p.2"></span> 
    1166       </p>
    1167       <ul class="empty">
    1168          <li>The public response directive indicates that a response whose associated request contains an 'Authentication' header <em class="bcp14">MAY</em> be stored (see <a href="#caching.authenticated.responses" title="Shared Caching of Authenticated Responses">Section&nbsp;2.6</a>).
    1169          </li>
    1170       </ul>
    1171       <p id="rfc.section.3.2.2.p.3"> <dfn>private</dfn>  <span id="rfc.iref.c.13"></span>  <span id="rfc.iref.p.3"></span> 
    1172       </p>
    1173       <ul class="empty">
    1174          <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 cache <em class="bcp14">MAY</em> store the response.
    1175          </li>
    1176          <li>If the private response directive specifies one or more field-names, this requirement is limited to the field-values associated
    1177             with the listed response header fields. That is, a shared cache <em class="bcp14">MUST NOT</em> store the specified field-names(s), whereas it <em class="bcp14">MAY</em> store the remainder of the response message.
    1178          </li>
    1179          <li> <b>Note:</b> This usage of the word private only controls where the response can be stored; it cannot ensure the privacy of the message
    1180             content. Also, private response directives with field-names are often handled by implementations as if an unqualified private
    1181             directive was received; i.e., the special handling for the qualified form is not widely implemented.
    1182          </li>
    1183       </ul>
    1184       <p id="rfc.section.3.2.2.p.4"> <dfn>no-cache</dfn>  <span id="rfc.iref.c.14"></span>  <span id="rfc.iref.n.4"></span> 
    1185       </p>
    1186       <ul class="empty">
    1187          <li>The no-cache response directive indicates that the response MUST NOT be used to satisfy a subsequent request without successful
    1188             validation on the origin server. This allows an origin server to prevent a cache from using it to satisfy a request without
    1189             contacting it, even by caches that have been configured to return stale responses.
    1190          </li>
    1191          <li>If the no-cache response directive specifies one or more field-names, this requirement is limited to the field-values associated
    1192             with the listed response header fields. That is, a cache <em class="bcp14">MUST NOT</em> send the specified field-name(s) in the response to a subsequent request without successful validation on the origin server.
    1193             This allows an origin server to prevent the re-use of certain header fields in a response, while still allowing caching of
    1194             the rest of the response.
    1195          </li>
    1196          <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
    1197             handled by implementations as if an unqualified no-cache directive was received; i.e., the special handling for the qualified
    1198             form is not widely implemented.
    1199          </li>
    1200       </ul>
    1201       <p id="rfc.section.3.2.2.p.5"> <dfn>no-store</dfn>  <span id="rfc.iref.c.15"></span>  <span id="rfc.iref.n.5"></span> 
    1202       </p>
    1203       <ul class="empty">
    1204          <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 private and shared caches. "<em class="bcp14">MUST NOT</em> store" in this context means that the cache <em class="bcp14">MUST NOT</em> intentionally store the information in non-volatile storage, and <em class="bcp14">MUST</em> make a best-effort attempt to remove the information from volatile storage as promptly as possible after forwarding it.
    1205          </li>
    1206          <li>This directive is NOT a reliable or sufficient mechanism for ensuring privacy. In particular, malicious or compromised caches
    1207             might not recognize or obey this directive, and communications networks might be vulnerable to eavesdropping.
    1208          </li>
    1209       </ul>
    1210       <p id="rfc.section.3.2.2.p.6"> <dfn>must-revalidate</dfn>  <span id="rfc.iref.c.16"></span>  <span id="rfc.iref.m.4"></span> 
    1211       </p>
    1212       <ul class="empty">
    1213          <li>The must-revalidate response directive indicates that once it has become stale, a cache <em class="bcp14">MUST NOT</em> use the response to satisfy subsequent requests without successful validation on the origin server.
    1214          </li>
    1215          <li>The must-revalidate directive is necessary to support reliable operation for certain protocol features. In all circumstances
    1216             a cache <em class="bcp14">MUST</em> obey the must-revalidate directive; in particular, if a cache cannot reach the origin server for any reason, it <em class="bcp14">MUST</em> generate a 504 (Gateway Timeout) response.
    1217          </li>
    1218          <li>A server <em class="bcp14">SHOULD</em> send the must-revalidate directive if and only if failure to validate a request on the representation could result in incorrect
    1219             operation, such as a silently unexecuted financial transaction.
    1220          </li>
    1221       </ul>
    1222       <p id="rfc.section.3.2.2.p.7"> <dfn>proxy-revalidate</dfn>  <span id="rfc.iref.c.17"></span>  <span id="rfc.iref.p.4"></span> 
    1223       </p>
    1224       <ul class="empty">
    1225          <li>The proxy-revalidate response directive has the same meaning as the must-revalidate response directive, except that it does
    1226             not apply to private caches.
    1227          </li>
    1228       </ul>
    1229       <p id="rfc.section.3.2.2.p.8"> <dfn>max-age</dfn>  <span id="rfc.iref.c.18"></span>  <span id="rfc.iref.m.5"></span> 
    1230       </p>
    1231       <ul class="empty">
    1232          <li>The max-age response directive indicates that the response is to be considered stale after its age is greater than the specified
    1233             number of seconds.
    1234          </li>
    1235       </ul>
    1236       <p id="rfc.section.3.2.2.p.9"> <dfn>s-maxage</dfn>  <span id="rfc.iref.c.19"></span>  <span id="rfc.iref.s.3"></span> 
    1237       </p>
    1238       <ul class="empty">
    1239          <li>The s-maxage response directive indicates that, in shared caches, the maximum age specified by this directive overrides the
    1240             maximum age specified by either the max-age directive or the Expires header field. The s-maxage directive also implies the
    1241             semantics of the proxy-revalidate response directive.
    1242          </li>
    1243       </ul>
    1244       <p id="rfc.section.3.2.2.p.10"> <dfn>no-transform</dfn>  <span id="rfc.iref.c.20"></span>  <span id="rfc.iref.n.6"></span> 
    1245       </p>
    1246       <ul class="empty">
    1247          <li>The no-transform response directive indicates that an intermediary (regardless of whether it implements a cache) <em class="bcp14">MUST NOT</em> change the Content-Encoding, Content-Range or Content-Type response header fields, nor the response representation.
    1248          </li>
    1249       </ul>
    1250       <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>
    1251       <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
    1252          value. Informational extensions (those that do not require a change in cache behavior) can be added without changing the semantics
    1253          of other directives. Behavioral extensions are designed to work by acting as modifiers to the existing base of cache directives.
    1254          Both the new directive and the standard directive are supplied, such that applications that do not understand the new directive
    1255          will default to the behavior specified by the standard directive, and those that understand the new directive will recognize
    1256          it as modifying the requirements associated with the standard directive. In this way, extensions to the cache-control directives
    1257          can be made without requiring changes to the base protocol.
    1258       </p>
    1259       <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,
    1260          obeying certain extensions, and ignoring all directives that it does not understand.
    1261       </p>
    1262       <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.
    1263          We define this new directive to mean that, in addition to any private cache, any cache that is shared only by members of the
    1264          community named within its value may cache the response. An origin server wishing to allow the UCI community to use an otherwise
    1265          private response in their shared cache(s) could do so by including
    1266       </p>
    1267       <div id="rfc.figure.u.12"></div><pre class="text">  Cache-Control: private, community="UCI"
     1220</pre><p id="rfc.section.3.2.2.p.2"><dfn>public</dfn> <span id="rfc.iref.c.12"></span> <span id="rfc.iref.p.2"></span>
     1221               </p>
     1222               <ul class="empty">
     1223                  <li>The public response directive indicates that a response whose associated request contains an 'Authentication' header <em class="bcp14">MAY</em> be stored (see <a href="#caching.authenticated.responses" title="Shared Caching of Authenticated Responses">Section&nbsp;2.6</a>).
     1224                  </li>
     1225               </ul>
     1226               <p id="rfc.section.3.2.2.p.3"><dfn>private</dfn> <span id="rfc.iref.c.13"></span> <span id="rfc.iref.p.3"></span>
     1227               </p>
     1228               <ul class="empty">
     1229                  <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 cache <em class="bcp14">MAY</em> store the response.
     1230                  </li>
     1231                  <li>If the private response directive specifies one or more field-names, this requirement is limited to the field-values associated
     1232                     with the listed response header fields. That is, a shared cache <em class="bcp14">MUST NOT</em> store the specified field-names(s), whereas it <em class="bcp14">MAY</em> store the remainder of the response message.
     1233                  </li>
     1234                  <li><b>Note:</b> This usage of the word private only controls where the response can be stored; it cannot ensure the privacy of the message
     1235                     content. Also, private response directives with field-names are often handled by implementations as if an unqualified private
     1236                     directive was received; i.e., the special handling for the qualified form is not widely implemented.
     1237                  </li>
     1238               </ul>
     1239               <p id="rfc.section.3.2.2.p.4"><dfn>no-cache</dfn> <span id="rfc.iref.c.14"></span> <span id="rfc.iref.n.4"></span>
     1240               </p>
     1241               <ul class="empty">
     1242                  <li>The no-cache response directive indicates that the response MUST NOT be used to satisfy a subsequent request without successful
     1243                     validation on the origin server. This allows an origin server to prevent a cache from using it to satisfy a request without
     1244                     contacting it, even by caches that have been configured to return stale responses.
     1245                  </li>
     1246                  <li>If the no-cache response directive specifies one or more field-names, this requirement is limited to the field-values associated
     1247                     with the listed response header fields. That is, a cache <em class="bcp14">MUST NOT</em> send the specified field-name(s) in the response to a subsequent request without successful validation on the origin server.
     1248                     This allows an origin server to prevent the re-use of certain header fields in a response, while still allowing caching of
     1249                     the rest of the response.
     1250                  </li>
     1251                  <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
     1252                     handled by implementations as if an unqualified no-cache directive was received; i.e., the special handling for the qualified
     1253                     form is not widely implemented.
     1254                  </li>
     1255               </ul>
     1256               <p id="rfc.section.3.2.2.p.5"><dfn>no-store</dfn> <span id="rfc.iref.c.15"></span> <span id="rfc.iref.n.5"></span>
     1257               </p>
     1258               <ul class="empty">
     1259                  <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 private and shared caches. "<em class="bcp14">MUST NOT</em> store" in this context means that the cache <em class="bcp14">MUST NOT</em> intentionally store the information in non-volatile storage, and <em class="bcp14">MUST</em> make a best-effort attempt to remove the information from volatile storage as promptly as possible after forwarding it.
     1260                  </li>
     1261                  <li>This directive is NOT a reliable or sufficient mechanism for ensuring privacy. In particular, malicious or compromised caches
     1262                     might not recognize or obey this directive, and communications networks might be vulnerable to eavesdropping.
     1263                  </li>
     1264               </ul>
     1265               <p id="rfc.section.3.2.2.p.6"><dfn>must-revalidate</dfn> <span id="rfc.iref.c.16"></span> <span id="rfc.iref.m.4"></span>
     1266               </p>
     1267               <ul class="empty">
     1268                  <li>The must-revalidate response directive indicates that once it has become stale, a cache <em class="bcp14">MUST NOT</em> use the response to satisfy subsequent requests without successful validation on the origin server.
     1269                  </li>
     1270                  <li>The must-revalidate directive is necessary to support reliable operation for certain protocol features. In all circumstances
     1271                     a cache <em class="bcp14">MUST</em> obey the must-revalidate directive; in particular, if a cache cannot reach the origin server for any reason, it <em class="bcp14">MUST</em> generate a 504 (Gateway Timeout) response.
     1272                  </li>
     1273                  <li>A server <em class="bcp14">SHOULD</em> send the must-revalidate directive if and only if failure to validate a request on the representation could result in incorrect
     1274                     operation, such as a silently unexecuted financial transaction.
     1275                  </li>
     1276               </ul>
     1277               <p id="rfc.section.3.2.2.p.7"><dfn>proxy-revalidate</dfn> <span id="rfc.iref.c.17"></span> <span id="rfc.iref.p.4"></span>
     1278               </p>
     1279               <ul class="empty">
     1280                  <li>The proxy-revalidate response directive has the same meaning as the must-revalidate response directive, except that it does
     1281                     not apply to private caches.
     1282                  </li>
     1283               </ul>
     1284               <p id="rfc.section.3.2.2.p.8"><dfn>max-age</dfn> <span id="rfc.iref.c.18"></span> <span id="rfc.iref.m.5"></span>
     1285               </p>
     1286               <ul class="empty">
     1287                  <li>The max-age response directive indicates that the response is to be considered stale after its age is greater than the specified
     1288                     number of seconds.
     1289                  </li>
     1290               </ul>
     1291               <p id="rfc.section.3.2.2.p.9"><dfn>s-maxage</dfn> <span id="rfc.iref.c.19"></span> <span id="rfc.iref.s.3"></span>
     1292               </p>
     1293               <ul class="empty">
     1294                  <li>The s-maxage response directive indicates that, in shared caches, the maximum age specified by this directive overrides the
     1295                     maximum age specified by either the max-age directive or the Expires header field. The s-maxage directive also implies the
     1296                     semantics of the proxy-revalidate response directive.
     1297                  </li>
     1298               </ul>
     1299               <p id="rfc.section.3.2.2.p.10"><dfn>no-transform</dfn> <span id="rfc.iref.c.20"></span> <span id="rfc.iref.n.6"></span>
     1300               </p>
     1301               <ul class="empty">
     1302                  <li>The no-transform response directive indicates that an intermediary (regardless of whether it implements a cache) <em class="bcp14">MUST NOT</em> change the Content-Encoding, Content-Range or Content-Type response header fields, nor the response representation.
     1303                  </li>
     1304               </ul>
     1305            </div>
     1306            <div id="cache.control.extensions">
     1307               <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>
     1308               <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
     1309                  value. Informational extensions (those that do not require a change in cache behavior) can be added without changing the semantics
     1310                  of other directives. Behavioral extensions are designed to work by acting as modifiers to the existing base of cache directives.
     1311                  Both the new directive and the standard directive are supplied, such that applications that do not understand the new directive
     1312                  will default to the behavior specified by the standard directive, and those that understand the new directive will recognize
     1313                  it as modifying the requirements associated with the standard directive. In this way, extensions to the cache-control directives
     1314                  can be made without requiring changes to the base protocol.
     1315               </p>
     1316               <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,
     1317                  obeying certain extensions, and ignoring all directives that it does not understand.
     1318               </p>
     1319               <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.
     1320                  We define this new directive to mean that, in addition to any private cache, any cache that is shared only by members of the
     1321                  community named within its value may cache the response. An origin server wishing to allow the UCI community to use an otherwise
     1322                  private response in their shared cache(s) could do so by including
     1323               </p>
     1324               <div id="rfc.figure.u.12"></div><pre class="text">  Cache-Control: private, community="UCI"
    12681325</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
    1269          it will also see and understand the private directive and thus default to the safe behavior.
    1270       </p>
    1271       <p id="rfc.section.3.2.3.p.6">A cache <em class="bcp14">MUST</em> ignore unrecognized cache directives; it is assumed that any cache directive likely to be unrecognized by an HTTP/1.1 cache
    1272          will be combined with standard directives (or the response's default cacheability) such that the cache behavior will remain
    1273          minimally correct even if the cache does not understand the extension(s).
    1274       </p>
    1275       <p id="rfc.section.3.2.3.p.7">The HTTP Cache Directive Registry defines the name space for the cache directives.</p>
    1276       <p id="rfc.section.3.2.3.p.8">A registration <em class="bcp14">MUST</em> include the following fields:
    1277       </p>
    1278       <ul>
    1279          <li>Cache Directive Name</li>
    1280          <li>Pointer to specification text</li>
    1281       </ul>
    1282       <p id="rfc.section.3.2.3.p.9">Values to be added to this name space are subject to IETF review (<a href="#RFC5226" id="rfc.xref.RFC5226.1"><cite title="Guidelines for Writing an IANA Considerations Section in RFCs">[RFC5226]</cite></a>, <a href="http://tools.ietf.org/html/rfc5226#section-4.1">Section 4.1</a>).
    1283       </p>
    1284       <p id="rfc.section.3.2.3.p.10">The registry itself is maintained at &lt;<a href="http://www.iana.org/assignments/http-cache-directives">http://www.iana.org/assignments/http-cache-directives</a>&gt;.
    1285       </p>
    1286       <div id="rfc.iref.e.2"></div>
    1287       <div id="rfc.iref.h.4"></div>
    1288       <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>
    1289       <p id="rfc.section.3.3.p.1">The "Expires" header field gives the date/time after which the response is considered stale. See <a href="#expiration.model" title="Freshness Model">Section&nbsp;2.3</a> for further discussion of the freshness model.
    1290       </p>
    1291       <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
    1292          that time.
    1293       </p>
    1294       <p id="rfc.section.3.3.p.3">The field-value is an absolute date and time as defined by HTTP-date in <a href="p1-messaging.html#date.time.formats.full.date" title="Date/Time Formats: Full Date">Section 6.1</a> of <a href="#Part1" id="rfc.xref.Part1.17"><cite title="HTTP/1.1, part 1: URIs, Connections, and Message Parsing">[Part1]</cite></a>; a sender <em class="bcp14">MUST</em> use the rfc1123-date format.
    1295       </p>
    1296       <div id="rfc.figure.u.13"></div><pre class="inline"><span id="rfc.iref.g.7"></span>  <a href="#header.expires" class="smpl">Expires</a> = <a href="#abnf.dependencies" class="smpl">HTTP-date</a>
    1297 </pre><div id="rfc.figure.u.14"></div>
    1298       <p>For example</p>  <pre class="text">  Expires: Thu, 01 Dec 1994 16:00:00 GMT
    1299 </pre><div class="note" id="rfc.section.3.3.p.6">
    1300          <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.
    1301          </p>
    1302       </div>
    1303       <p id="rfc.section.3.3.p.7">A server <em class="bcp14">SHOULD NOT</em> send Expires dates more than one year in the future.
    1304       </p>
    1305       <p id="rfc.section.3.3.p.8">A cache <em class="bcp14">MUST</em> treat other invalid date formats, especially including the value "0", as in the past (i.e., "already expired").
    1306       </p>
    1307       <div id="rfc.iref.p.5"></div>
    1308       <div id="rfc.iref.h.5"></div>
    1309       <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>
    1310       <p id="rfc.section.3.4.p.1">The "Pragma" header field allows backwards compatibility with HTTP/1.0 caches, so that clients can specify a "no-cache" request
    1311          that they will understand (as Cache-Control was not defined until HTTP/1.1). When the Cache-Control header is also present
    1312          and understood in a request, Pragma is ignored.
    1313       </p>
    1314       <p id="rfc.section.3.4.p.2">In HTTP/1.0, Pragma was defined as an extensible field for implementation-specified directives for recipients. This specification
    1315          deprecates such extensions to improve interoperability.
    1316       </p>
    1317       <div id="rfc.figure.u.15"></div><pre class="inline"><span id="rfc.iref.g.8"></span><span id="rfc.iref.g.9"></span><span id="rfc.iref.g.10"></span>  <a href="#header.pragma" class="smpl">Pragma</a>           = 1#<a href="#header.pragma" class="smpl">pragma-directive</a>
     1326                  it will also see and understand the private directive and thus default to the safe behavior.
     1327               </p>
     1328               <p id="rfc.section.3.2.3.p.6">A cache <em class="bcp14">MUST</em> ignore unrecognized cache directives; it is assumed that any cache directive likely to be unrecognized by an HTTP/1.1 cache
     1329                  will be combined with standard directives (or the response's default cacheability) such that the cache behavior will remain
     1330                  minimally correct even if the cache does not understand the extension(s).
     1331               </p>
     1332               <p id="rfc.section.3.2.3.p.7">The HTTP Cache Directive Registry defines the name space for the cache directives.</p>
     1333               <p id="rfc.section.3.2.3.p.8">A registration <em class="bcp14">MUST</em> include the following fields:
     1334               </p>
     1335               <ul>
     1336                  <li>Cache Directive Name</li>
     1337                  <li>Pointer to specification text</li>
     1338               </ul>
     1339               <p id="rfc.section.3.2.3.p.9">Values to be added to this name space are subject to IETF review (<a href="#RFC5226" id="rfc.xref.RFC5226.1"><cite title="Guidelines for Writing an IANA Considerations Section in RFCs">[RFC5226]</cite></a>, <a href="https://tools.ietf.org/html/rfc5226#section-4.1">Section 4.1</a>).
     1340               </p>
     1341               <p id="rfc.section.3.2.3.p.10">The registry itself is maintained at &lt;<a href="http://www.iana.org/assignments/http-cache-directives">http://www.iana.org/assignments/http-cache-directives</a>&gt;.
     1342               </p>
     1343            </div>
     1344         </div>
     1345         <div id="header.expires">
     1346            <div id="rfc.iref.e.2"></div>
     1347            <div id="rfc.iref.h.4"></div>
     1348            <h2 id="rfc.section.3.3"><a href="#rfc.section.3.3">3.3</a>&nbsp;<a href="#header.expires">Expires</a></h2>
     1349            <p id="rfc.section.3.3.p.1">The "Expires" header field gives the date/time after which the response is considered stale. See <a href="#expiration.model" title="Freshness Model">Section&nbsp;2.3</a> for further discussion of the freshness model.
     1350            </p>
     1351            <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
     1352               that time.
     1353            </p>
     1354            <p id="rfc.section.3.3.p.3">The field-value is an absolute date and time as defined by HTTP-date in <a href="p1-messaging.html#date.time.formats.full.date" title="Date/Time Formats: Full Date">Section 6.1</a> of <a href="#Part1" id="rfc.xref.Part1.17"><cite title="HTTP/1.1, part 1: URIs, Connections, and Message Parsing">[Part1]</cite></a>; a sender <em class="bcp14">MUST</em> use the rfc1123-date format.
     1355            </p>
     1356            <div id="rfc.figure.u.13"></div><pre class="inline"><span id="rfc.iref.g.7"></span>  <a href="#header.expires" class="smpl">Expires</a> = <a href="#abnf.dependencies" class="smpl">HTTP-date</a>
     1357</pre><div id="rfc.figure.u.14"></div>
     1358            <p>For example</p><pre class="text">  Expires: Thu, 01 Dec 1994 16:00:00 GMT
     1359</pre><div class="note" id="rfc.section.3.3.p.6">
     1360               <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.
     1361               </p>
     1362            </div>
     1363            <p id="rfc.section.3.3.p.7">A server <em class="bcp14">SHOULD NOT</em> send Expires dates more than one year in the future.
     1364            </p>
     1365            <p id="rfc.section.3.3.p.8">A cache <em class="bcp14">MUST</em> treat other invalid date formats, especially including the value "0", as in the past (i.e., "already expired").
     1366            </p>
     1367         </div>
     1368         <div id="header.pragma">
     1369            <div id="rfc.iref.p.5"></div>
     1370            <div id="rfc.iref.h.5"></div>
     1371            <h2 id="rfc.section.3.4"><a href="#rfc.section.3.4">3.4</a>&nbsp;<a href="#header.pragma">Pragma</a></h2>
     1372            <p id="rfc.section.3.4.p.1">The "Pragma" header field allows backwards compatibility with HTTP/1.0 caches, so that clients can specify a "no-cache" request
     1373               that they will understand (as Cache-Control was not defined until HTTP/1.1). When the Cache-Control header is also present
     1374               and understood in a request, Pragma is ignored.
     1375            </p>
     1376            <p id="rfc.section.3.4.p.2">In HTTP/1.0, Pragma was defined as an extensible field for implementation-specified directives for recipients. This specification
     1377               deprecates such extensions to improve interoperability.
     1378            </p>
     1379            <div id="rfc.figure.u.15"></div><pre class="inline"><span id="rfc.iref.g.8"></span><span id="rfc.iref.g.9"></span><span id="rfc.iref.g.10"></span>  <a href="#header.pragma" class="smpl">Pragma</a>           = 1#<a href="#header.pragma" class="smpl">pragma-directive</a>
    13181380  <a href="#header.pragma" class="smpl">pragma-directive</a> = "no-cache" / <a href="#header.pragma" class="smpl">extension-pragma</a>
    13191381  <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> ) ]
    13201382</pre><p id="rfc.section.3.4.p.4">When the Cache-Control header is not present in a request, the no-cache request pragma-directive <em class="bcp14">MUST</em> have the same effect on caches as if "Cache-Control: no-cache" were present (see <a href="#cache-request-directive" title="Request Cache-Control Directives">Section&nbsp;3.2.1</a>).
    1321       </p>
    1322       <p id="rfc.section.3.4.p.5">When sending a no-cache request, a client <em class="bcp14">SHOULD</em> include both pragma and cache-control directives unless Cache-Control: no-cache is purposefully omitted to target other Cache-Control
    1323          response directives at HTTP/1.1 caches. For example:
    1324       </p>
    1325       <div id="rfc.figure.u.16"></div> <pre class="text">GET / HTTP/1.1
     1383            </p>
     1384            <p id="rfc.section.3.4.p.5">When sending a no-cache request, a client <em class="bcp14">SHOULD</em> include both pragma and cache-control directives unless Cache-Control: no-cache is purposefully omitted to target other Cache-Control
     1385               response directives at HTTP/1.1 caches. For example:
     1386            </p>
     1387            <div id="rfc.figure.u.16"></div><pre class="text">GET / HTTP/1.1
    13261388Host: www.example.com
    13271389Cache-Control: max-age=30
    13281390Pragma: no-cache
    13291391
    1330 </pre> <p id="rfc.section.3.4.p.7">will constrain HTTP/1.1 caches to serve a response no older than 30 seconds, while precluding implementations that do not
    1331          understand Cache-Control from serving a cached response.
    1332       </p>
    1333       <div class="note" id="rfc.section.3.4.p.8">
    1334          <p> <b>Note:</b> Because the meaning of "Pragma: no-cache" in responses is not specified, it does not provide a reliable replacement for "Cache-Control:
    1335             no-cache" in them.
    1336          </p>
    1337       </div>
    1338       <div id="rfc.iref.v.2"></div>
    1339       <div id="rfc.iref.h.6"></div>
    1340       <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>
    1341       <p id="rfc.section.3.5.p.1">The "Vary" header field conveys the set of header fields that were used to select the representation.</p>
    1342       <p id="rfc.section.3.5.p.2">Caches use this information, in part, to determine whether a stored response can be used to satisfy a given request; see <a href="#caching.negotiated.responses" title="Caching Negotiated Responses">Section&nbsp;2.7</a>. determines, while the response is fresh, whether a cache is permitted to use the response to reply to a subsequent request
    1343          without validation; see <a href="#caching.negotiated.responses" title="Caching Negotiated Responses">Section&nbsp;2.7</a>.
    1344       </p>
    1345       <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
    1346          the representation.
    1347       </p>
    1348       <div id="rfc.figure.u.17"></div><pre class="inline"><span id="rfc.iref.g.11"></span>  <a href="#header.vary" class="smpl">Vary</a> = "*" / 1#<a href="#abnf.dependencies" class="smpl">field-name</a>
     1392</pre><p id="rfc.section.3.4.p.7">will constrain HTTP/1.1 caches to serve a response no older than 30 seconds, while precluding implementations that do not
     1393               understand Cache-Control from serving a cached response.
     1394            </p>
     1395            <div class="note" id="rfc.section.3.4.p.8">
     1396               <p><b>Note:</b> Because the meaning of "Pragma: no-cache" in responses is not specified, it does not provide a reliable replacement for "Cache-Control:
     1397                  no-cache" in them.
     1398               </p>
     1399            </div>
     1400         </div>
     1401         <div id="header.vary">
     1402            <div id="rfc.iref.v.2"></div>
     1403            <div id="rfc.iref.h.6"></div>
     1404            <h2 id="rfc.section.3.5"><a href="#rfc.section.3.5">3.5</a>&nbsp;<a href="#header.vary">Vary</a></h2>
     1405            <p id="rfc.section.3.5.p.1">The "Vary" header field conveys the set of header fields that were used to select the representation.</p>
     1406            <p id="rfc.section.3.5.p.2">Caches use this information, in part, to determine whether a stored response can be used to satisfy a given request; see <a href="#caching.negotiated.responses" title="Caching Negotiated Responses">Section&nbsp;2.7</a>. determines, while the response is fresh, whether a cache is permitted to use the response to reply to a subsequent request
     1407               without validation; see <a href="#caching.negotiated.responses" title="Caching Negotiated Responses">Section&nbsp;2.7</a>.
     1408            </p>
     1409            <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
     1410               the representation.
     1411            </p>
     1412            <div id="rfc.figure.u.17"></div><pre class="inline"><span id="rfc.iref.g.11"></span>  <a href="#header.vary" class="smpl">Vary</a> = "*" / 1#<a href="#abnf.dependencies" class="smpl">field-name</a>
    13491413</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 header fields.</p>
    1350       <p id="rfc.section.3.5.p.6">A server <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
    1351          to properly interpret future requests on that resource and informs the user agent about the presence of negotiation on that
    1352          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
    1353          the user agent with useful information about the dimensions over which the response varies at the time of the response.
    1354       </p>
    1355       <p id="rfc.section.3.5.p.7">A Vary field value of "*" signals that unspecified parameters not limited to the header fields (e.g., the network address
    1356          of the client), play a role in the selection of the response representation; therefore, a cache cannot determine whether this
    1357          response is appropriate. A proxy <em class="bcp14">MUST NOT</em> generate the "*" value.
    1358       </p>
    1359       <p id="rfc.section.3.5.p.8">The field-names given are not limited to the set of standard header fields defined by this specification. Field names are
    1360          case-insensitive.
    1361       </p>
    1362       <div id="rfc.iref.w.1"></div>
    1363       <div id="rfc.iref.h.7"></div>
    1364       <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>
    1365       <p id="rfc.section.3.6.p.1">The "Warning" header field is used to carry additional information about the status or transformation of a message that might
    1366          not be reflected in the message. This information is typically used to warn about possible incorrectness introduced by caching
    1367          operations or transformations applied to the payload of the message.
    1368       </p>
    1369       <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
    1370          code, distinguishes these responses from true failures.
    1371       </p>
    1372       <p id="rfc.section.3.6.p.3">Warning header fields can in general be applied to any message, however some warn-codes are specific to caches and can only
    1373          be applied to response messages.
    1374       </p>
    1375       <div id="rfc.figure.u.18"></div><pre class="inline"><span id="rfc.iref.g.12"></span><span id="rfc.iref.g.13"></span><span id="rfc.iref.g.14"></span><span id="rfc.iref.g.15"></span><span id="rfc.iref.g.16"></span><span id="rfc.iref.g.17"></span>  <a href="#header.warning" class="smpl">Warning</a>       = 1#<a href="#header.warning" class="smpl">warning-value</a>
     1414            <p id="rfc.section.3.5.p.6">A server <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
     1415               to properly interpret future requests on that resource and informs the user agent about the presence of negotiation on that
     1416               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
     1417               the user agent with useful information about the dimensions over which the response varies at the time of the response.
     1418            </p>
     1419            <p id="rfc.section.3.5.p.7">A Vary field value of "*" signals that unspecified parameters not limited to the header fields (e.g., the network address
     1420               of the client), play a role in the selection of the response representation; therefore, a cache cannot determine whether this
     1421               response is appropriate. A proxy <em class="bcp14">MUST NOT</em> generate the "*" value.
     1422            </p>
     1423            <p id="rfc.section.3.5.p.8">The field-names given are not limited to the set of standard header fields defined by this specification. Field names are
     1424               case-insensitive.
     1425            </p>
     1426         </div>
     1427         <div id="header.warning">
     1428            <div id="rfc.iref.w.1"></div>
     1429            <div id="rfc.iref.h.7"></div>
     1430            <h2 id="rfc.section.3.6"><a href="#rfc.section.3.6">3.6</a>&nbsp;<a href="#header.warning">Warning</a></h2>
     1431            <p id="rfc.section.3.6.p.1">The "Warning" header field is used to carry additional information about the status or transformation of a message that might
     1432               not be reflected in the message. This information is typically used to warn about possible incorrectness introduced by caching
     1433               operations or transformations applied to the payload of the message.
     1434            </p>
     1435            <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
     1436               code, distinguishes these responses from true failures.
     1437            </p>
     1438            <p id="rfc.section.3.6.p.3">Warning header fields can in general be applied to any message, however some warn-codes are specific to caches and can only
     1439               be applied to response messages.
     1440            </p>
     1441            <div id="rfc.figure.u.18"></div><pre class="inline"><span id="rfc.iref.g.12"></span><span id="rfc.iref.g.13"></span><span id="rfc.iref.g.14"></span><span id="rfc.iref.g.15"></span><span id="rfc.iref.g.16"></span><span id="rfc.iref.g.17"></span>  <a href="#header.warning" class="smpl">Warning</a>       = 1#<a href="#header.warning" class="smpl">warning-value</a>
    13761442 
    13771443  <a href="#header.warning" class="smpl">warning-value</a> = <a href="#header.warning" class="smpl">warn-code</a> <a href="#notation" class="smpl">SP</a> <a href="#header.warning" class="smpl">warn-agent</a> <a href="#notation" class="smpl">SP</a> <a href="#header.warning" class="smpl">warn-text</a>
     
    13851451  <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>
    13861452</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
    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 header fields <em class="bcp14">SHOULD</em> order them with this user agent behavior in mind. New Warning header fields <em class="bcp14">SHOULD</em> be added after any existing Warning headers fields.
    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 a cache after validation. They can only be generated by a cache when validating a cached entry, and <em class="bcp14">MUST NOT</em> be generated in any other situation.
    1398          </li>
    1399          <li>2xx Warnings describe some aspect of the representation that is not rectified by a validation (for example, a lossy compression
    1400             of the representation) and <em class="bcp14">MUST NOT</em> be deleted by a cache 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 header fields to a receiver whose version is HTTP/1.0 or lower,
    1404          then the sender <em class="bcp14">MUST</em> include in each warning-value a warn-date that matches the Date header field in the message.
    1405       </p>
    1406       <p id="rfc.section.3.6.p.10">If a system receives a message with a warning-value that includes a warn-date, and that warn-date is different from the Date
    1407          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 field <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>A cache <em class="bcp14">SHOULD</em> include this 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>A cache <em class="bcp14">SHOULD</em> include this when returning a stale response because an attempt to validate the response failed, due to an inability to reach
    1421             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>A cache <em class="bcp14">SHOULD</em> b include this if it 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>A cache <em class="bcp14">SHOULD</em> include this if it heuristically chose a freshness lifetime greater than 24 hours and the response's age is greater than 24
    1432             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 a proxy if it applies any transformation to the representation, such as changing the content-coding, media-type,
    1443             or modifying the representation data, unless this Warning code already appears in the response.
    1444          </li>
    1445       </ul>
    1446       <p id="rfc.section.3.6.p.18"> 299 Miscellaneous persistent warning </p>
    1447       <ul class="empty">
    1448          <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.
    1449          </li>
    1450       </ul>
    1451       <h1 id="rfc.section.4"><a href="#rfc.section.4">4.</a>&nbsp;<a id="history.lists" href="#history.lists">History Lists</a></h1>
    1452       <p id="rfc.section.4.p.1">User agents often have history mechanisms, such as "Back" buttons and history lists, that can be used to redisplay a representation
    1453          retrieved earlier in a session.
    1454       </p>
    1455       <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
    1456          it has expired.
    1457       </p>
    1458       <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
    1459          (e.g., Cache-Control: no-store).
    1460       </p>
    1461       <h1 id="rfc.section.5"><a href="#rfc.section.5">5.</a>&nbsp;<a id="IANA.considerations" href="#IANA.considerations">IANA Considerations</a></h1>
    1462       <h2 id="rfc.section.5.1"><a href="#rfc.section.5.1">5.1</a>&nbsp;<a id="cache.directive.registration" href="#cache.directive.registration">Cache Directive Registry</a></h2>
    1463       <p id="rfc.section.5.1.p.1">The registration procedure for HTTP Cache Directives is defined by <a href="#cache.control.extensions" title="Cache Control Extensions">Section&nbsp;3.2.3</a> of this document.
    1464       </p>
    1465       <p id="rfc.section.5.1.p.2">The HTTP Cache Directive Registry shall be created at &lt;<a href="http://www.iana.org/assignments/http-cache-directives">http://www.iana.org/assignments/http-cache-directives</a>&gt; and be populated with the registrations below:
    1466       </p>
    1467       <div id="rfc.table.1">
    1468          <div id="iana.cache.directive.registration.table"></div>
    1469          <table class="tt full left" cellpadding="3" cellspacing="0">
    1470             <thead>
    1471                <tr>
    1472                   <th>Cache Directive</th>
    1473                   <th>Reference</th>
    1474                </tr>
    1475             </thead>
    1476             <tbody>
    1477                <tr>
    1478                   <td class="left">max-age</td>
    1479                   <td class="left"> <a href="#cache-request-directive" title="Request Cache-Control Directives">Section&nbsp;3.2.1</a>, <a href="#cache-response-directive" title="Response Cache-Control Directives">Section&nbsp;3.2.2</a>
    1480                   </td>
    1481                </tr>
    1482                <tr>
    1483                   <td class="left">max-stale</td>
    1484                   <td class="left"> <a href="#cache-request-directive" title="Request Cache-Control Directives">Section&nbsp;3.2.1</a>
    1485                   </td>
    1486                </tr>
    1487                <tr>
    1488                   <td class="left">min-fresh</td>
    1489                   <td class="left"> <a href="#cache-request-directive" title="Request Cache-Control Directives">Section&nbsp;3.2.1</a>
    1490                   </td>
    1491                </tr>
    1492                <tr>
    1493                   <td class="left">must-revalidate</td>
    1494                   <td class="left"> <a href="#cache-response-directive" title="Response Cache-Control Directives">Section&nbsp;3.2.2</a>
    1495                   </td>
    1496                </tr>
    1497                <tr>
    1498                   <td class="left">no-cache</td>
    1499                   <td class="left"> <a href="#cache-request-directive" title="Request Cache-Control Directives">Section&nbsp;3.2.1</a>, <a href="#cache-response-directive" title="Response Cache-Control Directives">Section&nbsp;3.2.2</a>
    1500                   </td>
    1501                </tr>
    1502                <tr>
    1503                   <td class="left">no-store</td>
    1504                   <td class="left"> <a href="#cache-request-directive" title="Request Cache-Control Directives">Section&nbsp;3.2.1</a>, <a href="#cache-response-directive" title="Response Cache-Control Directives">Section&nbsp;3.2.2</a>
    1505                   </td>
    1506                </tr>
    1507                <tr>
    1508                   <td class="left">no-transform</td>
    1509                   <td class="left"> <a href="#cache-request-directive" title="Request Cache-Control Directives">Section&nbsp;3.2.1</a>, <a href="#cache-response-directive" title="Response Cache-Control Directives">Section&nbsp;3.2.2</a>
    1510                   </td>
    1511                </tr>
    1512                <tr>
    1513                   <td class="left">only-if-cached</td>
    1514                   <td class="left"> <a href="#cache-request-directive" title="Request Cache-Control Directives">Section&nbsp;3.2.1</a>
    1515                   </td>
    1516                </tr>
    1517                <tr>
    1518                   <td class="left">private</td>
    1519                   <td class="left"> <a href="#cache-response-directive" title="Response Cache-Control Directives">Section&nbsp;3.2.2</a>
    1520                   </td>
    1521                </tr>
    1522                <tr>
    1523                   <td class="left">proxy-revalidate</td>
    1524                   <td class="left"> <a href="#cache-response-directive" title="Response Cache-Control Directives">Section&nbsp;3.2.2</a>
    1525                   </td>
    1526                </tr>
    1527                <tr>
    1528                   <td class="left">public</td>
    1529                   <td class="left"> <a href="#cache-response-directive" title="Response Cache-Control Directives">Section&nbsp;3.2.2</a>
    1530                   </td>
    1531                </tr>
    1532                <tr>
    1533                   <td class="left">s-maxage</td>
    1534                   <td class="left"> <a href="#cache-response-directive" title="Response Cache-Control Directives">Section&nbsp;3.2.2</a>
    1535                   </td>
    1536                </tr>
    1537                <tr>
    1538                   <td class="left">stale-if-error</td>
    1539                   <td class="left"> <a href="#RFC5861" id="rfc.xref.RFC5861.1"><cite title="HTTP Cache-Control Extensions for Stale Content">[RFC5861]</cite></a>, <a href="http://tools.ietf.org/html/rfc5861#section-4">Section 4</a>
    1540                   </td>
    1541                </tr>
    1542                <tr>
    1543                   <td class="left">stale-while-revalidate</td>
    1544                   <td class="left"> <a href="#RFC5861" id="rfc.xref.RFC5861.2"><cite title="HTTP Cache-Control Extensions for Stale Content">[RFC5861]</cite></a>, <a href="http://tools.ietf.org/html/rfc5861#section-3">Section 3</a>
    1545                   </td>
    1546                </tr>
    1547             </tbody>
    1548          </table>
     1453               the same code number, only differing in warn-text.
     1454            </p>
     1455            <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.
     1456            </p>
     1457            <p id="rfc.section.3.6.p.7">Systems that generate multiple Warning header fields <em class="bcp14">SHOULD</em> order them with this user agent behavior in mind. New Warning header fields <em class="bcp14">SHOULD</em> be added after any existing Warning headers fields.
     1458            </p>
     1459            <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
     1460               a stored response after validation:
     1461            </p>
     1462            <ul>
     1463               <li>1xx Warnings describe the freshness or validation status of the response, and so <em class="bcp14">MUST</em> be deleted by a cache after validation. They can only be generated by a cache when validating a cached entry, and <em class="bcp14">MUST NOT</em> be generated in any other situation.
     1464               </li>
     1465               <li>2xx Warnings describe some aspect of the representation that is not rectified by a validation (for example, a lossy compression
     1466                  of the representation) and <em class="bcp14">MUST NOT</em> be deleted by a cache after validation, unless a full response is returned, in which case they <em class="bcp14">MUST</em> be.
     1467               </li>
     1468            </ul>
     1469            <p id="rfc.section.3.6.p.9">If an implementation sends a message with one or more Warning header fields to a receiver whose version is HTTP/1.0 or lower,
     1470               then the sender <em class="bcp14">MUST</em> include in each warning-value a warn-date that matches the Date header field in the message.
     1471            </p>
     1472            <p id="rfc.section.3.6.p.10">If a system receives a message with a warning-value that includes a warn-date, and that warn-date is different from the Date
     1473               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
     1474               header fields.) If all of the warning-values are deleted for this reason, the Warning header field <em class="bcp14">MUST</em> be deleted as well.
     1475            </p>
     1476            <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
     1477               of its meaning.
     1478            </p>
     1479            <p id="rfc.section.3.6.p.12"> 110 Response is stale </p>
     1480            <ul class="empty">
     1481               <li>A cache <em class="bcp14">SHOULD</em> include this whenever the returned response is stale.
     1482               </li>
     1483            </ul>
     1484            <p id="rfc.section.3.6.p.13"> 111 Revalidation failed </p>
     1485            <ul class="empty">
     1486               <li>A cache <em class="bcp14">SHOULD</em> include this when returning a stale response because an attempt to validate the response failed, due to an inability to reach
     1487                  the server.
     1488               </li>
     1489            </ul>
     1490            <p id="rfc.section.3.6.p.14"> 112 Disconnected operation </p>
     1491            <ul class="empty">
     1492               <li>A cache <em class="bcp14">SHOULD</em> b include this if it is intentionally disconnected from the rest of the network for a period of time.
     1493               </li>
     1494            </ul>
     1495            <p id="rfc.section.3.6.p.15"> 113 Heuristic expiration </p>
     1496            <ul class="empty">
     1497               <li>A cache <em class="bcp14">SHOULD</em> include this if it heuristically chose a freshness lifetime greater than 24 hours and the response's age is greater than 24
     1498                  hours.
     1499               </li>
     1500            </ul>
     1501            <p id="rfc.section.3.6.p.16"> 199 Miscellaneous warning </p>
     1502            <ul class="empty">
     1503               <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.
     1504               </li>
     1505            </ul>
     1506            <p id="rfc.section.3.6.p.17"> 214 Transformation applied </p>
     1507            <ul class="empty">
     1508               <li><em class="bcp14">MUST</em> be added by a proxy if it applies any transformation to the representation, such as changing the content-coding, media-type,
     1509                  or modifying the representation data, unless this Warning code already appears in the response.
     1510               </li>
     1511            </ul>
     1512            <p id="rfc.section.3.6.p.18"> 299 Miscellaneous persistent warning </p>
     1513            <ul class="empty">
     1514               <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.
     1515               </li>
     1516            </ul>
     1517         </div>
    15491518      </div>
    1550       <h2 id="rfc.section.5.2"><a href="#rfc.section.5.2">5.2</a>&nbsp;<a id="header.field.registration" href="#header.field.registration">Header Field Registration</a></h2>
    1551       <p id="rfc.section.5.2.p.1">The Message Header Field Registry located at &lt;<a href="http://www.iana.org/assignments/message-headers/message-header-index.html">http://www.iana.org/assignments/message-headers/message-header-index.html</a>&gt; shall be updated with the permanent registrations below (see <a href="#RFC3864" id="rfc.xref.RFC3864.1"><cite title="Registration Procedures for Message Header Fields">[RFC3864]</cite></a>):
    1552       </p>
    1553       <div id="rfc.table.2">
    1554          <div id="iana.header.registration.table"></div>
    1555          <table class="tt full left" cellpadding="3" cellspacing="0">
    1556             <thead>
    1557                <tr>
    1558                   <th>Header Field Name</th>
    1559                   <th>Protocol</th>
    1560                   <th>Status</th>
    1561                   <th>Reference</th>
    1562                </tr>
    1563             </thead>
    1564             <tbody>
    1565                <tr>
    1566                   <td class="left">Age</td>
    1567                   <td class="left">http</td>
    1568                   <td class="left">standard</td>
    1569                   <td class="left"> <a href="#header.age" id="rfc.xref.header.age.3" title="Age">Section&nbsp;3.1</a>
    1570                   </td>
    1571                </tr>
    1572                <tr>
    1573                   <td class="left">Cache-Control</td>
    1574                   <td class="left">http</td>
    1575                   <td class="left">standard</td>
    1576                   <td class="left"> <a href="#header.cache-control" id="rfc.xref.header.cache-control.3" title="Cache-Control">Section&nbsp;3.2</a>
    1577                   </td>
    1578                </tr>
    1579                <tr>
    1580                   <td class="left">Expires</td>
    1581                   <td class="left">http</td>
    1582                   <td class="left">standard</td>
    1583                   <td class="left"> <a href="#header.expires" id="rfc.xref.header.expires.4" title="Expires">Section&nbsp;3.3</a>
    1584                   </td>
    1585                </tr>
    1586                <tr>
    1587                   <td class="left">Pragma</td>
    1588                   <td class="left">http</td>
    1589                   <td class="left">standard</td>
    1590                   <td class="left"> <a href="#header.pragma" id="rfc.xref.header.pragma.3" title="Pragma">Section&nbsp;3.4</a>
    1591                   </td>
    1592                </tr>
    1593                <tr>
    1594                   <td class="left">Vary</td>
    1595                   <td class="left">http</td>
    1596                   <td class="left">standard</td>
    1597                   <td class="left"> <a href="#header.vary" id="rfc.xref.header.vary.2" title="Vary">Section&nbsp;3.5</a>
    1598                   </td>
    1599                </tr>
    1600                <tr>
    1601                   <td class="left">Warning</td>
    1602                   <td class="left">http</td>
    1603                   <td class="left">standard</td>
    1604                   <td class="left"> <a href="#header.warning" id="rfc.xref.header.warning.3" title="Warning">Section&nbsp;3.6</a>
    1605                   </td>
    1606                </tr>
    1607             </tbody>
    1608          </table>
     1519      <div id="history.lists">
     1520         <h1 id="rfc.section.4"><a href="#rfc.section.4">4.</a>&nbsp;<a href="#history.lists">History Lists</a></h1>
     1521         <p id="rfc.section.4.p.1">User agents often have history mechanisms, such as "Back" buttons and history lists, that can be used to redisplay a representation
     1522            retrieved earlier in a session.
     1523         </p>
     1524         <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
     1525            it has expired.
     1526         </p>
     1527         <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
     1528            (e.g., Cache-Control: no-store).
     1529         </p>
    16091530      </div>
    1610       <p id="rfc.section.5.2.p.2">The change controller is: "IETF (iesg@ietf.org) - Internet Engineering Task Force".</p>
    1611       <h1 id="rfc.section.6"><a href="#rfc.section.6">6.</a>&nbsp;<a id="security.considerations" href="#security.considerations">Security Considerations</a></h1>
    1612       <p id="rfc.section.6.p.1">Caches expose additional potential vulnerabilities, since the contents of the cache represent an attractive target for malicious
    1613          exploitation. Because cache contents persist after an HTTP request is complete, an attack on the cache can reveal information
    1614          long after a user believes that the information has been removed from the network. Therefore, cache contents need to be protected
    1615          as sensitive information.
    1616       </p>
    1617       <h1 id="rfc.section.7"><a href="#rfc.section.7">7.</a>&nbsp;<a id="ack" href="#ack">Acknowledgments</a></h1>
    1618       <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:
    1619          Shel Kaphan, Paul Leach, Koen Holtman, David Morris, and Larry Masinter.
    1620       </p>
     1531      <div id="IANA.considerations">
     1532         <h1 id="rfc.section.5"><a href="#rfc.section.5">5.</a>&nbsp;<a href="#IANA.considerations">IANA Considerations</a></h1>
     1533         <div id="cache.directive.registration">
     1534            <h2 id="rfc.section.5.1"><a href="#rfc.section.5.1">5.1</a>&nbsp;<a href="#cache.directive.registration">Cache Directive Registry</a></h2>
     1535            <p id="rfc.section.5.1.p.1">The registration procedure for HTTP Cache Directives is defined by <a href="#cache.control.extensions" title="Cache Control Extensions">Section&nbsp;3.2.3</a> of this document.
     1536            </p>
     1537            <p id="rfc.section.5.1.p.2">The HTTP Cache Directive Registry shall be created at &lt;<a href="http://www.iana.org/assignments/http-cache-directives">http://www.iana.org/assignments/http-cache-directives</a>&gt; and be populated with the registrations below:
     1538            </p>
     1539            <div id="rfc.table.1">
     1540               <div id="iana.cache.directive.registration.table"></div>
     1541               <table class="tt full left" cellpadding="3" cellspacing="0">
     1542                  <thead>
     1543                     <tr>
     1544                        <th>Cache Directive</th>
     1545                        <th>Reference</th>
     1546                     </tr>
     1547                  </thead>
     1548                  <tbody>
     1549                     <tr>
     1550                        <td class="left">max-age</td>
     1551                        <td class="left"><a href="#cache-request-directive" title="Request Cache-Control Directives">Section&nbsp;3.2.1</a>, <a href="#cache-response-directive" title="Response Cache-Control Directives">Section&nbsp;3.2.2</a>
     1552                        </td>
     1553                     </tr>
     1554                     <tr>
     1555                        <td class="left">max-stale</td>
     1556                        <td class="left"><a href="#cache-request-directive" title="Request Cache-Control Directives">Section&nbsp;3.2.1</a>
     1557                        </td>
     1558                     </tr>
     1559                     <tr>
     1560                        <td class="left">min-fresh</td>
     1561                        <td class="left"><a href="#cache-request-directive" title="Request Cache-Control Directives">Section&nbsp;3.2.1</a>
     1562                        </td>
     1563                     </tr>
     1564                     <tr>
     1565                        <td class="left">must-revalidate</td>
     1566                        <td class="left"><a href="#cache-response-directive" title="Response Cache-Control Directives">Section&nbsp;3.2.2</a>
     1567                        </td>
     1568                     </tr>
     1569                     <tr>
     1570                        <td class="left">no-cache</td>
     1571                        <td class="left"><a href="#cache-request-directive" title="Request Cache-Control Directives">Section&nbsp;3.2.1</a>, <a href="#cache-response-directive" title="Response Cache-Control Directives">Section&nbsp;3.2.2</a>
     1572                        </td>
     1573                     </tr>
     1574                     <tr>
     1575                        <td class="left">no-store</td>
     1576                        <td class="left"><a href="#cache-request-directive" title="Request Cache-Control Directives">Section&nbsp;3.2.1</a>, <a href="#cache-response-directive" title="Response Cache-Control Directives">Section&nbsp;3.2.2</a>
     1577                        </td>
     1578                     </tr>
     1579                     <tr>
     1580                        <td class="left">no-transform</td>
     1581                        <td class="left"><a href="#cache-request-directive" title="Request Cache-Control Directives">Section&nbsp;3.2.1</a>, <a href="#cache-response-directive" title="Response Cache-Control Directives">Section&nbsp;3.2.2</a>
     1582                        </td>
     1583                     </tr>
     1584                     <tr>
     1585                        <td class="left">only-if-cached</td>
     1586                        <td class="left"><a href="#cache-request-directive" title="Request Cache-Control Directives">Section&nbsp;3.2.1</a>
     1587                        </td>
     1588                     </tr>
     1589                     <tr>
     1590                        <td class="left">private</td>
     1591                        <td class="left"><a href="#cache-response-directive" title="Response Cache-Control Directives">Section&nbsp;3.2.2</a>
     1592                        </td>
     1593                     </tr>
     1594                     <tr>
     1595                        <td class="left">proxy-revalidate</td>
     1596                        <td class="left"><a href="#cache-response-directive" title="Response Cache-Control Directives">Section&nbsp;3.2.2</a>
     1597                        </td>
     1598                     </tr>
     1599                     <tr>
     1600                        <td class="left">public</td>
     1601                        <td class="left"><a href="#cache-response-directive" title="Response Cache-Control Directives">Section&nbsp;3.2.2</a>
     1602                        </td>
     1603                     </tr>
     1604                     <tr>
     1605                        <td class="left">s-maxage</td>
     1606                        <td class="left"><a href="#cache-response-directive" title="Response Cache-Control Directives">Section&nbsp;3.2.2</a>
     1607                        </td>
     1608                     </tr>
     1609                     <tr>
     1610                        <td class="left">stale-if-error</td>
     1611                        <td class="left"><a href="#RFC5861" id="rfc.xref.RFC5861.1"><cite title="HTTP Cache-Control Extensions for Stale Content">[RFC5861]</cite></a>, <a href="https://tools.ietf.org/html/rfc5861#section-4">Section 4</a>
     1612                        </td>
     1613                     </tr>
     1614                     <tr>
     1615                        <td class="left">stale-while-revalidate</td>
     1616                        <td class="left"><a href="#RFC5861" id="rfc.xref.RFC5861.2"><cite title="HTTP Cache-Control Extensions for Stale Content">[RFC5861]</cite></a>, <a href="https://tools.ietf.org/html/rfc5861#section-3">Section 3</a>
     1617                        </td>
     1618                     </tr>
     1619                  </tbody>
     1620               </table>
     1621            </div>
     1622         </div>
     1623         <div id="header.field.registration">
     1624            <h2 id="rfc.section.5.2"><a href="#rfc.section.5.2">5.2</a>&nbsp;<a href="#header.field.registration">Header Field Registration</a></h2>
     1625            <p id="rfc.section.5.2.p.1">The Message Header Field Registry located at &lt;<a href="http://www.iana.org/assignments/message-headers/message-header-index.html">http://www.iana.org/assignments/message-headers/message-header-index.html</a>&gt; shall be updated with the permanent registrations below (see <a href="#RFC3864" id="rfc.xref.RFC3864.1"><cite title="Registration Procedures for Message Header Fields">[RFC3864]</cite></a>):
     1626            </p>
     1627            <div id="rfc.table.2">
     1628               <div id="iana.header.registration.table"></div>
     1629               <table class="tt full left" cellpadding="3" cellspacing="0">
     1630                  <thead>
     1631                     <tr>
     1632                        <th>Header Field Name</th>
     1633                        <th>Protocol</th>
     1634                        <th>Status</th>
     1635                        <th>Reference</th>
     1636                     </tr>
     1637                  </thead>
     1638                  <tbody>
     1639                     <tr>
     1640                        <td class="left">Age</td>
     1641                        <td class="left">http</td>
     1642                        <td class="left">standard</td>
     1643                        <td class="left"><a href="#header.age" id="rfc.xref.header.age.3" title="Age">Section&nbsp;3.1</a>
     1644                        </td>
     1645                     </tr>
     1646                     <tr>
     1647                        <td class="left">Cache-Control</td>
     1648                        <td class="left">http</td>
     1649                        <td class="left">standard</td>
     1650                        <td class="left"><a href="#header.cache-control" id="rfc.xref.header.cache-control.3" title="Cache-Control">Section&nbsp;3.2</a>
     1651                        </td>
     1652                     </tr>
     1653                     <tr>
     1654                        <td class="left">Expires</td>
     1655                        <td class="left">http</td>
     1656                        <td class="left">standard</td>
     1657                        <td class="left"><a href="#header.expires" id="rfc.xref.header.expires.4" title="Expires">Section&nbsp;3.3</a>
     1658                        </td>
     1659                     </tr>
     1660                     <tr>
     1661                        <td class="left">Pragma</td>
     1662                        <td class="left">http</td>
     1663                        <td class="left">standard</td>
     1664                        <td class="left"><a href="#header.pragma" id="rfc.xref.header.pragma.3" title="Pragma">Section&nbsp;3.4</a>
     1665                        </td>
     1666                     </tr>
     1667                     <tr>
     1668                        <td class="left">Vary</td>
     1669                        <td class="left">http</td>
     1670                        <td class="left">standard</td>
     1671                        <td class="left"><a href="#header.vary" id="rfc.xref.header.vary.2" title="Vary">Section&nbsp;3.5</a>
     1672                        </td>
     1673                     </tr>
     1674                     <tr>
     1675                        <td class="left">Warning</td>
     1676                        <td class="left">http</td>
     1677                        <td class="left">standard</td>
     1678                        <td class="left"><a href="#header.warning" id="rfc.xref.header.warning.3" title="Warning">Section&nbsp;3.6</a>
     1679                        </td>
     1680                     </tr>
     1681                  </tbody>
     1682               </table>
     1683            </div>
     1684            <p id="rfc.section.5.2.p.2">The change controller is: "IETF (iesg@ietf.org) - Internet Engineering Task Force".</p>
     1685         </div>
     1686      </div>
     1687      <div id="security.considerations">
     1688         <h1 id="rfc.section.6"><a href="#rfc.section.6">6.</a>&nbsp;<a href="#security.considerations">Security Considerations</a></h1>
     1689         <p id="rfc.section.6.p.1">Caches expose additional potential vulnerabilities, since the contents of the cache represent an attractive target for malicious
     1690            exploitation. Because cache contents persist after an HTTP request is complete, an attack on the cache can reveal information
     1691            long after a user believes that the information has been removed from the network. Therefore, cache contents need to be protected
     1692            as sensitive information.
     1693         </p>
     1694      </div>
     1695      <div id="ack">
     1696         <h1 id="rfc.section.7"><a href="#rfc.section.7">7.</a>&nbsp;<a href="#ack">Acknowledgments</a></h1>
     1697         <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:
     1698            Shel Kaphan, Paul Leach, Koen Holtman, David Morris, and Larry Masinter.
     1699         </p>
     1700      </div>
    16211701      <h1 id="rfc.references"><a id="rfc.section.8" href="#rfc.section.8">8.</a> References
    16221702      </h1>
    16231703      <h2 id="rfc.references.1"><a href="#rfc.section.8.1" id="rfc.section.8.1">8.1</a> Normative References
    16241704      </h2>
    1625       <table>             
     1705      <table>
    16261706         <tr>
    16271707            <td class="reference"><b id="Part1">[Part1]</b></td>
    1628             <td class="top"><a href="mailto:fielding@gbiv.com" title="Adobe Systems Incorporated">Fielding, R., Ed.</a>, <a href="mailto:jg@freedesktop.org" title="Alcatel-Lucent Bell Labs">Gettys, J.</a>, <a href="mailto:JeffMogul@acm.org" title="Hewlett-Packard Company">Mogul, J.</a>, <a href="mailto:henrikn@microsoft.com" title="Microsoft Corporation">Frystyk, H.</a>, <a href="mailto:LMM@acm.org" title="Adobe Systems Incorporated">Masinter, L.</a>, <a href="mailto:paulle@microsoft.com" title="Microsoft Corporation">Leach, P.</a>, <a href="mailto:timbl@w3.org" title="World Wide Web Consortium">Berners-Lee, T.</a>, <a href="mailto:ylafon@w3.org" title="World Wide Web Consortium">Lafon, Y., Ed.</a>, and <a href="mailto:julian.reschke@greenbytes.de" title="greenbytes GmbH">J. Reschke, Ed.</a>, “<a href="http://tools.ietf.org/html/draft-ietf-httpbis-p1-messaging-15">HTTP/1.1, part 1: URIs, Connections, and Message Parsing</a>”, Internet-Draft&nbsp;draft-ietf-httpbis-p1-messaging-15 (work in progress), July&nbsp;2011.
     1708            <td class="top"><a href="mailto:fielding@gbiv.com" title="Adobe Systems Incorporated">Fielding, R., Ed.</a>, <a href="mailto:jg@freedesktop.org" title="Alcatel-Lucent Bell Labs">Gettys, J.</a>, <a href="mailto:JeffMogul@acm.org" title="Hewlett-Packard Company">Mogul, J.</a>, <a href="mailto:henrikn@microsoft.com" title="Microsoft Corporation">Frystyk, H.</a>, <a href="mailto:LMM@acm.org" title="Adobe Systems Incorporated">Masinter, L.</a>, <a href="mailto:paulle@microsoft.com" title="Microsoft Corporation">Leach, P.</a>, <a href="mailto:timbl@w3.org" title="World Wide Web Consortium">Berners-Lee, T.</a>, <a href="mailto:ylafon@w3.org" title="World Wide Web Consortium">Lafon, Y., Ed.</a>, and <a href="mailto:julian.reschke@greenbytes.de" title="greenbytes GmbH">J. Reschke, Ed.</a>, “<a href="https://tools.ietf.org/html/draft-ietf-httpbis-p1-messaging-15">HTTP/1.1, part 1: URIs, Connections, and Message Parsing</a>”, Internet-Draft&nbsp;draft-ietf-httpbis-p1-messaging-15 (work in progress), July&nbsp;2011.
    16291709            </td>
    16301710         </tr>
    16311711         <tr>
    16321712            <td class="reference"><b id="Part2">[Part2]</b></td>
    1633             <td class="top"><a href="mailto:fielding@gbiv.com" title="Adobe Systems Incorporated">Fielding, R., Ed.</a>, <a href="mailto:jg@freedesktop.org" title="Alcatel-Lucent Bell Labs">Gettys, J.</a>, <a href="mailto:JeffMogul@acm.org" title="Hewlett-Packard Company">Mogul, J.</a>, <a href="mailto:henrikn@microsoft.com" title="Microsoft Corporation">Frystyk, H.</a>, <a href="mailto:LMM@acm.org" title="Adobe Systems Incorporated">Masinter, L.</a>, <a href="mailto:paulle@microsoft.com" title="Microsoft Corporation">Leach, P.</a>, <a href="mailto:timbl@w3.org" title="World Wide Web Consortium">Berners-Lee, T.</a>, <a href="mailto:ylafon@w3.org" title="World Wide Web Consortium">Lafon, Y., Ed.</a>, and <a href="mailto:julian.reschke@greenbytes.de" title="greenbytes GmbH">J. Reschke, Ed.</a>, “<a href="http://tools.ietf.org/html/draft-ietf-httpbis-p2-semantics-15">HTTP/1.1, part 2: Message Semantics</a>”, Internet-Draft&nbsp;draft-ietf-httpbis-p2-semantics-15 (work in progress), July&nbsp;2011.
     1713            <td class="top"><a href="mailto:fielding@gbiv.com" title="Adobe Systems Incorporated">Fielding, R., Ed.</a>, <a href="mailto:jg@freedesktop.org" title="Alcatel-Lucent Bell Labs">Gettys, J.</a>, <a href="mailto:JeffMogul@acm.org" title="Hewlett-Packard Company">Mogul, J.</a>, <a href="mailto:henrikn@microsoft.com" title="Microsoft Corporation">Frystyk, H.</a>, <a href="mailto:LMM@acm.org" title="Adobe Systems Incorporated">Masinter, L.</a>, <a href="mailto:paulle@microsoft.com" title="Microsoft Corporation">Leach, P.</a>, <a href="mailto:timbl@w3.org" title="World Wide Web Consortium">Berners-Lee, T.</a>, <a href="mailto:ylafon@w3.org" title="World Wide Web Consortium">Lafon, Y., Ed.</a>, and <a href="mailto:julian.reschke@greenbytes.de" title="greenbytes GmbH">J. Reschke, Ed.</a>, “<a href="https://tools.ietf.org/html/draft-ietf-httpbis-p2-semantics-15">HTTP/1.1, part 2: Message Semantics</a>”, Internet-Draft&nbsp;draft-ietf-httpbis-p2-semantics-15 (work in progress), July&nbsp;2011.
    16341714            </td>
    16351715         </tr>
    16361716         <tr>
    16371717            <td class="reference"><b id="Part4">[Part4]</b></td>
    1638             <td class="top"><a href="mailto:fielding@gbiv.com" title="Adobe Systems Incorporated">Fielding, R., Ed.</a>, <a href="mailto:jg@freedesktop.org" title="Alcatel-Lucent Bell Labs">Gettys, J.</a>, <a href="mailto:JeffMogul@acm.org" title="Hewlett-Packard Company">Mogul, J.</a>, <a href="mailto:henrikn@microsoft.com" title="Microsoft Corporation">Frystyk, H.</a>, <a href="mailto:LMM@acm.org" title="Adobe Systems Incorporated">Masinter, L.</a>, <a href="mailto:paulle@microsoft.com" title="Microsoft Corporation">Leach, P.</a>, <a href="mailto:timbl@w3.org" title="World Wide Web Consortium">Berners-Lee, T.</a>, <a href="mailto:ylafon@w3.org" title="World Wide Web Consortium">Lafon, Y., Ed.</a>, and <a href="mailto:julian.reschke@greenbytes.de" title="greenbytes GmbH">J. Reschke, Ed.</a>, “<a href="http://tools.ietf.org/html/draft-ietf-httpbis-p4-conditional-15">HTTP/1.1, part 4: Conditional Requests</a>”, Internet-Draft&nbsp;draft-ietf-httpbis-p4-conditional-15 (work in progress), July&nbsp;2011.
     1718            <td class="top"><a href="mailto:fielding@gbiv.com" title="Adobe Systems Incorporated">Fielding, R., Ed.</a>, <a href="mailto:jg@freedesktop.org" title="Alcatel-Lucent Bell Labs">Gettys, J.</a>, <a href="mailto:JeffMogul@acm.org" title="Hewlett-Packard Company">Mogul, J.</a>, <a href="mailto:henrikn@microsoft.com" title="Microsoft Corporation">Frystyk, H.</a>, <a href="mailto:LMM@acm.org" title="Adobe Systems Incorporated">Masinter, L.</a>, <a href="mailto:paulle@microsoft.com" title="Microsoft Corporation">Leach, P.</a>, <a href="mailto:timbl@w3.org" title="World Wide Web Consortium">Berners-Lee, T.</a>, <a href="mailto:ylafon@w3.org" title="World Wide Web Consortium">Lafon, Y., Ed.</a>, and <a href="mailto:julian.reschke@greenbytes.de" title="greenbytes GmbH">J. Reschke, Ed.</a>, “<a href="https://tools.ietf.org/html/draft-ietf-httpbis-p4-conditional-15">HTTP/1.1, part 4: Conditional Requests</a>”, Internet-Draft&nbsp;draft-ietf-httpbis-p4-conditional-15 (work in progress), July&nbsp;2011.
    16391719            </td>
    16401720         </tr>
    16411721         <tr>
    16421722            <td class="reference"><b id="Part5">[Part5]</b></td>
    1643             <td class="top"><a href="mailto:fielding@gbiv.com" title="Adobe Systems Incorporated">Fielding, R., Ed.</a>, <a href="mailto:jg@freedesktop.org" title="Alcatel-Lucent Bell Labs">Gettys, J.</a>, <a href="mailto:JeffMogul@acm.org" title="Hewlett-Packard Company">Mogul, J.</a>, <a href="mailto:henrikn@microsoft.com" title="Microsoft Corporation">Frystyk, H.</a>, <a href="mailto:LMM@acm.org" title="Adobe Systems Incorporated">Masinter, L.</a>, <a href="mailto:paulle@microsoft.com" title="Microsoft Corporation">Leach, P.</a>, <a href="mailto:timbl@w3.org" title="World Wide Web Consortium">Berners-Lee, T.</a>, <a href="mailto:ylafon@w3.org" title="World Wide Web Consortium">Lafon, Y., Ed.</a>, and <a href="mailto:julian.reschke@greenbytes.de" title="greenbytes GmbH">J. Reschke, Ed.</a>, “<a href="http://tools.ietf.org/html/draft-ietf-httpbis-p5-range-15">HTTP/1.1, part 5: Range Requests and Partial Responses</a>”, Internet-Draft&nbsp;draft-ietf-httpbis-p5-range-15 (work in progress), July&nbsp;2011.
     1723            <td class="top"><a href="mailto:fielding@gbiv.com" title="Adobe Systems Incorporated">Fielding, R., Ed.</a>, <a href="mailto:jg@freedesktop.org" title="Alcatel-Lucent Bell Labs">Gettys, J.</a>, <a href="mailto:JeffMogul@acm.org" title="Hewlett-Packard Company">Mogul, J.</a>, <a href="mailto:henrikn@microsoft.com" title="Microsoft Corporation">Frystyk, H.</a>, <a href="mailto:LMM@acm.org" title="Adobe Systems Incorporated">Masinter, L.</a>, <a href="mailto:paulle@microsoft.com" title="Microsoft Corporation">Leach, P.</a>, <a href="mailto:timbl@w3.org" title="World Wide Web Consortium">Berners-Lee, T.</a>, <a href="mailto:ylafon@w3.org" title="World Wide Web Consortium">Lafon, Y., Ed.</a>, and <a href="mailto:julian.reschke@greenbytes.de" title="greenbytes GmbH">J. Reschke, Ed.</a>, “<a href="https://tools.ietf.org/html/draft-ietf-httpbis-p5-range-15">HTTP/1.1, part 5: Range Requests and Partial Responses</a>”, Internet-Draft&nbsp;draft-ietf-httpbis-p5-range-15 (work in progress), July&nbsp;2011.
    16441724            </td>
    16451725         </tr>
    16461726         <tr>
    16471727            <td class="reference"><b id="Part7">[Part7]</b></td>
    1648             <td class="top"><a href="mailto:fielding@gbiv.com" title="Adobe Systems Incorporated">Fielding, R., Ed.</a>, <a href="mailto:jg@freedesktop.org" title="Alcatel-Lucent Bell Labs">Gettys, J.</a>, <a href="mailto:JeffMogul@acm.org" title="Hewlett-Packard Company">Mogul, J.</a>, <a href="mailto:henrikn@microsoft.com" title="Microsoft Corporation">Frystyk, H.</a>, <a href="mailto:LMM@acm.org" title="Adobe Systems Incorporated">Masinter, L.</a>, <a href="mailto:paulle@microsoft.com" title="Microsoft Corporation">Leach, P.</a>, <a href="mailto:timbl@w3.org" title="World Wide Web Consortium">Berners-Lee, T.</a>, <a href="mailto:ylafon@w3.org" title="World Wide Web Consortium">Lafon, Y., Ed.</a>, and <a href="mailto:julian.reschke@greenbytes.de" title="greenbytes GmbH">J. Reschke, Ed.</a>, “<a href="http://tools.ietf.org/html/draft-ietf-httpbis-p7-auth-15">HTTP/1.1, part 7: Authentication</a>”, Internet-Draft&nbsp;draft-ietf-httpbis-p7-auth-15 (work in progress), July&nbsp;2011.
     1728            <td class="top"><a href="mailto:fielding@gbiv.com" title="Adobe Systems Incorporated">Fielding, R., Ed.</a>, <a href="mailto:jg@freedesktop.org" title="Alcatel-Lucent Bell Labs">Gettys, J.</a>, <a href="mailto:JeffMogul@acm.org" title="Hewlett-Packard Company">Mogul, J.</a>, <a href="mailto:henrikn@microsoft.com" title="Microsoft Corporation">Frystyk, H.</a>, <a href="mailto:LMM@acm.org" title="Adobe Systems Incorporated">Masinter, L.</a>, <a href="mailto:paulle@microsoft.com" title="Microsoft Corporation">Leach, P.</a>, <a href="mailto:timbl@w3.org" title="World Wide Web Consortium">Berners-Lee, T.</a>, <a href="mailto:ylafon@w3.org" title="World Wide Web Consortium">Lafon, Y., Ed.</a>, and <a href="mailto:julian.reschke@greenbytes.de" title="greenbytes GmbH">J. Reschke, Ed.</a>, “<a href="https://tools.ietf.org/html/draft-ietf-httpbis-p7-auth-15">HTTP/1.1, part 7: Authentication</a>”, Internet-Draft&nbsp;draft-ietf-httpbis-p7-auth-15 (work in progress), July&nbsp;2011.
    16491729            </td>
    16501730         </tr>
    16511731         <tr>
    16521732            <td class="reference"><b id="RFC2119">[RFC2119]</b></td>
    1653             <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.
     1733            <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.
    16541734            </td>
    16551735         </tr>
    16561736         <tr>
    16571737            <td class="reference"><b id="RFC5234">[RFC5234]</b></td>
    1658             <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.
     1738            <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.
    16591739            </td>
    16601740         </tr>
     
    16621742      <h2 id="rfc.references.2"><a href="#rfc.section.8.2" id="rfc.section.8.2">8.2</a> Informative References
    16631743      </h2>
    1664       <table>         
     1744      <table>
    16651745         <tr>
    16661746            <td class="reference"><b id="RFC1305">[RFC1305]</b></td>
    1667             <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.
     1747            <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.
    16681748            </td>
    16691749         </tr>
    16701750         <tr>
    16711751            <td class="reference"><b id="RFC2616">[RFC2616]</b></td>
    1672             <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.
     1752            <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.
    16731753            </td>
    16741754         </tr>
    16751755         <tr>
    16761756            <td class="reference"><b id="RFC3864">[RFC3864]</b></td>
    1677             <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.
     1757            <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.
    16781758            </td>
    16791759         </tr>
    16801760         <tr>
    16811761            <td class="reference"><b id="RFC5226">[RFC5226]</b></td>
    1682             <td class="top"><a href="mailto:narten@us.ibm.com" title="IBM">Narten, T.</a> and <a href="mailto:Harald@Alvestrand.no" title="Google">H. Alvestrand</a>, “<a href="http://tools.ietf.org/html/rfc5226">Guidelines for Writing an IANA Considerations Section in RFCs</a>”, BCP&nbsp;26, RFC&nbsp;5226, May&nbsp;2008.
     1762            <td class="top"><a href="mailto:narten@us.ibm.com" title="IBM">Narten, T.</a> and <a href="mailto:Harald@Alvestrand.no" title="Google">H. Alvestrand</a>, “<a href="https://tools.ietf.org/html/rfc5226">Guidelines for Writing an IANA Considerations Section in RFCs</a>”, BCP&nbsp;26, RFC&nbsp;5226, May&nbsp;2008.
    16831763            </td>
    16841764         </tr>
    16851765         <tr>
    16861766            <td class="reference"><b id="RFC5861">[RFC5861]</b></td>
    1687             <td class="top"><a href="mailto:mnot@yahoo-inc.com" title="Yahoo! Inc.">Nottingham, M.</a>, “<a href="http://tools.ietf.org/html/rfc5861">HTTP Cache-Control Extensions for Stale Content</a>”, RFC&nbsp;5861, April&nbsp;2010.
     1767            <td class="top"><a href="mailto:mnot@yahoo-inc.com" title="Yahoo! Inc.">Nottingham, M.</a>, “<a href="https://tools.ietf.org/html/rfc5861">HTTP Cache-Control Extensions for Stale Content</a>”, RFC&nbsp;5861, April&nbsp;2010.
    16881768            </td>
    16891769         </tr>
    16901770      </table>
    1691       <div class="avoidbreak">
    1692          <h1 id="rfc.authors"><a href="#rfc.authors">Authors' Addresses</a></h1>
    1693          <address class="vcard"><span class="vcardline"><span class="fn">Roy T. Fielding</span>
    1694                (editor)
    1695                <span class="n hidden"><span class="family-name">Fielding</span><span class="given-name">Roy T.</span></span></span><span class="org vcardline">Adobe Systems Incorporated</span><span class="adr"><span class="street-address vcardline">345 Park Ave</span><span class="vcardline"><span class="locality">San Jose</span>, <span class="region">CA</span>&nbsp;<span class="postal-code">95110</span></span><span class="country-name vcardline">USA</span></span><span class="vcardline">Email: <a href="mailto:fielding@gbiv.com"><span class="email">fielding@gbiv.com</span></a></span><span class="vcardline">URI: <a href="http://roy.gbiv.com/" class="url">http://roy.gbiv.com/</a></span></address>
    1696          <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">Alcatel-Lucent Bell Labs</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@freedesktop.org"><span class="email">jg@freedesktop.org</span></a></span><span class="vcardline">URI: <a href="http://gettys.wordpress.com/" class="url">http://gettys.wordpress.com/</a></span></address>
    1697          <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>
    1698          <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>
    1699          <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>
    1700          <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>
    1701          <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>
    1702          <address class="vcard"><span class="vcardline"><span class="fn">Yves Lafon</span>
    1703                (editor)
    1704                <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>
    1705          <address class="vcard"><span class="vcardline"><span class="fn">Mark Nottingham</span>
    1706                (editor)
    1707                <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>
    1708          <address class="vcard"><span class="vcardline"><span class="fn">Julian F. Reschke</span>
    1709                (editor)
    1710                <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>
     1771      <div id="changes.from.rfc.2616">
     1772         <h1 id="rfc.section.A" class="np"><a href="#rfc.section.A">A.</a>&nbsp;<a href="#changes.from.rfc.2616">Changes from RFC 2616</a></h1>
     1773         <p id="rfc.section.A.p.1">Make the specified age calculation algorithm less conservative. (<a href="#age.calculations" title="Calculating Age">Section&nbsp;2.3.2</a>)
     1774         </p>
     1775         <p id="rfc.section.A.p.2">Remove requirement to consider Content-Location in successful responses in order to determine the appropriate response to
     1776            use. (<a href="#validation.model" title="Validation Model">Section&nbsp;2.4</a>)
     1777         </p>
     1778         <p id="rfc.section.A.p.3">Clarify denial of service attack avoidance requirement. (<a href="#invalidation.after.updates.or.deletions" title="Request Methods that Invalidate">Section&nbsp;2.5</a>)
     1779         </p>
     1780         <p id="rfc.section.A.p.4">Change ABNF productions for header fields to only define the field value. (<a href="#header.fields" title="Header Field Definitions">Section&nbsp;3</a>)
     1781         </p>
     1782         <p id="rfc.section.A.p.5">Do not mention RFC 2047 encoding and multiple languages in Warning header fields anymore, as these aspects never were implemented.
     1783            (<a href="#header.warning" id="rfc.xref.header.warning.4" title="Warning">Section&nbsp;3.6</a>)
     1784         </p>
    17111785      </div>
    1712       <h1 id="rfc.section.A" class="np"><a href="#rfc.section.A">A.</a>&nbsp;<a id="changes.from.rfc.2616" href="#changes.from.rfc.2616">Changes from RFC 2616</a></h1>
    1713       <p id="rfc.section.A.p.1">Make the specified age calculation algorithm less conservative. (<a href="#age.calculations" title="Calculating Age">Section&nbsp;2.3.2</a>)
    1714       </p>
    1715       <p id="rfc.section.A.p.2">Remove requirement to consider Content-Location in successful responses in order to determine the appropriate response to
    1716          use. (<a href="#validation.model" title="Validation Model">Section&nbsp;2.4</a>)
    1717       </p>
    1718       <p id="rfc.section.A.p.3">Clarify denial of service attack avoidance requirement. (<a href="#invalidation.after.updates.or.deletions" title="Request Methods that Invalidate">Section&nbsp;2.5</a>)
    1719       </p>
    1720       <p id="rfc.section.A.p.4">Change ABNF productions for header fields to only define the field value. (<a href="#header.fields" title="Header Field Definitions">Section&nbsp;3</a>)
    1721       </p>
    1722       <p id="rfc.section.A.p.5">Do not mention RFC 2047 encoding and multiple languages in Warning header fields anymore, as these aspects never were implemented.
    1723          (<a href="#header.warning" id="rfc.xref.header.warning.4" title="Warning">Section&nbsp;3.6</a>)
    1724       </p>
    1725       <h1 id="rfc.section.B"><a href="#rfc.section.B">B.</a>&nbsp;<a id="collected.abnf" href="#collected.abnf">Collected ABNF</a></h1>
    1726       <div id="rfc.figure.u.19"></div> <pre class="inline"><a href="#header.age" class="smpl">Age</a> = delta-seconds
     1786      <div id="collected.abnf">
     1787         <h1 id="rfc.section.B"><a href="#rfc.section.B">B.</a>&nbsp;<a href="#collected.abnf">Collected ABNF</a></h1>
     1788         <div id="rfc.figure.u.19"></div><pre class="inline"><a href="#header.age" class="smpl">Age</a> = delta-seconds
    17271789
    17281790<a href="#header.cache-control" class="smpl">Cache-Control</a> = *( "," OWS ) cache-directive *( OWS "," [ OWS
     
    17791841<a href="#header.warning" class="smpl">warning-value</a> = warn-code SP warn-agent SP warn-text [ SP warn-date
    17801842 ]
    1781 </pre> <div id="rfc.figure.u.20"></div>
    1782       <p>ABNF diagnostics:</p><pre class="inline">; Age defined but not used
     1843</pre><div id="rfc.figure.u.20"></div>
     1844         <p>ABNF diagnostics:</p><pre class="inline">; Age defined but not used
    17831845; Cache-Control defined but not used
    17841846; Expires defined but not used
     
    17861848; Vary defined but not used
    17871849; Warning defined but not used
    1788 </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>
    1789       <h2 id="rfc.section.C.1"><a href="#rfc.section.C.1">C.1</a>&nbsp;Since RFC 2616
    1790       </h2>
    1791       <p id="rfc.section.C.1.p.1">Extracted relevant partitions from <a href="#RFC2616" id="rfc.xref.RFC2616.2"><cite title="Hypertext Transfer Protocol -- HTTP/1.1">[RFC2616]</cite></a>.
    1792       </p>
    1793       <h2 id="rfc.section.C.2"><a href="#rfc.section.C.2">C.2</a>&nbsp;Since draft-ietf-httpbis-p6-cache-00
    1794       </h2>
    1795       <p id="rfc.section.C.2.p.1">Closed issues: </p>
    1796       <ul>
    1797          <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;)
    1798          </li>
    1799          <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;)
    1800          </li>
    1801          <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"
    1802          </li>
    1803          <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"
    1804          </li>
    1805          <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"
    1806          </li>
    1807          <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"
    1808          </li>
    1809          <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"
    1810          </li>
    1811          <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"
    1812          </li>
    1813          <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"
    1814          </li>
    1815       </ul>
    1816       <p id="rfc.section.C.2.p.2">Other changes: </p>
    1817       <ul>
    1818          <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;)
    1819          </li>
    1820       </ul>
    1821       <h2 id="rfc.section.C.3"><a href="#rfc.section.C.3">C.3</a>&nbsp;Since draft-ietf-httpbis-p6-cache-01
    1822       </h2>
    1823       <p id="rfc.section.C.3.p.1">Closed issues: </p>
    1824       <ul>
    1825          <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"
    1826          </li>
    1827       </ul>
    1828       <p id="rfc.section.C.3.p.2">Other changes: </p>
    1829       <ul>
    1830          <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;)
    1831          </li>
    1832          <li>Add explicit references to BNF syntax and rules imported from other parts of the specification.</li>
    1833       </ul>
    1834       <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>
    1835       <p id="rfc.section.C.4.p.1">Ongoing work on IANA Message Header Field Registration (&lt;<a href="http://tools.ietf.org/wg/httpbis/trac/ticket/40">http://tools.ietf.org/wg/httpbis/trac/ticket/40</a>&gt;):
    1836       </p>
    1837       <ul>
    1838          <li>Reference RFC 3984, and update header field registrations for header fields defined in this document.</li>
    1839       </ul>
    1840       <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>
    1841       <p id="rfc.section.C.5.p.1">Closed issues: </p>
    1842       <ul>
    1843          <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"
    1844          </li>
    1845       </ul>
    1846       <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>
    1847       <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;):
    1848       </p>
    1849       <ul>
    1850          <li>Use "/" instead of "|" for alternatives.</li>
    1851          <li>Introduce new ABNF rules for "bad" whitespace ("BWS"), optional whitespace ("OWS") and required whitespace ("RWS").</li>
    1852          <li>Rewrite ABNFs to spell out whitespace rules, factor out header field value format definitions.</li>
    1853       </ul>
    1854       <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>
    1855       <p id="rfc.section.C.7.p.1">This is a total rewrite of this part of the specification.</p>
    1856       <p id="rfc.section.C.7.p.2">Affected issues: </p>
    1857       <ul>
    1858          <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"
    1859          </li>
    1860          <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"
    1861          </li>
    1862          <li> &lt;<a href="http://tools.ietf.org/wg/httpbis/trac/ticket/138">http://tools.ietf.org/wg/httpbis/trac/ticket/138</a>&gt;: "The role of Warning and Semantic Transparency in Caching"
    1863          </li>
    1864          <li> &lt;<a href="http://tools.ietf.org/wg/httpbis/trac/ticket/139">http://tools.ietf.org/wg/httpbis/trac/ticket/139</a>&gt;: "Methods and Caching"
    1865          </li>
    1866       </ul>
    1867       <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;):
    1868       </p>
    1869       <ul>
    1870          <li>Add appendix containing collected and expanded ABNF, reorganize ABNF introduction.</li>
    1871       </ul>
    1872       <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>
    1873       <p id="rfc.section.C.8.p.1">Closed issues: </p>
    1874       <ul>
    1875          <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"
    1876          </li>
    1877       </ul>
    1878       <p id="rfc.section.C.8.p.2">Affected issues: </p>
    1879       <ul>
    1880          <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"
    1881          </li>
    1882       </ul>
    1883       <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>
    1884       <p id="rfc.section.C.9.p.1">Closed issues: </p>
    1885       <ul>
    1886          <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"
    1887          </li>
    1888          <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"
    1889          </li>
    1890          <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"
    1891          </li>
    1892          <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"
    1893          </li>
    1894       </ul>
    1895       <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>
    1896       <p id="rfc.section.C.10.p.1">Closed issues: </p>
    1897       <ul>
    1898          <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"
    1899          </li>
    1900          <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"
    1901          </li>
    1902          <li> &lt;<a href="http://tools.ietf.org/wg/httpbis/trac/ticket/291">http://tools.ietf.org/wg/httpbis/trac/ticket/291</a>&gt;: "Cache Extensions can override no-store, etc."
    1903          </li>
    1904       </ul>
    1905       <p id="rfc.section.C.10.p.2">Affected issues: </p>
    1906       <ul>
    1907          <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
    1908          </li>
    1909       </ul>
    1910       <p id="rfc.section.C.10.p.3">Partly resolved issues: </p>
    1911       <ul>
    1912          <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"
    1913          </li>
    1914       </ul>
    1915       <h2 id="rfc.section.C.11"><a href="#rfc.section.C.11">C.11</a>&nbsp;<a id="changes.since.09" href="#changes.since.09">Since draft-ietf-httpbis-p6-cache-09</a></h2>
    1916       <p id="rfc.section.C.11.p.1">Closed issues: </p>
    1917       <ul>
    1918          <li> &lt;<a href="http://tools.ietf.org/wg/httpbis/trac/ticket/29">http://tools.ietf.org/wg/httpbis/trac/ticket/29</a>&gt;: "Age calculation"
    1919          </li>
    1920          <li> &lt;<a href="http://tools.ietf.org/wg/httpbis/trac/ticket/168">http://tools.ietf.org/wg/httpbis/trac/ticket/168</a>&gt;: "Clarify differences between / requirements for request and response CC directives"
    1921          </li>
    1922          <li> &lt;<a href="http://tools.ietf.org/wg/httpbis/trac/ticket/174">http://tools.ietf.org/wg/httpbis/trac/ticket/174</a>&gt;: "Caching authenticated responses"
    1923          </li>
    1924          <li> &lt;<a href="http://tools.ietf.org/wg/httpbis/trac/ticket/208">http://tools.ietf.org/wg/httpbis/trac/ticket/208</a>&gt;: "IANA registry for cache-control directives"
    1925          </li>
    1926          <li> &lt;<a href="http://tools.ietf.org/wg/httpbis/trac/ticket/211">http://tools.ietf.org/wg/httpbis/trac/ticket/211</a>&gt;: "Heuristic caching of URLs with query components"
    1927          </li>
    1928       </ul>
    1929       <p id="rfc.section.C.11.p.2">Partly resolved issues: </p>
    1930       <ul>
    1931          <li> &lt;<a href="http://tools.ietf.org/wg/httpbis/trac/ticket/196">http://tools.ietf.org/wg/httpbis/trac/ticket/196</a>&gt;: "Term for the requested resource's URI"
    1932          </li>
    1933       </ul>
    1934       <h2 id="rfc.section.C.12"><a href="#rfc.section.C.12">C.12</a>&nbsp;<a id="changes.since.10" href="#changes.since.10">Since draft-ietf-httpbis-p6-cache-10</a></h2>
    1935       <p id="rfc.section.C.12.p.1">Closed issues: </p>
    1936       <ul>
    1937          <li> &lt;<a href="http://tools.ietf.org/wg/httpbis/trac/ticket/109">http://tools.ietf.org/wg/httpbis/trac/ticket/109</a>&gt;: "Clarify entity / representation / variant terminology"
    1938          </li>
    1939          <li> &lt;<a href="http://tools.ietf.org/wg/httpbis/trac/ticket/220">http://tools.ietf.org/wg/httpbis/trac/ticket/220</a>&gt;: "consider removing the 'changes from 2068' sections"
    1940          </li>
    1941          <li> &lt;<a href="http://tools.ietf.org/wg/httpbis/trac/ticket/223">http://tools.ietf.org/wg/httpbis/trac/ticket/223</a>&gt;: "Allowing heuristic caching for new status codes"
    1942          </li>
    1943          <li>Clean up TODOs and prose in "Combining Responses."</li>
    1944       </ul>
    1945       <h2 id="rfc.section.C.13"><a href="#rfc.section.C.13">C.13</a>&nbsp;<a id="changes.since.11" href="#changes.since.11">Since draft-ietf-httpbis-p6-cache-11</a></h2>
    1946       <p id="rfc.section.C.13.p.1">Closed issues: </p>
    1947       <ul>
    1948          <li> &lt;<a href="http://tools.ietf.org/wg/httpbis/trac/ticket/204">http://tools.ietf.org/wg/httpbis/trac/ticket/204</a>&gt;: "Text about clock requirement for caches belongs in p6"
    1949          </li>
    1950       </ul>
    1951       <h2 id="rfc.section.C.14"><a href="#rfc.section.C.14">C.14</a>&nbsp;<a id="changes.since.12" href="#changes.since.12">Since draft-ietf-httpbis-p6-cache-12</a></h2>
    1952       <p id="rfc.section.C.14.p.1">Closed issues: </p>
    1953       <ul>
    1954          <li> &lt;<a href="http://tools.ietf.org/wg/httpbis/trac/ticket/224">http://tools.ietf.org/wg/httpbis/trac/ticket/224</a>&gt;: "Header Classification"
    1955          </li>
    1956          <li> &lt;<a href="http://tools.ietf.org/wg/httpbis/trac/ticket/268">http://tools.ietf.org/wg/httpbis/trac/ticket/268</a>&gt;: "Clarify 'public'"
    1957          </li>
    1958       </ul>
    1959       <h2 id="rfc.section.C.15"><a href="#rfc.section.C.15">C.15</a>&nbsp;<a id="changes.since.13" href="#changes.since.13">Since draft-ietf-httpbis-p6-cache-13</a></h2>
    1960       <p id="rfc.section.C.15.p.1">Closed issues: </p>
    1961       <ul>
    1962          <li> &lt;<a href="http://tools.ietf.org/wg/httpbis/trac/ticket/276">http://tools.ietf.org/wg/httpbis/trac/ticket/276</a>&gt;: "untangle ABNFs for header fields"
    1963          </li>
    1964       </ul>
    1965       <h2 id="rfc.section.C.16"><a href="#rfc.section.C.16">C.16</a>&nbsp;<a id="changes.since.14" href="#changes.since.14">Since draft-ietf-httpbis-p6-cache-14</a></h2>
    1966       <p id="rfc.section.C.16.p.1">Closed issues: </p>
    1967       <ul>
    1968          <li> &lt;<a href="http://tools.ietf.org/wg/httpbis/trac/ticket/38">http://tools.ietf.org/wg/httpbis/trac/ticket/38</a>&gt;: "Mismatch Vary"
    1969          </li>
    1970          <li> &lt;<a href="http://tools.ietf.org/wg/httpbis/trac/ticket/235">http://tools.ietf.org/wg/httpbis/trac/ticket/235</a>&gt;: "Cache Invalidation only happens upon successful responses"
    1971          </li>
    1972          <li> &lt;<a href="http://tools.ietf.org/wg/httpbis/trac/ticket/282">http://tools.ietf.org/wg/httpbis/trac/ticket/282</a>&gt;: "Recommend minimum sizes for protocol elements"
    1973          </li>
    1974          <li> &lt;<a href="http://tools.ietf.org/wg/httpbis/trac/ticket/289">http://tools.ietf.org/wg/httpbis/trac/ticket/289</a>&gt;: "Proxies don't 'understand' methods"
    1975          </li>
    1976          <li> &lt;<a href="http://tools.ietf.org/wg/httpbis/trac/ticket/292">http://tools.ietf.org/wg/httpbis/trac/ticket/292</a>&gt;: "Pragma"
    1977          </li>
    1978       </ul>
     1850</pre></div>
     1851      <div id="change.log">
     1852         <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>
     1853         <div>
     1854            <h2 id="rfc.section.C.1"><a href="#rfc.section.C.1">C.1</a>&nbsp;Since RFC 2616
     1855            </h2>
     1856            <p id="rfc.section.C.1.p.1">Extracted relevant partitions from <a href="#RFC2616" id="rfc.xref.RFC2616.2"><cite title="Hypertext Transfer Protocol -- HTTP/1.1">[RFC2616]</cite></a>.
     1857            </p>
     1858         </div>
     1859         <div>
     1860            <h2 id="rfc.section.C.2"><a href="#rfc.section.C.2">C.2</a>&nbsp;Since draft-ietf-httpbis-p6-cache-00
     1861            </h2>
     1862            <p id="rfc.section.C.2.p.1">Closed issues: </p>
     1863            <ul>
     1864               <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;)
     1865               </li>
     1866               <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;)
     1867               </li>
     1868               <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"
     1869               </li>
     1870               <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"
     1871               </li>
     1872               <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"
     1873               </li>
     1874               <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"
     1875               </li>
     1876               <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"
     1877               </li>
     1878               <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"
     1879               </li>
     1880               <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"
     1881               </li>
     1882            </ul>
     1883            <p id="rfc.section.C.2.p.2">Other changes: </p>
     1884            <ul>
     1885               <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;)
     1886               </li>
     1887            </ul>
     1888         </div>
     1889         <div>
     1890            <h2 id="rfc.section.C.3"><a href="#rfc.section.C.3">C.3</a>&nbsp;Since draft-ietf-httpbis-p6-cache-01
     1891            </h2>
     1892            <p id="rfc.section.C.3.p.1">Closed issues: </p>
     1893            <ul>
     1894               <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"
     1895               </li>
     1896            </ul>
     1897            <p id="rfc.section.C.3.p.2">Other changes: </p>
     1898            <ul>
     1899               <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;)
     1900               </li>
     1901               <li>Add explicit references to BNF syntax and rules imported from other parts of the specification.</li>
     1902            </ul>
     1903         </div>
     1904         <div id="changes.since.02">
     1905            <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>
     1906            <p id="rfc.section.C.4.p.1">Ongoing work on IANA Message Header Field Registration (&lt;<a href="http://tools.ietf.org/wg/httpbis/trac/ticket/40">http://tools.ietf.org/wg/httpbis/trac/ticket/40</a>&gt;):
     1907            </p>
     1908            <ul>
     1909               <li>Reference RFC 3984, and update header field registrations for header fields defined in this document.</li>
     1910            </ul>
     1911         </div>
     1912         <div id="changes.since.03">
     1913            <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>
     1914            <p id="rfc.section.C.5.p.1">Closed issues: </p>
     1915            <ul>
     1916               <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"
     1917               </li>
     1918            </ul>
     1919         </div>
     1920         <div id="changes.since.04">
     1921            <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>
     1922            <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;):
     1923            </p>
     1924            <ul>
     1925               <li>Use "/" instead of "|" for alternatives.</li>
     1926               <li>Introduce new ABNF rules for "bad" whitespace ("BWS"), optional whitespace ("OWS") and required whitespace ("RWS").</li>
     1927               <li>Rewrite ABNFs to spell out whitespace rules, factor out header field value format definitions.</li>
     1928            </ul>
     1929         </div>
     1930         <div id="changes.since.05">
     1931            <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>
     1932            <p id="rfc.section.C.7.p.1">This is a total rewrite of this part of the specification.</p>
     1933            <p id="rfc.section.C.7.p.2">Affected issues: </p>
     1934            <ul>
     1935               <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"
     1936               </li>
     1937               <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"
     1938               </li>
     1939               <li>&lt;<a href="http://tools.ietf.org/wg/httpbis/trac/ticket/138">http://tools.ietf.org/wg/httpbis/trac/ticket/138</a>&gt;: "The role of Warning and Semantic Transparency in Caching"
     1940               </li>
     1941               <li>&lt;<a href="http://tools.ietf.org/wg/httpbis/trac/ticket/139">http://tools.ietf.org/wg/httpbis/trac/ticket/139</a>&gt;: "Methods and Caching"
     1942               </li>
     1943            </ul>
     1944            <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;):
     1945            </p>
     1946            <ul>
     1947               <li>Add appendix containing collected and expanded ABNF, reorganize ABNF introduction.</li>
     1948            </ul>
     1949         </div>
     1950         <div id="changes.since.06">
     1951            <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>
     1952            <p id="rfc.section.C.8.p.1">Closed issues: </p>
     1953            <ul>
     1954               <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"
     1955               </li>
     1956            </ul>
     1957            <p id="rfc.section.C.8.p.2">Affected issues: </p>
     1958            <ul>
     1959               <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"
     1960               </li>
     1961            </ul>
     1962         </div>
     1963         <div id="changes.since.07">
     1964            <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>
     1965            <p id="rfc.section.C.9.p.1">Closed issues: </p>
     1966            <ul>
     1967               <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"
     1968               </li>
     1969               <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"
     1970               </li>
     1971               <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"
     1972               </li>
     1973               <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"
     1974               </li>
     1975            </ul>
     1976         </div>
     1977         <div id="changes.since.08">
     1978            <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>
     1979            <p id="rfc.section.C.10.p.1">Closed issues: </p>
     1980            <ul>
     1981               <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"
     1982               </li>
     1983               <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"
     1984               </li>
     1985               <li>&lt;<a href="http://tools.ietf.org/wg/httpbis/trac/ticket/291">http://tools.ietf.org/wg/httpbis/trac/ticket/291</a>&gt;: "Cache Extensions can override no-store, etc."
     1986               </li>
     1987            </ul>
     1988            <p id="rfc.section.C.10.p.2">Affected issues: </p>
     1989            <ul>
     1990               <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
     1991               </li>
     1992            </ul>
     1993            <p id="rfc.section.C.10.p.3">Partly resolved issues: </p>
     1994            <ul>
     1995               <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"
     1996               </li>
     1997            </ul>
     1998         </div>
     1999         <div id="changes.since.09">
     2000            <h2 id="rfc.section.C.11"><a href="#rfc.section.C.11">C.11</a>&nbsp;<a href="#changes.since.09">Since draft-ietf-httpbis-p6-cache-09</a></h2>
     2001            <p id="rfc.section.C.11.p.1">Closed issues: </p>
     2002            <ul>
     2003               <li>&lt;<a href="http://tools.ietf.org/wg/httpbis/trac/ticket/29">http://tools.ietf.org/wg/httpbis/trac/ticket/29</a>&gt;: "Age calculation"
     2004               </li>
     2005               <li>&lt;<a href="http://tools.ietf.org/wg/httpbis/trac/ticket/168">http://tools.ietf.org/wg/httpbis/trac/ticket/168</a>&gt;: "Clarify differences between / requirements for request and response CC directives"
     2006               </li>
     2007               <li>&lt;<a href="http://tools.ietf.org/wg/httpbis/trac/ticket/174">http://tools.ietf.org/wg/httpbis/trac/ticket/174</a>&gt;: "Caching authenticated responses"
     2008               </li>
     2009               <li>&lt;<a href="http://tools.ietf.org/wg/httpbis/trac/ticket/208">http://tools.ietf.org/wg/httpbis/trac/ticket/208</a>&gt;: "IANA registry for cache-control directives"
     2010               </li>
     2011               <li>&lt;<a href="http://tools.ietf.org/wg/httpbis/trac/ticket/211">http://tools.ietf.org/wg/httpbis/trac/ticket/211</a>&gt;: "Heuristic caching of URLs with query components"
     2012               </li>
     2013            </ul>
     2014            <p id="rfc.section.C.11.p.2">Partly resolved issues: </p>
     2015            <ul>
     2016               <li>&lt;<a href="http://tools.ietf.org/wg/httpbis/trac/ticket/196">http://tools.ietf.org/wg/httpbis/trac/ticket/196</a>&gt;: "Term for the requested resource's URI"
     2017               </li>
     2018            </ul>
     2019         </div>
     2020         <div id="changes.since.10">
     2021            <h2 id="rfc.section.C.12"><a href="#rfc.section.C.12">C.12</a>&nbsp;<a href="#changes.since.10">Since draft-ietf-httpbis-p6-cache-10</a></h2>
     2022            <p id="rfc.section.C.12.p.1">Closed issues: </p>
     2023            <ul>
     2024               <li>&lt;<a href="http://tools.ietf.org/wg/httpbis/trac/ticket/109">http://tools.ietf.org/wg/httpbis/trac/ticket/109</a>&gt;: "Clarify entity / representation / variant terminology"
     2025               </li>
     2026               <li>&lt;<a href="http://tools.ietf.org/wg/httpbis/trac/ticket/220">http://tools.ietf.org/wg/httpbis/trac/ticket/220</a>&gt;: "consider removing the 'changes from 2068' sections"
     2027               </li>
     2028               <li>&lt;<a href="http://tools.ietf.org/wg/httpbis/trac/ticket/223">http://tools.ietf.org/wg/httpbis/trac/ticket/223</a>&gt;: "Allowing heuristic caching for new status codes"
     2029               </li>
     2030               <li>Clean up TODOs and prose in "Combining Responses."</li>
     2031            </ul>
     2032         </div>
     2033         <div id="changes.since.11">
     2034            <h2 id="rfc.section.C.13"><a href="#rfc.section.C.13">C.13</a>&nbsp;<a href="#changes.since.11">Since draft-ietf-httpbis-p6-cache-11</a></h2>
     2035            <p id="rfc.section.C.13.p.1">Closed issues: </p>
     2036            <ul>
     2037               <li>&lt;<a href="http://tools.ietf.org/wg/httpbis/trac/ticket/204">http://tools.ietf.org/wg/httpbis/trac/ticket/204</a>&gt;: "Text about clock requirement for caches belongs in p6"
     2038               </li>
     2039            </ul>
     2040         </div>
     2041         <div id="changes.since.12">
     2042            <h2 id="rfc.section.C.14"><a href="#rfc.section.C.14">C.14</a>&nbsp;<a href="#changes.since.12">Since draft-ietf-httpbis-p6-cache-12</a></h2>
     2043            <p id="rfc.section.C.14.p.1">Closed issues: </p>
     2044            <ul>
     2045               <li>&lt;<a href="http://tools.ietf.org/wg/httpbis/trac/ticket/224">http://tools.ietf.org/wg/httpbis/trac/ticket/224</a>&gt;: "Header Classification"
     2046               </li>
     2047               <li>&lt;<a href="http://tools.ietf.org/wg/httpbis/trac/ticket/268">http://tools.ietf.org/wg/httpbis/trac/ticket/268</a>&gt;: "Clarify 'public'"
     2048               </li>
     2049            </ul>
     2050         </div>
     2051         <div id="changes.since.13">
     2052            <h2 id="rfc.section.C.15"><a href="#rfc.section.C.15">C.15</a>&nbsp;<a href="#changes.since.13">Since draft-ietf-httpbis-p6-cache-13</a></h2>
     2053            <p id="rfc.section.C.15.p.1">Closed issues: </p>
     2054            <ul>
     2055               <li>&lt;<a href="http://tools.ietf.org/wg/httpbis/trac/ticket/276">http://tools.ietf.org/wg/httpbis/trac/ticket/276</a>&gt;: "untangle ABNFs for header fields"
     2056               </li>
     2057            </ul>
     2058         </div>
     2059         <div id="changes.since.14">
     2060            <h2 id="rfc.section.C.16"><a href="#rfc.section.C.16">C.16</a>&nbsp;<a href="#changes.since.14">Since draft-ietf-httpbis-p6-cache-14</a></h2>
     2061            <p id="rfc.section.C.16.p.1">Closed issues: </p>
     2062            <ul>
     2063               <li>&lt;<a href="http://tools.ietf.org/wg/httpbis/trac/ticket/38">http://tools.ietf.org/wg/httpbis/trac/ticket/38</a>&gt;: "Mismatch Vary"
     2064               </li>
     2065               <li>&lt;<a href="http://tools.ietf.org/wg/httpbis/trac/ticket/235">http://tools.ietf.org/wg/httpbis/trac/ticket/235</a>&gt;: "Cache Invalidation only happens upon successful responses"
     2066               </li>
     2067               <li>&lt;<a href="http://tools.ietf.org/wg/httpbis/trac/ticket/282">http://tools.ietf.org/wg/httpbis/trac/ticket/282</a>&gt;: "Recommend minimum sizes for protocol elements"
     2068               </li>
     2069               <li>&lt;<a href="http://tools.ietf.org/wg/httpbis/trac/ticket/289">http://tools.ietf.org/wg/httpbis/trac/ticket/289</a>&gt;: "Proxies don't 'understand' methods"
     2070               </li>
     2071               <li>&lt;<a href="http://tools.ietf.org/wg/httpbis/trac/ticket/292">http://tools.ietf.org/wg/httpbis/trac/ticket/292</a>&gt;: "Pragma"
     2072               </li>
     2073            </ul>
     2074         </div>
     2075      </div>
    19792076      <h1 id="rfc.index"><a href="#rfc.index">Index</a></h1>
    19802077      <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>
     
    22002297         </ul>
    22012298      </div>
     2299      <div class="avoidbreak">
     2300         <h1 id="rfc.authors"><a href="#rfc.authors">Authors' Addresses</a></h1>
     2301         <p><b>Roy T. Fielding</b>
     2302            (editor)
     2303            <br>Adobe Systems Incorporated<br>345 Park Ave<br>San Jose, CA&nbsp;95110<br>USA<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>
     2304         <p><b>Jim Gettys</b><br>Alcatel-Lucent Bell Labs<br>21 Oak Knoll Road<br>Carlisle, MA&nbsp;01741<br>USA<br>Email: <a href="mailto:jg@freedesktop.org">jg@freedesktop.org</a><br>URI: <a href="http://gettys.wordpress.com/">http://gettys.wordpress.com/</a></p>
     2305         <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>
     2306         <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>
     2307         <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>
     2308         <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>
     2309         <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>
     2310         <p><b>Yves Lafon</b>
     2311            (editor)
     2312            <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>
     2313         <p><b>Mark Nottingham</b>
     2314            (editor)
     2315            <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>
     2316         <p><b>Julian F. Reschke</b>
     2317            (editor)
     2318            <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>
     2319      </div>
    22022320   </body>
    22032321</html>
Note: See TracChangeset for help on using the changeset viewer.