Changeset 2266


Ignore:
Timestamp:
May 20, 2013, 2:51:33 PM (6 years ago)
Author:
julian.reschke@…
Message:

header -> header field

Location:
draft-ietf-httpbis/latest
Files:
2 edited

Legend:

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

    r2265 r2266  
    10871087      <p id="rfc.section.4.3.p.5">The stored response with matching selecting header fields is known as the selected response.</p>
    10881088      <p id="rfc.section.4.3.p.6">If multiple selected responses are available (potentially including responses without a Vary header), the cache will need
    1089          to choose one to use. When a selecting header has a known mechanism for doing so (e.g., qvalues on <a href="p2-semantics.html#header.accept" class="smpl">Accept</a> and similar request headers), that mechanism <em class="bcp14">MAY</em> be used to select preferred responses; of the remainder, the most recent response (as determined by the <a href="p2-semantics.html#header.date" class="smpl">Date</a> header field) is used, as per <a href="#constructing.responses.from.caches" title="Constructing Responses from Caches">Section&nbsp;4</a>.
     1089         to choose one to use. When a selecting header has a known mechanism for doing so (e.g., qvalues on <a href="p2-semantics.html#header.accept" class="smpl">Accept</a> and similar request header fields), that mechanism <em class="bcp14">MAY</em> be used to select preferred responses; of the remainder, the most recent response (as determined by the <a href="p2-semantics.html#header.date" class="smpl">Date</a> header field) is used, as per <a href="#constructing.responses.from.caches" title="Constructing Responses from Caches">Section&nbsp;4</a>.
    10901090      </p>
    10911091      <p id="rfc.section.4.3.p.7">If no selected response is available, the cache cannot satisfy the presented request. Typically, it is forwarded to the origin
     
    17571757      <p id="rfc.section.10.p.6">Note that the Set-Cookie response header <a href="#RFC6265" id="rfc.xref.RFC6265.1"><cite title="HTTP State Management Mechanism">[RFC6265]</cite></a> does not inhibit caching; a cacheable response with a Set-Cookie header can be (and often is) used to satisfy subsequent requests
    17581758         to caches. Servers who wish to control caching of these responses are encouraged to emit appropriate Cache-Control response
    1759          headers.
     1759         header fields.
    17601760      </p>
    17611761      <h1 id="rfc.section.11"><a href="#rfc.section.11">11.</a>&nbsp;<a id="acks" href="#acks">Acknowledgments</a></h1>
  • draft-ietf-httpbis/latest/p6-cache.xml

    r2265 r2266  
    926926   responses without a Vary header), the cache will need to choose one to use.
    927927   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
     928   <x:ref>Accept</x:ref> and similar request header fields), that mechanism &MAY; be
    929929   used to select preferred responses; of the remainder, the most recent
    930930   response (as determined by the <x:ref>Date</x:ref> header field) is used, as
     
    20552055   often is) used to satisfy subsequent requests to caches. Servers who wish
    20562056   to control caching of these responses are encouraged to emit appropriate
    2057    Cache-Control response headers.
     2057   Cache-Control response header fields.
    20582058</t>
    20592059
Note: See TracChangeset for help on using the changeset viewer.