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

dquote cache directive names in introductory sentences

File:
1 edited

Legend:

Unmodified
Added
Removed

  • 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.