Ignore:
Timestamp:
Jul 14, 2012, 11:33:38 AM (7 years ago)
Author:
julian.reschke@…
Message:

dquote cache directive names in introductory sentences

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

Legend:

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

    r1776 r1779  
    12591259      <div id="rfc.iref.n.1"></div>
    12601260      <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>
    1261       <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.
     1261      <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.
    12621262      </p>
    12631263      <div id="rfc.iref.c.8"></div>
    12641264      <div id="rfc.iref.n.2"></div>
    12651265      <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>
    1266       <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.
     1266      <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.
    12671267      </p>
    12681268      <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
     
    12801280         </li>
    12811281      </ul>
    1282       <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 specified
    1283          number of seconds. Unless the max-stale request directive is also present, the client is not willing to accept a stale response.
     1282      <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
     1283         specified number of seconds. Unless the max-stale request directive is also present, the client is not willing to accept a
     1284         stale response.
    12841285      </p>
    12851286      <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.
     
    12931294         </li>
    12941295      </ul>
    1295       <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 expiration
     1296      <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 expiration
    12961297         time. If max-stale is assigned a value, then the client is willing to accept a response that has exceeded its expiration time
    12971298         by no more than the specified number of seconds. If no value is assigned to max-stale, then the client is willing to accept
     
    13081309         </li>
    13091310      </ul>
    1310       <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 less
    1311          than its current age plus the specified time in seconds. That is, the client wants a response that will still be fresh for
    1312          at least the specified number of seconds.
     1311      <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
     1312         less than its current age plus the specified time in seconds. That is, the client wants a response that will still be fresh
     1313         for at least the specified number of seconds.
    13131314      </p>
    13141315      <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.
     
    13171318      <div id="rfc.iref.n.3"></div>
    13181319      <h4 id="rfc.section.7.2.1.6"><a href="#rfc.section.7.2.1.6">7.2.1.6</a>&nbsp;<a id="cache-request-directive.no-transform" href="#cache-request-directive.no-transform">no-transform</a></h4>
    1319       <p id="rfc.section.7.2.1.6.p.1">The no-transform request directive indicates that an intermediary (whether or not it implements a cache) <em class="bcp14">MUST NOT</em> change the <a href="p2-semantics.html#header.content-encoding" class="smpl">Content-Encoding</a>, <a href="p5-range.html#header.content-range" class="smpl">Content-Range</a> or <a href="p2-semantics.html#header.content-type" class="smpl">Content-Type</a> request header fields, nor the request representation.
     1320      <p id="rfc.section.7.2.1.6.p.1">The "no-transform" request directive indicates that an intermediary (whether or not it implements a cache) <em class="bcp14">MUST NOT</em> change the <a href="p2-semantics.html#header.content-encoding" class="smpl">Content-Encoding</a>, <a href="p5-range.html#header.content-range" class="smpl">Content-Range</a> or <a href="p2-semantics.html#header.content-type" class="smpl">Content-Type</a> request header fields, nor the request representation.
    13201321      </p>
    13211322      <div id="rfc.iref.c.13"></div>
    13221323      <div id="rfc.iref.o.1"></div>
    13231324      <h4 id="rfc.section.7.2.1.7"><a href="#rfc.section.7.2.1.7">7.2.1.7</a>&nbsp;<a id="cache-request-directive.only-if-cached" href="#cache-request-directive.only-if-cached">only-if-cached</a></h4>
    1324       <p id="rfc.section.7.2.1.7.p.1">The only-if-cached request directive indicates that the client only wishes to obtain a stored response. If it receives this
     1325      <p id="rfc.section.7.2.1.7.p.1">The "only-if-cached" request directive indicates that the client only wishes to obtain a stored response. If it receives this
    13251326         directive, a cache <em class="bcp14">SHOULD</em> either respond using a stored response that is consistent with the other constraints of the request, or respond with a <a href="p2-semantics.html#status.504" class="smpl">504 (Gateway
    13261327            Timeout)</a> status code. If a group of caches is being operated as a unified system with good internal connectivity, a member cache <em class="bcp14">MAY</em> forward such a request within that group of caches.
     
    13301331      <div id="rfc.iref.p.2"></div>
    13311332      <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.only-if-cached" href="#cache-response-directive.only-if-cached">public</a></h4>
    1332       <p id="rfc.section.7.2.2.1.p.1">The public response directive indicates that a response whose associated request contains an 'Authentication' header <em class="bcp14">MAY</em> be stored (see <a href="#caching.authenticated.responses" title="Storing Responses to Authenticated Requests">Section&nbsp;3.2</a>).
     1333      <p id="rfc.section.7.2.2.1.p.1">The "public" response directive indicates that a response whose associated request contains an 'Authentication' header <em class="bcp14">MAY</em> be stored (see <a href="#caching.authenticated.responses" title="Storing Responses to Authenticated Requests">Section&nbsp;3.2</a>).
    13331334      </p>
    13341335      <div id="rfc.iref.c.15"></div>
     
    13401341         </li>
    13411342      </ul>
    1342       <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.
     1343      <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.
    13431344      </p>
    13441345      <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
     
    13621363         </li>
    13631364      </ul>
    1364       <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
     1365      <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
    13651366         prevent a cache from using it to satisfy a request without contacting it, even by caches that have been configured to return
    13661367         stale responses.
     
    13821383      <div id="rfc.iref.n.5"></div>
    13831384      <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>
    1384       <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.
     1385      <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.
    13851386      </p>
    13861387      <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
     
    13901391      <div id="rfc.iref.m.4"></div>
    13911392      <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>
    1392       <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.
     1393      <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.
    13931394      </p>
    13941395      <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
     
    14011402      <div id="rfc.iref.p.4"></div>
    14021403      <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>
    1403       <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
     1404      <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
    14041405         not apply to private caches.
    14051406      </p>
     
    14121413         </li>
    14131414      </ul>
    1414       <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
     1415      <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
    14151416         number of seconds.
    14161417      </p>
     
    14251426         </li>
    14261427      </ul>
    1427       <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 the
    1428          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.
     1428      <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
     1429         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.
    14291430      </p>
    14301431      <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.
     
    14331434      <div id="rfc.iref.n.6"></div>
    14341435      <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>
    1435       <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> change the <a href="p2-semantics.html#header.content-encoding" class="smpl">Content-Encoding</a>, <a href="p5-range.html#header.content-range" class="smpl">Content-Range</a> or <a href="p2-semantics.html#header.content-type" class="smpl">Content-Type</a> response header fields, nor the response representation.
     1436      <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> change the <a href="p2-semantics.html#header.content-encoding" class="smpl">Content-Encoding</a>, <a href="p5-range.html#header.content-range" class="smpl">Content-Range</a> or <a href="p2-semantics.html#header.content-type" class="smpl">Content-Type</a> response header fields, nor the response representation.
    14361437      </p>
    14371438      <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>
  • draft-ietf-httpbis/latest/p6-cache.xml

    r1776 r1779  
    552552   responses to be stored is present in the response.
    553553</t>
    554 
    555554<t>
    556555   In this specification, the following <x:ref>Cache-Control</x:ref> response
     
    558557   must-revalidate, public, s-maxage.
    559558</t>
    560 
    561559<t>
    562560   Note that cached responses that contain the "must-revalidate" and/or
     
    12721270</t>
    12731271
    1274 <section anchor="cache-request-directive"
    1275    title="Request Cache-Control Directives">
     1272<section title="Request Cache-Control Directives" anchor="cache-request-directive">
    12761273
    12771274<section title="no-cache" anchor="cache-request-directive.no-cache">
     
    12791276   <iref item="no-cache" primary="true" subitem="Cache Directive" />
    12801277<t>
    1281    The no-cache request directive indicates that a cache &MUST-NOT;
     1278   The "no-cache" request directive indicates that a cache &MUST-NOT;
    12821279   use a stored response to satisfy the request without successful
    12831280   validation on the origin server.
     
    12891286   <iref item="no-store" primary="true" subitem="Cache Directive" />
    12901287<t>
    1291    The no-store request directive indicates that a cache &MUST-NOT;
     1288   The "no-store" request directive indicates that a cache &MUST-NOT;
    12921289   store any part of either this request or any response to it. This
    12931290   directive applies to both private and shared caches. "&MUST-NOT;
     
    13221319</t>
    13231320<t>
    1324    The max-age request directive indicates that the client is unwilling to
     1321   The "max-age" request directive indicates that the client is unwilling to
    13251322   accept a response whose age is greater than the specified number of
    13261323   seconds. Unless the max-stale request directive is also present, the
     
    13461343</t>
    13471344<t>
    1348    The max-stale request directive indicates that the client is willing
     1345   The "max-stale" request directive indicates that the client is willing
    13491346   to accept a response that has exceeded its expiration time. If max-stale
    13501347   is assigned a value, then the client is willing to accept a response
     
    13721369</t>
    13731370<t>
    1374    The min-fresh request directive indicates that the client is willing
     1371   The "min-fresh" request directive indicates that the client is willing
    13751372   to accept a response whose freshness lifetime is no less than its
    13761373   current age plus the specified time in seconds. That is, the client
     
    13891386   <iref item="no-transform" primary="true" subitem="Cache Directive" />
    13901387<t>
    1391    The no-transform request directive indicates that an intermediary
     1388   The "no-transform" request directive indicates that an intermediary
    13921389   (whether or not it implements a cache) &MUST-NOT; change the
    13931390   <x:ref>Content-Encoding</x:ref>, <x:ref>Content-Range</x:ref> or
     
    14011398   <iref item="only-if-cached" primary="true" subitem="Cache Directive" />
    14021399<t>
    1403    The only-if-cached request directive indicates that the client only wishes
     1400   The "only-if-cached" request directive indicates that the client only wishes
    14041401   to obtain a stored response. If it receives this directive, a cache &SHOULD;
    14051402   either respond using a stored response that is consistent with the other
     
    14201417   <iref item="public" primary="true" subitem="Cache Directive" />
    14211418<t>
    1422    The public response directive indicates that a response whose
     1419   The "public" response directive indicates that a response whose
    14231420   associated request contains an 'Authentication' header &MAY; be
    14241421   stored (see <xref target="caching.authenticated.responses" />).
     
    14381435</t>
    14391436<t>
    1440    The private response directive indicates that the response message is
     1437   The "private" response directive indicates that the response message is
    14411438   intended for a single user and &MUST-NOT; be stored by a shared cache. A
    14421439   private cache &MAY; store the response.
     
    14801477</t>
    14811478<t>
    1482    The no-cache response directive indicates that the response &MUST-NOT;
     1479   The "no-cache" response directive indicates that the response &MUST-NOT;
    14831480   be used to satisfy a subsequent request without successful validation on
    14841481   the origin server. This allows an origin server to prevent a cache from
     
    15181515   <iref item="no-store" primary="true" subitem="Cache Directive" />
    15191516<t>
    1520    The no-store response directive indicates that a cache &MUST-NOT;
     1517   The "no-store" response directive indicates that a cache &MUST-NOT;
    15211518   store any part of either the immediate request or response. This
    15221519   directive applies to both private and shared caches. "&MUST-NOT;
     
    15381535   <iref item="must-revalidate" primary="true" subitem="Cache Directive" />
    15391536<t>
    1540    The must-revalidate response directive indicates that once it has
     1537   The "must-revalidate" response directive indicates that once it has
    15411538   become stale, a cache &MUST-NOT; use the response to satisfy subsequent
    15421539   requests without successful validation on the origin server.
     
    15611558   <iref item="proxy-revalidate" primary="true" subitem="Cache Directive" />
    15621559<t>
    1563    The proxy-revalidate response directive has the same meaning as the
     1560   The "proxy-revalidate" response directive has the same meaning as the
    15641561   must-revalidate response directive, except that it does not apply to
    15651562   private caches.
     
    15791576</t>
    15801577<t>
    1581    The max-age response directive indicates that the response is to be
     1578   The "max-age" response directive indicates that the response is to be
    15821579   considered stale after its age is greater than the specified number of
    15831580   seconds.
     
    16021599</t>
    16031600<t>
    1604    The s-maxage response directive indicates that, in shared caches, the
     1601   The "s-maxage" response directive indicates that, in shared caches, the
    16051602   maximum age specified by this directive overrides the maximum age
    16061603   specified by either the max-age directive or the <x:ref>Expires</x:ref>
     
    16191616   <iref item="no-transform" primary="true" subitem="Cache Directive" />
    16201617<t>
    1621    The no-transform response directive indicates that an intermediary
     1618   The "no-transform" response directive indicates that an intermediary
    16221619   (regardless of whether it implements a cache) &MUST-NOT; change the
    16231620   <x:ref>Content-Encoding</x:ref>, <x:ref>Content-Range</x:ref> or
Note: See TracChangeset for help on using the changeset viewer.