Changeset 2512


Ignore:
Timestamp:
19/12/13 03:07:42 (6 years ago)
Author:
mnot@…
Message:

clear up "cache directive" language

File:
1 edited

Legend:

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

    r2511 r2512  
    290290      target="header.cache-control" />) does not appear in request or response
    291291      header fields, and</t>
    292       <t>the "private" cache response directive (see <xref
     292      <t>the "private" response directive (see <xref
    293293      target="cache-response-directive.private" />) does not appear in the
    294294      response, if the cache is shared, and</t>
     
    301301            <t>contains an <x:ref>Expires</x:ref> header field (see
    302302            <xref target="header.expires"/>), or</t>
    303             <t>contains a max-age response cache directive (see <xref
     303            <t>contains a max-age response directive (see <xref
    304304            target="cache-response-directive.max-age" />), or</t>
    305             <t>contains a s-maxage response cache directive (see <xref
     305            <t>contains a s-maxage response directive (see <xref
    306306            target="cache-response-directive.s-maxage" />) and the cache is
    307307            shared, or</t>
     
    311311            <t>has a status code that is defined as cacheable by default
    312312            (see <xref target="heuristic.freshness" />), or</t>
    313             <t>contains a public response cache directive (see <xref
     313            <t>contains a public response directive (see <xref
    314314            target="cache-response-directive.public"/>).</t>
    315315         </list>
     
    567567   provide an explicit expiration time in the future, using either the
    568568   <x:ref>Expires</x:ref> header field (<xref target="header.expires" />) or
    569    the max-age response cache directive (<xref
     569   the max-age response directive (<xref
    570570   target="cache-response-directive.max-age" />). Generally, origin servers
    571571   will assign future explicit expiration times to responses in the belief
     
    637637   freshness_lifetime) of a response by using the first match of:
    638638   <list style="symbols">
    639       <t>If the cache is shared and the s-maxage response cache directive
     639      <t>If the cache is shared and the s-maxage response directive
    640640      (<xref target="cache-response-directive.s-maxage" />) is present, use its value,
    641641      or</t>
    642       <t>If the max-age response cache directive (<xref
     642      <t>If the max-age response directive (<xref
    643643      target="cache-response-directive.max-age" />) is present, use its value, or</t>
    644644      <t>If the <x:ref>Expires</x:ref> response header field
     
    679679   freshness whose status codes are defined as cacheable by default (see
    680680   &status-overview;), and those responses without explicit freshness that have
    681    been marked as explicitly cacheable (e.g., with a "public" response cache
     681   been marked as explicitly cacheable (e.g., with a "public" response
    682682   directive).
    683683</t>
     
    12181218</t>
    12191219<t>
    1220    The "max-age" request directive indicates that the client is unwilling to
    1221    accept a response whose age is greater than the specified number of
    1222    seconds. Unless the max-stale request directive is also present, the
    1223    client is not willing to accept a stale response.
     1220   The "max-age" request directive indicates that the client is unwilling
     1221   to accept a response whose age is greater than the specified number of
     1222   seconds. Unless the max-stale request directive is also present, the client
     1223   is not willing to accept a stale response.
    12241224</t>
    12251225<t>
     
    25252525</t>
    25262526<t>
    2527   The "no-store" cache request directive doesn't apply to responses; i.e.,
     2527  The "no-store" request directive doesn't apply to responses; i.e.,
    25282528  a cache can satisfy a request with no-store on it, and does not invalidate
    25292529  it.
     
    25382538</t>
    25392539<t>
    2540   The "no-cache" response cache directive's meaning has been clarified.
     2540  The "no-cache" response directive's meaning has been clarified.
    25412541  (<xref target="cache-response-directive.no-cache" />)
    25422542</t>
Note: See TracChangeset for help on using the changeset viewer.