Ignore:
Timestamp:
May 6, 2013, 11:33:20 PM (7 years ago)
Author:
mnot@…
Message:

Move "Combining Partial Responses" up into "Storing Responses in Caches"; revise title of "Freshening Responses with 304 Not Modified". See #469

File:
1 edited

Legend:

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

    r2237 r2238  
    465465</t>
    466466</section>
     467
     468<section anchor="combining.responses" title="Combining Partial Content">
     469<t>
     470   A response might transfer only a partial representation if the
     471   connection closed prematurely or if the request used one or more Range
     472   specifiers (&partial;).  After several such transfers, a cache might have
     473   received several ranges of the same representation.  A cache &MAY; combine
     474   these ranges into a single stored response, and reuse that response to
     475   satisfy later requests, if they all share the same strong validator and
     476   the cache complies with the client requirements in &combining-byte-ranges;.
     477</t>
     478<t>
     479   When combining the new response with one or more stored responses, a
     480   cache &MUST;:
     481   <list style="symbols">
     482      <t>delete any <x:ref>Warning</x:ref> header fields in the stored response
     483         with warn-code 1xx (see <xref target="header.warning" />);</t>
     484      <t>retain any <x:ref>Warning</x:ref> header fields in the stored response
     485         with warn-code 2xx; and,</t>
     486      <t>use other header fields provided in the new response, aside
     487         from <x:ref>Content-Range</x:ref>, to replace all instances of the
     488         corresponding header fields in the stored response.</t>
     489   </list>
     490</t>
     491</section>
     492
    467493</section>
    468494
     
    875901</t>
    876902
    877 <section anchor="freshening.responses" title="Freshening Responses with 304 Not Modified">
     903<section anchor="freshening.responses" title="Freshening Stored Responses upon Validation">
    878904<t>
    879905   When a cache receives a <x:ref>304 (Not Modified)</x:ref> response and
     
    9811007</section>
    9821008
    983 
    984 <section anchor="combining.responses" title="Combining Partial Content">
    985 <t>
    986    A response might transfer only a partial representation if the
    987    connection closed prematurely or if the request used one or more Range
    988    specifiers (&partial;).  After several such transfers, a cache might have
    989    received several ranges of the same representation.  A cache &MAY; combine
    990    these ranges into a single stored response, and reuse that response to
    991    satisfy later requests, if they all share the same strong validator and
    992    the cache complies with the client requirements in &combining-byte-ranges;.
    993 </t>
    994 <t>
    995    When combining the new response with one or more stored responses, a
    996    cache &MUST;:
    997    <list style="symbols">
    998       <t>delete any <x:ref>Warning</x:ref> header fields in the stored response
    999          with warn-code 1xx (see <xref target="header.warning" />);</t>
    1000       <t>retain any <x:ref>Warning</x:ref> header fields in the stored response
    1001          with warn-code 2xx; and,</t>
    1002       <t>use other header fields provided in the new response, aside
    1003          from <x:ref>Content-Range</x:ref>, to replace all instances of the
    1004          corresponding header fields in the stored response.</t>
    1005    </list>
    1006 </t>
    1007 </section>
    10081009</section>
    10091010
Note: See TracChangeset for help on using the changeset viewer.