Ignore:
Timestamp:
Jul 15, 2012, 10:51:16 AM (7 years ago)
Author:
julian.reschke@…
Message:

make links to cache directive definitions more specific

File:
1 edited

Legend:

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

    r1779 r1793  
    478478      header fields, and</t>
    479479      <t>the "private" cache response directive (see <xref
    480       target="cache-response-directive" />) does not appear in the response, if
    481       the cache is shared, and</t>
     480      target="cache-response-directive.private" />) does not appear in the
     481      response, if the cache is shared, and</t>
    482482      <t>the <x:ref>Authorization</x:ref> header field (see
    483483      &header-authorization;) does not appear in the request, if the cache is
     
    489489            <xref target="header.expires"/>), or</t>
    490490            <t>contains a max-age response cache directive (see <xref
    491             target="cache-response-directive" />), or</t>
     491            target="cache-response-directive.max-age" />), or</t>
    492492            <t>contains a s-maxage response cache directive and the cache is
    493493            shared, or</t>
     
    587587      successfully validated (<xref target="validation.model"/>), and</t>
    588588      <t>the stored response does not contain the no-cache cache directive
    589       (<xref target="cache-response-directive"/>), unless it is successfully
    590       validated (<xref target="validation.model"/>), and</t>
     589      (<xref target="cache-response-directive.no-cache"/>), unless it is
     590      successfully validated (<xref target="validation.model"/>), and</t>
    591591      <t>the stored response is either:
    592592         <list style="symbols">
     
    646646   <x:ref>Expires</x:ref> header field (<xref target="header.expires" />) or
    647647   the max-age response cache directive (<xref
    648    target="cache-response-directive" />). Generally, origin servers will
     648   target="cache-response-directive.max-age" />). Generally, origin servers will
    649649   assign future explicit expiration times to responses in the belief that the
    650650   representation is not likely to change in a semantically significant way
     
    699699   <list style="symbols">
    700700      <t>If the cache is shared and the s-maxage response cache directive
    701       (<xref target="cache-response-directive" />) is present, use its value,
     701      (<xref target="cache-response-directive.s-maxage" />) is present, use its value,
    702702      or</t>
    703703      <t>If the max-age response cache directive (<xref
    704       target="cache-response-directive" />) is present, use its value, or</t>
     704      target="cache-response-directive.max-age" />) is present, use its value, or</t>
    705705      <t>If the <x:ref>Expires</x:ref> response header field
    706706      (<xref target="header.expires" />) is present, use its value minus the
     
    17391739   <t>
    17401740       &Note; If a response includes a <x:ref>Cache-Control</x:ref> field with
    1741        the max-age directive (see <xref target="cache-response-directive" />),
     1741       the max-age directive (see <xref target="cache-response-directive.max-age" />),
    17421742       that directive overrides the Expires field. Likewise, the s-maxage
    1743        directive overrides Expires in shared caches.
     1743       directive (<xref target="cache-response-directive.s-maxage" />) overrides
     1744       the <x:ref>Expires</x:ref> header fieldin shared caches.
    17441745   </t>
    17451746</x:note>
Note: See TracChangeset for help on using the changeset viewer.