Ignore:
Timestamp:
15/09/13 02:23:08 (7 years ago)
Author:
fielding@…
Message:

uniform terminology for private cache (not non-shared), user agent, and avoid plural subjects in requirements; clarify that recipients don't have to parse all received URIs; addresses #234

File:
1 edited

Legend:

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

    r2401 r2402  
    697697      <div id="rfc.iref.s.1"></div>
    698698      <div id="rfc.iref.p.1"></div>
    699       <div id="shared.and.non-shared.caches">
     699      <div id="shared.and.private.caches">
    700700         <p id="rfc.section.1.p.3">A <dfn>shared cache</dfn> is a cache that stores responses to be reused by more than one user; shared caches are usually (but not always) deployed as
    701701            a part of an intermediary. A <dfn>private cache</dfn>, in contrast, is dedicated to a single user.
     
    720720      <div id="rfc.figure.u.1"></div><pre class="inline"><span id="rfc.iref.g.1"></span>  <a href="#delta-seconds" class="smpl">delta-seconds</a>  = 1*<a href="#imported.abnf" class="smpl">DIGIT</a>
    721721</pre><p id="rfc.section.1.2.1.p.3">If a cache receives a delta-seconds value larger than the largest positive integer it can represent, or if any of its subsequent
    722          calculations overflows, it <em class="bcp14">MUST</em> consider the value to be 2147483648 (2<sup>31</sup>). Recipients parsing a delta-seconds value <em class="bcp14">MUST</em> use an arithmetic type of at least 31 bits of range, and senders <em class="bcp14">MUST NOT</em> generate delta-seconds with a value greater than 2147483648.
     722         calculations overflows, the cache <em class="bcp14">MUST</em> consider the value to be 2147483648 (2<sup>31</sup>). A recipient parsing a delta-seconds value <em class="bcp14">MUST</em> use an arithmetic type of at least 31 bits of range, and a sender <em class="bcp14">MUST NOT</em> generate delta-seconds with a value greater than 2147483648.
    723723      </p>
    724724      <div id="rfc.iref.c.2"></div>
     
    912912      <p id="rfc.section.4.2.p.12"></p>
    913913      <ul>
    914          <li>Although all date formats are specified to be case-sensitive, cache recipients <em class="bcp14">SHOULD</em> match day, week and timezone names case-insensitively.
     914         <li>Although all date formats are specified to be case-sensitive, a cache recipient <em class="bcp14">SHOULD</em> match day, week, and timezone names case-insensitively.
    915915         </li>
    916916         <li>If a cache recipient's internal implementation of time has less resolution than the value of an HTTP-date, the recipient <em class="bcp14">MUST</em> internally represent a parsed <a href="#header.expires" class="smpl">Expires</a> date as the nearest time equal to or earlier than the received value.
    917917         </li>
    918          <li>Cache recipients <em class="bcp14">MUST NOT</em> allow local time zones to influence the calculation or comparison of an age or expiration time.
    919          </li>
    920          <li>Cache recipients <em class="bcp14">SHOULD</em> consider a date with a zone abbreviation other than GMT or UTC to be invalid for calculating expiration.
     918         <li>A cache recipient <em class="bcp14">MUST NOT</em> allow local time zones to influence the calculation or comparison of an age or expiration time.
     919         </li>
     920         <li>A cache recipient <em class="bcp14">SHOULD</em> consider a date with a zone abbreviation other than GMT or UTC to be invalid for calculating expiration.
    921921         </li>
    922922      </ul>
     
    12001200      <p id="rfc.section.5.2.p.5">Cache directives are identified by a token, to be compared case-insensitively, and have an optional argument, that can use
    12011201         both token and quoted-string syntax. For the directives defined below that define arguments, recipients ought to accept both
    1202          forms, even if one is documented to be preferred. For any directive not defined by this specification, recipients <em class="bcp14">MUST</em> accept both forms.
     1202         forms, even if one is documented to be preferred. For any directive not defined by this specification, a recipient <em class="bcp14">MUST</em> accept both forms.
    12031203      </p>
    12041204      <div id="rfc.figure.u.7"></div><pre class="inline"><span id="rfc.iref.g.3"></span><span id="rfc.iref.g.4"></span>  <a href="#header.cache-control" class="smpl">Cache-Control</a>   = 1#<a href="#header.cache-control" class="smpl">cache-directive</a>
     
    12181218         stale response.
    12191219      </p>
    1220       <p id="rfc.section.5.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.
     1220      <p id="rfc.section.5.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"'. A sender <em class="bcp14">SHOULD NOT</em> generate the quoted-string form.
    12211221      </p>
    12221222      <div id="rfc.iref.m.2"></div>
     
    12321232         to accept a stale response of any age.
    12331233      </p>
    1234       <p id="rfc.section.5.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.
     1234      <p id="rfc.section.5.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"'. A sender <em class="bcp14">SHOULD NOT</em> generate the quoted-string form.
    12351235      </p>
    12361236      <div id="rfc.iref.m.3"></div>
     
    12451245         for at least the specified number of seconds.
    12461246      </p>
    1247       <p id="rfc.section.5.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.
     1247      <p id="rfc.section.5.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"'. A sender <em class="bcp14">SHOULD NOT</em> generate the quoted-string form.
    12481248      </p>
    12491249      <div id="rfc.iref.n.1"></div>
     
    13021302         received; i.e., the special handling for the qualified form is not widely implemented.
    13031303      </p>
    1304       <p id="rfc.section.5.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).
     1304      <p id="rfc.section.5.2.2.2.p.6"><b>Note:</b> This directive uses the quoted-string form of the argument syntax. A sender <em class="bcp14">SHOULD NOT</em> generate the token form (even if quoting appears not to be needed for single-entry lists).
    13051305      </p>
    13061306      <div id="rfc.iref.n.5"></div>
     
    13171317      <div id="rfc.iref.p.2"></div>
    13181318      <h4 id="rfc.section.5.2.2.5"><a href="#rfc.section.5.2.2.5">5.2.2.5</a>&nbsp;<a id="cache-response-directive.public" href="#cache-response-directive.public">public</a></h4>
    1319       <p id="rfc.section.5.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
     1319      <p id="rfc.section.5.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 private 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
    13201320         as cacheable.)
    13211321      </p>
     
    13371337         was received; i.e., the special handling for the qualified form is not widely implemented.
    13381338      </p>
    1339       <p id="rfc.section.5.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).
     1339      <p id="rfc.section.5.2.2.6.p.6"><b>Note:</b> This directive uses the quoted-string form of the argument syntax. A sender <em class="bcp14">SHOULD NOT</em> generate the token form (even if quoting appears not to be needed for single-entry lists).
    13401340      </p>
    13411341      <div id="rfc.iref.p.4"></div>
     
    13541354         number of seconds.
    13551355      </p>
    1356       <p id="rfc.section.5.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.
     1356      <p id="rfc.section.5.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"'. A sender <em class="bcp14">SHOULD NOT</em> generate the quoted-string form.
    13571357      </p>
    13581358      <div id="rfc.iref.s.4"></div>
     
    13661366         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.
    13671367      </p>
    1368       <p id="rfc.section.5.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.
     1368      <p id="rfc.section.5.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"'. A sender <em class="bcp14">SHOULD NOT</em> generate the quoted-string form.
    13691369      </p>
    13701370      <h3 id="rfc.section.5.2.3"><a href="#rfc.section.5.2.3">5.2.3</a>&nbsp;<a id="cache.control.extensions" href="#cache.control.extensions">Cache Control Extensions</a></h3>
Note: See TracChangeset for help on using the changeset viewer.