Ignore:
Timestamp:
Jul 14, 2012, 7:09:09 AM (7 years ago)
Author:
julian.reschke@…
Message:

header -> header field (#234)

File:
1 edited

Legend:

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

    r1770 r1772  
    11331133   the same as that in a selected GET response (as per
    11341134   <xref target="caching.negotiated.responses"/>), the cache &SHOULD; update
    1135    the remaining headers in the stored response using the following rules:
     1135   the remaining header fields in the stored response using the following
     1136   rules:
    11361137   <list style="symbols">
    11371138      <t>delete any <x:ref>Warning</x:ref> header fields in the stored response
     
    19241925   Systems that generate multiple Warning header fields are encouraged to
    19251926   order them with this user agent behavior in mind. New Warning header fields
    1926    are added after any existing Warning headers fields.
     1927   are added after any existing Warning header fields.
    19271928</t>
    19281929<t>
     
    26722673    <t>
    26732674      <eref target="http://tools.ietf.org/wg/httpbis/trac/ticket/353"/>:
    2674       "Multiple values in Cache-Control headers"
     2675      "Multiple values in Cache-Control header fields"
    26752676    </t>
    26762677    <t>
Note: See TracChangeset for help on using the changeset viewer.