Ignore:
Timestamp:
May 8, 2013, 6:19:12 AM (6 years ago)
Author:
mnot@…
Message:

Remove misleading language about Vary and future requests, and account for case where some stored responses don't have Vary; see #471

File:
1 edited

Legend:

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

    r2247 r2248  
    916916</t>
    917917<t>
    918    A <x:ref>Vary</x:ref> header field-value of "*" always fails to match, and
    919    subsequent requests to that resource can only be properly interpreted by the
    920    origin server.
     918   A <x:ref>Vary</x:ref> header field-value of "*" always fails to match.
    921919</t>
    922920<t>
     
    925923</t>
    926924<t>
    927    If multiple selected responses are available, the most recent response
    928    (as determined by the <x:ref>Date</x:ref> header field) is used; see <xref
     925   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
    929928   target="constructing.responses.from.caches"/>.
    930929</t>
     
    26522651      "placement of extension point considerations"
    26532652    </t>
     2653    <t>
     2654      <eref target="http://tools.ietf.org/wg/httpbis/trac/ticket/471"/>:
     2655      "Vary and future requests"
     2656    </t>
    26542657  </list>
    26552658</t>
Note: See TracChangeset for help on using the changeset viewer.