Ignore:
Timestamp:
19/05/13 08:44:58 (7 years ago)
Author:
fielding@…
Message:

(editorial) rephrase [2227] to be more consistent with the other recommendations for header fields and the definition of Vary

File:
1 edited

Legend:

Unmodified
Added
Removed
  • draft-ietf-httpbis/latest/p2-semantics.xml

    r2246 r2254  
    46644664    <x:lt><t>Under what conditions intermediaries are allowed to insert,
    46654665      delete, or modify the field's value.</t></x:lt>
    4666     <x:lt><t>That when the header is used in requests and affects response
    4667       selection (&caching-neg-resp;), it ought to be listed in the
    4668       <x:ref>Vary</x:ref> response header field (<xref target="header.vary"/>).</t></x:lt>
     4666    <x:lt><t>Whether it is appropriate to list the field-name in a
     4667      <x:ref>Vary</x:ref> response header field (e.g., when the request header
     4668      field is used by an origin server's content selection algorithm; see
     4669      <xref target="header.vary"/>).</t></x:lt>
    46694670    <x:lt><t>Whether the header field is useful or allowable in trailers (see
    46704671      &chunked-encoding;).</t></x:lt>
Note: See TracChangeset for help on using the changeset viewer.