Ignore:
Timestamp:
25/04/13 14:25:26 (7 years ago)
Author:
julian.reschke@…
Message:

augment considerations for new header fields

File:
1 edited

Legend:

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

    r2223 r2227  
    46424642      responses or requests, in all messages, only on responses to a
    46434643      particular request method, etc.</t></x:lt>
     4644    <x:lt><t>Whether the field should be stored by origin servers that
     4645      understand it upon a PUT request.</t></x:lt>
    46444646    <x:lt><t>Whether the field semantics are further refined by the context,
    46454647      such as by existing request methods or status codes.</t></x:lt>
     
    46494651    <x:lt><t>Under what conditions intermediaries are allowed to insert,
    46504652      delete, or modify the field's value.</t></x:lt>
    4651     <x:lt><t>How the header field might interact with caching (see
    4652       <xref target="Part6"/>).</t></x:lt>
     4653    <x:lt><t>That when the header is used in requests and affects response
     4654      selection (&caching-neg-resp;), it ought to be listed in the
     4655      <x:ref>Vary</x:ref> response header field (<xref target="header.vary"/>).</t></x:lt>
    46534656    <x:lt><t>Whether the header field is useful or allowable in trailers (see
    46544657      &chunked-encoding;).</t></x:lt>
Note: See TracChangeset for help on using the changeset viewer.