Ignore:
Timestamp:
01/01/11 17:23:02 (9 years ago)
Author:
julian.reschke@…
Message:

bump up document dates, update to latest version of rfc2629.xslt

File:
1 edited

Legend:

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

    r230 r1099  
    22  PUBLIC "-//W3C//DTD HTML 4.01//EN">
    33<html lang="en">
    4    <head profile="http://www.w3.org/2006/03/hcard">
     4   <head profile="http://www.w3.org/2006/03/hcard 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)">
     
    3737}
    3838
    39 dl.empty dd {
     39ul.empty {
     40  list-style-type: none;
     41}
     42ul.empty li {
    4043  margin-top: .5em;
    4144}
     
    6265  page-break-after: avoid;
    6366}
    64 h2 a {
    65   color: black;
    66 }
    67 h3 {
     67h3, h4, h5, h6 {
    6868  font-size: 10pt;
    6969  page-break-after: avoid;
    7070}
    71 h3 a {
    72   color: black;
    73 }
    74 h4 {
    75   font-size: 10pt;
    76   page-break-after: avoid;
    77 }
    78 h4 a {
    79   color: black;
    80 }
    81 h5 {
    82   font-size: 10pt;
    83   page-break-after: avoid;
    84 }
    85 h5 a {
     71h2 a, h3 a, h4 a, h5 a, h6 a {
    8672  color: black;
    8773}
     
    135121}
    136122table.header {
     123  border-spacing: 1px;
    137124  width: 95%;
    138125  font-size: 10pt;
     
    146133  white-space: nowrap;
    147134}
    148 td.header {
     135table.header td {
    149136  background-color: gray;
    150137  width: 50%;
    151138}
    152 td.header a {
     139table.header a {
    153140  color: white;
    154141}
     
    161148  display:table-header-group;
    162149}
    163 ul.toc {
     150ul.toc, ul.toc ul {
    164151  list-style: none;
    165152  margin-left: 1.5em;
     
    167154  padding-left: 0em;
    168155}
    169 li.tocline0 {
     156ul.toc li {
    170157  line-height: 150%;
    171158  font-weight: bold;
     
    174161  margin-right: 0em;
    175162}
    176 li.tocline1 {
     163ul.toc li li {
    177164  line-height: normal;
    178165  font-weight: normal;
     
    181168  margin-right: 0em;
    182169}
    183 li.tocline2 {
     170li.excluded {
    184171  font-size: 0pt;
    185172}
     
    187174  margin-left: 0em;
    188175}
    189 ul.ind {
     176ul.ind, ul.ind ul {
    190177  list-style: none;
    191178  margin-left: 1.5em;
    192179  margin-right: 0em;
    193180  padding-left: 0em;
    194 }
    195 li.indline0 {
     181  page-break-before: avoid;
     182}
     183ul.ind li {
    196184  font-weight: bold;
    197185  line-height: 200%;
     
    199187  margin-right: 0em;
    200188}
    201 li.indline1 {
     189ul.ind li li {
    202190  font-weight: normal;
    203191  line-height: 150%;
    204192  margin-left: 0em;
    205193  margin-right: 0em;
     194}
     195.avoidbreak {
     196  page-break-inside: avoid;
    206197}
    207198.bcp14 {
     
    288279  }
    289280 
    290   a.iref {
     281  ul.ind li li a {
    291282    content: target-counter(attr(href), page);
    292283  }
     
    301292@page {
    302293  @top-left {
    303        content: "INTERNET DRAFT";
     294       content: "Internet-Draft";
    304295  }
    305296  @top-right {
     
    343334      <link rel="Chapter" href="#rfc.section.7" title="7 References">
    344335      <link rel="Appendix" title="A Changes from RFC 2068" href="#rfc.section.A">
    345       <meta name="generator" content="http://greenbytes.de/tech/webdav/rfc2629.xslt, Revision 1.365, 2008-03-07 07:17:25, XSLT vendor: SAXON 8.9 from Saxonica http://www.saxonica.com/">
    346       <link rel="schema.DC" href="http://purl.org/dc/elements/1.1/">
    347       <meta name="DC.Creator" content="Fielding, R.">
    348       <meta name="DC.Creator" content="Gettys, J.">
    349       <meta name="DC.Creator" content="Mogul, J.">
    350       <meta name="DC.Creator" content="Frystyk, H.">
    351       <meta name="DC.Creator" content="Masinter, L.">
    352       <meta name="DC.Creator" content="Leach, P.">
    353       <meta name="DC.Creator" content="Berners-Lee, T.">
    354       <meta name="DC.Identifier" content="urn:ietf:id:draft-ietf-httpbis-p6-cache-00">
    355       <meta name="DC.Date.Issued" scheme="ISO8601" content="2007-12">
    356       <meta name="DC.Relation.Replaces" content="urn:ietf:rfc:2068">
    357       <meta name="DC.Relation.Replaces" content="urn:ietf:rfc:2616">
    358       <meta name="DC.Description.Abstract" content="The Hypertext Transfer Protocol (HTTP) is an application-level protocol for distributed, collaborative, hypermedia information systems. HTTP has been in use by the World Wide Web global information initiative since 1990. This document is Part 6 of the seven-part specification that defines the protocol referred to as &#34;HTTP/1.1&#34; and, taken together, obsoletes RFC 2616. Part 6 defines requirements on HTTP caches and the associated header fields that control cache behavior or indicate cacheable response messages.">
     336      <meta name="generator" content="http://greenbytes.de/tech/webdav/rfc2629.xslt, Revision 1.537, 2010-12-30 14:21:59, XSLT vendor: SAXON 8.9 from Saxonica http://www.saxonica.com/">
     337      <link rel="schema.dct" href="http://purl.org/dc/terms/">
     338      <meta name="dct.creator" content="Fielding, R.">
     339      <meta name="dct.creator" content="Gettys, J.">
     340      <meta name="dct.creator" content="Mogul, J.">
     341      <meta name="dct.creator" content="Frystyk, H.">
     342      <meta name="dct.creator" content="Masinter, L.">
     343      <meta name="dct.creator" content="Leach, P.">
     344      <meta name="dct.creator" content="Berners-Lee, T.">
     345      <meta name="dct.identifier" content="urn:ietf:id:draft-ietf-httpbis-p6-cache-00">
     346      <meta name="dct.issued" scheme="ISO8601" content="2007-12-20">
     347      <meta name="dct.replaces" content="urn:ietf:rfc:2068">
     348      <meta name="dct.replaces" content="urn:ietf:rfc:2616">
     349      <meta name="dct.abstract" content="The Hypertext Transfer Protocol (HTTP) is an application-level protocol for distributed, collaborative, hypermedia information systems. HTTP has been in use by the World Wide Web global information initiative since 1990. This document is Part 6 of the seven-part specification that defines the protocol referred to as &#34;HTTP/1.1&#34; and, taken together, obsoletes RFC 2616. Part 6 defines requirements on HTTP caches and the associated header fields that control cache behavior or indicate cacheable response messages.">
     350      <meta name="description" content="The Hypertext Transfer Protocol (HTTP) is an application-level protocol for distributed, collaborative, hypermedia information systems. HTTP has been in use by the World Wide Web global information initiative since 1990. This document is Part 6 of the seven-part specification that defines the protocol referred to as &#34;HTTP/1.1&#34; and, taken together, obsoletes RFC 2616. Part 6 defines requirements on HTTP caches and the associated header fields that control cache behavior or indicate cacheable response messages.">
    359351   </head>
    360352   <body>
    361       <table summary="header information" class="header" border="0" cellpadding="1" cellspacing="1">
    362          <tr>
    363             <td class="header left">Network Working Group</td>
    364             <td class="header right">R. Fielding, Editor</td>
    365          </tr>
    366          <tr>
    367             <td class="header left">Internet Draft</td>
    368             <td class="header right">Day Software</td>
    369          </tr>
    370          <tr>
    371             <td class="header left">
    372                &lt;draft-ietf-httpbis-p6-cache-00&gt;
    373                
    374             </td>
    375             <td class="header right">J. Gettys</td>
    376          </tr>
    377          <tr>
    378             <td class="header left">Obsoletes: <a href="http://tools.ietf.org/html/rfc2068">2068</a>,
    379                <a href="http://tools.ietf.org/html/rfc2616">2616</a> (if approved)
    380             </td>
    381             <td class="header right">One Laptop per Child</td>
    382          </tr>
    383          <tr>
    384             <td class="header left">Intended status: Standards Track</td>
    385             <td class="header right">J. Mogul</td>
    386          </tr>
    387          <tr>
    388             <td class="header left">Expires: June 2008</td>
    389             <td class="header right">HP</td>
    390          </tr>
    391          <tr>
    392             <td class="header left"></td>
    393             <td class="header right">H. Frystyk</td>
    394          </tr>
    395          <tr>
    396             <td class="header left"></td>
    397             <td class="header right">Microsoft</td>
    398          </tr>
    399          <tr>
    400             <td class="header left"></td>
    401             <td class="header right">L. Masinter</td>
    402          </tr>
    403          <tr>
    404             <td class="header left"></td>
    405             <td class="header right">Adobe Systems</td>
    406          </tr>
    407          <tr>
    408             <td class="header left"></td>
    409             <td class="header right">P. Leach</td>
    410          </tr>
    411          <tr>
    412             <td class="header left"></td>
    413             <td class="header right">Microsoft</td>
    414          </tr>
    415          <tr>
    416             <td class="header left"></td>
    417             <td class="header right">T. Berners-Lee</td>
    418          </tr>
    419          <tr>
    420             <td class="header left"></td>
    421             <td class="header right">W3C/MIT</td>
    422          </tr>
    423          <tr>
    424             <td class="header left"></td>
    425             <td class="header right">December 20, 2007</td>
    426          </tr>
     353      <table class="header">
     354         <tbody>
     355            <tr>
     356               <td class="left">Network Working Group</td>
     357               <td class="right">R. Fielding, Editor</td>
     358            </tr>
     359            <tr>
     360               <td class="left">Internet-Draft</td>
     361               <td class="right">Day Software</td>
     362            </tr>
     363            <tr>
     364               <td class="left">Obsoletes: <a href="http://tools.ietf.org/html/rfc2068">2068</a>, <a href="http://tools.ietf.org/html/rfc2616">2616</a> (if approved)
     365               </td>
     366               <td class="right">J. Gettys</td>
     367            </tr>
     368            <tr>
     369               <td class="left">Intended status: Standards Track</td>
     370               <td class="right">One Laptop per Child</td>
     371            </tr>
     372            <tr>
     373               <td class="left">Expires: June 22, 2008</td>
     374               <td class="right">J. Mogul</td>
     375            </tr>
     376            <tr>
     377               <td class="left"></td>
     378               <td class="right">HP</td>
     379            </tr>
     380            <tr>
     381               <td class="left"></td>
     382               <td class="right">H. Frystyk</td>
     383            </tr>
     384            <tr>
     385               <td class="left"></td>
     386               <td class="right">Microsoft</td>
     387            </tr>
     388            <tr>
     389               <td class="left"></td>
     390               <td class="right">L. Masinter</td>
     391            </tr>
     392            <tr>
     393               <td class="left"></td>
     394               <td class="right">Adobe Systems</td>
     395            </tr>
     396            <tr>
     397               <td class="left"></td>
     398               <td class="right">P. Leach</td>
     399            </tr>
     400            <tr>
     401               <td class="left"></td>
     402               <td class="right">Microsoft</td>
     403            </tr>
     404            <tr>
     405               <td class="left"></td>
     406               <td class="right">T. Berners-Lee</td>
     407            </tr>
     408            <tr>
     409               <td class="left"></td>
     410               <td class="right">W3C/MIT</td>
     411            </tr>
     412            <tr>
     413               <td class="left"></td>
     414               <td class="right">December 20, 2007</td>
     415            </tr>
     416         </tbody>
    427417      </table>
    428418      <p class="title">HTTP/1.1, part 6: Caching<br><span class="filename">draft-ietf-httpbis-p6-cache-00</span></p>
     
    439429         in progress”.
    440430      </p>
    441       <p>The list of current Internet-Drafts can be accessed at &lt;<a href="http://www.ietf.org/ietf/1id-abstracts.txt">http://www.ietf.org/ietf/1id-abstracts.txt</a>&gt;.
    442       </p>
    443       <p>The list of Internet-Draft Shadow Directories can be accessed at &lt;<a href="http://www.ietf.org/shadow.html">http://www.ietf.org/shadow.html</a>&gt;.
    444       </p>
    445       <p>This Internet-Draft will expire in June 2008.</p>
     431      <p>The list of current Internet-Drafts can be accessed at <a href="http://www.ietf.org/ietf/1id-abstracts.txt">http://www.ietf.org/ietf/1id-abstracts.txt</a>.
     432      </p>
     433      <p>The list of Internet-Draft Shadow Directories can be accessed at <a href="http://www.ietf.org/shadow.html">http://www.ietf.org/shadow.html</a>.
     434      </p>
     435      <p>This Internet-Draft will expire on June 22, 2008.</p>
    446436      <h1 id="rfc.abstract"><a href="#rfc.abstract">Abstract</a></h1>
    447437      <p>The Hypertext Transfer Protocol (HTTP) is an application-level protocol for distributed, collaborative, hypermedia information
     
    465455      <h1 class="np" id="rfc.toc"><a href="#rfc.toc">Table of Contents</a></h1>
    466456      <ul class="toc">
    467          <li class="tocline0">1.&nbsp;&nbsp;&nbsp;<a href="#introduction">Introduction</a><ul class="toc">
    468                <li class="tocline1">1.1&nbsp;&nbsp;&nbsp;<a href="#intro.terminology">Terminology</a></li>
    469                <li class="tocline1">1.2&nbsp;&nbsp;&nbsp;<a href="#delta.seconds">Delta Seconds</a></li>
     457         <li>1.&nbsp;&nbsp;&nbsp;<a href="#introduction">Introduction</a><ul>
     458               <li>1.1&nbsp;&nbsp;&nbsp;<a href="#intro.terminology">Terminology</a></li>
     459               <li>1.2&nbsp;&nbsp;&nbsp;<a href="#delta.seconds">Delta Seconds</a></li>
    470460            </ul>
    471461         </li>
    472          <li class="tocline0">2.&nbsp;&nbsp;&nbsp;<a href="#caching">Caching in HTTP</a><ul class="toc">
    473                <li class="tocline1">2.1&nbsp;&nbsp;&nbsp;<a href="#caching.overview">Overview</a><ul class="toc">
    474                      <li class="tocline1">2.1.1&nbsp;&nbsp;&nbsp;<a href="#cache.correctness">Cache Correctness</a></li>
    475                      <li class="tocline1">2.1.2&nbsp;&nbsp;&nbsp;<a href="#warnings">Warnings</a></li>
    476                      <li class="tocline1">2.1.3&nbsp;&nbsp;&nbsp;<a href="#cache-control.mechanisms">Cache-control Mechanisms</a></li>
    477                      <li class="tocline1">2.1.4&nbsp;&nbsp;&nbsp;<a href="#explicit.ua.warnings">Explicit User Agent Warnings</a></li>
    478                      <li class="tocline1">2.1.5&nbsp;&nbsp;&nbsp;<a href="#exceptions.to.the.rules.and.warnings">Exceptions to the Rules and Warnings</a></li>
    479                      <li class="tocline1">2.1.6&nbsp;&nbsp;&nbsp;<a href="#client-controlled.behavior">Client-controlled Behavior</a></li>
     462         <li>2.&nbsp;&nbsp;&nbsp;<a href="#caching">Caching in HTTP</a><ul>
     463               <li>2.1&nbsp;&nbsp;&nbsp;<a href="#caching.overview">Overview</a><ul>
     464                     <li>2.1.1&nbsp;&nbsp;&nbsp;<a href="#cache.correctness">Cache Correctness</a></li>
     465                     <li>2.1.2&nbsp;&nbsp;&nbsp;<a href="#warnings">Warnings</a></li>
     466                     <li>2.1.3&nbsp;&nbsp;&nbsp;<a href="#cache-control.mechanisms">Cache-control Mechanisms</a></li>
     467                     <li>2.1.4&nbsp;&nbsp;&nbsp;<a href="#explicit.ua.warnings">Explicit User Agent Warnings</a></li>
     468                     <li>2.1.5&nbsp;&nbsp;&nbsp;<a href="#exceptions.to.the.rules.and.warnings">Exceptions to the Rules and Warnings</a></li>
     469                     <li>2.1.6&nbsp;&nbsp;&nbsp;<a href="#client-controlled.behavior">Client-controlled Behavior</a></li>
    480470                  </ul>
    481471               </li>
    482                <li class="tocline1">2.2&nbsp;&nbsp;&nbsp;<a href="#expiration.model">Expiration Model</a><ul class="toc">
    483                      <li class="tocline1">2.2.1&nbsp;&nbsp;&nbsp;<a href="#server-specified.expiration">Server-Specified Expiration</a></li>
    484                      <li class="tocline1">2.2.2&nbsp;&nbsp;&nbsp;<a href="#heuristic.expiration">Heuristic Expiration</a></li>
    485                      <li class="tocline1">2.2.3&nbsp;&nbsp;&nbsp;<a href="#age.calculations">Age Calculations</a></li>
    486                      <li class="tocline1">2.2.4&nbsp;&nbsp;&nbsp;<a href="#expiration.calculations">Expiration Calculations</a></li>
    487                      <li class="tocline1">2.2.5&nbsp;&nbsp;&nbsp;<a href="#disambiguating.expiration.values">Disambiguating Expiration Values</a></li>
    488                      <li class="tocline1">2.2.6&nbsp;&nbsp;&nbsp;<a href="#disambiguating.multiple.responses">Disambiguating Multiple Responses</a></li>
     472               <li>2.2&nbsp;&nbsp;&nbsp;<a href="#expiration.model">Expiration Model</a><ul>
     473                     <li>2.2.1&nbsp;&nbsp;&nbsp;<a href="#server-specified.expiration">Server-Specified Expiration</a></li>
     474                     <li>2.2.2&nbsp;&nbsp;&nbsp;<a href="#heuristic.expiration">Heuristic Expiration</a></li>
     475                     <li>2.2.3&nbsp;&nbsp;&nbsp;<a href="#age.calculations">Age Calculations</a></li>
     476                     <li>2.2.4&nbsp;&nbsp;&nbsp;<a href="#expiration.calculations">Expiration Calculations</a></li>
     477                     <li>2.2.5&nbsp;&nbsp;&nbsp;<a href="#disambiguating.expiration.values">Disambiguating Expiration Values</a></li>
     478                     <li>2.2.6&nbsp;&nbsp;&nbsp;<a href="#disambiguating.multiple.responses">Disambiguating Multiple Responses</a></li>
    489479                  </ul>
    490480               </li>
    491                <li class="tocline1">2.3&nbsp;&nbsp;&nbsp;<a href="#validation.model">Validation Model</a><ul class="toc">
    492                      <li class="tocline1">2.3.1&nbsp;&nbsp;&nbsp;<a href="#last-modified.dates">Last-Modified Dates</a></li>
    493                      <li class="tocline1">2.3.2&nbsp;&nbsp;&nbsp;<a href="#entity.tag.cache.validators">Entity Tag Cache Validators</a></li>
    494                      <li class="tocline1">2.3.3&nbsp;&nbsp;&nbsp;<a href="#non-validating.conditionals">Non-validating Conditionals</a></li>
     481               <li>2.3&nbsp;&nbsp;&nbsp;<a href="#validation.model">Validation Model</a><ul>
     482                     <li>2.3.1&nbsp;&nbsp;&nbsp;<a href="#last-modified.dates">Last-Modified Dates</a></li>
     483                     <li>2.3.2&nbsp;&nbsp;&nbsp;<a href="#entity.tag.cache.validators">Entity Tag Cache Validators</a></li>
     484                     <li>2.3.3&nbsp;&nbsp;&nbsp;<a href="#non-validating.conditionals">Non-validating Conditionals</a></li>
    495485                  </ul>
    496486               </li>
    497                <li class="tocline1">2.4&nbsp;&nbsp;&nbsp;<a href="#response.cacheability">Response Cacheability</a></li>
    498                <li class="tocline1">2.5&nbsp;&nbsp;&nbsp;<a href="#constructing.responses.from.caches">Constructing Responses From Caches</a><ul class="toc">
    499                      <li class="tocline1">2.5.1&nbsp;&nbsp;&nbsp;<a href="#end-to-end.and.hop-by-hop.headers">End-to-end and Hop-by-hop Headers</a></li>
    500                      <li class="tocline1">2.5.2&nbsp;&nbsp;&nbsp;<a href="#non-modifiable.headers">Non-modifiable Headers</a></li>
    501                      <li class="tocline1">2.5.3&nbsp;&nbsp;&nbsp;<a href="#combining.headers">Combining Headers</a></li>
     487               <li>2.4&nbsp;&nbsp;&nbsp;<a href="#response.cacheability">Response Cacheability</a></li>
     488               <li>2.5&nbsp;&nbsp;&nbsp;<a href="#constructing.responses.from.caches">Constructing Responses From Caches</a><ul>
     489                     <li>2.5.1&nbsp;&nbsp;&nbsp;<a href="#end-to-end.and.hop-by-hop.headers">End-to-end and Hop-by-hop Headers</a></li>
     490                     <li>2.5.2&nbsp;&nbsp;&nbsp;<a href="#non-modifiable.headers">Non-modifiable Headers</a></li>
     491                     <li>2.5.3&nbsp;&nbsp;&nbsp;<a href="#combining.headers">Combining Headers</a></li>
    502492                  </ul>
    503493               </li>
    504                <li class="tocline1">2.6&nbsp;&nbsp;&nbsp;<a href="#caching.negotiated.responses">Caching Negotiated Responses</a></li>
    505                <li class="tocline1">2.7&nbsp;&nbsp;&nbsp;<a href="#shared.and.non-shared.caches">Shared and Non-Shared Caches</a></li>
    506                <li class="tocline1">2.8&nbsp;&nbsp;&nbsp;<a href="#errors.or.incomplete.response.cache.behavior">Errors or Incomplete Response Cache Behavior</a></li>
    507                <li class="tocline1">2.9&nbsp;&nbsp;&nbsp;<a href="#side.effects.of.get.and.head">Side Effects of GET and HEAD</a></li>
    508                <li class="tocline1">2.10&nbsp;&nbsp;&nbsp;<a href="#invalidation.after.updates.or.deletions">Invalidation After Updates or Deletions</a></li>
    509                <li class="tocline1">2.11&nbsp;&nbsp;&nbsp;<a href="#write-through.mandatory">Write-Through Mandatory</a></li>
    510                <li class="tocline1">2.12&nbsp;&nbsp;&nbsp;<a href="#cache.replacement">Cache Replacement</a></li>
    511                <li class="tocline1">2.13&nbsp;&nbsp;&nbsp;<a href="#history.lists">History Lists</a></li>
     494               <li>2.6&nbsp;&nbsp;&nbsp;<a href="#caching.negotiated.responses">Caching Negotiated Responses</a></li>
     495               <li>2.7&nbsp;&nbsp;&nbsp;<a href="#shared.and.non-shared.caches">Shared and Non-Shared Caches</a></li>
     496               <li>2.8&nbsp;&nbsp;&nbsp;<a href="#errors.or.incomplete.response.cache.behavior">Errors or Incomplete Response Cache Behavior</a></li>
     497               <li>2.9&nbsp;&nbsp;&nbsp;<a href="#side.effects.of.get.and.head">Side Effects of GET and HEAD</a></li>
     498               <li>2.10&nbsp;&nbsp;&nbsp;<a href="#invalidation.after.updates.or.deletions">Invalidation After Updates or Deletions</a></li>
     499               <li>2.11&nbsp;&nbsp;&nbsp;<a href="#write-through.mandatory">Write-Through Mandatory</a></li>
     500               <li>2.12&nbsp;&nbsp;&nbsp;<a href="#cache.replacement">Cache Replacement</a></li>
     501               <li>2.13&nbsp;&nbsp;&nbsp;<a href="#history.lists">History Lists</a></li>
    512502            </ul>
    513503         </li>
    514          <li class="tocline0">3.&nbsp;&nbsp;&nbsp;<a href="#header.fields">Header Field Definitions</a><ul class="toc">
    515                <li class="tocline1">3.1&nbsp;&nbsp;&nbsp;<a href="#header.age">Age</a></li>
    516                <li class="tocline1">3.2&nbsp;&nbsp;&nbsp;<a href="#header.cache-control">Cache-Control</a><ul class="toc">
    517                      <li class="tocline1">3.2.1&nbsp;&nbsp;&nbsp;<a href="#what.is.cacheable">What is Cacheable</a></li>
    518                      <li class="tocline1">3.2.2&nbsp;&nbsp;&nbsp;<a href="#what.may.be.stored.by.caches">What May be Stored by Caches</a></li>
    519                      <li class="tocline1">3.2.3&nbsp;&nbsp;&nbsp;<a href="#modifications.of.the.basic.expiration.mechanism">Modifications of the Basic Expiration Mechanism</a></li>
    520                      <li class="tocline1">3.2.4&nbsp;&nbsp;&nbsp;<a href="#cache.revalidation.and.reload.controls">Cache Revalidation and Reload Controls</a></li>
    521                      <li class="tocline1">3.2.5&nbsp;&nbsp;&nbsp;<a href="#no-transform.directive">No-Transform Directive</a></li>
    522                      <li class="tocline1">3.2.6&nbsp;&nbsp;&nbsp;<a href="#cache.control.extensions">Cache Control Extensions</a></li>
     504         <li>3.&nbsp;&nbsp;&nbsp;<a href="#header.fields">Header Field Definitions</a><ul>
     505               <li>3.1&nbsp;&nbsp;&nbsp;<a href="#header.age">Age</a></li>
     506               <li>3.2&nbsp;&nbsp;&nbsp;<a href="#header.cache-control">Cache-Control</a><ul>
     507                     <li>3.2.1&nbsp;&nbsp;&nbsp;<a href="#what.is.cacheable">What is Cacheable</a></li>
     508                     <li>3.2.2&nbsp;&nbsp;&nbsp;<a href="#what.may.be.stored.by.caches">What May be Stored by Caches</a></li>
     509                     <li>3.2.3&nbsp;&nbsp;&nbsp;<a href="#modifications.of.the.basic.expiration.mechanism">Modifications of the Basic Expiration Mechanism</a></li>
     510                     <li>3.2.4&nbsp;&nbsp;&nbsp;<a href="#cache.revalidation.and.reload.controls">Cache Revalidation and Reload Controls</a></li>
     511                     <li>3.2.5&nbsp;&nbsp;&nbsp;<a href="#no-transform.directive">No-Transform Directive</a></li>
     512                     <li>3.2.6&nbsp;&nbsp;&nbsp;<a href="#cache.control.extensions">Cache Control Extensions</a></li>
    523513                  </ul>
    524514               </li>
    525                <li class="tocline1">3.3&nbsp;&nbsp;&nbsp;<a href="#header.expires">Expires</a></li>
    526                <li class="tocline1">3.4&nbsp;&nbsp;&nbsp;<a href="#header.pragma">Pragma</a></li>
    527                <li class="tocline1">3.5&nbsp;&nbsp;&nbsp;<a href="#header.vary">Vary</a></li>
    528                <li class="tocline1">3.6&nbsp;&nbsp;&nbsp;<a href="#header.warning">Warning</a></li>
     515               <li>3.3&nbsp;&nbsp;&nbsp;<a href="#header.expires">Expires</a></li>
     516               <li>3.4&nbsp;&nbsp;&nbsp;<a href="#header.pragma">Pragma</a></li>
     517               <li>3.5&nbsp;&nbsp;&nbsp;<a href="#header.vary">Vary</a></li>
     518               <li>3.6&nbsp;&nbsp;&nbsp;<a href="#header.warning">Warning</a></li>
    529519            </ul>
    530520         </li>
    531          <li class="tocline0">4.&nbsp;&nbsp;&nbsp;<a href="#IANA.considerations">IANA Considerations</a></li>
    532          <li class="tocline0">5.&nbsp;&nbsp;&nbsp;<a href="#security.considerations">Security Considerations</a></li>
    533          <li class="tocline0">6.&nbsp;&nbsp;&nbsp;<a href="#ack">Acknowledgments</a></li>
    534          <li class="tocline0">7.&nbsp;&nbsp;&nbsp;<a href="#rfc.references">References</a></li>
    535          <li class="tocline0"><a href="#rfc.authors">Authors' Addresses</a></li>
    536          <li class="tocline0">A.&nbsp;&nbsp;&nbsp;<a href="#changes.from.rfc.2068">Changes from RFC 2068</a></li>
    537          <li class="tocline0"><a href="#rfc.ipr">Intellectual Property and Copyright Statements</a></li>
    538          <li class="tocline0"><a href="#rfc.index">Index</a></li>
     521         <li>4.&nbsp;&nbsp;&nbsp;<a href="#IANA.considerations">IANA Considerations</a></li>
     522         <li>5.&nbsp;&nbsp;&nbsp;<a href="#security.considerations">Security Considerations</a></li>
     523         <li>6.&nbsp;&nbsp;&nbsp;<a href="#ack">Acknowledgments</a></li>
     524         <li>7.&nbsp;&nbsp;&nbsp;<a href="#rfc.references">References</a></li>
     525         <li><a href="#rfc.authors">Authors' Addresses</a></li>
     526         <li>A.&nbsp;&nbsp;&nbsp;<a href="#changes.from.rfc.2068">Changes from RFC 2068</a></li>
     527         <li><a href="#rfc.index">Index</a></li>
     528         <li><a href="#rfc.ipr">Intellectual Property and Copyright Statements</a></li>
    539529      </ul>
    540530      <h1 id="rfc.section.1" class="np"><a href="#rfc.section.1">1.</a>&nbsp;<a id="introduction" href="#introduction">Introduction</a></h1>
     
    546536      <p id="rfc.section.1.1.p.2"> <span id="rfc.iref.c.1"></span>  <dfn>cache</dfn> 
    547537      </p>
    548       <dl class="empty">
    549          <dd>A program's local store of response messages and the subsystem that controls its message storage, retrieval, and deletion.
     538      <ul class="empty">
     539         <li>A program's local store of response messages and the subsystem that controls its message storage, retrieval, and deletion.
    550540            A cache stores cacheable responses in order to reduce the response time and network bandwidth consumption on future, equivalent
    551541            requests. Any client or server may include a cache, though a cache cannot be used by a server that is acting as a tunnel.
    552          </dd>
    553       </dl>
     542         </li>
     543      </ul>
    554544      <p id="rfc.section.1.1.p.3"> <span id="rfc.iref.c.2"></span>  <dfn>cacheable</dfn> 
    555545      </p>
    556       <dl class="empty">
    557          <dd>A response is cacheable if a cache is allowed to store a copy of the response message for use in answering subsequent requests.
     546      <ul class="empty">
     547         <li>A response is cacheable if a cache is allowed to store a copy of the response message for use in answering subsequent requests.
    558548            The rules for determining the cacheability of HTTP responses are defined in <a href="#caching" title="Caching in HTTP">Section&nbsp;2</a>. Even if a resource is cacheable, there may be additional constraints on whether a cache can use the cached copy for a particular
    559549            request.
    560          </dd>
    561       </dl>
     550         </li>
     551      </ul>
    562552      <p id="rfc.section.1.1.p.4"> <span id="rfc.iref.f.1"></span>  <dfn>first-hand</dfn> 
    563553      </p>
    564       <dl class="empty">
    565          <dd>A response is first-hand if it comes directly and without unnecessary delay from the origin server, perhaps via one or more
     554      <ul class="empty">
     555         <li>A response is first-hand if it comes directly and without unnecessary delay from the origin server, perhaps via one or more
    566556            proxies. A response is also first-hand if its validity has just been checked directly with the origin server.
    567          </dd>
    568       </dl>
     557         </li>
     558      </ul>
    569559      <p id="rfc.section.1.1.p.5"> <span id="rfc.iref.e.1"></span>  <dfn>explicit expiration time</dfn> 
    570560      </p>
    571       <dl class="empty">
    572          <dd>The time at which the origin server intends that an entity should no longer be returned by a cache without further validation.</dd>
    573       </dl>
     561      <ul class="empty">
     562         <li>The time at which the origin server intends that an entity should no longer be returned by a cache without further validation.</li>
     563      </ul>
    574564      <p id="rfc.section.1.1.p.6"> <span id="rfc.iref.h.1"></span>  <dfn>heuristic expiration time</dfn> 
    575565      </p>
    576       <dl class="empty">
    577          <dd>An expiration time assigned by a cache when no explicit expiration time is available.</dd>
    578       </dl>
     566      <ul class="empty">
     567         <li>An expiration time assigned by a cache when no explicit expiration time is available.</li>
     568      </ul>
    579569      <p id="rfc.section.1.1.p.7"> <span id="rfc.iref.a.1"></span>  <dfn>age</dfn> 
    580570      </p>
    581       <dl class="empty">
    582          <dd>The age of a response is the time since it was sent by, or successfully validated with, the origin server.</dd>
    583       </dl>
     571      <ul class="empty">
     572         <li>The age of a response is the time since it was sent by, or successfully validated with, the origin server.</li>
     573      </ul>
    584574      <p id="rfc.section.1.1.p.8"> <span id="rfc.iref.f.2"></span>  <dfn>freshness lifetime</dfn> 
    585575      </p>
    586       <dl class="empty">
    587          <dd>The length of time between the generation of a response and its expiration time.</dd>
    588       </dl>
     576      <ul class="empty">
     577         <li>The length of time between the generation of a response and its expiration time.</li>
     578      </ul>
    589579      <p id="rfc.section.1.1.p.9"> <span id="rfc.iref.f.3"></span>  <dfn>fresh</dfn> 
    590580      </p>
    591       <dl class="empty">
    592          <dd>A response is fresh if its age has not yet exceeded its freshness lifetime.</dd>
    593       </dl>
     581      <ul class="empty">
     582         <li>A response is fresh if its age has not yet exceeded its freshness lifetime.</li>
     583      </ul>
    594584      <p id="rfc.section.1.1.p.10"> <span id="rfc.iref.s.1"></span>  <dfn>stale</dfn> 
    595585      </p>
    596       <dl class="empty">
    597          <dd>A response is stale if its age has passed its freshness lifetime.</dd>
    598       </dl>
     586      <ul class="empty">
     587         <li>A response is stale if its age has passed its freshness lifetime.</li>
     588      </ul>
    599589      <p id="rfc.section.1.1.p.11"> <span id="rfc.iref.s.2"></span>  <dfn>semantically transparent</dfn> 
    600590      </p>
    601       <dl class="empty">
    602          <dd>A cache behaves in a "semantically transparent" manner, with respect to a particular response, when its use affects neither
     591      <ul class="empty">
     592         <li>A cache behaves in a "semantically transparent" manner, with respect to a particular response, when its use affects neither
    603593            the requesting client nor the origin server, except to improve performance. When a cache is semantically transparent, the
    604594            client receives exactly the same response (except for hop-by-hop headers) that it would have received had its request been
    605595            handled directly by the origin server.
    606          </dd>
    607       </dl>
     596         </li>
     597      </ul>
    608598      <p id="rfc.section.1.1.p.12"> <span id="rfc.iref.v.1"></span>  <dfn>validator</dfn> 
    609599      </p>
    610       <dl class="empty">
    611          <dd>A protocol element (e.g., an entity tag or a Last-Modified time) that is used to find out whether a cache entry is an equivalent
     600      <ul class="empty">
     601         <li>A protocol element (e.g., an entity tag or a Last-Modified time) that is used to find out whether a cache entry is an equivalent
    612602            copy of an entity.
    613          </dd>
    614       </dl>
     603         </li>
     604      </ul>
    615605      <h2 id="rfc.section.1.2"><a href="#rfc.section.1.2">1.2</a>&nbsp;<a id="delta.seconds" href="#delta.seconds">Delta Seconds</a></h2>
    616606      <p id="rfc.section.1.2.p.1">Some HTTP header fields allow a time value to be specified as an integer number of seconds, represented in decimal, after
     
    648638      </ol>
    649639      <p id="rfc.section.2.1.p.5">A basic principle is that it must be possible for the clients to detect any potential relaxation of semantic transparency. </p>
    650       <dl class="empty">
    651          <dd> <b>Note:</b> The server, cache, or client implementor might be faced with design decisions not explicitly discussed in this specification.
     640      <ul class="empty">
     641         <li> <b>Note:</b> The server, cache, or client implementor might be faced with design decisions not explicitly discussed in this specification.
    652642            If a decision might affect semantic transparency, the implementor ought to err on the side of maintaining transparency unless
    653643            a careful and complete analysis shows significant benefits in breaking transparency.
    654          </dd>
    655       </dl>
     644         </li>
     645      </ul>
    656646      <h3 id="rfc.section.2.1.1"><a href="#rfc.section.2.1.1">2.1.1</a>&nbsp;<a id="cache.correctness" href="#cache.correctness">Cache Correctness</a></h3>
    657647      <p id="rfc.section.2.1.1.p.1">A correct cache <em class="bcp14">MUST</em> respond to a request with the most up-to-date response held by the cache that is appropriate to the request (see sections <a href="#disambiguating.expiration.values" title="Disambiguating Expiration Values">2.2.5</a>, <a href="#disambiguating.multiple.responses" title="Disambiguating Multiple Responses">2.2.6</a>, and <a href="#cache.replacement" title="Cache Replacement">2.12</a>) which meets one of the following conditions:
     
    925915         either that a method be performed if and only if a validator matches or if and only if no validators match.
    926916      </p>
    927       <dl class="empty">
    928          <dd> <b>Note:</b> a response that lacks a validator may still be cached, and served from cache until it expires, unless this is explicitly prohibited
     917      <ul class="empty">
     918         <li> <b>Note:</b> a response that lacks a validator may still be cached, and served from cache until it expires, unless this is explicitly prohibited
    929919            by a cache-control directive. However, a cache cannot do a conditional retrieval if it does not have a validator for the entity,
    930920            which means it will not be refreshable after it expires.
    931          </dd>
    932       </dl>
     921         </li>
     922      </ul>
    933923      <h3 id="rfc.section.2.3.1"><a href="#rfc.section.2.3.1">2.3.1</a>&nbsp;<a id="last-modified.dates" href="#last-modified.dates">Last-Modified Dates</a></h3>
    934924      <p id="rfc.section.2.3.1.p.1">The Last-Modified entity-header field value is often used as a cache validator. In simple terms, a cache entry is considered
     
    954944         such a response was taken from a cache by comparing the Date header to the current time.
    955945      </p>
    956       <dl class="empty">
    957          <dd> <b>Note:</b> some HTTP/1.0 caches are known to violate this expectation without providing any Warning.
    958          </dd>
    959       </dl>
     946      <ul class="empty">
     947         <li> <b>Note:</b> some HTTP/1.0 caches are known to violate this expectation without providing any Warning.
     948         </li>
     949      </ul>
    960950      <p id="rfc.section.2.4.p.2">However, in some cases it might be inappropriate for a cache to retain an entity, or to return it in response to a subsequent
    961951         request. This might be because absolute semantic transparency is deemed necessary by the service author, or because of security
     
    10291019      <p id="rfc.section.2.5.2.p.6">A non-transparent proxy <em class="bcp14">MAY</em> modify or add these fields to a message that does not include no-transform, but if it does so, it <em class="bcp14">MUST</em> add a Warning 214 (Transformation applied) if one does not already appear in the message (see <a href="#header.warning" id="rfc.xref.header.warning.4" title="Warning">Section&nbsp;3.6</a>).
    10301020      </p>
    1031       <dl class="empty">
    1032          <dd>Warning: unnecessary modification of end-to-end headers might cause authentication failures if stronger authentication mechanisms
     1021      <ul class="empty">
     1022         <li>Warning: unnecessary modification of end-to-end headers might cause authentication failures if stronger authentication mechanisms
    10331023            are introduced in later versions of HTTP. Such authentication mechanisms <em class="bcp14">MAY</em> rely on the values of header fields not listed here.
    1034          </dd>
    1035       </dl>
     1024         </li>
     1025      </ul>
    10361026      <p id="rfc.section.2.5.2.p.7">The Content-Length field of a request or response is added or deleted according to the rules in <a href="p1-messaging.html#message.length" title="Message Length">Section 4.4</a> of <a href="#Part1" id="rfc.xref.Part1.3"><cite title="HTTP/1.1, part 1: URIs, Connections, and Message Parsing">[Part1]</cite></a>. A transparent proxy <em class="bcp14">MUST</em> preserve the entity-length (<a href="p3-payload.html#entity.length" title="Entity Length">Section 3.2.2</a> of <a href="#Part3" id="rfc.xref.Part3.1"><cite title="HTTP/1.1, part 3: Message Payload and Content Negotiation">[Part3]</cite></a>) of the entity-body, although it <em class="bcp14">MAY</em> change the transfer-length (<a href="p1-messaging.html#message.length" title="Message Length">Section 4.4</a> of <a href="#Part1" id="rfc.xref.Part1.4"><cite title="HTTP/1.1, part 1: URIs, Connections, and Message Parsing">[Part1]</cite></a>).
    10371027      </p>
     
    10601050         stored with the cache entry (except for stored Warning headers with warn-code 1xx, which are deleted even if not overridden).
    10611051      </p>
    1062       <dl class="empty">
    1063          <dd> <b>Note:</b> this rule allows an origin server to use a 304 (Not Modified) or a 206 (Partial Content) response to update any header associated
     1052      <ul class="empty">
     1053         <li> <b>Note:</b> this rule allows an origin server to use a 304 (Not Modified) or a 206 (Partial Content) response to update any header associated
    10641054            with a previous response for the same entity or sub-ranges thereof, although it might not always be meaningful or correct
    10651055            to do so. This rule does not allow an origin server to use a 304 (Not Modified) or a 206 (Partial Content) response to entirely
    10661056            delete a header that it had provided with a previous response.
    1067          </dd>
    1068       </dl>
     1057         </li>
     1058      </ul>
    10691059      <h2 id="rfc.section.2.6"><a href="#rfc.section.2.6">2.6</a>&nbsp;<a id="caching.negotiated.responses" href="#caching.negotiated.responses">Caching Negotiated Responses</a></h2>
    10701060      <p id="rfc.section.2.6.p.1">Use of server-driven content negotiation (<a href="p3-payload.html#server-driven.negotiation" title="Server-driven Negotiation">Section 4.1</a> of <a href="#Part3" id="rfc.xref.Part3.2"><cite title="HTTP/1.1, part 3: Message Payload and Content Negotiation">[Part3]</cite></a>), as indicated by the presence of a Vary header field in a response, alters the conditions and procedure by which a cache
     
    11601150         to be returned. If it inserts the new response into cache storage the rules in <a href="#combining.headers" title="Combining Headers">Section&nbsp;2.5.3</a> apply.
    11611151      </p>
    1162       <dl class="empty">
    1163          <dd> <b>Note:</b> a new response that has an older Date header value than existing cached responses is not cacheable.
    1164          </dd>
    1165       </dl>
     1152      <ul class="empty">
     1153         <li> <b>Note:</b> a new response that has an older Date header value than existing cached responses is not cacheable.
     1154         </li>
     1155      </ul>
    11661156      <h2 id="rfc.section.2.13"><a href="#rfc.section.2.13">2.13</a>&nbsp;<a id="history.lists" href="#history.lists">History Lists</a></h2>
    11671157      <p id="rfc.section.2.13.p.1">User agents often have history mechanisms, such as "Back" buttons and history lists, which can be used to redisplay an entity
     
    11751165      </p>
    11761166      <p id="rfc.section.2.13.p.4">This is not to be construed to prohibit the history mechanism from telling the user that a view might be stale. </p>
    1177       <dl class="empty">
    1178          <dd> <b>Note:</b> if history list mechanisms unnecessarily prevent users from viewing stale resources, this will tend to force service authors
     1167      <ul class="empty">
     1168         <li> <b>Note:</b> if history list mechanisms unnecessarily prevent users from viewing stale resources, this will tend to force service authors
    11791169            to avoid using HTTP expiration controls and cache controls when they would otherwise like to. Service authors may consider
    11801170            it important that users not be presented with error messages or warning messages when they use navigation controls (such as
     
    11821172            user interface considerations may force service authors to resort to other means of preventing caching (e.g. "once-only" URLs)
    11831173            in order not to suffer the effects of improperly functioning history mechanisms.
    1184          </dd>
    1185       </dl>
     1174         </li>
     1175      </ul>
    11861176      <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>
    11871177      <p id="rfc.section.3.p.1">This section defines the syntax and semantics of all standard HTTP/1.1 header fields. For entity-header fields, both sender
     
    12091199         is to be given in the response.
    12101200      </p>
    1211       <dl class="empty">
    1212          <dd>Note that HTTP/1.0 caches might not implement Cache-Control and might only implement Pragma: no-cache (see <a href="#header.pragma" id="rfc.xref.header.pragma.1" title="Pragma">Section&nbsp;3.4</a>).
    1213          </dd>
    1214       </dl>
     1201      <ul class="empty">
     1202         <li>Note that HTTP/1.0 caches might not implement Cache-Control and might only implement Pragma: no-cache (see <a href="#header.pragma" id="rfc.xref.header.pragma.1" title="Pragma">Section&nbsp;3.4</a>).
     1203         </li>
     1204      </ul>
    12151205      <p id="rfc.section.3.2.p.2">Cache directives <em class="bcp14">MUST</em> be passed through by a proxy or gateway application, regardless of their significance to that application, since the directives
    12161206         might be applicable to all recipients along the request/response chain. It is not possible to specify a cache-directive for
     
    12661256      <p id="rfc.section.3.2.1.p.2"> <span id="rfc.iref.c.4"></span>  <span id="rfc.iref.p.1"></span> public
    12671257      </p>
    1268       <dl class="empty">
    1269          <dd>Indicates that the response <em class="bcp14">MAY</em> be cached by any cache, even if it would normally be non-cacheable or cacheable only within a non-shared cache. (See also
     1258      <ul class="empty">
     1259         <li>Indicates that the response <em class="bcp14">MAY</em> be cached by any cache, even if it would normally be non-cacheable or cacheable only within a non-shared cache. (See also
    12701260            Authorization, <a href="p7-auth.html#header.authorization" title="Authorization">Section 3.1</a> of <a href="#Part7" id="rfc.xref.Part7.2"><cite title="HTTP/1.1, part 7: Authentication">[Part7]</cite></a>, for additional details.)
    1271          </dd>
    1272       </dl>
     1261         </li>
     1262      </ul>
    12731263      <p id="rfc.section.3.2.1.p.3"> <span id="rfc.iref.c.5"></span>  <span id="rfc.iref.p.2"></span> private
    12741264      </p>
    1275       <dl class="empty">
    1276          <dd>Indicates that all or part of the response message is intended for a single user and <em class="bcp14">MUST NOT</em> be cached by a shared cache. This allows an origin server to state that the specified parts of the response are intended for
     1265      <ul class="empty">
     1266         <li>Indicates that all or part of the response message is intended for a single user and <em class="bcp14">MUST NOT</em> be cached by a shared cache. This allows an origin server to state that the specified parts of the response are intended for
    12771267            only one user and are not a valid response for requests by other users. A private (non-shared) cache <em class="bcp14">MAY</em> cache the response.
    1278          </dd>
    1279          <dd> <b>Note:</b> This usage of the word private only controls where the response may be cached, and cannot ensure the privacy of the message
     1268         </li>
     1269         <li> <b>Note:</b> This usage of the word private only controls where the response may be cached, and cannot ensure the privacy of the message
    12801270            content.
    1281          </dd>
    1282       </dl>
     1271         </li>
     1272      </ul>
    12831273      <p id="rfc.section.3.2.1.p.4"> <span id="rfc.iref.c.6"></span>  <span id="rfc.iref.n.1"></span> no-cache
    12841274      </p>
    1285       <dl class="empty">
    1286          <dd>If the no-cache directive does not specify a field-name, then a cache <em class="bcp14">MUST NOT</em> use the response to satisfy a subsequent request without successful revalidation with the origin server. This allows an origin
     1275      <ul class="empty">
     1276         <li>If the no-cache directive does not specify a field-name, then a cache <em class="bcp14">MUST NOT</em> use the response to satisfy a subsequent request without successful revalidation with the origin server. This allows an origin
    12871277            server to prevent caching even by caches that have been configured to return stale responses to client requests.
    1288          </dd>
    1289          <dd>If the no-cache directive does specify one or more field-names, then a cache <em class="bcp14">MAY</em> use the response to satisfy a subsequent request, subject to any other restrictions on caching. However, the specified field-name(s) <em class="bcp14">MUST NOT</em> be sent in the response to a subsequent request without successful revalidation with the origin server. This allows an origin
     1278         </li>
     1279         <li>If the no-cache directive does specify one or more field-names, then a cache <em class="bcp14">MAY</em> use the response to satisfy a subsequent request, subject to any other restrictions on caching. However, the specified field-name(s) <em class="bcp14">MUST NOT</em> be sent in the response to a subsequent request without successful revalidation with the origin server. This allows an origin
    12901280            server to prevent the re-use of certain header fields in a response, while still allowing caching of the rest of the response.
    1291             <dl class="empty">
    1292                <dd> <b>Note:</b> Most HTTP/1.0 caches will not recognize or obey this directive.
    1293                </dd>
    1294             </dl>
    1295          </dd>
    1296       </dl>
     1281            <ul class="empty">
     1282               <li> <b>Note:</b> Most HTTP/1.0 caches will not recognize or obey this directive.
     1283               </li>
     1284            </ul>
     1285         </li>
     1286      </ul>
    12971287      <h3 id="rfc.section.3.2.2"><a href="#rfc.section.3.2.2">3.2.2</a>&nbsp;<a id="what.may.be.stored.by.caches" href="#what.may.be.stored.by.caches">What May be Stored by Caches</a></h3>
    12981288      <p id="rfc.section.3.2.2.p.1"> <span id="rfc.iref.c.7"></span>  <span id="rfc.iref.n.2"></span> no-store
    12991289      </p>
    1300       <dl class="empty">
    1301          <dd>The purpose of the no-store directive is to prevent the inadvertent release or retention of sensitive information (for example,
     1290      <ul class="empty">
     1291         <li>The purpose of the no-store directive is to prevent the inadvertent release or retention of sensitive information (for example,
    13021292            on backup tapes). The no-store directive applies to the entire message, and <em class="bcp14">MAY</em> be sent either in a response or in a request. If sent in a request, a cache <em class="bcp14">MUST NOT</em> store any part of either this request or any response to it. If sent in a response, a cache <em class="bcp14">MUST NOT</em> store any part of either this response or the request that elicited it. This directive applies to both non-shared and shared
    13031293            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.
    1304          </dd>
    1305          <dd>Even when this directive is associated with a response, users might explicitly store such a response outside of the caching
     1294         </li>
     1295         <li>Even when this directive is associated with a response, users might explicitly store such a response outside of the caching
    13061296            system (e.g., with a "Save As" dialog). History buffers <em class="bcp14">MAY</em> store such responses as part of their normal operation.
    1307          </dd>
    1308          <dd>The purpose of this directive is to meet the stated requirements of certain users and service authors who are concerned about
     1297         </li>
     1298         <li>The purpose of this directive is to meet the stated requirements of certain users and service authors who are concerned about
    13091299            accidental releases of information via unanticipated accesses to cache data structures. While the use of this directive might
    13101300            improve privacy in some cases, we caution that it is NOT in any way a reliable or sufficient mechanism for ensuring privacy.
    13111301            In particular, malicious or compromised caches might not recognize or obey this directive, and communications networks might
    13121302            be vulnerable to eavesdropping.
    1313          </dd>
    1314       </dl>
     1303         </li>
     1304      </ul>
    13151305      <h3 id="rfc.section.3.2.3"><a href="#rfc.section.3.2.3">3.2.3</a>&nbsp;<a id="modifications.of.the.basic.expiration.mechanism" href="#modifications.of.the.basic.expiration.mechanism">Modifications of the Basic Expiration Mechanism</a></h3>
    13161306      <p id="rfc.section.3.2.3.p.1">The expiration time of an entity <em class="bcp14">MAY</em> be specified by the origin server using the Expires header (see <a href="#header.expires" id="rfc.xref.header.expires.2" title="Expires">Section&nbsp;3.3</a>). Alternatively, it <em class="bcp14">MAY</em> be specified using the max-age directive in a response. When the max-age cache-control directive is present in a cached response,
     
    13281318         does not include a Cache-Control header field, it <em class="bcp14">SHOULD</em> consider the response to be non-cacheable in order to retain compatibility with HTTP/1.0 servers.
    13291319      </p>
    1330       <dl class="empty">
    1331          <dd> <b>Note:</b> An origin server might wish to use a relatively new HTTP cache control feature, such as the "private" directive, on a network
     1320      <ul class="empty">
     1321         <li> <b>Note:</b> An origin server might wish to use a relatively new HTTP cache control feature, such as the "private" directive, on a network
    13321322            including older caches that do not understand that feature. The origin server will need to combine the new feature with an
    13331323            Expires field whose value is less than or equal to the Date value. This will prevent older caches from improperly caching
    13341324            the response.
    1335          </dd>
    1336       </dl>
     1325         </li>
     1326      </ul>
    13371327      <p id="rfc.section.3.2.3.p.4"> <span id="rfc.iref.c.8"></span>  <span id="rfc.iref.s.3"></span> s-maxage
    13381328      </p>
    1339       <dl class="empty">
    1340          <dd>If a response includes an s-maxage directive, then for a shared cache (but not for a private cache), the maximum age specified
     1329      <ul class="empty">
     1330         <li>If a response includes an s-maxage directive, then for a shared cache (but not for a private cache), the maximum age specified
    13411331            by this directive overrides the maximum age specified by either the max-age directive or the Expires header. The s-maxage
    13421332            directive also implies the semantics of the proxy-revalidate directive (see <a href="#cache.revalidation.and.reload.controls" title="Cache Revalidation and Reload Controls">Section&nbsp;3.2.4</a>), i.e., that the shared cache must not use the entry after it becomes stale to respond to a subsequent request without first
    13431333            revalidating it with the origin server. The s-maxage directive is always ignored by a private cache.
    1344          </dd>
    1345       </dl>
     1334         </li>
     1335      </ul>
    13461336      <p id="rfc.section.3.2.3.p.5">Note that most older caches, not compliant with this specification, do not implement any cache-control directives. An origin
    13471337         server wishing to use a cache-control directive that restricts, but does not prevent, caching by an HTTP/1.1-compliant cache <em class="bcp14">MAY</em> exploit the requirement that the max-age directive overrides the Expires header, and the fact that pre-HTTP/1.1-compliant
     
    13521342      <p id="rfc.section.3.2.3.p.7"> <span id="rfc.iref.c.9"></span>  <span id="rfc.iref.m.1"></span> max-age
    13531343      </p>
    1354       <dl class="empty">
    1355          <dd>Indicates that the client is willing to accept a response whose age is no greater than the specified time in seconds. Unless
     1344      <ul class="empty">
     1345         <li>Indicates that the client is willing to accept a response whose age is no greater than the specified time in seconds. Unless
    13561346            max-stale directive is also included, the client is not willing to accept a stale response.
    1357          </dd>
    1358       </dl>
     1347         </li>
     1348      </ul>
    13591349      <p id="rfc.section.3.2.3.p.8"> <span id="rfc.iref.c.10"></span>  <span id="rfc.iref.m.2"></span> min-fresh
    13601350      </p>
    1361       <dl class="empty">
    1362          <dd>Indicates that the client is willing to accept a response whose freshness lifetime is no less than its current age plus the
     1351      <ul class="empty">
     1352         <li>Indicates that the client is willing to accept a response whose freshness lifetime is no less than its current age plus the
    13631353            specified time in seconds. That is, the client wants a response that will still be fresh for at least the specified number
    13641354            of seconds.
    1365          </dd>
    1366       </dl>
     1355         </li>
     1356      </ul>
    13671357      <p id="rfc.section.3.2.3.p.9"> <span id="rfc.iref.c.11"></span>  <span id="rfc.iref.m.3"></span> max-stale
    13681358      </p>
    1369       <dl class="empty">
    1370          <dd>Indicates that the client is willing to accept a response that has exceeded its expiration time. If max-stale is assigned
     1359      <ul class="empty">
     1360         <li>Indicates that the client is willing to accept a response that has exceeded its expiration time. If max-stale is assigned
    13711361            a value, then the client is willing to accept a response that has exceeded its expiration time by no more than the specified
    13721362            number of seconds. If no value is assigned to max-stale, then the client is willing to accept a stale response of any age.
    1373          </dd>
    1374       </dl>
     1363         </li>
     1364      </ul>
    13751365      <p id="rfc.section.3.2.3.p.10">If a cache returns a stale response, either because of a max-stale directive on a request, or because the cache is configured
    13761366         to override the expiration time of a response, the cache <em class="bcp14">MUST</em> attach a Warning header to the stale response, using Warning 110 (Response is stale).
     
    13941384      <p id="rfc.section.3.2.4.p.3">The client can specify these three kinds of action using Cache-Control request directives:</p>
    13951385      <p id="rfc.section.3.2.4.p.4">End-to-end reload </p>
    1396       <dl class="empty">
    1397          <dd>The request includes a "no-cache" cache-control directive or, for compatibility with HTTP/1.0 clients, "Pragma: no-cache".
     1386      <ul class="empty">
     1387         <li>The request includes a "no-cache" cache-control directive or, for compatibility with HTTP/1.0 clients, "Pragma: no-cache".
    13981388            Field names <em class="bcp14">MUST NOT</em> be included with the no-cache directive in a request. The server <em class="bcp14">MUST NOT</em> use a cached copy when responding to such a request.
    1399          </dd>
    1400       </dl>
     1389         </li>
     1390      </ul>
    14011391      <p id="rfc.section.3.2.4.p.5">Specific end-to-end revalidation </p>
    1402       <dl class="empty">
    1403          <dd>The request includes a "max-age=0" cache-control directive, which forces each cache along the path to the origin server to
     1392      <ul class="empty">
     1393         <li>The request includes a "max-age=0" cache-control directive, which forces each cache along the path to the origin server to
    14041394            revalidate its own entry, if any, with the next cache or server. The initial request includes a cache-validating conditional
    14051395            with the client's current validator.
    1406          </dd>
    1407       </dl>
     1396         </li>
     1397      </ul>
    14081398      <p id="rfc.section.3.2.4.p.6">Unspecified end-to-end revalidation </p>
    1409       <dl class="empty">
    1410          <dd>The request includes "max-age=0" cache-control directive, which forces each cache along the path to the origin server to revalidate
     1399      <ul class="empty">
     1400         <li>The request includes "max-age=0" cache-control directive, which forces each cache along the path to the origin server to revalidate
    14111401            its own entry, if any, with the next cache or server. The initial request does not include a cache-validating conditional;
    14121402            the first cache along the path (if any) that holds a cache entry for this resource includes a cache-validating conditional
    14131403            with its current validator.
    1414          </dd>
    1415       </dl>
     1404         </li>
     1405      </ul>
    14161406      <p id="rfc.section.3.2.4.p.7"> <span id="rfc.iref.c.12"></span>  <span id="rfc.iref.m.4"></span> max-age
    14171407      </p>
    1418       <dl class="empty">
    1419          <dd>When an intermediate cache is forced, by means of a max-age=0 directive, to revalidate its own cache entry, and the client
     1408      <ul class="empty">
     1409         <li>When an intermediate cache is forced, by means of a max-age=0 directive, to revalidate its own cache entry, and the client
    14201410            has supplied its own validator in the request, the supplied validator might differ from the validator currently stored with
    14211411            the cache entry. In this case, the cache <em class="bcp14">MAY</em> use either validator in making its own request without affecting semantic transparency.
    1422          </dd>
    1423          <dd>However, the choice of validator might affect performance. The best approach is for the intermediate cache to use its own
     1412         </li>
     1413         <li>However, the choice of validator might affect performance. The best approach is for the intermediate cache to use its own
    14241414            validator when making its request. If the server replies with 304 (Not Modified), then the cache can return its now validated
    14251415            copy to the client with a 200 (OK) response. If the server replies with a new entity and cache validator, however, the intermediate
     
    14271417            If the client's validator is equal to the origin server's, then the intermediate cache simply returns 304 (Not Modified).
    14281418            Otherwise, it returns the new entity with a 200 (OK) response.
    1429          </dd>
    1430          <dd>If a request includes the no-cache directive, it <em class="bcp14">SHOULD NOT</em> include min-fresh, max-stale, or max-age.
    1431          </dd>
    1432       </dl>
     1419         </li>
     1420         <li>If a request includes the no-cache directive, it <em class="bcp14">SHOULD NOT</em> include min-fresh, max-stale, or max-age.
     1421         </li>
     1422      </ul>
    14331423      <p id="rfc.section.3.2.4.p.8"> <span id="rfc.iref.c.13"></span>  <span id="rfc.iref.o.1"></span> only-if-cached
    14341424      </p>
    1435       <dl class="empty">
    1436          <dd>In some cases, such as times of extremely poor network connectivity, a client may want a cache to return only those responses
     1425      <ul class="empty">
     1426         <li>In some cases, such as times of extremely poor network connectivity, a client may want a cache to return only those responses
    14371427            that it currently has stored, and not to reload or revalidate with the origin server. To do this, the client may include the
    14381428            only-if-cached directive in a request. If it receives this directive, a cache <em class="bcp14">SHOULD</em> either respond using a cached entry that is consistent with the other constraints of the request, or respond with a 504 (Gateway
    14391429            Timeout) status. However, if a group of caches is being operated as a unified system with good internal connectivity, such
    14401430            a request <em class="bcp14">MAY</em> be forwarded within that group of caches.
    1441          </dd>
    1442       </dl>
     1431         </li>
     1432      </ul>
    14431433      <p id="rfc.section.3.2.4.p.9"> <span id="rfc.iref.c.14"></span>  <span id="rfc.iref.m.5"></span> must-revalidate
    14441434      </p>
    1445       <dl class="empty">
    1446          <dd>Because a cache <em class="bcp14">MAY</em> be configured to ignore a server's specified expiration time, and because a client request <em class="bcp14">MAY</em> include a max-stale directive (which has a similar effect), the protocol also includes a mechanism for the origin server to
     1435      <ul class="empty">
     1436         <li>Because a cache <em class="bcp14">MAY</em> be configured to ignore a server's specified expiration time, and because a client request <em class="bcp14">MAY</em> include a max-stale directive (which has a similar effect), the protocol also includes a mechanism for the origin server to
    14471437            require revalidation of a cache entry on any subsequent use. When the must-revalidate directive is present in a response received
    14481438            by a cache, that cache <em class="bcp14">MUST NOT</em> use the entry after it becomes stale to respond to a subsequent request without first revalidating it with the origin server.
    14491439            (I.e., the cache <em class="bcp14">MUST</em> do an end-to-end revalidation every time, if, based solely on the origin server's Expires or max-age value, the cached response
    14501440            is stale.)
    1451          </dd>
    1452          <dd>The must-revalidate directive is necessary to support reliable operation for certain protocol features. In all circumstances
     1441         </li>
     1442         <li>The must-revalidate directive is necessary to support reliable operation for certain protocol features. In all circumstances
    14531443            an HTTP/1.1 cache <em class="bcp14">MUST</em> obey the must-revalidate directive; in particular, if the cache cannot reach the origin server for any reason, it <em class="bcp14">MUST</em> generate a 504 (Gateway Timeout) response.
    1454          </dd>
    1455          <dd>Servers <em class="bcp14">SHOULD</em> send the must-revalidate directive if and only if failure to revalidate a request on the entity could result in incorrect
     1444         </li>
     1445         <li>Servers <em class="bcp14">SHOULD</em> send the must-revalidate directive if and only if failure to revalidate a request on the entity could result in incorrect
    14561446            operation, such as a silently unexecuted financial transaction. Recipients <em class="bcp14">MUST NOT</em> take any automated action that violates this directive, and <em class="bcp14">MUST NOT</em> automatically provide an unvalidated copy of the entity if revalidation fails.
    1457          </dd>
    1458          <dd>Although this is not recommended, user agents operating under severe connectivity constraints <em class="bcp14">MAY</em> violate this directive but, if so, <em class="bcp14">MUST</em> explicitly warn the user that an unvalidated response has been provided. The warning <em class="bcp14">MUST</em> be provided on each unvalidated access, and <em class="bcp14">SHOULD</em> require explicit user confirmation.
    1459          </dd>
    1460       </dl>
     1447         </li>
     1448         <li>Although this is not recommended, user agents operating under severe connectivity constraints <em class="bcp14">MAY</em> violate this directive but, if so, <em class="bcp14">MUST</em> explicitly warn the user that an unvalidated response has been provided. The warning <em class="bcp14">MUST</em> be provided on each unvalidated access, and <em class="bcp14">SHOULD</em> require explicit user confirmation.
     1449         </li>
     1450      </ul>
    14611451      <p id="rfc.section.3.2.4.p.10"> <span id="rfc.iref.c.15"></span>  <span id="rfc.iref.p.3"></span> proxy-revalidate
    14621452      </p>
    1463       <dl class="empty">
    1464          <dd>The proxy-revalidate directive has the same meaning as the must-revalidate directive, except that it does not apply to non-shared
     1453      <ul class="empty">
     1454         <li>The proxy-revalidate directive has the same meaning as the must-revalidate directive, except that it does not apply to non-shared
    14651455            user agent caches. It can be used on a response to an authenticated request to permit the user's cache to store and later
    14661456            return the response without needing to revalidate it (since it has already been authenticated once by that user), while still
     
    14681458            Note that such authenticated responses also need the public cache control directive in order to allow them to be cached at
    14691459            all.
    1470          </dd>
    1471       </dl>
     1460         </li>
     1461      </ul>
    14721462      <h3 id="rfc.section.3.2.5"><a href="#rfc.section.3.2.5">3.2.5</a>&nbsp;<a id="no-transform.directive" href="#no-transform.directive">No-Transform Directive</a></h3>
    14731463      <p id="rfc.section.3.2.5.p.1"> <span id="rfc.iref.c.16"></span>  <span id="rfc.iref.n.3"></span> no-transform
    14741464      </p>
    1475       <dl class="empty">
    1476          <dd>Implementors of intermediate caches (proxies) have found it useful to convert the media type of certain entity bodies. A non-transparent
     1465      <ul class="empty">
     1466         <li>Implementors of intermediate caches (proxies) have found it useful to convert the media type of certain entity bodies. A non-transparent
    14771467            proxy might, for example, convert between image formats in order to save cache space or to reduce the amount of traffic on
    14781468            a slow link.
    1479          </dd>
    1480          <dd>Serious operational problems occur, however, when these transformations are applied to entity bodies intended for certain
     1469         </li>
     1470         <li>Serious operational problems occur, however, when these transformations are applied to entity bodies intended for certain
    14811471            kinds of applications. For example, applications for medical imaging, scientific data analysis and those using end-to-end
    14821472            authentication, all depend on receiving an entity body that is bit for bit identical to the original entity-body.
    1483          </dd>
    1484          <dd>Therefore, if a message includes the no-transform directive, an intermediate cache or proxy <em class="bcp14">MUST NOT</em> change those headers that are listed in <a href="#non-modifiable.headers" title="Non-modifiable Headers">Section&nbsp;2.5.2</a> as being subject to the no-transform directive. This implies that the cache or proxy <em class="bcp14">MUST NOT</em> change any aspect of the entity-body that is specified by these headers, including the value of the entity-body itself.
    1485          </dd>
    1486       </dl>
     1473         </li>
     1474         <li>Therefore, if a message includes the no-transform directive, an intermediate cache or proxy <em class="bcp14">MUST NOT</em> change those headers that are listed in <a href="#non-modifiable.headers" title="Non-modifiable Headers">Section&nbsp;2.5.2</a> as being subject to the no-transform directive. This implies that the cache or proxy <em class="bcp14">MUST NOT</em> change any aspect of the entity-body that is specified by these headers, including the value of the entity-body itself.
     1475         </li>
     1476      </ul>
    14871477      <h3 id="rfc.section.3.2.6"><a href="#rfc.section.3.2.6">3.2.6</a>&nbsp;<a id="cache.control.extensions" href="#cache.control.extensions">Cache Control Extensions</a></h3>
    14881478      <p id="rfc.section.3.2.6.p.1">The Cache-Control header field can be extended through the use of one or more cache-extension tokens, each with an optional
     
    15251515      <div id="rfc.figure.u.14"></div><pre class="text">   Expires: Thu, 01 Dec 1994 16:00:00 GMT
    15261516</pre><p id="rfc.section.3.3.p.7"> </p>
    1527       <dl class="empty">
    1528          <dd> <b>Note:</b> if a response includes a Cache-Control field with the max-age directive (see <a href="#modifications.of.the.basic.expiration.mechanism" title="Modifications of the Basic Expiration Mechanism">Section&nbsp;3.2.3</a>), that directive overrides the Expires field.
    1529          </dd>
    1530       </dl>
     1517      <ul class="empty">
     1518         <li> <b>Note:</b> if a response includes a Cache-Control field with the max-age directive (see <a href="#modifications.of.the.basic.expiration.mechanism" title="Modifications of the Basic Expiration Mechanism">Section&nbsp;3.2.3</a>), that directive overrides the Expires field.
     1519         </li>
     1520      </ul>
    15311521      <p id="rfc.section.3.3.p.8">HTTP/1.1 clients and caches <em class="bcp14">MUST</em> treat other invalid date formats, especially including the value "0", as in the past (i.e., "already expired").
    15321522      </p>
     
    15611551         HTTP.
    15621552      </p>
    1563       <dl class="empty">
    1564          <dd> <b>Note:</b> because the meaning of "Pragma: no-cache as a response header field is not actually specified, it does not provide a reliable
     1553      <ul class="empty">
     1554         <li> <b>Note:</b> because the meaning of "Pragma: no-cache as a response header field is not actually specified, it does not provide a reliable
    15651555            replacement for "Cache-Control: no-cache" in a response
    1566          </dd>
    1567       </dl>
     1556         </li>
     1557      </ul>
    15681558      <div id="rfc.iref.v.2"></div>
    15691559      <div id="rfc.iref.h.6"></div>
     
    16401630      </p>
    16411631      <p id="rfc.section.3.6.p.12">110 Response is stale </p>
    1642       <dl class="empty">
    1643          <dd> <em class="bcp14">MUST</em> be included whenever the returned response is stale.
    1644          </dd>
    1645       </dl>
     1632      <ul class="empty">
     1633         <li> <em class="bcp14">MUST</em> be included whenever the returned response is stale.
     1634         </li>
     1635      </ul>
    16461636      <p id="rfc.section.3.6.p.13">111 Revalidation failed </p>
    1647       <dl class="empty">
    1648          <dd> <em class="bcp14">MUST</em> be included if a cache returns a stale response because an attempt to revalidate the response failed, due to an inability
     1637      <ul class="empty">
     1638         <li> <em class="bcp14">MUST</em> be included if a cache returns a stale response because an attempt to revalidate the response failed, due to an inability
    16491639            to reach the server.
    1650          </dd>
    1651       </dl>
     1640         </li>
     1641      </ul>
    16521642      <p id="rfc.section.3.6.p.14">112 Disconnected operation </p>
    1653       <dl class="empty">
    1654          <dd> <em class="bcp14">SHOULD</em> be included if the cache is intentionally disconnected from the rest of the network for a period of time.
    1655          </dd>
    1656       </dl>
     1643      <ul class="empty">
     1644         <li> <em class="bcp14">SHOULD</em> be included if the cache is intentionally disconnected from the rest of the network for a period of time.
     1645         </li>
     1646      </ul>
    16571647      <p id="rfc.section.3.6.p.15">113 Heuristic expiration </p>
    1658       <dl class="empty">
    1659          <dd> <em class="bcp14">MUST</em> be included if the cache heuristically chose a freshness lifetime greater than 24 hours and the response's age is greater
     1648      <ul class="empty">
     1649         <li> <em class="bcp14">MUST</em> be included if the cache heuristically chose a freshness lifetime greater than 24 hours and the response's age is greater
    16601650            than 24 hours.
    1661          </dd>
    1662       </dl>
     1651         </li>
     1652      </ul>
    16631653      <p id="rfc.section.3.6.p.16">199 Miscellaneous warning </p>
    1664       <dl class="empty">
    1665          <dd>The warning text <em class="bcp14">MAY</em> 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.
    1666          </dd>
    1667       </dl>
     1654      <ul class="empty">
     1655         <li>The warning text <em class="bcp14">MAY</em> 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.
     1656         </li>
     1657      </ul>
    16681658      <p id="rfc.section.3.6.p.17">214 Transformation applied </p>
    1669       <dl class="empty">
    1670          <dd> <em class="bcp14">MUST</em> be added by an intermediate cache or proxy if it applies any transformation changing the content-coding (as specified in the
     1659      <ul class="empty">
     1660         <li> <em class="bcp14">MUST</em> be added by an intermediate cache or proxy if it applies any transformation changing the content-coding (as specified in the
    16711661            Content-Encoding header) or media-type (as specified in the Content-Type header) of the response, or the entity-body of the
    16721662            response, unless this Warning code already appears in the response.
    1673          </dd>
    1674       </dl>
     1663         </li>
     1664      </ul>
    16751665      <p id="rfc.section.3.6.p.18">299 Miscellaneous persistent warning </p>
    1676       <dl class="empty">
    1677          <dd>The warning text <em class="bcp14">MAY</em> 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.
    1678          </dd>
    1679       </dl>
     1666      <ul class="empty">
     1667         <li>The warning text <em class="bcp14">MAY</em> 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.
     1668         </li>
     1669      </ul>
    16801670      <p id="rfc.section.3.6.p.19">If an implementation sends a message with one or more Warning headers whose version is HTTP/1.0 or lower, then the sender <em class="bcp14">MUST</em> include in each warning-value a warn-date that matches the date in the response.
    16811671      </p>
     
    16991689      <h1 id="rfc.references"><a href="#rfc.section.7" id="rfc.section.7">7.</a> References
    17001690      </h1>
    1701       <table summary="References">                 
     1691      <table>                 
    17021692         <tr>
    17031693            <td class="reference"><b id="Part1">[Part1]</b></td>
    1704             <td class="top"><a title="Day Software">Fielding, R., Ed.</a>, <a title="One Laptop per Child">Gettys, J.</a>, <a title="Hewlett-Packard Company">Mogul, J.</a>, <a title="Microsoft Corporation">Frystyk, H.</a>, <a title="Adobe Systems, Incorporated">Masinter, L.</a>, <a title="Microsoft Corporation">Leach, P.</a>, and <a title="World Wide Web Consortium">T. Berners-Lee</a>, “<a href="http://tools.ietf.org/html/draft-ietf-httpbis-p1-messaging-00">HTTP/1.1, part 1: URIs, Connections, and Message Parsing</a>”, Internet-Draft&nbsp;draft-ietf-httpbis-p1-messaging-00 (work in progress), December&nbsp;2007.
     1694            <td class="top"><a href="mailto:fielding@gbiv.com" title="Day Software">Fielding, R., Ed.</a>, <a href="mailto:jg@laptop.org" title="One Laptop per Child">Gettys, J.</a>, <a href="mailto:JeffMogul@acm.org" title="Hewlett-Packard Company">Mogul, J.</a>, <a href="mailto:henrikn@microsoft.com" title="Microsoft Corporation">Frystyk, H.</a>, <a href="mailto:LMM@acm.org" title="Adobe Systems, Incorporated">Masinter, L.</a>, <a href="mailto:paulle@microsoft.com" title="Microsoft Corporation">Leach, P.</a>, and <a href="mailto:timbl@w3.org" title="World Wide Web Consortium">T. Berners-Lee</a>, “<a href="http://tools.ietf.org/html/draft-ietf-httpbis-p1-messaging-00">HTTP/1.1, part 1: URIs, Connections, and Message Parsing</a>”, Internet-Draft&nbsp;draft-ietf-httpbis-p1-messaging-00 (work in progress), December&nbsp;2007.
    17051695            </td>
    17061696         </tr>
    17071697         <tr>
    17081698            <td class="reference"><b id="Part2">[Part2]</b></td>
    1709             <td class="top"><a title="Day Software">Fielding, R., Ed.</a>, <a title="One Laptop per Child">Gettys, J.</a>, <a title="Hewlett-Packard Company">Mogul, J.</a>, <a title="Microsoft Corporation">Frystyk, H.</a>, <a title="Adobe Systems, Incorporated">Masinter, L.</a>, <a title="Microsoft Corporation">Leach, P.</a>, and <a title="World Wide Web Consortium">T. Berners-Lee</a>, “<a href="http://tools.ietf.org/html/draft-ietf-httpbis-p2-semantics-00">HTTP/1.1, part 2: Message Semantics</a>”, Internet-Draft&nbsp;draft-ietf-httpbis-p2-semantics-00 (work in progress), December&nbsp;2007.
     1699            <td class="top"><a href="mailto:fielding@gbiv.com" title="Day Software">Fielding, R., Ed.</a>, <a href="mailto:jg@laptop.org" title="One Laptop per Child">Gettys, J.</a>, <a href="mailto:JeffMogul@acm.org" title="Hewlett-Packard Company">Mogul, J.</a>, <a href="mailto:henrikn@microsoft.com" title="Microsoft Corporation">Frystyk, H.</a>, <a href="mailto:LMM@acm.org" title="Adobe Systems, Incorporated">Masinter, L.</a>, <a href="mailto:paulle@microsoft.com" title="Microsoft Corporation">Leach, P.</a>, and <a href="mailto:timbl@w3.org" title="World Wide Web Consortium">T. Berners-Lee</a>, “<a href="http://tools.ietf.org/html/draft-ietf-httpbis-p2-semantics-00">HTTP/1.1, part 2: Message Semantics</a>”, Internet-Draft&nbsp;draft-ietf-httpbis-p2-semantics-00 (work in progress), December&nbsp;2007.
    17101700            </td>
    17111701         </tr>
    17121702         <tr>
    17131703            <td class="reference"><b id="Part3">[Part3]</b></td>
    1714             <td class="top"><a title="Day Software">Fielding, R., Ed.</a>, <a title="One Laptop per Child">Gettys, J.</a>, <a title="Hewlett-Packard Company">Mogul, J.</a>, <a title="Microsoft Corporation">Frystyk, H.</a>, <a title="Adobe Systems, Incorporated">Masinter, L.</a>, <a title="Microsoft Corporation">Leach, P.</a>, and <a title="World Wide Web Consortium">T. Berners-Lee</a>, “<a href="http://tools.ietf.org/html/draft-ietf-httpbis-p3-payload-00">HTTP/1.1, part 3: Message Payload and Content Negotiation</a>”, Internet-Draft&nbsp;draft-ietf-httpbis-p3-payload-00 (work in progress), December&nbsp;2007.
     1704            <td class="top"><a href="mailto:fielding@gbiv.com" title="Day Software">Fielding, R., Ed.</a>, <a href="mailto:jg@laptop.org" title="One Laptop per Child">Gettys, J.</a>, <a href="mailto:JeffMogul@acm.org" title="Hewlett-Packard Company">Mogul, J.</a>, <a href="mailto:henrikn@microsoft.com" title="Microsoft Corporation">Frystyk, H.</a>, <a href="mailto:LMM@acm.org" title="Adobe Systems, Incorporated">Masinter, L.</a>, <a href="mailto:paulle@microsoft.com" title="Microsoft Corporation">Leach, P.</a>, and <a href="mailto:timbl@w3.org" title="World Wide Web Consortium">T. Berners-Lee</a>, “<a href="http://tools.ietf.org/html/draft-ietf-httpbis-p3-payload-00">HTTP/1.1, part 3: Message Payload and Content Negotiation</a>”, Internet-Draft&nbsp;draft-ietf-httpbis-p3-payload-00 (work in progress), December&nbsp;2007.
    17151705            </td>
    17161706         </tr>
    17171707         <tr>
    17181708            <td class="reference"><b id="Part4">[Part4]</b></td>
    1719             <td class="top"><a title="Day Software">Fielding, R., Ed.</a>, <a title="One Laptop per Child">Gettys, J.</a>, <a title="Hewlett-Packard Company">Mogul, J.</a>, <a title="Microsoft Corporation">Frystyk, H.</a>, <a title="Adobe Systems, Incorporated">Masinter, L.</a>, <a title="Microsoft Corporation">Leach, P.</a>, and <a title="World Wide Web Consortium">T. Berners-Lee</a>, “<a href="http://tools.ietf.org/html/draft-ietf-httpbis-p4-conditional-00">HTTP/1.1, part 4: Conditional Requests</a>”, Internet-Draft&nbsp;draft-ietf-httpbis-p4-conditional-00 (work in progress), December&nbsp;2007.
     1709            <td class="top"><a href="mailto:fielding@gbiv.com" title="Day Software">Fielding, R., Ed.</a>, <a href="mailto:jg@laptop.org" title="One Laptop per Child">Gettys, J.</a>, <a href="mailto:JeffMogul@acm.org" title="Hewlett-Packard Company">Mogul, J.</a>, <a href="mailto:henrikn@microsoft.com" title="Microsoft Corporation">Frystyk, H.</a>, <a href="mailto:LMM@acm.org" title="Adobe Systems, Incorporated">Masinter, L.</a>, <a href="mailto:paulle@microsoft.com" title="Microsoft Corporation">Leach, P.</a>, and <a href="mailto:timbl@w3.org" title="World Wide Web Consortium">T. Berners-Lee</a>, “<a href="http://tools.ietf.org/html/draft-ietf-httpbis-p4-conditional-00">HTTP/1.1, part 4: Conditional Requests</a>”, Internet-Draft&nbsp;draft-ietf-httpbis-p4-conditional-00 (work in progress), December&nbsp;2007.
    17201710            </td>
    17211711         </tr>
    17221712         <tr>
    17231713            <td class="reference"><b id="Part5">[Part5]</b></td>
    1724             <td class="top"><a title="Day Software">Fielding, R., Ed.</a>, <a title="One Laptop per Child">Gettys, J.</a>, <a title="Hewlett-Packard Company">Mogul, J.</a>, <a title="Microsoft Corporation">Frystyk, H.</a>, <a title="Adobe Systems, Incorporated">Masinter, L.</a>, <a title="Microsoft Corporation">Leach, P.</a>, and <a title="World Wide Web Consortium">T. Berners-Lee</a>, “<a href="http://tools.ietf.org/html/draft-ietf-httpbis-p5-range-00">HTTP/1.1, part 5: Range Requests and Partial Responses</a>”, Internet-Draft&nbsp;draft-ietf-httpbis-p5-range-00 (work in progress), December&nbsp;2007.
     1714            <td class="top"><a href="mailto:fielding@gbiv.com" title="Day Software">Fielding, R., Ed.</a>, <a href="mailto:jg@laptop.org" title="One Laptop per Child">Gettys, J.</a>, <a href="mailto:JeffMogul@acm.org" title="Hewlett-Packard Company">Mogul, J.</a>, <a href="mailto:henrikn@microsoft.com" title="Microsoft Corporation">Frystyk, H.</a>, <a href="mailto:LMM@acm.org" title="Adobe Systems, Incorporated">Masinter, L.</a>, <a href="mailto:paulle@microsoft.com" title="Microsoft Corporation">Leach, P.</a>, and <a href="mailto:timbl@w3.org" title="World Wide Web Consortium">T. Berners-Lee</a>, “<a href="http://tools.ietf.org/html/draft-ietf-httpbis-p5-range-00">HTTP/1.1, part 5: Range Requests and Partial Responses</a>”, Internet-Draft&nbsp;draft-ietf-httpbis-p5-range-00 (work in progress), December&nbsp;2007.
    17251715            </td>
    17261716         </tr>
    17271717         <tr>
    17281718            <td class="reference"><b id="Part7">[Part7]</b></td>
    1729             <td class="top"><a title="Day Software">Fielding, R., Ed.</a>, <a title="One Laptop per Child">Gettys, J.</a>, <a title="Hewlett-Packard Company">Mogul, J.</a>, <a title="Microsoft Corporation">Frystyk, H.</a>, <a title="Adobe Systems, Incorporated">Masinter, L.</a>, <a title="Microsoft Corporation">Leach, P.</a>, and <a title="World Wide Web Consortium">T. Berners-Lee</a>, “<a href="http://tools.ietf.org/html/draft-ietf-httpbis-p7-auth-00">HTTP/1.1, part 7: Authentication</a>”, Internet-Draft&nbsp;draft-ietf-httpbis-p7-auth-00 (work in progress), December&nbsp;2007.
     1719            <td class="top"><a href="mailto:fielding@gbiv.com" title="Day Software">Fielding, R., Ed.</a>, <a href="mailto:jg@laptop.org" title="One Laptop per Child">Gettys, J.</a>, <a href="mailto:JeffMogul@acm.org" title="Hewlett-Packard Company">Mogul, J.</a>, <a href="mailto:henrikn@microsoft.com" title="Microsoft Corporation">Frystyk, H.</a>, <a href="mailto:LMM@acm.org" title="Adobe Systems, Incorporated">Masinter, L.</a>, <a href="mailto:paulle@microsoft.com" title="Microsoft Corporation">Leach, P.</a>, and <a href="mailto:timbl@w3.org" title="World Wide Web Consortium">T. Berners-Lee</a>, “<a href="http://tools.ietf.org/html/draft-ietf-httpbis-p7-auth-00">HTTP/1.1, part 7: Authentication</a>”, Internet-Draft&nbsp;draft-ietf-httpbis-p7-auth-00 (work in progress), December&nbsp;2007.
    17301720            </td>
    17311721         </tr>
    17321722         <tr>
    17331723            <td class="reference"><b id="RFC1305">[RFC1305]</b></td>
    1734             <td class="top"><a 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.
     1724            <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.
    17351725            </td>
    17361726         </tr>
    17371727         <tr>
    17381728            <td class="reference"><b id="RFC2047">[RFC2047]</b></td>
    1739             <td class="top"><a title="University of Tennessee">Moore, K.</a>, “<a href="http://tools.ietf.org/html/rfc2047">MIME (Multipurpose Internet Mail Extensions) Part Three: Message Header Extensions for Non-ASCII Text</a>”, RFC&nbsp;2047, November&nbsp;1996.
     1729            <td class="top"><a href="mailto:moore@cs.utk.edu" title="University of Tennessee">Moore, K.</a>, “<a href="http://tools.ietf.org/html/rfc2047">MIME (Multipurpose Internet Mail Extensions) Part Three: Message Header Extensions for Non-ASCII Text</a>”, RFC&nbsp;2047, November&nbsp;1996.
    17401730            </td>
    17411731         </tr>
    17421732         <tr>
    17431733            <td class="reference"><b id="RFC2616">[RFC2616]</b></td>
    1744             <td class="top"><a title="University of California, Irvine">Fielding, R.</a>, <a title="W3C">Gettys, J.</a>, <a title="Compaq Computer Corporation">Mogul, J.</a>, <a title="MIT Laboratory for Computer Science">Frystyk, H.</a>, <a title="Xerox Corporation">Masinter, L.</a>, <a title="Microsoft Corporation">Leach, P.</a>, and <a 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.
     1734            <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.
    17451735            </td>
    17461736         </tr>
    17471737      </table>
    1748       <h1 id="rfc.authors"><a href="#rfc.authors">Authors' Addresses</a></h1>
    1749       <address class="vcard"><span class="vcardline"><span class="fn">Roy T. Fielding</span>
    1750             (editor)
    1751             <span class="n hidden"><span class="family-name">Fielding</span><span class="given-name">Roy T.</span></span></span><span class="org vcardline">Day Software</span><span class="adr"><span class="street-address vcardline">23 Corporate Plaza DR, Suite 280</span><span class="vcardline"><span class="locality">Newport Beach</span>, <span class="region">CA</span>&nbsp;<span class="postal-code">92660</span></span><span class="country-name vcardline">USA</span></span><span class="vcardline tel">Phone: <a href="tel:+1-949-706-5300"><span class="value">+1-949-706-5300</span></a></span><span class="vcardline tel"><span class="type">Fax</span>: <a href="fax:+1-949-706-5305"><span class="value">+1-949-706-5305</span></a></span><span class="vcardline">EMail: <a><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>
    1752       <address class="vcard"><span class="vcardline"><span class="fn">Jim Gettys</span><span class="n hidden"><span class="family-name">Gettys</span><span class="given-name">Jim</span></span></span><span class="org vcardline">One Laptop per Child</span><span class="adr"><span class="street-address vcardline">21 Oak Knoll Road</span><span class="vcardline"><span class="locality">Carlisle</span>, <span class="region">MA</span>&nbsp;<span class="postal-code">01741</span></span><span class="country-name vcardline">USA</span></span><span class="vcardline">EMail: <a><span class="email">jg@laptop.org</span></a></span><span class="vcardline">URI: <a href="http://www.laptop.org/" class="url">http://www.laptop.org/</a></span></address>
    1753       <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><span class="email">JeffMogul@acm.org</span></a></span></address>
    1754       <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><span class="email">henrikn@microsoft.com</span></a></span></address>
    1755       <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><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>
    1756       <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><span class="email">paulle@microsoft.com</span></a></span></address>
    1757       <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><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>
    1758       <h1 id="rfc.section.A"><a href="#rfc.section.A">A.</a>&nbsp;<a id="changes.from.rfc.2068" href="#changes.from.rfc.2068">Changes from RFC 2068</a></h1>
     1738      <div class="avoidbreak">
     1739         <h1 id="rfc.authors"><a href="#rfc.authors">Authors' Addresses</a></h1>
     1740         <address class="vcard"><span class="vcardline"><span class="fn">Roy T. Fielding</span>
     1741               (editor)
     1742               <span class="n hidden"><span class="family-name">Fielding</span><span class="given-name">Roy T.</span></span></span><span class="org vcardline">Day Software</span><span class="adr"><span class="street-address vcardline">23 Corporate Plaza DR, Suite 280</span><span class="vcardline"><span class="locality">Newport Beach</span>, <span class="region">CA</span>&nbsp;<span class="postal-code">92660</span></span><span class="country-name vcardline">USA</span></span><span class="vcardline tel">Phone: <a href="tel:+1-949-706-5300"><span class="value">+1-949-706-5300</span></a></span><span class="vcardline tel"><span class="type">Fax</span>: <a href="fax:+1-949-706-5305"><span class="value">+1-949-706-5305</span></a></span><span class="vcardline">EMail: <a href="mailto:fielding@gbiv.com"><span class="email">fielding@gbiv.com</span></a></span><span class="vcardline">URI: <a href="http://roy.gbiv.com/" class="url">http://roy.gbiv.com/</a></span></address>
     1743         <address class="vcard"><span class="vcardline"><span class="fn">Jim Gettys</span><span class="n hidden"><span class="family-name">Gettys</span><span class="given-name">Jim</span></span></span><span class="org vcardline">One Laptop per Child</span><span class="adr"><span class="street-address vcardline">21 Oak Knoll Road</span><span class="vcardline"><span class="locality">Carlisle</span>, <span class="region">MA</span>&nbsp;<span class="postal-code">01741</span></span><span class="country-name vcardline">USA</span></span><span class="vcardline">EMail: <a href="mailto:jg@laptop.org"><span class="email">jg@laptop.org</span></a></span><span class="vcardline">URI: <a href="http://www.laptop.org/" class="url">http://www.laptop.org/</a></span></address>
     1744         <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>
     1745         <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>
     1746         <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>
     1747         <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>
     1748         <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>
     1749      </div>
     1750      <h1 id="rfc.section.A" class="np"><a href="#rfc.section.A">A.</a>&nbsp;<a id="changes.from.rfc.2068" href="#changes.from.rfc.2068">Changes from RFC 2068</a></h1>
    17591751      <p id="rfc.section.A.p.1">A case was missed in the Cache-Control model of HTTP/1.1; s-maxage was introduced to add this missing case. (Sections <a href="#response.cacheability" title="Response Cacheability">2.4</a>, <a href="#header.cache-control" id="rfc.xref.header.cache-control.11" title="Cache-Control">3.2</a>, <a href="#modifications.of.the.basic.expiration.mechanism" title="Modifications of the Basic Expiration Mechanism">3.2.3</a>)
    17601752      </p>
     
    17631755      <p id="rfc.section.A.p.3">Warnings could be cached incorrectly, or not updated appropriately. (Section <a href="#warnings" title="Warnings">2.1.2</a>, <a href="#expiration.calculations" title="Expiration Calculations">2.2.4</a>, <a href="#non-modifiable.headers" title="Non-modifiable Headers">2.5.2</a>, <a href="#combining.headers" title="Combining Headers">2.5.3</a>, <a href="#modifications.of.the.basic.expiration.mechanism" title="Modifications of the Basic Expiration Mechanism">3.2.3</a>, and <a href="#header.warning" id="rfc.xref.header.warning.6" title="Warning">3.6</a>) Warning also needed to be a general header, as PUT or other methods may have need for it in requests.
    17641756      </p>
     1757      <h1 id="rfc.index"><a href="#rfc.index">Index</a></h1>
     1758      <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>
     1759      </p>
     1760      <div class="print2col">
     1761         <ul class="ind">
     1762            <li><a id="rfc.index.A" href="#rfc.index.A"><b>A</b></a><ul>
     1763                  <li>age&nbsp;&nbsp;<a href="#rfc.iref.a.1">1.1</a></li>
     1764                  <li>Age header&nbsp;&nbsp;<a href="#rfc.iref.a.2"><b>3.1</b></a></li>
     1765               </ul>
     1766            </li>
     1767            <li><a id="rfc.index.C" href="#rfc.index.C"><b>C</b></a><ul>
     1768                  <li>cache&nbsp;&nbsp;<a href="#rfc.iref.c.1">1.1</a></li>
     1769                  <li>Cache Directives&nbsp;&nbsp;
     1770                     <ul>
     1771                        <li>max-age&nbsp;&nbsp;<a href="#rfc.iref.c.9"><b>3.2.3</b></a>, <a href="#rfc.iref.c.12"><b>3.2.4</b></a></li>
     1772                        <li>max-stale&nbsp;&nbsp;<a href="#rfc.iref.c.11"><b>3.2.3</b></a></li>
     1773                        <li>min-fresh&nbsp;&nbsp;<a href="#rfc.iref.c.10"><b>3.2.3</b></a></li>
     1774                        <li>must-revalidate&nbsp;&nbsp;<a href="#rfc.iref.c.14"><b>3.2.4</b></a></li>
     1775                        <li>no-cache&nbsp;&nbsp;<a href="#rfc.iref.c.6"><b>3.2.1</b></a></li>
     1776                        <li>no-store&nbsp;&nbsp;<a href="#rfc.iref.c.7"><b>3.2.2</b></a></li>
     1777                        <li>no-transform&nbsp;&nbsp;<a href="#rfc.iref.c.16"><b>3.2.5</b></a></li>
     1778                        <li>only-if-cached&nbsp;&nbsp;<a href="#rfc.iref.c.13"><b>3.2.4</b></a></li>
     1779                        <li>private&nbsp;&nbsp;<a href="#rfc.iref.c.5"><b>3.2.1</b></a></li>
     1780                        <li>proxy-revalidate&nbsp;&nbsp;<a href="#rfc.iref.c.15"><b>3.2.4</b></a></li>
     1781                        <li>public&nbsp;&nbsp;<a href="#rfc.iref.c.4"><b>3.2.1</b></a></li>
     1782                        <li>s-maxage&nbsp;&nbsp;<a href="#rfc.iref.c.8"><b>3.2.3</b></a></li>
     1783                     </ul>
     1784                  </li>
     1785                  <li>Cache-Control header&nbsp;&nbsp;<a href="#rfc.xref.header.cache-control.1">2.1.1</a>, <a href="#rfc.xref.header.cache-control.2">2.1.1</a>, <a href="#rfc.xref.header.cache-control.3">2.1.3</a>, <a href="#rfc.xref.header.cache-control.4">2.2.1</a>, <a href="#rfc.xref.header.cache-control.5">2.2.5</a>, <a href="#rfc.xref.header.cache-control.6">2.4</a>, <a href="#rfc.xref.header.cache-control.7">2.4</a>, <a href="#rfc.xref.header.cache-control.8">2.8</a>, <a href="#rfc.iref.c.3"><b>3.2</b></a>, <a href="#rfc.xref.header.cache-control.9">3.3</a>, <a href="#rfc.xref.header.cache-control.10">3.4</a>, <a href="#rfc.xref.header.cache-control.11">A</a></li>
     1786                  <li>cacheable&nbsp;&nbsp;<a href="#rfc.iref.c.2">1.1</a></li>
     1787               </ul>
     1788            </li>
     1789            <li><a id="rfc.index.E" href="#rfc.index.E"><b>E</b></a><ul>
     1790                  <li>Expires header&nbsp;&nbsp;<a href="#rfc.xref.header.expires.1">2.4</a>, <a href="#rfc.xref.header.expires.2">3.2.3</a>, <a href="#rfc.iref.e.2"><b>3.3</b></a></li>
     1791                  <li>explicit expiration time&nbsp;&nbsp;<a href="#rfc.iref.e.1">1.1</a></li>
     1792               </ul>
     1793            </li>
     1794            <li><a id="rfc.index.F" href="#rfc.index.F"><b>F</b></a><ul>
     1795                  <li>first-hand&nbsp;&nbsp;<a href="#rfc.iref.f.1">1.1</a></li>
     1796                  <li>fresh&nbsp;&nbsp;<a href="#rfc.iref.f.3">1.1</a></li>
     1797                  <li>freshness lifetime&nbsp;&nbsp;<a href="#rfc.iref.f.2">1.1</a></li>
     1798               </ul>
     1799            </li>
     1800            <li><a id="rfc.index.G" href="#rfc.index.G"><b>G</b></a><ul>
     1801                  <li><tt>Grammar</tt>&nbsp;&nbsp;
     1802                     <ul>
     1803                        <li><tt>Age</tt>&nbsp;&nbsp;<a href="#rfc.iref.g.2"><b>3.1</b></a></li>
     1804                        <li><tt>age-value</tt>&nbsp;&nbsp;<a href="#rfc.iref.g.3"><b>3.1</b></a></li>
     1805                        <li><tt>Cache-Control</tt>&nbsp;&nbsp;<a href="#rfc.iref.g.4"><b>3.2</b></a></li>
     1806                        <li><tt>cache-directive</tt>&nbsp;&nbsp;<a href="#rfc.iref.g.5"><b>3.2</b></a></li>
     1807                        <li><tt>cache-extension</tt>&nbsp;&nbsp;<a href="#rfc.iref.g.8"><b>3.2</b></a></li>
     1808                        <li><tt>cache-request-directive</tt>&nbsp;&nbsp;<a href="#rfc.iref.g.6"><b>3.2</b></a></li>
     1809                        <li><tt>cache-response-directive</tt>&nbsp;&nbsp;<a href="#rfc.iref.g.7"><b>3.2</b></a></li>
     1810                        <li><tt>delta-seconds</tt>&nbsp;&nbsp;<a href="#rfc.iref.g.1"><b>1.2</b></a></li>
     1811                        <li><tt>Expires</tt>&nbsp;&nbsp;<a href="#rfc.iref.g.9"><b>3.3</b></a></li>
     1812                        <li><tt>extension-pragma</tt>&nbsp;&nbsp;<a href="#rfc.iref.g.12"><b>3.4</b></a></li>
     1813                        <li><tt>Pragma</tt>&nbsp;&nbsp;<a href="#rfc.iref.g.10"><b>3.4</b></a></li>
     1814                        <li><tt>pragma-directive</tt>&nbsp;&nbsp;<a href="#rfc.iref.g.11"><b>3.4</b></a></li>
     1815                        <li><tt>Vary</tt>&nbsp;&nbsp;<a href="#rfc.iref.g.13"><b>3.5</b></a></li>
     1816                        <li><tt>warn-agent</tt>&nbsp;&nbsp;<a href="#rfc.iref.g.17"><b>3.6</b></a></li>
     1817                        <li><tt>warn-code</tt>&nbsp;&nbsp;<a href="#rfc.iref.g.16"><b>3.6</b></a></li>
     1818                        <li><tt>warn-date</tt>&nbsp;&nbsp;<a href="#rfc.iref.g.19"><b>3.6</b></a></li>
     1819                        <li><tt>warn-text</tt>&nbsp;&nbsp;<a href="#rfc.iref.g.18"><b>3.6</b></a></li>
     1820                        <li><tt>Warning</tt>&nbsp;&nbsp;<a href="#rfc.iref.g.14"><b>3.6</b></a></li>
     1821                        <li><tt>warning-value</tt>&nbsp;&nbsp;<a href="#rfc.iref.g.15"><b>3.6</b></a></li>
     1822                     </ul>
     1823                  </li>
     1824               </ul>
     1825            </li>
     1826            <li><a id="rfc.index.H" href="#rfc.index.H"><b>H</b></a><ul>
     1827                  <li>Headers&nbsp;&nbsp;
     1828                     <ul>
     1829                        <li>Age&nbsp;&nbsp;<a href="#rfc.iref.h.2"><b>3.1</b></a></li>
     1830                        <li>Cache-Control&nbsp;&nbsp;<a href="#rfc.xref.header.cache-control.1">2.1.1</a>, <a href="#rfc.xref.header.cache-control.2">2.1.1</a>, <a href="#rfc.xref.header.cache-control.3">2.1.3</a>, <a href="#rfc.xref.header.cache-control.4">2.2.1</a>, <a href="#rfc.xref.header.cache-control.5">2.2.5</a>, <a href="#rfc.xref.header.cache-control.6">2.4</a>, <a href="#rfc.xref.header.cache-control.7">2.4</a>, <a href="#rfc.xref.header.cache-control.8">2.8</a>, <a href="#rfc.iref.h.3"><b>3.2</b></a>, <a href="#rfc.xref.header.cache-control.9">3.3</a>, <a href="#rfc.xref.header.cache-control.10">3.4</a>, <a href="#rfc.xref.header.cache-control.11">A</a></li>
     1831                        <li>Expires&nbsp;&nbsp;<a href="#rfc.xref.header.expires.1">2.4</a>, <a href="#rfc.xref.header.expires.2">3.2.3</a>, <a href="#rfc.iref.h.4"><b>3.3</b></a></li>
     1832                        <li>Pragma&nbsp;&nbsp;<a href="#rfc.xref.header.pragma.1">3.2</a>, <a href="#rfc.iref.h.5"><b>3.4</b></a></li>
     1833                        <li>Vary&nbsp;&nbsp;<a href="#rfc.xref.header.vary.1">2.6</a>, <a href="#rfc.iref.h.6"><b>3.5</b></a></li>
     1834                        <li>Warning&nbsp;&nbsp;<a href="#rfc.xref.header.warning.1">2.1.1</a>, <a href="#rfc.xref.header.warning.2">2.1.2</a>, <a href="#rfc.xref.header.warning.3">2.1.2</a>, <a href="#rfc.xref.header.warning.4">2.5.2</a>, <a href="#rfc.xref.header.warning.5">2.5.3</a>, <a href="#rfc.iref.h.7"><b>3.6</b></a>, <a href="#rfc.xref.header.warning.6">A</a></li>
     1835                     </ul>
     1836                  </li>
     1837                  <li>heuristic expiration time&nbsp;&nbsp;<a href="#rfc.iref.h.1">1.1</a></li>
     1838               </ul>
     1839            </li>
     1840            <li><a id="rfc.index.M" href="#rfc.index.M"><b>M</b></a><ul>
     1841                  <li>max-age&nbsp;&nbsp;
     1842                     <ul>
     1843                        <li>Cache Directive&nbsp;&nbsp;<a href="#rfc.iref.m.1"><b>3.2.3</b></a>, <a href="#rfc.iref.m.4"><b>3.2.4</b></a></li>
     1844                     </ul>
     1845                  </li>
     1846                  <li>max-stale&nbsp;&nbsp;
     1847                     <ul>
     1848                        <li>Cache Directive&nbsp;&nbsp;<a href="#rfc.iref.m.3"><b>3.2.3</b></a></li>
     1849                     </ul>
     1850                  </li>
     1851                  <li>min-fresh&nbsp;&nbsp;
     1852                     <ul>
     1853                        <li>Cache Directive&nbsp;&nbsp;<a href="#rfc.iref.m.2"><b>3.2.3</b></a></li>
     1854                     </ul>
     1855                  </li>
     1856                  <li>must-revalidate&nbsp;&nbsp;
     1857                     <ul>
     1858                        <li>Cache Directive&nbsp;&nbsp;<a href="#rfc.iref.m.5"><b>3.2.4</b></a></li>
     1859                     </ul>
     1860                  </li>
     1861               </ul>
     1862            </li>
     1863            <li><a id="rfc.index.N" href="#rfc.index.N"><b>N</b></a><ul>
     1864                  <li>no-cache&nbsp;&nbsp;
     1865                     <ul>
     1866                        <li>Cache Directive&nbsp;&nbsp;<a href="#rfc.iref.n.1"><b>3.2.1</b></a></li>
     1867                     </ul>
     1868                  </li>
     1869                  <li>no-store&nbsp;&nbsp;
     1870                     <ul>
     1871                        <li>Cache Directive&nbsp;&nbsp;<a href="#rfc.iref.n.2"><b>3.2.2</b></a></li>
     1872                     </ul>
     1873                  </li>
     1874                  <li>no-transform&nbsp;&nbsp;
     1875                     <ul>
     1876                        <li>Cache Directive&nbsp;&nbsp;<a href="#rfc.iref.n.3"><b>3.2.5</b></a></li>
     1877                     </ul>
     1878                  </li>
     1879               </ul>
     1880            </li>
     1881            <li><a id="rfc.index.O" href="#rfc.index.O"><b>O</b></a><ul>
     1882                  <li>only-if-cached&nbsp;&nbsp;
     1883                     <ul>
     1884                        <li>Cache Directive&nbsp;&nbsp;<a href="#rfc.iref.o.1"><b>3.2.4</b></a></li>
     1885                     </ul>
     1886                  </li>
     1887               </ul>
     1888            </li>
     1889            <li><a id="rfc.index.P" href="#rfc.index.P"><b>P</b></a><ul>
     1890                  <li><em>Part1</em>&nbsp;&nbsp;<a href="#rfc.xref.Part1.1">2.2.3</a>, <a href="#rfc.xref.Part1.2">2.5.1</a>, <a href="#rfc.xref.Part1.3">2.5.2</a>, <a href="#rfc.xref.Part1.4">2.5.2</a>, <a href="#rfc.xref.Part1.5">2.6</a>, <a href="#rfc.xref.Part1.6">3.3</a>, <a href="#Part1"><b>7</b></a><ul>
     1891                        <li><em>Section 3.3.1</em>&nbsp;&nbsp;<a href="#rfc.xref.Part1.6">3.3</a></li>
     1892                        <li><em>Section 4.2</em>&nbsp;&nbsp;<a href="#rfc.xref.Part1.5">2.6</a></li>
     1893                        <li><em>Section 4.4</em>&nbsp;&nbsp;<a href="#rfc.xref.Part1.3">2.5.2</a>, <a href="#rfc.xref.Part1.4">2.5.2</a></li>
     1894                        <li><em>Section 8.1</em>&nbsp;&nbsp;<a href="#rfc.xref.Part1.2">2.5.1</a></li>
     1895                        <li><em>Section 8.3</em>&nbsp;&nbsp;<a href="#rfc.xref.Part1.1">2.2.3</a></li>
     1896                     </ul>
     1897                  </li>
     1898                  <li><em>Part2</em>&nbsp;&nbsp;<a href="#rfc.xref.Part2.1">2.9</a>, <a href="#Part2"><b>7</b></a><ul>
     1899                        <li><em>Section 8.1.1</em>&nbsp;&nbsp;<a href="#rfc.xref.Part2.1">2.9</a></li>
     1900                     </ul>
     1901                  </li>
     1902                  <li><em>Part3</em>&nbsp;&nbsp;<a href="#rfc.xref.Part3.1">2.5.2</a>, <a href="#rfc.xref.Part3.2">2.6</a>, <a href="#Part3"><b>7</b></a><ul>
     1903                        <li><em>Section 3.2.2</em>&nbsp;&nbsp;<a href="#rfc.xref.Part3.1">2.5.2</a></li>
     1904                        <li><em>Section 4.1</em>&nbsp;&nbsp;<a href="#rfc.xref.Part3.2">2.6</a></li>
     1905                     </ul>
     1906                  </li>
     1907                  <li><em>Part4</em>&nbsp;&nbsp;<a href="#rfc.xref.Part4.1">2.3</a>, <a href="#rfc.xref.Part4.2">2.3.2</a>, <a href="#Part4"><b>7</b></a><ul>
     1908                        <li><em>Section 2</em>&nbsp;&nbsp;<a href="#rfc.xref.Part4.2">2.3.2</a></li>
     1909                        <li><em>Section 4</em>&nbsp;&nbsp;<a href="#rfc.xref.Part4.1">2.3</a></li>
     1910                     </ul>
     1911                  </li>
     1912                  <li><em>Part5</em>&nbsp;&nbsp;<a href="#rfc.xref.Part5.1">2.5.3</a>, <a href="#rfc.xref.Part5.2">2.8</a>, <a href="#Part5"><b>7</b></a><ul>
     1913                        <li><em>Section 4</em>&nbsp;&nbsp;<a href="#rfc.xref.Part5.1">2.5.3</a>, <a href="#rfc.xref.Part5.2">2.8</a></li>
     1914                     </ul>
     1915                  </li>
     1916                  <li><em>Part7</em>&nbsp;&nbsp;<a href="#rfc.xref.Part7.1">2.4</a>, <a href="#rfc.xref.Part7.2">3.2.1</a>, <a href="#Part7"><b>7</b></a><ul>
     1917                        <li><em>Section 3.1</em>&nbsp;&nbsp;<a href="#rfc.xref.Part7.1">2.4</a>, <a href="#rfc.xref.Part7.2">3.2.1</a></li>
     1918                     </ul>
     1919                  </li>
     1920                  <li>Pragma header&nbsp;&nbsp;<a href="#rfc.xref.header.pragma.1">3.2</a>, <a href="#rfc.iref.p.4"><b>3.4</b></a></li>
     1921                  <li>private&nbsp;&nbsp;
     1922                     <ul>
     1923                        <li>Cache Directive&nbsp;&nbsp;<a href="#rfc.iref.p.2"><b>3.2.1</b></a></li>
     1924                     </ul>
     1925                  </li>
     1926                  <li>proxy-revalidate&nbsp;&nbsp;
     1927                     <ul>
     1928                        <li>Cache Directive&nbsp;&nbsp;<a href="#rfc.iref.p.3"><b>3.2.4</b></a></li>
     1929                     </ul>
     1930                  </li>
     1931                  <li>public&nbsp;&nbsp;
     1932                     <ul>
     1933                        <li>Cache Directive&nbsp;&nbsp;<a href="#rfc.iref.p.1"><b>3.2.1</b></a></li>
     1934                     </ul>
     1935                  </li>
     1936               </ul>
     1937            </li>
     1938            <li><a id="rfc.index.R" href="#rfc.index.R"><b>R</b></a><ul>
     1939                  <li><em>RFC1305</em>&nbsp;&nbsp;<a href="#rfc.xref.RFC1305.1">2.2.3</a>, <a href="#RFC1305"><b>7</b></a></li>
     1940                  <li><em>RFC2047</em>&nbsp;&nbsp;<a href="#rfc.xref.RFC2047.1">3.6</a>, <a href="#RFC2047"><b>7</b></a></li>
     1941                  <li><em>RFC2616</em>&nbsp;&nbsp;<a href="#rfc.xref.RFC2616.1">§</a>, <a href="#rfc.xref.RFC2616.2">1</a>, <a href="#RFC2616"><b>7</b></a></li>
     1942               </ul>
     1943            </li>
     1944            <li><a id="rfc.index.S" href="#rfc.index.S"><b>S</b></a><ul>
     1945                  <li>s-maxage&nbsp;&nbsp;
     1946                     <ul>
     1947                        <li>Cache Directive&nbsp;&nbsp;<a href="#rfc.iref.s.3"><b>3.2.3</b></a></li>
     1948                     </ul>
     1949                  </li>
     1950                  <li>semantically transparent&nbsp;&nbsp;<a href="#rfc.iref.s.2">1.1</a></li>
     1951                  <li>stale&nbsp;&nbsp;<a href="#rfc.iref.s.1">1.1</a></li>
     1952               </ul>
     1953            </li>
     1954            <li><a id="rfc.index.V" href="#rfc.index.V"><b>V</b></a><ul>
     1955                  <li>validator&nbsp;&nbsp;<a href="#rfc.iref.v.1">1.1</a></li>
     1956                  <li>Vary header&nbsp;&nbsp;<a href="#rfc.xref.header.vary.1">2.6</a>, <a href="#rfc.iref.v.2"><b>3.5</b></a></li>
     1957               </ul>
     1958            </li>
     1959            <li><a id="rfc.index.W" href="#rfc.index.W"><b>W</b></a><ul>
     1960                  <li>Warning header&nbsp;&nbsp;<a href="#rfc.xref.header.warning.1">2.1.1</a>, <a href="#rfc.xref.header.warning.2">2.1.2</a>, <a href="#rfc.xref.header.warning.3">2.1.2</a>, <a href="#rfc.xref.header.warning.4">2.5.2</a>, <a href="#rfc.xref.header.warning.5">2.5.3</a>, <a href="#rfc.iref.w.1"><b>3.6</b></a>, <a href="#rfc.xref.header.warning.6">A</a></li>
     1961               </ul>
     1962            </li>
     1963         </ul>
     1964      </div>
    17651965      <h1><a id="rfc.copyright" href="#rfc.copyright">Full Copyright Statement</a></h1>
     1966      <p>Copyright © The IETF Trust (2007).</p>
    17661967      <p>This document is subject to the rights, licenses and restrictions contained in BCP 78, and except as set forth therein, the
    17671968         authors retain all their rights.
     
    17811982      <p>Copies of IPR disclosures made to the IETF Secretariat and any assurances of licenses to be made available, or the result
    17821983         of an attempt made to obtain a general license or permission for the use of such proprietary rights by implementers or users
    1783          of this specification can be obtained from the IETF on-line IPR repository at &lt;<a href="http://www.ietf.org/ipr">http://www.ietf.org/ipr</a>&gt;.
     1984         of this specification can be obtained from the IETF on-line IPR repository at <a href="http://www.ietf.org/ipr">http://www.ietf.org/ipr</a>.
    17841985      </p>
    17851986      <p>The IETF invites any interested party to bring to its attention any copyrights, patents or patent applications, or other proprietary
     
    17871988         at <a href="mailto:ietf-ipr@ietf.org">ietf-ipr@ietf.org</a>.
    17881989      </p>
    1789       <h1 id="rfc.index"><a href="#rfc.index">Index</a></h1>
    1790       <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>
    1791       </p>
    1792       <div class="print2col">
    1793          <ul class="ind">
    1794             <li class="indline0"><a id="rfc.index.A" href="#rfc.index.A"><b>A</b></a><ul class="ind">
    1795                   <li class="indline1">age&nbsp;&nbsp;<a class="iref" href="#rfc.iref.a.1">1.1</a></li>
    1796                   <li class="indline1">Age header&nbsp;&nbsp;<a class="iref" href="#rfc.iref.a.2"><b>3.1</b></a></li>
    1797                </ul>
    1798             </li>
    1799             <li class="indline0"><a id="rfc.index.C" href="#rfc.index.C"><b>C</b></a><ul class="ind">
    1800                   <li class="indline1">cache&nbsp;&nbsp;<a class="iref" href="#rfc.iref.c.1">1.1</a></li>
    1801                   <li class="indline1">Cache Directives&nbsp;&nbsp;
    1802                      <ul class="ind">
    1803                         <li class="indline1">max-age&nbsp;&nbsp;<a class="iref" href="#rfc.iref.c.9"><b>3.2.3</b></a>, <a class="iref" href="#rfc.iref.c.12"><b>3.2.4</b></a></li>
    1804                         <li class="indline1">max-stale&nbsp;&nbsp;<a class="iref" href="#rfc.iref.c.11"><b>3.2.3</b></a></li>
    1805                         <li class="indline1">min-fresh&nbsp;&nbsp;<a class="iref" href="#rfc.iref.c.10"><b>3.2.3</b></a></li>
    1806                         <li class="indline1">must-revalidate&nbsp;&nbsp;<a class="iref" href="#rfc.iref.c.14"><b>3.2.4</b></a></li>
    1807                         <li class="indline1">no-cache&nbsp;&nbsp;<a class="iref" href="#rfc.iref.c.6"><b>3.2.1</b></a></li>
    1808                         <li class="indline1">no-store&nbsp;&nbsp;<a class="iref" href="#rfc.iref.c.7"><b>3.2.2</b></a></li>
    1809                         <li class="indline1">no-transform&nbsp;&nbsp;<a class="iref" href="#rfc.iref.c.16"><b>3.2.5</b></a></li>
    1810                         <li class="indline1">only-if-cached&nbsp;&nbsp;<a class="iref" href="#rfc.iref.c.13"><b>3.2.4</b></a></li>
    1811                         <li class="indline1">private&nbsp;&nbsp;<a class="iref" href="#rfc.iref.c.5"><b>3.2.1</b></a></li>
    1812                         <li class="indline1">proxy-revalidate&nbsp;&nbsp;<a class="iref" href="#rfc.iref.c.15"><b>3.2.4</b></a></li>
    1813                         <li class="indline1">public&nbsp;&nbsp;<a class="iref" href="#rfc.iref.c.4"><b>3.2.1</b></a></li>
    1814                         <li class="indline1">s-maxage&nbsp;&nbsp;<a class="iref" href="#rfc.iref.c.8"><b>3.2.3</b></a></li>
    1815                      </ul>
    1816                   </li>
    1817                   <li class="indline1">Cache-Control header&nbsp;&nbsp;<a class="iref" href="#rfc.xref.header.cache-control.1">2.1.1</a>, <a class="iref" href="#rfc.xref.header.cache-control.2">2.1.1</a>, <a class="iref" href="#rfc.xref.header.cache-control.3">2.1.3</a>, <a class="iref" href="#rfc.xref.header.cache-control.4">2.2.1</a>, <a class="iref" href="#rfc.xref.header.cache-control.5">2.2.5</a>, <a class="iref" href="#rfc.xref.header.cache-control.6">2.4</a>, <a class="iref" href="#rfc.xref.header.cache-control.7">2.4</a>, <a class="iref" href="#rfc.xref.header.cache-control.8">2.8</a>, <a class="iref" href="#rfc.iref.c.3"><b>3.2</b></a>, <a class="iref" href="#rfc.xref.header.cache-control.9">3.3</a>, <a class="iref" href="#rfc.xref.header.cache-control.10">3.4</a>, <a class="iref" href="#rfc.xref.header.cache-control.11">A</a></li>
    1818                   <li class="indline1">cacheable&nbsp;&nbsp;<a class="iref" href="#rfc.iref.c.2">1.1</a></li>
    1819                </ul>
    1820             </li>
    1821             <li class="indline0"><a id="rfc.index.E" href="#rfc.index.E"><b>E</b></a><ul class="ind">
    1822                   <li class="indline1">Expires header&nbsp;&nbsp;<a class="iref" href="#rfc.xref.header.expires.1">2.4</a>, <a class="iref" href="#rfc.xref.header.expires.2">3.2.3</a>, <a class="iref" href="#rfc.iref.e.2"><b>3.3</b></a></li>
    1823                   <li class="indline1">explicit expiration time&nbsp;&nbsp;<a class="iref" href="#rfc.iref.e.1">1.1</a></li>
    1824                </ul>
    1825             </li>
    1826             <li class="indline0"><a id="rfc.index.F" href="#rfc.index.F"><b>F</b></a><ul class="ind">
    1827                   <li class="indline1">first-hand&nbsp;&nbsp;<a class="iref" href="#rfc.iref.f.1">1.1</a></li>
    1828                   <li class="indline1">fresh&nbsp;&nbsp;<a class="iref" href="#rfc.iref.f.3">1.1</a></li>
    1829                   <li class="indline1">freshness lifetime&nbsp;&nbsp;<a class="iref" href="#rfc.iref.f.2">1.1</a></li>
    1830                </ul>
    1831             </li>
    1832             <li class="indline0"><a id="rfc.index.G" href="#rfc.index.G"><b>G</b></a><ul class="ind">
    1833                   <li class="indline1"><tt>Grammar</tt>&nbsp;&nbsp;
    1834                      <ul class="ind">
    1835                         <li class="indline1"><tt>Age</tt>&nbsp;&nbsp;<a class="iref" href="#rfc.iref.g.2"><b>3.1</b></a></li>
    1836                         <li class="indline1"><tt>age-value</tt>&nbsp;&nbsp;<a class="iref" href="#rfc.iref.g.3"><b>3.1</b></a></li>
    1837                         <li class="indline1"><tt>Cache-Control</tt>&nbsp;&nbsp;<a class="iref" href="#rfc.iref.g.4"><b>3.2</b></a></li>
    1838                         <li class="indline1"><tt>cache-directive</tt>&nbsp;&nbsp;<a class="iref" href="#rfc.iref.g.5"><b>3.2</b></a></li>
    1839                         <li class="indline1"><tt>cache-extension</tt>&nbsp;&nbsp;<a class="iref" href="#rfc.iref.g.8"><b>3.2</b></a></li>
    1840                         <li class="indline1"><tt>cache-request-directive</tt>&nbsp;&nbsp;<a class="iref" href="#rfc.iref.g.6"><b>3.2</b></a></li>
    1841                         <li class="indline1"><tt>cache-response-directive</tt>&nbsp;&nbsp;<a class="iref" href="#rfc.iref.g.7"><b>3.2</b></a></li>
    1842                         <li class="indline1"><tt>delta-seconds</tt>&nbsp;&nbsp;<a class="iref" href="#rfc.iref.g.1"><b>1.2</b></a></li>
    1843                         <li class="indline1"><tt>Expires</tt>&nbsp;&nbsp;<a class="iref" href="#rfc.iref.g.9"><b>3.3</b></a></li>
    1844                         <li class="indline1"><tt>extension-pragma</tt>&nbsp;&nbsp;<a class="iref" href="#rfc.iref.g.12"><b>3.4</b></a></li>
    1845                         <li class="indline1"><tt>Pragma</tt>&nbsp;&nbsp;<a class="iref" href="#rfc.iref.g.10"><b>3.4</b></a></li>
    1846                         <li class="indline1"><tt>pragma-directive</tt>&nbsp;&nbsp;<a class="iref" href="#rfc.iref.g.11"><b>3.4</b></a></li>
    1847                         <li class="indline1"><tt>Vary</tt>&nbsp;&nbsp;<a class="iref" href="#rfc.iref.g.13"><b>3.5</b></a></li>
    1848                         <li class="indline1"><tt>warn-agent</tt>&nbsp;&nbsp;<a class="iref" href="#rfc.iref.g.17"><b>3.6</b></a></li>
    1849                         <li class="indline1"><tt>warn-code</tt>&nbsp;&nbsp;<a class="iref" href="#rfc.iref.g.16"><b>3.6</b></a></li>
    1850                         <li class="indline1"><tt>warn-date</tt>&nbsp;&nbsp;<a class="iref" href="#rfc.iref.g.19"><b>3.6</b></a></li>
    1851                         <li class="indline1"><tt>warn-text</tt>&nbsp;&nbsp;<a class="iref" href="#rfc.iref.g.18"><b>3.6</b></a></li>
    1852                         <li class="indline1"><tt>Warning</tt>&nbsp;&nbsp;<a class="iref" href="#rfc.iref.g.14"><b>3.6</b></a></li>
    1853                         <li class="indline1"><tt>warning-value</tt>&nbsp;&nbsp;<a class="iref" href="#rfc.iref.g.15"><b>3.6</b></a></li>
    1854                      </ul>
    1855                   </li>
    1856                </ul>
    1857             </li>
    1858             <li class="indline0"><a id="rfc.index.H" href="#rfc.index.H"><b>H</b></a><ul class="ind">
    1859                   <li class="indline1">Headers&nbsp;&nbsp;
    1860                      <ul class="ind">
    1861                         <li class="indline1">Age&nbsp;&nbsp;<a class="iref" href="#rfc.iref.h.2"><b>3.1</b></a></li>
    1862                         <li class="indline1">Cache-Control&nbsp;&nbsp;<a class="iref" href="#rfc.xref.header.cache-control.1">2.1.1</a>, <a class="iref" href="#rfc.xref.header.cache-control.2">2.1.1</a>, <a class="iref" href="#rfc.xref.header.cache-control.3">2.1.3</a>, <a class="iref" href="#rfc.xref.header.cache-control.4">2.2.1</a>, <a class="iref" href="#rfc.xref.header.cache-control.5">2.2.5</a>, <a class="iref" href="#rfc.xref.header.cache-control.6">2.4</a>, <a class="iref" href="#rfc.xref.header.cache-control.7">2.4</a>, <a class="iref" href="#rfc.xref.header.cache-control.8">2.8</a>, <a class="iref" href="#rfc.iref.h.3"><b>3.2</b></a>, <a class="iref" href="#rfc.xref.header.cache-control.9">3.3</a>, <a class="iref" href="#rfc.xref.header.cache-control.10">3.4</a>, <a class="iref" href="#rfc.xref.header.cache-control.11">A</a></li>
    1863                         <li class="indline1">Expires&nbsp;&nbsp;<a class="iref" href="#rfc.xref.header.expires.1">2.4</a>, <a class="iref" href="#rfc.xref.header.expires.2">3.2.3</a>, <a class="iref" href="#rfc.iref.h.4"><b>3.3</b></a></li>
    1864                         <li class="indline1">Pragma&nbsp;&nbsp;<a class="iref" href="#rfc.xref.header.pragma.1">3.2</a>, <a class="iref" href="#rfc.iref.h.5"><b>3.4</b></a></li>
    1865                         <li class="indline1">Vary&nbsp;&nbsp;<a class="iref" href="#rfc.xref.header.vary.1">2.6</a>, <a class="iref" href="#rfc.iref.h.6"><b>3.5</b></a></li>
    1866                         <li class="indline1">Warning&nbsp;&nbsp;<a class="iref" href="#rfc.xref.header.warning.1">2.1.1</a>, <a class="iref" href="#rfc.xref.header.warning.2">2.1.2</a>, <a class="iref" href="#rfc.xref.header.warning.3">2.1.2</a>, <a class="iref" href="#rfc.xref.header.warning.4">2.5.2</a>, <a class="iref" href="#rfc.xref.header.warning.5">2.5.3</a>, <a class="iref" href="#rfc.iref.h.7"><b>3.6</b></a>, <a class="iref" href="#rfc.xref.header.warning.6">A</a></li>
    1867                      </ul>
    1868                   </li>
    1869                   <li class="indline1">heuristic expiration time&nbsp;&nbsp;<a class="iref" href="#rfc.iref.h.1">1.1</a></li>
    1870                </ul>
    1871             </li>
    1872             <li class="indline0"><a id="rfc.index.M" href="#rfc.index.M"><b>M</b></a><ul class="ind">
    1873                   <li class="indline1">max-age&nbsp;&nbsp;
    1874                      <ul class="ind">
    1875                         <li class="indline1">Cache Directive&nbsp;&nbsp;<a class="iref" href="#rfc.iref.m.1"><b>3.2.3</b></a>, <a class="iref" href="#rfc.iref.m.4"><b>3.2.4</b></a></li>
    1876                      </ul>
    1877                   </li>
    1878                   <li class="indline1">max-stale&nbsp;&nbsp;
    1879                      <ul class="ind">
    1880                         <li class="indline1">Cache Directive&nbsp;&nbsp;<a class="iref" href="#rfc.iref.m.3"><b>3.2.3</b></a></li>
    1881                      </ul>
    1882                   </li>
    1883                   <li class="indline1">min-fresh&nbsp;&nbsp;
    1884                      <ul class="ind">
    1885                         <li class="indline1">Cache Directive&nbsp;&nbsp;<a class="iref" href="#rfc.iref.m.2"><b>3.2.3</b></a></li>
    1886                      </ul>
    1887                   </li>
    1888                   <li class="indline1">must-revalidate&nbsp;&nbsp;
    1889                      <ul class="ind">
    1890                         <li class="indline1">Cache Directive&nbsp;&nbsp;<a class="iref" href="#rfc.iref.m.5"><b>3.2.4</b></a></li>
    1891                      </ul>
    1892                   </li>
    1893                </ul>
    1894             </li>
    1895             <li class="indline0"><a id="rfc.index.N" href="#rfc.index.N"><b>N</b></a><ul class="ind">
    1896                   <li class="indline1">no-cache&nbsp;&nbsp;
    1897                      <ul class="ind">
    1898                         <li class="indline1">Cache Directive&nbsp;&nbsp;<a class="iref" href="#rfc.iref.n.1"><b>3.2.1</b></a></li>
    1899                      </ul>
    1900                   </li>
    1901                   <li class="indline1">no-store&nbsp;&nbsp;
    1902                      <ul class="ind">
    1903                         <li class="indline1">Cache Directive&nbsp;&nbsp;<a class="iref" href="#rfc.iref.n.2"><b>3.2.2</b></a></li>
    1904                      </ul>
    1905                   </li>
    1906                   <li class="indline1">no-transform&nbsp;&nbsp;
    1907                      <ul class="ind">
    1908                         <li class="indline1">Cache Directive&nbsp;&nbsp;<a class="iref" href="#rfc.iref.n.3"><b>3.2.5</b></a></li>
    1909                      </ul>
    1910                   </li>
    1911                </ul>
    1912             </li>
    1913             <li class="indline0"><a id="rfc.index.O" href="#rfc.index.O"><b>O</b></a><ul class="ind">
    1914                   <li class="indline1">only-if-cached&nbsp;&nbsp;
    1915                      <ul class="ind">
    1916                         <li class="indline1">Cache Directive&nbsp;&nbsp;<a class="iref" href="#rfc.iref.o.1"><b>3.2.4</b></a></li>
    1917                      </ul>
    1918                   </li>
    1919                </ul>
    1920             </li>
    1921             <li class="indline0"><a id="rfc.index.P" href="#rfc.index.P"><b>P</b></a><ul class="ind">
    1922                   <li class="indline1"><em>Part1</em>&nbsp;&nbsp;<a class="iref" href="#rfc.xref.Part1.1">2.2.3</a>, <a class="iref" href="#rfc.xref.Part1.2">2.5.1</a>, <a class="iref" href="#rfc.xref.Part1.3">2.5.2</a>, <a class="iref" href="#rfc.xref.Part1.4">2.5.2</a>, <a class="iref" href="#rfc.xref.Part1.5">2.6</a>, <a class="iref" href="#rfc.xref.Part1.6">3.3</a>, <a class="iref" href="#Part1"><b>7</b></a><ul class="ind">
    1923                         <li class="indline1"><em>Section 3.3.1</em>&nbsp;&nbsp;<a class="iref" href="#rfc.xref.Part1.6">3.3</a></li>
    1924                         <li class="indline1"><em>Section 4.2</em>&nbsp;&nbsp;<a class="iref" href="#rfc.xref.Part1.5">2.6</a></li>
    1925                         <li class="indline1"><em>Section 4.4</em>&nbsp;&nbsp;<a class="iref" href="#rfc.xref.Part1.3">2.5.2</a>, <a class="iref" href="#rfc.xref.Part1.4">2.5.2</a></li>
    1926                         <li class="indline1"><em>Section 8.1</em>&nbsp;&nbsp;<a class="iref" href="#rfc.xref.Part1.2">2.5.1</a></li>
    1927                         <li class="indline1"><em>Section 8.3</em>&nbsp;&nbsp;<a class="iref" href="#rfc.xref.Part1.1">2.2.3</a></li>
    1928                      </ul>
    1929                   </li>
    1930                   <li class="indline1"><em>Part2</em>&nbsp;&nbsp;<a class="iref" href="#rfc.xref.Part2.1">2.9</a>, <a class="iref" href="#Part2"><b>7</b></a><ul class="ind">
    1931                         <li class="indline1"><em>Section 8.1.1</em>&nbsp;&nbsp;<a class="iref" href="#rfc.xref.Part2.1">2.9</a></li>
    1932                      </ul>
    1933                   </li>
    1934                   <li class="indline1"><em>Part3</em>&nbsp;&nbsp;<a class="iref" href="#rfc.xref.Part3.1">2.5.2</a>, <a class="iref" href="#rfc.xref.Part3.2">2.6</a>, <a class="iref" href="#Part3"><b>7</b></a><ul class="ind">
    1935                         <li class="indline1"><em>Section 3.2.2</em>&nbsp;&nbsp;<a class="iref" href="#rfc.xref.Part3.1">2.5.2</a></li>
    1936                         <li class="indline1"><em>Section 4.1</em>&nbsp;&nbsp;<a class="iref" href="#rfc.xref.Part3.2">2.6</a></li>
    1937                      </ul>
    1938                   </li>
    1939                   <li class="indline1"><em>Part4</em>&nbsp;&nbsp;<a class="iref" href="#rfc.xref.Part4.1">2.3</a>, <a class="iref" href="#rfc.xref.Part4.2">2.3.2</a>, <a class="iref" href="#Part4"><b>7</b></a><ul class="ind">
    1940                         <li class="indline1"><em>Section 2</em>&nbsp;&nbsp;<a class="iref" href="#rfc.xref.Part4.2">2.3.2</a></li>
    1941                         <li class="indline1"><em>Section 4</em>&nbsp;&nbsp;<a class="iref" href="#rfc.xref.Part4.1">2.3</a></li>
    1942                      </ul>
    1943                   </li>
    1944                   <li class="indline1"><em>Part5</em>&nbsp;&nbsp;<a class="iref" href="#rfc.xref.Part5.1">2.5.3</a>, <a class="iref" href="#rfc.xref.Part5.2">2.8</a>, <a class="iref" href="#Part5"><b>7</b></a><ul class="ind">
    1945                         <li class="indline1"><em>Section 4</em>&nbsp;&nbsp;<a class="iref" href="#rfc.xref.Part5.1">2.5.3</a>, <a class="iref" href="#rfc.xref.Part5.2">2.8</a></li>
    1946                      </ul>
    1947                   </li>
    1948                   <li class="indline1"><em>Part7</em>&nbsp;&nbsp;<a class="iref" href="#rfc.xref.Part7.1">2.4</a>, <a class="iref" href="#rfc.xref.Part7.2">3.2.1</a>, <a class="iref" href="#Part7"><b>7</b></a><ul class="ind">
    1949                         <li class="indline1"><em>Section 3.1</em>&nbsp;&nbsp;<a class="iref" href="#rfc.xref.Part7.1">2.4</a>, <a class="iref" href="#rfc.xref.Part7.2">3.2.1</a></li>
    1950                      </ul>
    1951                   </li>
    1952                   <li class="indline1">Pragma header&nbsp;&nbsp;<a class="iref" href="#rfc.xref.header.pragma.1">3.2</a>, <a class="iref" href="#rfc.iref.p.4"><b>3.4</b></a></li>
    1953                   <li class="indline1">private&nbsp;&nbsp;
    1954                      <ul class="ind">
    1955                         <li class="indline1">Cache Directive&nbsp;&nbsp;<a class="iref" href="#rfc.iref.p.2"><b>3.2.1</b></a></li>
    1956                      </ul>
    1957                   </li>
    1958                   <li class="indline1">proxy-revalidate&nbsp;&nbsp;
    1959                      <ul class="ind">
    1960                         <li class="indline1">Cache Directive&nbsp;&nbsp;<a class="iref" href="#rfc.iref.p.3"><b>3.2.4</b></a></li>
    1961                      </ul>
    1962                   </li>
    1963                   <li class="indline1">public&nbsp;&nbsp;
    1964                      <ul class="ind">
    1965                         <li class="indline1">Cache Directive&nbsp;&nbsp;<a class="iref" href="#rfc.iref.p.1"><b>3.2.1</b></a></li>
    1966                      </ul>
    1967                   </li>
    1968                </ul>
    1969             </li>
    1970             <li class="indline0"><a id="rfc.index.R" href="#rfc.index.R"><b>R</b></a><ul class="ind">
    1971                   <li class="indline1"><em>RFC1305</em>&nbsp;&nbsp;<a class="iref" href="#rfc.xref.RFC1305.1">2.2.3</a>, <a class="iref" href="#RFC1305"><b>7</b></a></li>
    1972                   <li class="indline1"><em>RFC2047</em>&nbsp;&nbsp;<a class="iref" href="#rfc.xref.RFC2047.1">3.6</a>, <a class="iref" href="#RFC2047"><b>7</b></a></li>
    1973                   <li class="indline1"><em>RFC2616</em>&nbsp;&nbsp;<a class="iref" href="#rfc.xref.RFC2616.1">§</a>, <a class="iref" href="#rfc.xref.RFC2616.2">1</a>, <a class="iref" href="#RFC2616"><b>7</b></a></li>
    1974                </ul>
    1975             </li>
    1976             <li class="indline0"><a id="rfc.index.S" href="#rfc.index.S"><b>S</b></a><ul class="ind">
    1977                   <li class="indline1">s-maxage&nbsp;&nbsp;
    1978                      <ul class="ind">
    1979                         <li class="indline1">Cache Directive&nbsp;&nbsp;<a class="iref" href="#rfc.iref.s.3"><b>3.2.3</b></a></li>
    1980                      </ul>
    1981                   </li>
    1982                   <li class="indline1">semantically transparent&nbsp;&nbsp;<a class="iref" href="#rfc.iref.s.2">1.1</a></li>
    1983                   <li class="indline1">stale&nbsp;&nbsp;<a class="iref" href="#rfc.iref.s.1">1.1</a></li>
    1984                </ul>
    1985             </li>
    1986             <li class="indline0"><a id="rfc.index.V" href="#rfc.index.V"><b>V</b></a><ul class="ind">
    1987                   <li class="indline1">validator&nbsp;&nbsp;<a class="iref" href="#rfc.iref.v.1">1.1</a></li>
    1988                   <li class="indline1">Vary header&nbsp;&nbsp;<a class="iref" href="#rfc.xref.header.vary.1">2.6</a>, <a class="iref" href="#rfc.iref.v.2"><b>3.5</b></a></li>
    1989                </ul>
    1990             </li>
    1991             <li class="indline0"><a id="rfc.index.W" href="#rfc.index.W"><b>W</b></a><ul class="ind">
    1992                   <li class="indline1">Warning header&nbsp;&nbsp;<a class="iref" href="#rfc.xref.header.warning.1">2.1.1</a>, <a class="iref" href="#rfc.xref.header.warning.2">2.1.2</a>, <a class="iref" href="#rfc.xref.header.warning.3">2.1.2</a>, <a class="iref" href="#rfc.xref.header.warning.4">2.5.2</a>, <a class="iref" href="#rfc.xref.header.warning.5">2.5.3</a>, <a class="iref" href="#rfc.iref.w.1"><b>3.6</b></a>, <a class="iref" href="#rfc.xref.header.warning.6">A</a></li>
    1993                </ul>
    1994             </li>
    1995          </ul>
    1996       </div>
    19971990   </body>
    19981991</html>
Note: See TracChangeset for help on using the changeset viewer.