Ignore:
Timestamp:
06/01/13 11:23:55 (10 years ago)
Author:
fielding@…
Message:

delegate cache requirements from 304 to p6; related to #406

File:
1 edited

Legend:

Unmodified
Added
Removed
  • draft-ietf-httpbis/latest/p4-conditional.xml

    r2080 r2093  
    2727  <!ENTITY semantics                  "<xref target='Part2' xmlns:x='http://purl.org/net/xml2rfc/ext'/>">
    2828  <!ENTITY caching                    "<xref target='Part6' xmlns:x='http://purl.org/net/xml2rfc/ext'/>">
     29  <!ENTITY freshening-responses       "<xref target='Part6' x:rel='#freshening.responses' xmlns:x='http://purl.org/net/xml2rfc/ext'/>">
    2930  <!ENTITY header-accept-encoding     "<xref target='Part2' x:rel='#header.accept-encoding' xmlns:x='http://purl.org/net/xml2rfc/ext'/>">
    3031  <!ENTITY header-if-range            "<xref target='Part5' x:rel='#header.if-range' xmlns:x='http://purl.org/net/xml2rfc/ext'/>">
     
    958959   a sender &SHOULD-NOT; generate representation metadata other
    959960   than the above listed fields unless said metadata exists for the
    960    purpose of guiding cache updates (e.g., future HTTP extensions).
    961 </t>
    962 <t>
    963    If the recipient of a 304 response does not have a cached representation
    964    corresponding to the entity-tag indicated by the 304 response, then the
    965    recipient &MUST-NOT; use the 304 to update its own cache.  If this
    966    conditional request originated with an outbound client, such as a user agent
    967    with its own cache sending a conditional GET to a shared proxy, then the 304
    968    response &MAY; be forwarded to that client.  Otherwise, the recipient &MUST;
    969    disregard the 304 response and repeat the request without any preconditions.
    970 </t>
    971 <t>
    972    If a cache uses a received 304 response to update a cache entry, the
    973    cache &MUST; update the entry to reflect any new field values given in
    974    the response.
     961   purpose of guiding cache updates (e.g., <x:ref>Last-Modified</x:ref> might
     962   be useful if the response does not have an <x:ref>ETag</x:ref> field).
     963</t>
     964<t>
     965   Requirements on a cache that receives a 304 response are defined in
     966   &freshening-responses;. If the conditional request originated with an
     967   outbound client, such as a user agent with its own cache sending a
     968   conditional GET to a shared proxy, then the proxy &SHOULD; forward the
     969   304 response to that client.
    975970</t>
    976971</section>
Note: See TracChangeset for help on using the changeset viewer.