Ignore:
Timestamp:
20/05/13 01:43:03 (9 years ago)
Author:
mnot@…
Message:

Allow selecting headers to be smart about selecting a negotiated representation; see #453

File:
1 edited

Legend:

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

    r2250 r2264  
    924924<t>
    925925   If multiple selected responses are available (potentially including
    926    responses without a Vary header), the most recent response (as determined by
    927    the <x:ref>Date</x:ref> header field) is used; see <xref
    928    target="constructing.responses.from.caches"/>.
     926   responses without a Vary header), the cache will need to choose one to use.
     927   When a selecting header has a known mechanism for doing so (e.g., qvalues on
     928   <x:ref>Accept</x:ref> and similar request headers), that mechanism &MAY; be
     929   used to select preferred responses; of the remainder, the most recent
     930   response (as determined by the <x:ref>Date</x:ref> header field) is used, as
     931   per <xref target="constructing.responses.from.caches"/>.
    929932</t>
    930933<t>
Note: See TracChangeset for help on using the changeset viewer.