Changeset 2236


Ignore:
Timestamp:
May 6, 2013, 11:21:36 PM (6 years ago)
Author:
mnot@…
Message:

Alphabetise cache-control directives; see #469

Location:
draft-ietf-httpbis/latest
Files:
2 edited

Legend:

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

    r2235 r2236  
    614614               <li><a href="#rfc.section.7.2">7.2</a>&nbsp;&nbsp;&nbsp;<a href="#header.cache-control">Cache-Control</a><ul>
    615615                     <li><a href="#rfc.section.7.2.1">7.2.1</a>&nbsp;&nbsp;&nbsp;<a href="#cache-request-directive">Request Cache-Control Directives</a><ul>
    616                            <li><a href="#rfc.section.7.2.1.1">7.2.1.1</a>&nbsp;&nbsp;&nbsp;<a href="#cache-request-directive.no-cache">no-cache</a></li>
    617                            <li><a href="#rfc.section.7.2.1.2">7.2.1.2</a>&nbsp;&nbsp;&nbsp;<a href="#cache-request-directive.no-store">no-store</a></li>
    618                            <li><a href="#rfc.section.7.2.1.3">7.2.1.3</a>&nbsp;&nbsp;&nbsp;<a href="#cache-request-directive.max-age">max-age</a></li>
    619                            <li><a href="#rfc.section.7.2.1.4">7.2.1.4</a>&nbsp;&nbsp;&nbsp;<a href="#cache-request-directive.max-stale">max-stale</a></li>
    620                            <li><a href="#rfc.section.7.2.1.5">7.2.1.5</a>&nbsp;&nbsp;&nbsp;<a href="#cache-request-directive.min-fresh">min-fresh</a></li>
     616                           <li><a href="#rfc.section.7.2.1.1">7.2.1.1</a>&nbsp;&nbsp;&nbsp;<a href="#cache-request-directive.max-age">max-age</a></li>
     617                           <li><a href="#rfc.section.7.2.1.2">7.2.1.2</a>&nbsp;&nbsp;&nbsp;<a href="#cache-request-directive.max-stale">max-stale</a></li>
     618                           <li><a href="#rfc.section.7.2.1.3">7.2.1.3</a>&nbsp;&nbsp;&nbsp;<a href="#cache-request-directive.min-fresh">min-fresh</a></li>
     619                           <li><a href="#rfc.section.7.2.1.4">7.2.1.4</a>&nbsp;&nbsp;&nbsp;<a href="#cache-request-directive.no-cache">no-cache</a></li>
     620                           <li><a href="#rfc.section.7.2.1.5">7.2.1.5</a>&nbsp;&nbsp;&nbsp;<a href="#cache-request-directive.no-store">no-store</a></li>
    621621                           <li><a href="#rfc.section.7.2.1.6">7.2.1.6</a>&nbsp;&nbsp;&nbsp;<a href="#cache-request-directive.no-transform">no-transform</a></li>
    622622                           <li><a href="#rfc.section.7.2.1.7">7.2.1.7</a>&nbsp;&nbsp;&nbsp;<a href="#cache-request-directive.only-if-cached">only-if-cached</a></li>
     
    624624                     </li>
    625625                     <li><a href="#rfc.section.7.2.2">7.2.2</a>&nbsp;&nbsp;&nbsp;<a href="#cache-response-directive">Response Cache-Control Directives</a><ul>
    626                            <li><a href="#rfc.section.7.2.2.1">7.2.2.1</a>&nbsp;&nbsp;&nbsp;<a href="#cache-response-directive.public">public</a></li>
    627                            <li><a href="#rfc.section.7.2.2.2">7.2.2.2</a>&nbsp;&nbsp;&nbsp;<a href="#cache-response-directive.private">private</a></li>
    628                            <li><a href="#rfc.section.7.2.2.3">7.2.2.3</a>&nbsp;&nbsp;&nbsp;<a href="#cache-response-directive.no-cache">no-cache</a></li>
    629                            <li><a href="#rfc.section.7.2.2.4">7.2.2.4</a>&nbsp;&nbsp;&nbsp;<a href="#cache-response-directive.no-store">no-store</a></li>
    630                            <li><a href="#rfc.section.7.2.2.5">7.2.2.5</a>&nbsp;&nbsp;&nbsp;<a href="#cache-response-directive.must-revalidate">must-revalidate</a></li>
    631                            <li><a href="#rfc.section.7.2.2.6">7.2.2.6</a>&nbsp;&nbsp;&nbsp;<a href="#cache-response-directive.proxy-revalidate">proxy-revalidate</a></li>
    632                            <li><a href="#rfc.section.7.2.2.7">7.2.2.7</a>&nbsp;&nbsp;&nbsp;<a href="#cache-response-directive.max-age">max-age</a></li>
    633                            <li><a href="#rfc.section.7.2.2.8">7.2.2.8</a>&nbsp;&nbsp;&nbsp;<a href="#cache-response-directive.s-maxage">s-maxage</a></li>
    634                            <li><a href="#rfc.section.7.2.2.9">7.2.2.9</a>&nbsp;&nbsp;&nbsp;<a href="#cache-response-directive.no-transform">no-transform</a></li>
     626                           <li><a href="#rfc.section.7.2.2.1">7.2.2.1</a>&nbsp;&nbsp;&nbsp;<a href="#cache-response-directive.must-revalidate">must-revalidate</a></li>
     627                           <li><a href="#rfc.section.7.2.2.2">7.2.2.2</a>&nbsp;&nbsp;&nbsp;<a href="#cache-response-directive.no-cache">no-cache</a></li>
     628                           <li><a href="#rfc.section.7.2.2.3">7.2.2.3</a>&nbsp;&nbsp;&nbsp;<a href="#cache-response-directive.no-store">no-store</a></li>
     629                           <li><a href="#rfc.section.7.2.2.4">7.2.2.4</a>&nbsp;&nbsp;&nbsp;<a href="#cache-response-directive.no-transform">no-transform</a></li>
     630                           <li><a href="#rfc.section.7.2.2.5">7.2.2.5</a>&nbsp;&nbsp;&nbsp;<a href="#cache-response-directive.public">public</a></li>
     631                           <li><a href="#rfc.section.7.2.2.6">7.2.2.6</a>&nbsp;&nbsp;&nbsp;<a href="#cache-response-directive.private">private</a></li>
     632                           <li><a href="#rfc.section.7.2.2.7">7.2.2.7</a>&nbsp;&nbsp;&nbsp;<a href="#cache-response-directive.proxy-revalidate">proxy-revalidate</a></li>
     633                           <li><a href="#rfc.section.7.2.2.8">7.2.2.8</a>&nbsp;&nbsp;&nbsp;<a href="#cache-response-directive.max-age">max-age</a></li>
     634                           <li><a href="#rfc.section.7.2.2.9">7.2.2.9</a>&nbsp;&nbsp;&nbsp;<a href="#cache-response-directive.s-maxage">s-maxage</a></li>
    635635                        </ul>
    636636                     </li>
     
    811811         <li>the "no-store" cache directive (see <a href="#header.cache-control" id="rfc.xref.header.cache-control.1" title="Cache-Control">Section&nbsp;7.2</a>) does not appear in request or response header fields, and
    812812         </li>
    813          <li>the "private" cache response directive (see <a href="#cache-response-directive.private" title="private">Section&nbsp;7.2.2.2</a>) does not appear in the response, if the cache is shared, and
     813         <li>the "private" cache response directive (see <a href="#cache-response-directive.private" title="private">Section&nbsp;7.2.2.6</a>) does not appear in the response, if the cache is shared, and
    814814         </li>
    815815         <li>the <a href="p7-auth.html#header.authorization" class="smpl">Authorization</a> header field (see <a href="p7-auth.html#header.authorization" title="Authorization">Section 4.1</a> of <a href="#Part7" id="rfc.xref.Part7.1"><cite title="Hypertext Transfer Protocol (HTTP/1.1): Authentication">[Part7]</cite></a>) does not appear in the request, if the cache is shared, unless the response explicitly allows it (see <a href="#caching.authenticated.responses" title="Storing Responses to Authenticated Requests">Section&nbsp;3.2</a>), and
     
    819819               <li>contains an <a href="#header.expires" class="smpl">Expires</a> header field (see <a href="#header.expires" id="rfc.xref.header.expires.1" title="Expires">Section&nbsp;7.3</a>), or
    820820               </li>
    821                <li>contains a max-age response cache directive (see <a href="#cache-response-directive.max-age" title="max-age">Section&nbsp;7.2.2.7</a>), or
     821               <li>contains a max-age response cache directive (see <a href="#cache-response-directive.max-age" title="max-age">Section&nbsp;7.2.2.8</a>), or
    822822               </li>
    823                <li>contains a s-maxage response cache directive (see <a href="#cache-response-directive.s-maxage" title="s-maxage">Section&nbsp;7.2.2.8</a>) and the cache is shared, or
     823               <li>contains a s-maxage response cache directive (see <a href="#cache-response-directive.s-maxage" title="s-maxage">Section&nbsp;7.2.2.9</a>) and the cache is shared, or
    824824               </li>
    825825               <li>contains a Cache Control Extension (see <a href="#cache.control.extensions" title="Cache Control Extensions">Section&nbsp;7.2.3</a>) that allows it to be cached, or
     
    827827               <li>has a status code that is defined as cacheable (see <a href="#heuristic.freshness" title="Calculating Heuristic Freshness">Section&nbsp;4.1.2</a>), or
    828828               </li>
    829                <li>contains a public response cache directive (see <a href="#cache-response-directive.public" title="public">Section&nbsp;7.2.2.1</a>).
     829               <li>contains a public response cache directive (see <a href="#cache-response-directive.public" title="public">Section&nbsp;7.2.2.5</a>).
    830830               </li>
    831831            </ul>
     
    868868         <li>the presented request does not contain the no-cache pragma (<a href="#header.pragma" id="rfc.xref.header.pragma.1" title="Pragma">Section&nbsp;7.4</a>), nor the no-cache cache directive (<a href="#cache-request-directive" title="Request Cache-Control Directives">Section&nbsp;7.2.1</a>), unless the stored response is successfully validated (<a href="#validation.model" title="Validation">Section&nbsp;4.2</a>), and
    869869         </li>
    870          <li>the stored response does not contain the no-cache cache directive (<a href="#cache-response-directive.no-cache" title="no-cache">Section&nbsp;7.2.2.3</a>), unless it is successfully validated (<a href="#validation.model" title="Validation">Section&nbsp;4.2</a>), and
     870         <li>the stored response does not contain the no-cache cache directive (<a href="#cache-response-directive.no-cache" title="no-cache">Section&nbsp;7.2.2.2</a>), unless it is successfully validated (<a href="#validation.model" title="Validation">Section&nbsp;4.2</a>), and
    871871         </li>
    872872         <li>the stored response is either:
     
    900900      </p>
    901901      <p id="rfc.section.4.1.p.2">The primary mechanism for determining freshness is for an origin server to provide an explicit expiration time in the future,
    902          using either the <a href="#header.expires" class="smpl">Expires</a> header field (<a href="#header.expires" id="rfc.xref.header.expires.2" title="Expires">Section&nbsp;7.3</a>) or the max-age response cache directive (<a href="#cache-response-directive.max-age" title="max-age">Section&nbsp;7.2.2.7</a>). Generally, origin servers will assign future explicit expiration times to responses in the belief that the representation
     902         using either the <a href="#header.expires" class="smpl">Expires</a> header field (<a href="#header.expires" id="rfc.xref.header.expires.2" title="Expires">Section&nbsp;7.3</a>) or the max-age response cache directive (<a href="#cache-response-directive.max-age" title="max-age">Section&nbsp;7.2.2.8</a>). Generally, origin servers will assign future explicit expiration times to responses in the belief that the representation
    903903         is not likely to change in a semantically significant way before the expiration time is reached.
    904904      </p>
     
    935935      <p id="rfc.section.4.1.1.p.1">A cache can calculate the freshness lifetime (denoted as freshness_lifetime) of a response by using the first match of: </p>
    936936      <ul>
    937          <li>If the cache is shared and the s-maxage response cache directive (<a href="#cache-response-directive.s-maxage" title="s-maxage">Section&nbsp;7.2.2.8</a>) is present, use its value, or
    938          </li>
    939          <li>If the max-age response cache directive (<a href="#cache-response-directive.max-age" title="max-age">Section&nbsp;7.2.2.7</a>) is present, use its value, or
     937         <li>If the cache is shared and the s-maxage response cache directive (<a href="#cache-response-directive.s-maxage" title="s-maxage">Section&nbsp;7.2.2.9</a>) is present, use its value, or
     938         </li>
     939         <li>If the max-age response cache directive (<a href="#cache-response-directive.max-age" title="max-age">Section&nbsp;7.2.2.8</a>) is present, use its value, or
    940940         </li>
    941941         <li>If the <a href="#header.expires" class="smpl">Expires</a> response header field (<a href="#header.expires" id="rfc.xref.header.expires.3" title="Expires">Section&nbsp;7.3</a>) is present, use its value minus the value of the <a href="p2-semantics.html#header.date" class="smpl">Date</a> response header field, or
     
    12101210</pre><p id="rfc.section.7.2.p.7">For the cache directives defined below, no argument is defined (nor allowed) unless stated otherwise.</p>
    12111211      <h3 id="rfc.section.7.2.1"><a href="#rfc.section.7.2.1">7.2.1</a>&nbsp;<a id="cache-request-directive" href="#cache-request-directive">Request Cache-Control Directives</a></h3>
    1212       <div id="rfc.iref.n.1"></div>
    1213       <h4 id="rfc.section.7.2.1.1"><a href="#rfc.section.7.2.1.1">7.2.1.1</a>&nbsp;<a id="cache-request-directive.no-cache" href="#cache-request-directive.no-cache">no-cache</a></h4>
    1214       <p id="rfc.section.7.2.1.1.p.1">The "no-cache" request directive indicates that a cache <em class="bcp14">MUST NOT</em> use a stored response to satisfy the request without successful validation on the origin server.
    1215       </p>
    1216       <div id="rfc.iref.n.2"></div>
    1217       <h4 id="rfc.section.7.2.1.2"><a href="#rfc.section.7.2.1.2">7.2.1.2</a>&nbsp;<a id="cache-request-directive.no-store" href="#cache-request-directive.no-store">no-store</a></h4>
    1218       <p id="rfc.section.7.2.1.2.p.1">The "no-store" request directive indicates that a cache <em class="bcp14">MUST NOT</em> store any part of either this request or any response to it. This directive applies to both private and shared caches. "<em class="bcp14">MUST NOT</em> store" in this context means that the cache <em class="bcp14">MUST NOT</em> intentionally store the information in non-volatile storage, and <em class="bcp14">MUST</em> make a best-effort attempt to remove the information from volatile storage as promptly as possible after forwarding it.
    1219       </p>
    1220       <p id="rfc.section.7.2.1.2.p.2">This directive is NOT a reliable or sufficient mechanism for ensuring privacy. In particular, malicious or compromised caches
    1221          might not recognize or obey this directive, and communications networks might be vulnerable to eavesdropping.
    1222       </p>
    1223       <p id="rfc.section.7.2.1.2.p.3">Note that if a request containing this directive is satisfied from a cache, the no-store request directive does not apply
    1224          to the already stored response.
    1225       </p>
    12261212      <div id="rfc.iref.m.1"></div>
    1227       <h4 id="rfc.section.7.2.1.3"><a href="#rfc.section.7.2.1.3">7.2.1.3</a>&nbsp;<a id="cache-request-directive.max-age" href="#cache-request-directive.max-age">max-age</a></h4>
    1228       <p id="rfc.section.7.2.1.3.p.1">Argument syntax: </p>
     1213      <h4 id="rfc.section.7.2.1.1"><a href="#rfc.section.7.2.1.1">7.2.1.1</a>&nbsp;<a id="cache-request-directive.max-age" href="#cache-request-directive.max-age">max-age</a></h4>
     1214      <p id="rfc.section.7.2.1.1.p.1">Argument syntax: </p>
    12291215      <ul class="empty">
    12301216         <li> <a href="#delta-seconds" class="smpl">delta-seconds</a> (see <a href="#delta-seconds" title="Delta Seconds">Section&nbsp;1.3.1</a>)
    12311217         </li>
    12321218      </ul>
    1233       <p id="rfc.section.7.2.1.3.p.2">The "max-age" request directive indicates that the client is unwilling to accept a response whose age is greater than the
     1219      <p id="rfc.section.7.2.1.1.p.2">The "max-age" request directive indicates that the client is unwilling to accept a response whose age is greater than the
    12341220         specified number of seconds. Unless the max-stale request directive is also present, the client is not willing to accept a
    12351221         stale response.
    12361222      </p>
    1237       <p id="rfc.section.7.2.1.3.p.3"> <b>Note:</b> This directive uses the token form of the argument syntax; e.g., 'max-age=5', not 'max-age="5"'. Senders <em class="bcp14">SHOULD NOT</em> use the quoted-string form.
     1223      <p id="rfc.section.7.2.1.1.p.3"> <b>Note:</b> This directive uses the token form of the argument syntax; e.g., 'max-age=5', not 'max-age="5"'. Senders <em class="bcp14">SHOULD NOT</em> use the quoted-string form.
    12381224      </p>
    12391225      <div id="rfc.iref.m.2"></div>
    1240       <h4 id="rfc.section.7.2.1.4"><a href="#rfc.section.7.2.1.4">7.2.1.4</a>&nbsp;<a id="cache-request-directive.max-stale" href="#cache-request-directive.max-stale">max-stale</a></h4>
    1241       <p id="rfc.section.7.2.1.4.p.1">Argument syntax: </p>
     1226      <h4 id="rfc.section.7.2.1.2"><a href="#rfc.section.7.2.1.2">7.2.1.2</a>&nbsp;<a id="cache-request-directive.max-stale" href="#cache-request-directive.max-stale">max-stale</a></h4>
     1227      <p id="rfc.section.7.2.1.2.p.1">Argument syntax: </p>
    12421228      <ul class="empty">
    12431229         <li> <a href="#delta-seconds" class="smpl">delta-seconds</a> (see <a href="#delta-seconds" title="Delta Seconds">Section&nbsp;1.3.1</a>)
    12441230         </li>
    12451231      </ul>
    1246       <p id="rfc.section.7.2.1.4.p.2">The "max-stale" request directive indicates that the client is willing to accept a response that has exceeded its freshness
     1232      <p id="rfc.section.7.2.1.2.p.2">The "max-stale" request directive indicates that the client is willing to accept a response that has exceeded its freshness
    12471233         lifetime. If max-stale is assigned a value, then the client is willing to accept a response that has exceeded its freshness
    12481234         lifetime by no more than the specified number of seconds. If no value is assigned to max-stale, then the client is willing
    12491235         to accept a stale response of any age.
    12501236      </p>
    1251       <p id="rfc.section.7.2.1.4.p.3"> <b>Note:</b> This directive uses the token form of the argument syntax; e.g., 'max-stale=10', not 'max-stale="10"'. Senders <em class="bcp14">SHOULD NOT</em> use the quoted-string form.
     1237      <p id="rfc.section.7.2.1.2.p.3"> <b>Note:</b> This directive uses the token form of the argument syntax; e.g., 'max-stale=10', not 'max-stale="10"'. Senders <em class="bcp14">SHOULD NOT</em> use the quoted-string form.
    12521238      </p>
    12531239      <div id="rfc.iref.m.3"></div>
    1254       <h4 id="rfc.section.7.2.1.5"><a href="#rfc.section.7.2.1.5">7.2.1.5</a>&nbsp;<a id="cache-request-directive.min-fresh" href="#cache-request-directive.min-fresh">min-fresh</a></h4>
    1255       <p id="rfc.section.7.2.1.5.p.1">Argument syntax: </p>
     1240      <h4 id="rfc.section.7.2.1.3"><a href="#rfc.section.7.2.1.3">7.2.1.3</a>&nbsp;<a id="cache-request-directive.min-fresh" href="#cache-request-directive.min-fresh">min-fresh</a></h4>
     1241      <p id="rfc.section.7.2.1.3.p.1">Argument syntax: </p>
    12561242      <ul class="empty">
    12571243         <li> <a href="#delta-seconds" class="smpl">delta-seconds</a> (see <a href="#delta-seconds" title="Delta Seconds">Section&nbsp;1.3.1</a>)
    12581244         </li>
    12591245      </ul>
    1260       <p id="rfc.section.7.2.1.5.p.2">The "min-fresh" request directive indicates that the client is willing to accept a response whose freshness lifetime is no
     1246      <p id="rfc.section.7.2.1.3.p.2">The "min-fresh" request directive indicates that the client is willing to accept a response whose freshness lifetime is no
    12611247         less than its current age plus the specified time in seconds. That is, the client wants a response that will still be fresh
    12621248         for at least the specified number of seconds.
    12631249      </p>
    1264       <p id="rfc.section.7.2.1.5.p.3"> <b>Note:</b> This directive uses the token form of the argument syntax; e.g., 'min-fresh=20', not 'min-fresh="20"'. Senders <em class="bcp14">SHOULD NOT</em> use the quoted-string form.
     1250      <p id="rfc.section.7.2.1.3.p.3"> <b>Note:</b> This directive uses the token form of the argument syntax; e.g., 'min-fresh=20', not 'min-fresh="20"'. Senders <em class="bcp14">SHOULD NOT</em> use the quoted-string form.
     1251      </p>
     1252      <div id="rfc.iref.n.1"></div>
     1253      <h4 id="rfc.section.7.2.1.4"><a href="#rfc.section.7.2.1.4">7.2.1.4</a>&nbsp;<a id="cache-request-directive.no-cache" href="#cache-request-directive.no-cache">no-cache</a></h4>
     1254      <p id="rfc.section.7.2.1.4.p.1">The "no-cache" request directive indicates that a cache <em class="bcp14">MUST NOT</em> use a stored response to satisfy the request without successful validation on the origin server.
     1255      </p>
     1256      <div id="rfc.iref.n.2"></div>
     1257      <h4 id="rfc.section.7.2.1.5"><a href="#rfc.section.7.2.1.5">7.2.1.5</a>&nbsp;<a id="cache-request-directive.no-store" href="#cache-request-directive.no-store">no-store</a></h4>
     1258      <p id="rfc.section.7.2.1.5.p.1">The "no-store" request directive indicates that a cache <em class="bcp14">MUST NOT</em> store any part of either this request or any response to it. This directive applies to both private and shared caches. "<em class="bcp14">MUST NOT</em> store" in this context means that the cache <em class="bcp14">MUST NOT</em> intentionally store the information in non-volatile storage, and <em class="bcp14">MUST</em> make a best-effort attempt to remove the information from volatile storage as promptly as possible after forwarding it.
     1259      </p>
     1260      <p id="rfc.section.7.2.1.5.p.2">This directive is NOT a reliable or sufficient mechanism for ensuring privacy. In particular, malicious or compromised caches
     1261         might not recognize or obey this directive, and communications networks might be vulnerable to eavesdropping.
     1262      </p>
     1263      <p id="rfc.section.7.2.1.5.p.3">Note that if a request containing this directive is satisfied from a cache, the no-store request directive does not apply
     1264         to the already stored response.
    12651265      </p>
    12661266      <div id="rfc.iref.n.3"></div>
     
    12751275      </p>
    12761276      <h3 id="rfc.section.7.2.2"><a href="#rfc.section.7.2.2">7.2.2</a>&nbsp;<a id="cache-response-directive" href="#cache-response-directive">Response Cache-Control Directives</a></h3>
     1277      <div id="rfc.iref.m.4"></div>
     1278      <h4 id="rfc.section.7.2.2.1"><a href="#rfc.section.7.2.2.1">7.2.2.1</a>&nbsp;<a id="cache-response-directive.must-revalidate" href="#cache-response-directive.must-revalidate">must-revalidate</a></h4>
     1279      <p id="rfc.section.7.2.2.1.p.1">The "must-revalidate" response directive indicates that once it has become stale, a cache <em class="bcp14">MUST NOT</em> use the response to satisfy subsequent requests without successful validation on the origin server.
     1280      </p>
     1281      <p id="rfc.section.7.2.2.1.p.2">The must-revalidate directive is necessary to support reliable operation for certain protocol features. In all circumstances
     1282         a cache <em class="bcp14">MUST</em> obey the must-revalidate directive; in particular, if a cache cannot reach the origin server for any reason, it <em class="bcp14">MUST</em> generate a <a href="p2-semantics.html#status.504" class="smpl">504 (Gateway Timeout)</a> response.
     1283      </p>
     1284      <p id="rfc.section.7.2.2.1.p.3">The must-revalidate directive ought to be used by servers if and only if failure to validate a request on the representation
     1285         could result in incorrect operation, such as a silently unexecuted financial transaction.
     1286      </p>
     1287      <div id="rfc.iref.n.4"></div>
     1288      <h4 id="rfc.section.7.2.2.2"><a href="#rfc.section.7.2.2.2">7.2.2.2</a>&nbsp;<a id="cache-response-directive.no-cache" href="#cache-response-directive.no-cache">no-cache</a></h4>
     1289      <p id="rfc.section.7.2.2.2.p.1">Argument syntax: </p>
     1290      <ul class="empty">
     1291         <li>#<a href="#imported.abnf" class="smpl">field-name</a>
     1292         </li>
     1293      </ul>
     1294      <p id="rfc.section.7.2.2.2.p.2">The "no-cache" response directive indicates that the response <em class="bcp14">MUST NOT</em> be used to satisfy a subsequent request without successful validation on the origin server. This allows an origin server to
     1295         prevent a cache from using it to satisfy a request without contacting it, even by caches that have been configured to send
     1296         stale responses.
     1297      </p>
     1298      <p id="rfc.section.7.2.2.2.p.3">If the no-cache response directive specifies one or more field-names, then a cache <em class="bcp14">MAY</em> use the response to satisfy a subsequent request, subject to any other restrictions on caching. However, any header fields
     1299         in the response that have the field-name(s) listed <em class="bcp14">MUST NOT</em> be sent in the response to a subsequent request without successful revalidation with the origin server. This allows an origin
     1300         server to prevent the re-use of certain header fields in a response, while still allowing caching of the rest of the response.
     1301      </p>
     1302      <p id="rfc.section.7.2.2.2.p.4">The field-names given are not limited to the set of header fields defined by this specification. Field names are case-insensitive.</p>
     1303      <p id="rfc.section.7.2.2.2.p.5"> <b>Note:</b> Although it has been back-ported to many implementations, some HTTP/1.0 caches will not recognize or obey this directive.
     1304         Also, no-cache response directives with field-names are often handled by implementations as if an unqualified no-cache directive
     1305         was received; i.e., the special handling for the qualified form is not widely implemented.
     1306      </p>
     1307      <p id="rfc.section.7.2.2.2.p.6"> <b>Note:</b> This directive uses the quoted-string form of the argument syntax. Senders <em class="bcp14">SHOULD NOT</em> use the token form (even if quoting appears not to be needed for single-entry lists).
     1308      </p>
     1309      <div id="rfc.iref.n.5"></div>
     1310      <h4 id="rfc.section.7.2.2.3"><a href="#rfc.section.7.2.2.3">7.2.2.3</a>&nbsp;<a id="cache-response-directive.no-store" href="#cache-response-directive.no-store">no-store</a></h4>
     1311      <p id="rfc.section.7.2.2.3.p.1">The "no-store" response directive indicates that a cache <em class="bcp14">MUST NOT</em> store any part of either the immediate request or response. This directive applies to both private and shared caches. "<em class="bcp14">MUST NOT</em> store" in this context means that the cache <em class="bcp14">MUST NOT</em> intentionally store the information in non-volatile storage, and <em class="bcp14">MUST</em> make a best-effort attempt to remove the information from volatile storage as promptly as possible after forwarding it.
     1312      </p>
     1313      <p id="rfc.section.7.2.2.3.p.2">This directive is NOT a reliable or sufficient mechanism for ensuring privacy. In particular, malicious or compromised caches
     1314         might not recognize or obey this directive, and communications networks might be vulnerable to eavesdropping.
     1315      </p>
     1316      <div id="rfc.iref.n.6"></div>
     1317      <h4 id="rfc.section.7.2.2.4"><a href="#rfc.section.7.2.2.4">7.2.2.4</a>&nbsp;<a id="cache-response-directive.no-transform" href="#cache-response-directive.no-transform">no-transform</a></h4>
     1318      <p id="rfc.section.7.2.2.4.p.1">The "no-transform" response directive indicates that an intermediary (regardless of whether it implements a cache) <em class="bcp14">MUST NOT</em> transform the payload, as defined in <a href="p1-messaging.html#message.transformations" title="Transformations">Section 5.7.2</a> of <a href="#Part1" id="rfc.xref.Part1.10"><cite title="Hypertext Transfer Protocol (HTTP/1.1): Message Syntax and Routing">[Part1]</cite></a>.
     1319      </p>
    12771320      <div id="rfc.iref.p.2"></div>
    1278       <h4 id="rfc.section.7.2.2.1"><a href="#rfc.section.7.2.2.1">7.2.2.1</a>&nbsp;<a id="cache-response-directive.public" href="#cache-response-directive.public">public</a></h4>
    1279       <p id="rfc.section.7.2.2.1.p.1">The "public" response directive indicates that any cache <em class="bcp14">MAY</em> store the response, even if the response would normally be non-cacheable or cacheable only within a non-shared cache. (See <a href="#caching.authenticated.responses" title="Storing Responses to Authenticated Requests">Section&nbsp;3.2</a> for additional details related to the use of public in response to a request containing <a href="p7-auth.html#header.authorization" class="smpl">Authorization</a>, and <a href="#response.cacheability" title="Storing Responses in Caches">Section&nbsp;3</a> for details of how public affects responses that would normally not be stored, due to their status codes not being defined
     1321      <h4 id="rfc.section.7.2.2.5"><a href="#rfc.section.7.2.2.5">7.2.2.5</a>&nbsp;<a id="cache-response-directive.public" href="#cache-response-directive.public">public</a></h4>
     1322      <p id="rfc.section.7.2.2.5.p.1">The "public" response directive indicates that any cache <em class="bcp14">MAY</em> store the response, even if the response would normally be non-cacheable or cacheable only within a non-shared cache. (See <a href="#caching.authenticated.responses" title="Storing Responses to Authenticated Requests">Section&nbsp;3.2</a> for additional details related to the use of public in response to a request containing <a href="p7-auth.html#header.authorization" class="smpl">Authorization</a>, and <a href="#response.cacheability" title="Storing Responses in Caches">Section&nbsp;3</a> for details of how public affects responses that would normally not be stored, due to their status codes not being defined
    12801323         as cacheable.)
    12811324      </p>
    12821325      <div id="rfc.iref.p.3"></div>
    1283       <h4 id="rfc.section.7.2.2.2"><a href="#rfc.section.7.2.2.2">7.2.2.2</a>&nbsp;<a id="cache-response-directive.private" href="#cache-response-directive.private">private</a></h4>
    1284       <p id="rfc.section.7.2.2.2.p.1">Argument syntax: </p>
     1326      <h4 id="rfc.section.7.2.2.6"><a href="#rfc.section.7.2.2.6">7.2.2.6</a>&nbsp;<a id="cache-response-directive.private" href="#cache-response-directive.private">private</a></h4>
     1327      <p id="rfc.section.7.2.2.6.p.1">Argument syntax: </p>
    12851328      <ul class="empty">
    12861329         <li>#<a href="#imported.abnf" class="smpl">field-name</a>
    12871330         </li>
    12881331      </ul>
    1289       <p id="rfc.section.7.2.2.2.p.2">The "private" response directive indicates that the response message is intended for a single user and <em class="bcp14">MUST NOT</em> be stored by a shared cache. A private cache <em class="bcp14">MAY</em> store the response and reuse it for later requests, even if the response would normally be non-cacheable.
    1290       </p>
    1291       <p id="rfc.section.7.2.2.2.p.3">If the private response directive specifies one or more field-names, this requirement is limited to the field-values associated
     1332      <p id="rfc.section.7.2.2.6.p.2">The "private" response directive indicates that the response message is intended for a single user and <em class="bcp14">MUST NOT</em> be stored by a shared cache. A private cache <em class="bcp14">MAY</em> store the response and reuse it for later requests, even if the response would normally be non-cacheable.
     1333      </p>
     1334      <p id="rfc.section.7.2.2.6.p.3">If the private response directive specifies one or more field-names, this requirement is limited to the field-values associated
    12921335         with the listed response header fields. That is, a shared cache <em class="bcp14">MUST NOT</em> store the specified field-names(s), whereas it <em class="bcp14">MAY</em> store the remainder of the response message.
    12931336      </p>
    1294       <p id="rfc.section.7.2.2.2.p.4">The field-names given are not limited to the set of header fields defined by this specification. Field names are case-insensitive.</p>
    1295       <p id="rfc.section.7.2.2.2.p.5"> <b>Note:</b> This usage of the word "private" only controls where the response can be stored; it cannot ensure the privacy of the message
     1337      <p id="rfc.section.7.2.2.6.p.4">The field-names given are not limited to the set of header fields defined by this specification. Field names are case-insensitive.</p>
     1338      <p id="rfc.section.7.2.2.6.p.5"> <b>Note:</b> This usage of the word "private" only controls where the response can be stored; it cannot ensure the privacy of the message
    12961339         content. Also, private response directives with field-names are often handled by implementations as if an unqualified private
    12971340         directive was received; i.e., the special handling for the qualified form is not widely implemented.
    12981341      </p>
    1299       <p id="rfc.section.7.2.2.2.p.6"> <b>Note:</b> This directive uses the quoted-string form of the argument syntax. Senders <em class="bcp14">SHOULD NOT</em> use the token form (even if quoting appears not to be needed for single-entry lists).
    1300       </p>
    1301       <div id="rfc.iref.n.4"></div>
    1302       <h4 id="rfc.section.7.2.2.3"><a href="#rfc.section.7.2.2.3">7.2.2.3</a>&nbsp;<a id="cache-response-directive.no-cache" href="#cache-response-directive.no-cache">no-cache</a></h4>
    1303       <p id="rfc.section.7.2.2.3.p.1">Argument syntax: </p>
    1304       <ul class="empty">
    1305          <li>#<a href="#imported.abnf" class="smpl">field-name</a>
    1306          </li>
    1307       </ul>
    1308       <p id="rfc.section.7.2.2.3.p.2">The "no-cache" response directive indicates that the response <em class="bcp14">MUST NOT</em> be used to satisfy a subsequent request without successful validation on the origin server. This allows an origin server to
    1309          prevent a cache from using it to satisfy a request without contacting it, even by caches that have been configured to send
    1310          stale responses.
    1311       </p>
    1312       <p id="rfc.section.7.2.2.3.p.3">If the no-cache response directive specifies one or more field-names, then a cache <em class="bcp14">MAY</em> use the response to satisfy a subsequent request, subject to any other restrictions on caching. However, any header fields
    1313          in the response that have the field-name(s) listed <em class="bcp14">MUST NOT</em> be sent in the response to a subsequent request without successful revalidation with the origin server. This allows an origin
    1314          server to prevent the re-use of certain header fields in a response, while still allowing caching of the rest of the response.
    1315       </p>
    1316       <p id="rfc.section.7.2.2.3.p.4">The field-names given are not limited to the set of header fields defined by this specification. Field names are case-insensitive.</p>
    1317       <p id="rfc.section.7.2.2.3.p.5"> <b>Note:</b> Although it has been back-ported to many implementations, some HTTP/1.0 caches will not recognize or obey this directive.
    1318          Also, no-cache response directives with field-names are often handled by implementations as if an unqualified no-cache directive
    1319          was received; i.e., the special handling for the qualified form is not widely implemented.
    1320       </p>
    1321       <p id="rfc.section.7.2.2.3.p.6"> <b>Note:</b> This directive uses the quoted-string form of the argument syntax. Senders <em class="bcp14">SHOULD NOT</em> use the token form (even if quoting appears not to be needed for single-entry lists).
    1322       </p>
    1323       <div id="rfc.iref.n.5"></div>
    1324       <h4 id="rfc.section.7.2.2.4"><a href="#rfc.section.7.2.2.4">7.2.2.4</a>&nbsp;<a id="cache-response-directive.no-store" href="#cache-response-directive.no-store">no-store</a></h4>
    1325       <p id="rfc.section.7.2.2.4.p.1">The "no-store" response directive indicates that a cache <em class="bcp14">MUST NOT</em> store any part of either the immediate request or response. This directive applies to both private and shared caches. "<em class="bcp14">MUST NOT</em> store" in this context means that the cache <em class="bcp14">MUST NOT</em> intentionally store the information in non-volatile storage, and <em class="bcp14">MUST</em> make a best-effort attempt to remove the information from volatile storage as promptly as possible after forwarding it.
    1326       </p>
    1327       <p id="rfc.section.7.2.2.4.p.2">This directive is NOT a reliable or sufficient mechanism for ensuring privacy. In particular, malicious or compromised caches
    1328          might not recognize or obey this directive, and communications networks might be vulnerable to eavesdropping.
    1329       </p>
    1330       <div id="rfc.iref.m.4"></div>
    1331       <h4 id="rfc.section.7.2.2.5"><a href="#rfc.section.7.2.2.5">7.2.2.5</a>&nbsp;<a id="cache-response-directive.must-revalidate" href="#cache-response-directive.must-revalidate">must-revalidate</a></h4>
    1332       <p id="rfc.section.7.2.2.5.p.1">The "must-revalidate" response directive indicates that once it has become stale, a cache <em class="bcp14">MUST NOT</em> use the response to satisfy subsequent requests without successful validation on the origin server.
    1333       </p>
    1334       <p id="rfc.section.7.2.2.5.p.2">The must-revalidate directive is necessary to support reliable operation for certain protocol features. In all circumstances
    1335          a cache <em class="bcp14">MUST</em> obey the must-revalidate directive; in particular, if a cache cannot reach the origin server for any reason, it <em class="bcp14">MUST</em> generate a <a href="p2-semantics.html#status.504" class="smpl">504 (Gateway Timeout)</a> response.
    1336       </p>
    1337       <p id="rfc.section.7.2.2.5.p.3">The must-revalidate directive ought to be used by servers if and only if failure to validate a request on the representation
    1338          could result in incorrect operation, such as a silently unexecuted financial transaction.
     1342      <p id="rfc.section.7.2.2.6.p.6"> <b>Note:</b> This directive uses the quoted-string form of the argument syntax. Senders <em class="bcp14">SHOULD NOT</em> use the token form (even if quoting appears not to be needed for single-entry lists).
    13391343      </p>
    13401344      <div id="rfc.iref.p.4"></div>
    1341       <h4 id="rfc.section.7.2.2.6"><a href="#rfc.section.7.2.2.6">7.2.2.6</a>&nbsp;<a id="cache-response-directive.proxy-revalidate" href="#cache-response-directive.proxy-revalidate">proxy-revalidate</a></h4>
    1342       <p id="rfc.section.7.2.2.6.p.1">The "proxy-revalidate" response directive has the same meaning as the must-revalidate response directive, except that it does
     1345      <h4 id="rfc.section.7.2.2.7"><a href="#rfc.section.7.2.2.7">7.2.2.7</a>&nbsp;<a id="cache-response-directive.proxy-revalidate" href="#cache-response-directive.proxy-revalidate">proxy-revalidate</a></h4>
     1346      <p id="rfc.section.7.2.2.7.p.1">The "proxy-revalidate" response directive has the same meaning as the must-revalidate response directive, except that it does
    13431347         not apply to private caches.
    13441348      </p>
    13451349      <div id="rfc.iref.m.5"></div>
    1346       <h4 id="rfc.section.7.2.2.7"><a href="#rfc.section.7.2.2.7">7.2.2.7</a>&nbsp;<a id="cache-response-directive.max-age" href="#cache-response-directive.max-age">max-age</a></h4>
    1347       <p id="rfc.section.7.2.2.7.p.1">Argument syntax: </p>
     1350      <h4 id="rfc.section.7.2.2.8"><a href="#rfc.section.7.2.2.8">7.2.2.8</a>&nbsp;<a id="cache-response-directive.max-age" href="#cache-response-directive.max-age">max-age</a></h4>
     1351      <p id="rfc.section.7.2.2.8.p.1">Argument syntax: </p>
    13481352      <ul class="empty">
    13491353         <li> <a href="#delta-seconds" class="smpl">delta-seconds</a> (see <a href="#delta-seconds" title="Delta Seconds">Section&nbsp;1.3.1</a>)
    13501354         </li>
    13511355      </ul>
    1352       <p id="rfc.section.7.2.2.7.p.2">The "max-age" response directive indicates that the response is to be considered stale after its age is greater than the specified
     1356      <p id="rfc.section.7.2.2.8.p.2">The "max-age" response directive indicates that the response is to be considered stale after its age is greater than the specified
    13531357         number of seconds.
    13541358      </p>
    1355       <p id="rfc.section.7.2.2.7.p.3"> <b>Note:</b> This directive uses the token form of the argument syntax; e.g., 'max-age=5', not 'max-age="5"'. Senders <em class="bcp14">SHOULD NOT</em> use the quoted-string form.
     1359      <p id="rfc.section.7.2.2.8.p.3"> <b>Note:</b> This directive uses the token form of the argument syntax; e.g., 'max-age=5', not 'max-age="5"'. Senders <em class="bcp14">SHOULD NOT</em> use the quoted-string form.
    13561360      </p>
    13571361      <div id="rfc.iref.s.4"></div>
    1358       <h4 id="rfc.section.7.2.2.8"><a href="#rfc.section.7.2.2.8">7.2.2.8</a>&nbsp;<a id="cache-response-directive.s-maxage" href="#cache-response-directive.s-maxage">s-maxage</a></h4>
    1359       <p id="rfc.section.7.2.2.8.p.1">Argument syntax: </p>
     1362      <h4 id="rfc.section.7.2.2.9"><a href="#rfc.section.7.2.2.9">7.2.2.9</a>&nbsp;<a id="cache-response-directive.s-maxage" href="#cache-response-directive.s-maxage">s-maxage</a></h4>
     1363      <p id="rfc.section.7.2.2.9.p.1">Argument syntax: </p>
    13601364      <ul class="empty">
    13611365         <li> <a href="#delta-seconds" class="smpl">delta-seconds</a> (see <a href="#delta-seconds" title="Delta Seconds">Section&nbsp;1.3.1</a>)
    13621366         </li>
    13631367      </ul>
    1364       <p id="rfc.section.7.2.2.8.p.2">The "s-maxage" response directive indicates that, in shared caches, the maximum age specified by this directive overrides
     1368      <p id="rfc.section.7.2.2.9.p.2">The "s-maxage" response directive indicates that, in shared caches, the maximum age specified by this directive overrides
    13651369         the maximum age specified by either the max-age directive or the <a href="#header.expires" class="smpl">Expires</a> header field. The s-maxage directive also implies the semantics of the proxy-revalidate response directive.
    13661370      </p>
    1367       <p id="rfc.section.7.2.2.8.p.3"> <b>Note:</b> This directive uses the token form of the argument syntax; e.g., 's-maxage=10', not 's-maxage="10"'. Senders <em class="bcp14">SHOULD NOT</em> use the quoted-string form.
    1368       </p>
    1369       <div id="rfc.iref.n.6"></div>
    1370       <h4 id="rfc.section.7.2.2.9"><a href="#rfc.section.7.2.2.9">7.2.2.9</a>&nbsp;<a id="cache-response-directive.no-transform" href="#cache-response-directive.no-transform">no-transform</a></h4>
    1371       <p id="rfc.section.7.2.2.9.p.1">The "no-transform" response directive indicates that an intermediary (regardless of whether it implements a cache) <em class="bcp14">MUST NOT</em> transform the payload, as defined in <a href="p1-messaging.html#message.transformations" title="Transformations">Section 5.7.2</a> of <a href="#Part1" id="rfc.xref.Part1.10"><cite title="Hypertext Transfer Protocol (HTTP/1.1): Message Syntax and Routing">[Part1]</cite></a>.
     1371      <p id="rfc.section.7.2.2.9.p.3"> <b>Note:</b> This directive uses the token form of the argument syntax; e.g., 's-maxage=10', not 's-maxage="10"'. Senders <em class="bcp14">SHOULD NOT</em> use the quoted-string form.
    13721372      </p>
    13731373      <h3 id="rfc.section.7.2.3"><a href="#rfc.section.7.2.3">7.2.3</a>&nbsp;<a id="cache.control.extensions" href="#cache.control.extensions">Cache Control Extensions</a></h3>
     
    14321432</pre><p id="rfc.section.7.3.p.6">A cache recipient <em class="bcp14">MUST</em> interpret invalid date formats, especially the value "0", as representing a time in the past (i.e., "already expired").
    14331433      </p>
    1434       <p id="rfc.section.7.3.p.7">If a response includes a <a href="#header.cache-control" class="smpl">Cache-Control</a> field with the max-age directive (<a href="#cache-response-directive.max-age" title="max-age">Section&nbsp;7.2.2.7</a>), a recipient <em class="bcp14">MUST</em> ignore the Expires field. Likewise, if a response includes the s-maxage directive (<a href="#cache-response-directive.s-maxage" title="s-maxage">Section&nbsp;7.2.2.8</a>), a shared cache recipient <em class="bcp14">MUST</em> ignore the Expires field. In both these cases, the value in Expires is only intended for recipients that have not yet implemented
     1434      <p id="rfc.section.7.3.p.7">If a response includes a <a href="#header.cache-control" class="smpl">Cache-Control</a> field with the max-age directive (<a href="#cache-response-directive.max-age" title="max-age">Section&nbsp;7.2.2.8</a>), a recipient <em class="bcp14">MUST</em> ignore the Expires field. Likewise, if a response includes the s-maxage directive (<a href="#cache-response-directive.s-maxage" title="s-maxage">Section&nbsp;7.2.2.9</a>), a shared cache recipient <em class="bcp14">MUST</em> ignore the Expires field. In both these cases, the value in Expires is only intended for recipients that have not yet implemented
    14351435         the Cache-Control field.
    14361436      </p>
     
    15941594               <tr>
    15951595                  <td class="left">max-age</td>
    1596                   <td class="left"> <a href="#cache-request-directive.max-age" title="max-age">Section&nbsp;7.2.1.3</a>, <a href="#cache-response-directive.max-age" title="max-age">Section&nbsp;7.2.2.7</a>
     1596                  <td class="left"> <a href="#cache-request-directive.max-age" title="max-age">Section&nbsp;7.2.1.1</a>, <a href="#cache-response-directive.max-age" title="max-age">Section&nbsp;7.2.2.8</a>
    15971597                  </td>
    15981598               </tr>
    15991599               <tr>
    16001600                  <td class="left">max-stale</td>
    1601                   <td class="left"> <a href="#cache-request-directive.max-stale" title="max-stale">Section&nbsp;7.2.1.4</a>
     1601                  <td class="left"> <a href="#cache-request-directive.max-stale" title="max-stale">Section&nbsp;7.2.1.2</a>
    16021602                  </td>
    16031603               </tr>
    16041604               <tr>
    16051605                  <td class="left">min-fresh</td>
    1606                   <td class="left"> <a href="#cache-request-directive.min-fresh" title="min-fresh">Section&nbsp;7.2.1.5</a>
     1606                  <td class="left"> <a href="#cache-request-directive.min-fresh" title="min-fresh">Section&nbsp;7.2.1.3</a>
    16071607                  </td>
    16081608               </tr>
    16091609               <tr>
    16101610                  <td class="left">must-revalidate</td>
    1611                   <td class="left"> <a href="#cache-response-directive.must-revalidate" title="must-revalidate">Section&nbsp;7.2.2.5</a>
     1611                  <td class="left"> <a href="#cache-response-directive.must-revalidate" title="must-revalidate">Section&nbsp;7.2.2.1</a>
    16121612                  </td>
    16131613               </tr>
    16141614               <tr>
    16151615                  <td class="left">no-cache</td>
    1616                   <td class="left"> <a href="#cache-request-directive.no-cache" title="no-cache">Section&nbsp;7.2.1.1</a>, <a href="#cache-response-directive.no-cache" title="no-cache">Section&nbsp;7.2.2.3</a>
     1616                  <td class="left"> <a href="#cache-request-directive.no-cache" title="no-cache">Section&nbsp;7.2.1.4</a>, <a href="#cache-response-directive.no-cache" title="no-cache">Section&nbsp;7.2.2.2</a>
    16171617                  </td>
    16181618               </tr>
    16191619               <tr>
    16201620                  <td class="left">no-store</td>
    1621                   <td class="left"> <a href="#cache-request-directive.no-store" title="no-store">Section&nbsp;7.2.1.2</a>, <a href="#cache-response-directive.no-store" title="no-store">Section&nbsp;7.2.2.4</a>
     1621                  <td class="left"> <a href="#cache-request-directive.no-store" title="no-store">Section&nbsp;7.2.1.5</a>, <a href="#cache-response-directive.no-store" title="no-store">Section&nbsp;7.2.2.3</a>
    16221622                  </td>
    16231623               </tr>
    16241624               <tr>
    16251625                  <td class="left">no-transform</td>
    1626                   <td class="left"> <a href="#cache-request-directive.no-transform" title="no-transform">Section&nbsp;7.2.1.6</a>, <a href="#cache-response-directive.no-transform" title="no-transform">Section&nbsp;7.2.2.9</a>
     1626                  <td class="left"> <a href="#cache-request-directive.no-transform" title="no-transform">Section&nbsp;7.2.1.6</a>, <a href="#cache-response-directive.no-transform" title="no-transform">Section&nbsp;7.2.2.4</a>
    16271627                  </td>
    16281628               </tr>
     
    16341634               <tr>
    16351635                  <td class="left">private</td>
    1636                   <td class="left"> <a href="#cache-response-directive.private" title="private">Section&nbsp;7.2.2.2</a>
     1636                  <td class="left"> <a href="#cache-response-directive.private" title="private">Section&nbsp;7.2.2.6</a>
    16371637                  </td>
    16381638               </tr>
    16391639               <tr>
    16401640                  <td class="left">proxy-revalidate</td>
    1641                   <td class="left"> <a href="#cache-response-directive.proxy-revalidate" title="proxy-revalidate">Section&nbsp;7.2.2.6</a>
     1641                  <td class="left"> <a href="#cache-response-directive.proxy-revalidate" title="proxy-revalidate">Section&nbsp;7.2.2.7</a>
    16421642                  </td>
    16431643               </tr>
    16441644               <tr>
    16451645                  <td class="left">public</td>
    1646                   <td class="left"> <a href="#cache-response-directive.public" title="public">Section&nbsp;7.2.2.1</a>
     1646                  <td class="left"> <a href="#cache-response-directive.public" title="public">Section&nbsp;7.2.2.5</a>
    16471647                  </td>
    16481648               </tr>
    16491649               <tr>
    16501650                  <td class="left">s-maxage</td>
    1651                   <td class="left"> <a href="#cache-response-directive.s-maxage" title="s-maxage">Section&nbsp;7.2.2.8</a>
     1651                  <td class="left"> <a href="#cache-response-directive.s-maxage" title="s-maxage">Section&nbsp;7.2.2.9</a>
    16521652                  </td>
    16531653               </tr>
     
    19251925      </p>
    19261926      <p id="rfc.section.A.p.14">The "no-store" cache request directive doesn't apply to responses; i.e., a cache can satisfy a request with no-store on it,
    1927          and does not invalidate it. (<a href="#cache-request-directive.no-store" title="no-store">Section&nbsp;7.2.1.2</a>)
    1928       </p>
    1929       <p id="rfc.section.A.p.15">The "no-cache" response cache directive's meaning has been clarified. (<a href="#cache-response-directive.no-cache" title="no-cache">Section&nbsp;7.2.2.3</a>)
     1927         and does not invalidate it. (<a href="#cache-request-directive.no-store" title="no-store">Section&nbsp;7.2.1.5</a>)
     1928      </p>
     1929      <p id="rfc.section.A.p.15">The "no-cache" response cache directive's meaning has been clarified. (<a href="#cache-response-directive.no-cache" title="no-cache">Section&nbsp;7.2.2.2</a>)
    19301930      </p>
    19311931      <p id="rfc.section.A.p.16">New status codes can now define that caches are allowed to use heuristic freshness with them. (<a href="#heuristic.freshness" title="Calculating Heuristic Freshness">Section&nbsp;4.1.2</a>)
     
    21262126            </li>
    21272127            <li><a id="rfc.index.M" href="#rfc.index.M"><b>M</b></a><ul>
    2128                   <li>max-age (cache directive)&nbsp;&nbsp;<a href="#rfc.iref.m.1"><b>7.2.1.3</b></a>, <a href="#rfc.iref.m.5"><b>7.2.2.7</b></a></li>
    2129                   <li>max-stale (cache directive)&nbsp;&nbsp;<a href="#rfc.iref.m.2"><b>7.2.1.4</b></a></li>
    2130                   <li>min-fresh (cache directive)&nbsp;&nbsp;<a href="#rfc.iref.m.3"><b>7.2.1.5</b></a></li>
    2131                   <li>must-revalidate (cache directive)&nbsp;&nbsp;<a href="#rfc.iref.m.4"><b>7.2.2.5</b></a></li>
     2128                  <li>max-age (cache directive)&nbsp;&nbsp;<a href="#rfc.iref.m.1"><b>7.2.1.1</b></a>, <a href="#rfc.iref.m.5"><b>7.2.2.8</b></a></li>
     2129                  <li>max-stale (cache directive)&nbsp;&nbsp;<a href="#rfc.iref.m.2"><b>7.2.1.2</b></a></li>
     2130                  <li>min-fresh (cache directive)&nbsp;&nbsp;<a href="#rfc.iref.m.3"><b>7.2.1.3</b></a></li>
     2131                  <li>must-revalidate (cache directive)&nbsp;&nbsp;<a href="#rfc.iref.m.4"><b>7.2.2.1</b></a></li>
    21322132               </ul>
    21332133            </li>
    21342134            <li><a id="rfc.index.N" href="#rfc.index.N"><b>N</b></a><ul>
    2135                   <li>no-cache (cache directive)&nbsp;&nbsp;<a href="#rfc.iref.n.1"><b>7.2.1.1</b></a>, <a href="#rfc.iref.n.4"><b>7.2.2.3</b></a></li>
    2136                   <li>no-store (cache directive)&nbsp;&nbsp;<a href="#rfc.iref.n.2"><b>7.2.1.2</b></a>, <a href="#rfc.iref.n.5"><b>7.2.2.4</b></a></li>
    2137                   <li>no-transform (cache directive)&nbsp;&nbsp;<a href="#rfc.iref.n.3"><b>7.2.1.6</b></a>, <a href="#rfc.iref.n.6"><b>7.2.2.9</b></a></li>
     2135                  <li>no-cache (cache directive)&nbsp;&nbsp;<a href="#rfc.iref.n.1"><b>7.2.1.4</b></a>, <a href="#rfc.iref.n.4"><b>7.2.2.2</b></a></li>
     2136                  <li>no-store (cache directive)&nbsp;&nbsp;<a href="#rfc.iref.n.2"><b>7.2.1.5</b></a>, <a href="#rfc.iref.n.5"><b>7.2.2.3</b></a></li>
     2137                  <li>no-transform (cache directive)&nbsp;&nbsp;<a href="#rfc.iref.n.3"><b>7.2.1.6</b></a>, <a href="#rfc.iref.n.6"><b>7.2.2.4</b></a></li>
    21382138               </ul>
    21392139            </li>
     
    21432143            </li>
    21442144            <li><a id="rfc.index.P" href="#rfc.index.P"><b>P</b></a><ul>
    2145                   <li><em>Part1</em>&nbsp;&nbsp;<a href="#rfc.xref.Part1.1">1.2</a>, <a href="#rfc.xref.Part1.2">1.3</a>, <a href="#rfc.xref.Part1.3">3.1</a>, <a href="#rfc.xref.Part1.4">4</a>, <a href="#rfc.xref.Part1.5">4.3</a>, <a href="#rfc.xref.Part1.6">6</a>, <a href="#rfc.xref.Part1.7">6</a>, <a href="#rfc.xref.Part1.8">6</a>, <a href="#rfc.xref.Part1.9">7.2.1.6</a>, <a href="#rfc.xref.Part1.10">7.2.2.9</a>, <a href="#rfc.xref.Part1.11">10</a>, <a href="#rfc.xref.Part1.12">11</a>, <a href="#Part1"><b>12.1</b></a>, <a href="#rfc.xref.Part1.13">B</a>, <a href="#rfc.xref.Part1.14">B</a>, <a href="#rfc.xref.Part1.15">B</a>, <a href="#rfc.xref.Part1.16">B</a>, <a href="#rfc.xref.Part1.17">B</a>, <a href="#rfc.xref.Part1.18">B</a>, <a href="#rfc.xref.Part1.19">B</a>, <a href="#rfc.xref.Part1.20">B</a>, <a href="#rfc.xref.Part1.21">C</a><ul>
     2145                  <li><em>Part1</em>&nbsp;&nbsp;<a href="#rfc.xref.Part1.1">1.2</a>, <a href="#rfc.xref.Part1.2">1.3</a>, <a href="#rfc.xref.Part1.3">3.1</a>, <a href="#rfc.xref.Part1.4">4</a>, <a href="#rfc.xref.Part1.5">4.3</a>, <a href="#rfc.xref.Part1.6">6</a>, <a href="#rfc.xref.Part1.7">6</a>, <a href="#rfc.xref.Part1.8">6</a>, <a href="#rfc.xref.Part1.9">7.2.1.6</a>, <a href="#rfc.xref.Part1.10">7.2.2.4</a>, <a href="#rfc.xref.Part1.11">10</a>, <a href="#rfc.xref.Part1.12">11</a>, <a href="#Part1"><b>12.1</b></a>, <a href="#rfc.xref.Part1.13">B</a>, <a href="#rfc.xref.Part1.14">B</a>, <a href="#rfc.xref.Part1.15">B</a>, <a href="#rfc.xref.Part1.16">B</a>, <a href="#rfc.xref.Part1.17">B</a>, <a href="#rfc.xref.Part1.18">B</a>, <a href="#rfc.xref.Part1.19">B</a>, <a href="#rfc.xref.Part1.20">B</a>, <a href="#rfc.xref.Part1.21">C</a><ul>
    21462146                        <li><em>Section 1.2</em>&nbsp;&nbsp;<a href="#rfc.xref.Part1.2">1.3</a>, <a href="#rfc.xref.Part1.21">C</a></li>
    21472147                        <li><em>Section 2.5</em>&nbsp;&nbsp;<a href="#rfc.xref.Part1.1">1.2</a></li>
     
    21522152                        <li><em>Section 5.5</em>&nbsp;&nbsp;<a href="#rfc.xref.Part1.4">4</a>, <a href="#rfc.xref.Part1.6">6</a>, <a href="#rfc.xref.Part1.7">6</a>, <a href="#rfc.xref.Part1.8">6</a></li>
    21532153                        <li><em>Section 5.7.1</em>&nbsp;&nbsp;<a href="#rfc.xref.Part1.19">B</a></li>
    2154                         <li><em>Section 5.7.2</em>&nbsp;&nbsp;<a href="#rfc.xref.Part1.9">7.2.1.6</a>, <a href="#rfc.xref.Part1.10">7.2.2.9</a></li>
     2154                        <li><em>Section 5.7.2</em>&nbsp;&nbsp;<a href="#rfc.xref.Part1.9">7.2.1.6</a>, <a href="#rfc.xref.Part1.10">7.2.2.4</a></li>
    21552155                        <li><em>Section 9</em>&nbsp;&nbsp;<a href="#rfc.xref.Part1.12">11</a></li>
    21562156                     </ul>
     
    21782178                  </li>
    21792179                  <li>Pragma header field&nbsp;&nbsp;<a href="#rfc.xref.header.pragma.1">4</a>, <a href="#rfc.iref.p.5"><b>7.4</b></a>, <a href="#rfc.xref.header.pragma.2">9.3</a>, <a href="#rfc.xref.header.pragma.3">A</a></li>
    2180                   <li>private (cache directive)&nbsp;&nbsp;<a href="#rfc.iref.p.3"><b>7.2.2.2</b></a></li>
     2180                  <li>private (cache directive)&nbsp;&nbsp;<a href="#rfc.iref.p.3"><b>7.2.2.6</b></a></li>
    21812181                  <li>private cache&nbsp;&nbsp;<a href="#rfc.iref.p.1">1.1</a></li>
    2182                   <li>proxy-revalidate (cache directive)&nbsp;&nbsp;<a href="#rfc.iref.p.4"><b>7.2.2.6</b></a></li>
    2183                   <li>public (cache directive)&nbsp;&nbsp;<a href="#rfc.iref.p.2"><b>7.2.2.1</b></a></li>
     2182                  <li>proxy-revalidate (cache directive)&nbsp;&nbsp;<a href="#rfc.iref.p.4"><b>7.2.2.7</b></a></li>
     2183                  <li>public (cache directive)&nbsp;&nbsp;<a href="#rfc.iref.p.2"><b>7.2.2.5</b></a></li>
    21842184               </ul>
    21852185            </li>
     
    22082208            </li>
    22092209            <li><a id="rfc.index.S" href="#rfc.index.S"><b>S</b></a><ul>
    2210                   <li>s-maxage (cache directive)&nbsp;&nbsp;<a href="#rfc.iref.s.4"><b>7.2.2.8</b></a></li>
     2210                  <li>s-maxage (cache directive)&nbsp;&nbsp;<a href="#rfc.iref.s.4"><b>7.2.2.9</b></a></li>
    22112211                  <li>shared cache&nbsp;&nbsp;<a href="#rfc.iref.s.1">1.1</a></li>
    22122212                  <li>stale&nbsp;&nbsp;<a href="#rfc.iref.s.2">1.1</a></li>
  • draft-ietf-httpbis/latest/p6-cache.xml

    r2235 r2236  
    11651165<section title="Request Cache-Control Directives" anchor="cache-request-directive">
    11661166
     1167<section title="max-age" anchor="cache-request-directive.max-age">
     1168   <iref item="max-age (cache directive)" primary="true" />
     1169<t>
     1170   Argument syntax:
     1171   <list>
     1172      <t>
     1173        <x:ref>delta-seconds</x:ref> (see <xref target="delta-seconds"/>)
     1174      </t>
     1175   </list>
     1176</t>
     1177<t>
     1178   The "max-age" request directive indicates that the client is unwilling to
     1179   accept a response whose age is greater than the specified number of
     1180   seconds. Unless the max-stale request directive is also present, the
     1181   client is not willing to accept a stale response.
     1182</t>
     1183<t>
     1184   &Note; This directive uses the token form of the argument syntax;
     1185   e.g., 'max-age=5', not 'max-age="5"'. Senders &SHOULD-NOT; use the
     1186   quoted-string form.
     1187</t>
     1188</section>
     1189
     1190<section title="max-stale" anchor="cache-request-directive.max-stale">
     1191   <iref item="max-stale (cache directive)" primary="true" />
     1192<t>
     1193   Argument syntax:
     1194   <list>
     1195      <t>
     1196        <x:ref>delta-seconds</x:ref> (see <xref target="delta-seconds"/>)
     1197      </t>
     1198   </list>
     1199</t>
     1200<t>
     1201   The "max-stale" request directive indicates that the client is willing
     1202   to accept a response that has exceeded its freshness lifetime. If max-stale
     1203   is assigned a value, then the client is willing to accept a response
     1204   that has exceeded its freshness lifetime by no more than the specified
     1205   number of seconds. If no value is assigned to max-stale, then the client
     1206   is willing to accept a stale response of any age.
     1207</t>
     1208<t>
     1209   &Note; This directive uses the token form of the argument syntax;
     1210   e.g., 'max-stale=10', not 'max-stale="10"'. Senders &SHOULD-NOT; use the
     1211   quoted-string form.
     1212</t>
     1213</section>
     1214
     1215<section title="min-fresh" anchor="cache-request-directive.min-fresh">
     1216   <iref item="min-fresh (cache directive)" primary="true" />
     1217<t>
     1218   Argument syntax:
     1219   <list>
     1220      <t>
     1221        <x:ref>delta-seconds</x:ref> (see <xref target="delta-seconds"/>)
     1222      </t>
     1223   </list>
     1224</t>
     1225<t>
     1226   The "min-fresh" request directive indicates that the client is willing
     1227   to accept a response whose freshness lifetime is no less than its
     1228   current age plus the specified time in seconds. That is, the client
     1229   wants a response that will still be fresh for at least the specified
     1230   number of seconds.
     1231</t>
     1232<t>
     1233   &Note; This directive uses the token form of the argument syntax;
     1234   e.g., 'min-fresh=20', not 'min-fresh="20"'. Senders &SHOULD-NOT; use the
     1235   quoted-string form.
     1236</t>
     1237</section>
     1238
    11671239<section title="no-cache" anchor="cache-request-directive.no-cache">
    11681240   <iref item="no-cache (cache directive)" primary="true" />
     
    11981270</section>
    11991271
    1200 <section title="max-age" anchor="cache-request-directive.max-age">
    1201    <iref item="max-age (cache directive)" primary="true" />
    1202 <t>
    1203    Argument syntax:
    1204    <list>
    1205       <t>
    1206         <x:ref>delta-seconds</x:ref> (see <xref target="delta-seconds"/>)
    1207       </t>
    1208    </list>
    1209 </t>
    1210 <t>
    1211    The "max-age" request directive indicates that the client is unwilling to
    1212    accept a response whose age is greater than the specified number of
    1213    seconds. Unless the max-stale request directive is also present, the
    1214    client is not willing to accept a stale response.
    1215 </t>
    1216 <t>
    1217    &Note; This directive uses the token form of the argument syntax;
    1218    e.g., 'max-age=5', not 'max-age="5"'. Senders &SHOULD-NOT; use the
    1219    quoted-string form.
    1220 </t>
    1221 </section>
    1222 
    1223 <section title="max-stale" anchor="cache-request-directive.max-stale">
    1224    <iref item="max-stale (cache directive)" primary="true" />
    1225 <t>
    1226    Argument syntax:
    1227    <list>
    1228       <t>
    1229         <x:ref>delta-seconds</x:ref> (see <xref target="delta-seconds"/>)
    1230       </t>
    1231    </list>
    1232 </t>
    1233 <t>
    1234    The "max-stale" request directive indicates that the client is willing
    1235    to accept a response that has exceeded its freshness lifetime. If max-stale
    1236    is assigned a value, then the client is willing to accept a response
    1237    that has exceeded its freshness lifetime by no more than the specified
    1238    number of seconds. If no value is assigned to max-stale, then the client
    1239    is willing to accept a stale response of any age.
    1240 </t>
    1241 <t>
    1242    &Note; This directive uses the token form of the argument syntax;
    1243    e.g., 'max-stale=10', not 'max-stale="10"'. Senders &SHOULD-NOT; use the
    1244    quoted-string form.
    1245 </t>
    1246 </section>
    1247 
    1248 <section title="min-fresh" anchor="cache-request-directive.min-fresh">
    1249    <iref item="min-fresh (cache directive)" primary="true" />
    1250 <t>
    1251    Argument syntax:
    1252    <list>
    1253       <t>
    1254         <x:ref>delta-seconds</x:ref> (see <xref target="delta-seconds"/>)
    1255       </t>
    1256    </list>
    1257 </t>
    1258 <t>
    1259    The "min-fresh" request directive indicates that the client is willing
    1260    to accept a response whose freshness lifetime is no less than its
    1261    current age plus the specified time in seconds. That is, the client
    1262    wants a response that will still be fresh for at least the specified
    1263    number of seconds.
    1264 </t>
    1265 <t>
    1266    &Note; This directive uses the token form of the argument syntax;
    1267    e.g., 'min-fresh=20', not 'min-fresh="20"'. Senders &SHOULD-NOT; use the
    1268    quoted-string form.
    1269 </t>
    1270 </section>
    1271 
    12721272<section title="no-transform" anchor="cache-request-directive.no-transform">
    12731273   <iref item="no-transform (cache directive)" primary="true" />
     
    12971297   <x:anchor-alias value="cache-response-directive" />
    12981298
    1299 <section title="public" anchor="cache-response-directive.public">
    1300    <iref item="public (cache directive)" primary="true" />
    1301 <t>
    1302    The "public" response directive indicates that any cache &MAY; store the
    1303    response, even if the response would normally be non-cacheable or cacheable
    1304    only within a non-shared cache. (See <xref
    1305    target="caching.authenticated.responses"/> for additional details related
    1306    to the use of public in response to a request containing
    1307    <x:ref>Authorization</x:ref>, and <xref target="response.cacheability"/>
    1308    for details of how public affects responses that would normally not be
    1309    stored, due to their status codes not being defined as cacheable.)
    1310 </t>
    1311 </section>
    1312 
    1313 <section title="private" anchor="cache-response-directive.private">
    1314    <iref item="private (cache directive)" primary="true" />
    1315 <t>
    1316    Argument syntax:
    1317    <list>
    1318       <t>
    1319         #<x:ref>field-name</x:ref>
    1320       </t>
    1321    </list>
    1322 </t>
    1323 <t>
    1324    The "private" response directive indicates that the response message is
    1325    intended for a single user and &MUST-NOT; be stored by a shared cache. A
    1326    private cache &MAY; store the response and reuse it for later requests,
    1327    even if the response would normally be non-cacheable.
    1328 </t>
    1329 <t>
    1330    If the private response directive specifies one or more field-names,
    1331    this requirement is limited to the field-values associated with the
    1332    listed response header fields. That is, a shared cache &MUST-NOT; store
    1333    the specified field-names(s), whereas it &MAY; store the remainder of the
    1334    response message.
    1335 </t>
    1336 <t>
    1337    The field-names given are not limited to the set of header
    1338    fields defined by this specification. Field names are case-insensitive.
    1339 </t>
    1340 <t>
    1341    &Note; This usage of the word "private" only controls
    1342    where the response can be stored; it cannot ensure the privacy of the
    1343    message content. Also, private response directives with field-names are
    1344    often handled by implementations as if an unqualified private directive
    1345    was received; i.e., the special handling for the qualified form is not
    1346    widely implemented.
    1347 </t>
    1348 <t>
    1349    &Note; This directive uses the quoted-string form of the argument syntax.
    1350    Senders &SHOULD-NOT; use the token form (even if quoting appears not to be
    1351    needed for single-entry lists).
     1299<section title="must-revalidate" anchor="cache-response-directive.must-revalidate">
     1300   <iref item="must-revalidate (cache directive)" primary="true" />
     1301<t>
     1302   The "must-revalidate" response directive indicates that once it has
     1303   become stale, a cache &MUST-NOT; use the response to satisfy subsequent
     1304   requests without successful validation on the origin server.
     1305</t>
     1306<t>
     1307   The must-revalidate directive is necessary to support reliable
     1308   operation for certain protocol features. In all circumstances a
     1309   cache &MUST; obey the must-revalidate directive; in particular,
     1310   if a cache cannot reach the origin server for any reason, it &MUST;
     1311   generate a <x:ref>504 (Gateway Timeout)</x:ref> response.
     1312</t>
     1313<t>
     1314   The must-revalidate directive ought to be used by servers if and only
     1315   if failure to validate a request on the representation could result in
     1316   incorrect operation, such as a silently unexecuted financial
     1317   transaction.
    13521318</t>
    13531319</section>
     
    14171383</section>
    14181384
    1419 <section title="must-revalidate" anchor="cache-response-directive.must-revalidate">
    1420    <iref item="must-revalidate (cache directive)" primary="true" />
    1421 <t>
    1422    The "must-revalidate" response directive indicates that once it has
    1423    become stale, a cache &MUST-NOT; use the response to satisfy subsequent
    1424    requests without successful validation on the origin server.
    1425 </t>
    1426 <t>
    1427    The must-revalidate directive is necessary to support reliable
    1428    operation for certain protocol features. In all circumstances a
    1429    cache &MUST; obey the must-revalidate directive; in particular,
    1430    if a cache cannot reach the origin server for any reason, it &MUST;
    1431    generate a <x:ref>504 (Gateway Timeout)</x:ref> response.
    1432 </t>
    1433 <t>
    1434    The must-revalidate directive ought to be used by servers if and only
    1435    if failure to validate a request on the representation could result in
    1436    incorrect operation, such as a silently unexecuted financial
    1437    transaction.
     1385<section title="no-transform" anchor="cache-response-directive.no-transform">
     1386   <iref item="no-transform (cache directive)" primary="true" />
     1387<t>
     1388   The "no-transform" response directive indicates that an intermediary
     1389   (regardless of whether it implements a cache) &MUST-NOT; transform the
     1390   payload, as defined in &transformations;.
     1391</t>
     1392</section>
     1393
     1394<section title="public" anchor="cache-response-directive.public">
     1395   <iref item="public (cache directive)" primary="true" />
     1396<t>
     1397   The "public" response directive indicates that any cache &MAY; store the
     1398   response, even if the response would normally be non-cacheable or cacheable
     1399   only within a non-shared cache. (See <xref
     1400   target="caching.authenticated.responses"/> for additional details related
     1401   to the use of public in response to a request containing
     1402   <x:ref>Authorization</x:ref>, and <xref target="response.cacheability"/>
     1403   for details of how public affects responses that would normally not be
     1404   stored, due to their status codes not being defined as cacheable.)
     1405</t>
     1406</section>
     1407
     1408<section title="private" anchor="cache-response-directive.private">
     1409   <iref item="private (cache directive)" primary="true" />
     1410<t>
     1411   Argument syntax:
     1412   <list>
     1413      <t>
     1414        #<x:ref>field-name</x:ref>
     1415      </t>
     1416   </list>
     1417</t>
     1418<t>
     1419   The "private" response directive indicates that the response message is
     1420   intended for a single user and &MUST-NOT; be stored by a shared cache. A
     1421   private cache &MAY; store the response and reuse it for later requests,
     1422   even if the response would normally be non-cacheable.
     1423</t>
     1424<t>
     1425   If the private response directive specifies one or more field-names,
     1426   this requirement is limited to the field-values associated with the
     1427   listed response header fields. That is, a shared cache &MUST-NOT; store
     1428   the specified field-names(s), whereas it &MAY; store the remainder of the
     1429   response message.
     1430</t>
     1431<t>
     1432   The field-names given are not limited to the set of header
     1433   fields defined by this specification. Field names are case-insensitive.
     1434</t>
     1435<t>
     1436   &Note; This usage of the word "private" only controls
     1437   where the response can be stored; it cannot ensure the privacy of the
     1438   message content. Also, private response directives with field-names are
     1439   often handled by implementations as if an unqualified private directive
     1440   was received; i.e., the special handling for the qualified form is not
     1441   widely implemented.
     1442</t>
     1443<t>
     1444   &Note; This directive uses the quoted-string form of the argument syntax.
     1445   Senders &SHOULD-NOT; use the token form (even if quoting appears not to be
     1446   needed for single-entry lists).
    14381447</t>
    14391448</section>
     
    14911500   e.g., 's-maxage=10', not 's-maxage="10"'. Senders &SHOULD-NOT; use the
    14921501   quoted-string form.
    1493 </t>
    1494 </section>
    1495 
    1496 <section title="no-transform" anchor="cache-response-directive.no-transform">
    1497    <iref item="no-transform (cache directive)" primary="true" />
    1498 <t>
    1499    The "no-transform" response directive indicates that an intermediary
    1500    (regardless of whether it implements a cache) &MUST-NOT; transform the
    1501    payload, as defined in &transformations;.
    15021502</t>
    15031503</section>
Note: See TracChangeset for help on using the changeset viewer.