Ignore:
Timestamp:
Jul 8, 2012, 12:13:21 PM (7 years ago)
Author:
julian.reschke@…
Message:

Work-in-progress: hyperlink header field definitions (P1)

File:
1 edited

Legend:

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

    r1740 r1741  
    808808<t>
    809809   unless the cache is confident in the value of the <x:ref>Age</x:ref> header
    810    field (e.g., because there are no HTTP/1.0 hops in the Via header field), in
    811    which case the corrected_age_value &MAY; be used as the
     810   field (e.g., because there are no HTTP/1.0 hops in the <x:ref>Via</x:ref>
     811   header field), in which case the corrected_age_value &MAY; be used as the
    812812   corrected_initial_age.</t>
    813813<t>
     
    991991   If one or more stored GET responses can be selected (as per <xref
    992992   target="caching.negotiated.responses"/>) for a HEAD request, and the
    993    Content-Length, <x:ref>ETag</x:ref> or <x:ref>Last-Modified</x:ref> value of
    994    a HEAD response differs from that in a selected GET response, the cache
    995    &MUST; consider that selected response to be stale.
    996 </t>
    997 <t>
    998    If the Content-Length, <x:ref>ETag</x:ref> and <x:ref>Last-Modified</x:ref>
    999    values of a HEAD response (when present) are the same as that in a selected
    1000    GET response (as per <xref target="caching.negotiated.responses"/>), the
    1001    cache &SHOULD; update the remaining headers in the stored response using the
    1002    following rules:
     993   <x:ref>Content-Length</x:ref>, <x:ref>ETag</x:ref> or
     994   <x:ref>Last-Modified</x:ref> value of a HEAD response differs from that in a
     995   selected GET response, the cache &MUST; consider that selected response to
     996   be stale.
     997</t>
     998<t>
     999   If the <x:ref>Content-Length</x:ref>, <x:ref>ETag</x:ref> and
     1000   <x:ref>Last-Modified</x:ref> values of a HEAD response (when present) are
     1001   the same as that in a selected GET response (as per
     1002   <xref target="caching.negotiated.responses"/>), the cache &SHOULD; update
     1003   the remaining headers in the stored response using the following rules:
    10031004   <list style="symbols">
    10041005      <t>delete any <x:ref>Warning</x:ref> header fields in the stored response
     
    22802281    </front>
    22812282    <seriesInfo name="Internet-Draft" value="draft-ietf-httpbis-p1-messaging-&ID-VERSION;" />
    2282     <x:source basename="p1-messaging" href="p1-messaging.xml" />
     2283    <x:source basename="p1-messaging" href="p1-messaging.xml">
     2284      <x:defines>Content-Length</x:defines>
     2285      <x:defines>Via</x:defines>
     2286    </x:source>
    22832287  </reference>
    22842288
Note: See TracChangeset for help on using the changeset viewer.