Changeset 2238 for draft-ietf-httpbis/latest/p6-cache.xml
- Timestamp:
- 07/05/13 06:33:20 (8 years ago)
- File:
-
- 1 edited
Legend:
- Unmodified
- Added
- Removed
-
draft-ietf-httpbis/latest/p6-cache.xml
r2237 r2238 465 465 </t> 466 466 </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 467 493 </section> 468 494 … … 875 901 </t> 876 902 877 <section anchor="freshening.responses" title="Freshening Responses with 304 Not Modified">903 <section anchor="freshening.responses" title="Freshening Stored Responses upon Validation"> 878 904 <t> 879 905 When a cache receives a <x:ref>304 (Not Modified)</x:ref> response and … … 981 1007 </section> 982 1008 983 984 <section anchor="combining.responses" title="Combining Partial Content">985 <t>986 A response might transfer only a partial representation if the987 connection closed prematurely or if the request used one or more Range988 specifiers (&partial;). After several such transfers, a cache might have989 received several ranges of the same representation. A cache &MAY; combine990 these ranges into a single stored response, and reuse that response to991 satisfy later requests, if they all share the same strong validator and992 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, a996 cache &MUST;:997 <list style="symbols">998 <t>delete any <x:ref>Warning</x:ref> header fields in the stored response999 with warn-code 1xx (see <xref target="header.warning" />);</t>1000 <t>retain any <x:ref>Warning</x:ref> header fields in the stored response1001 with warn-code 2xx; and,</t>1002 <t>use other header fields provided in the new response, aside1003 from <x:ref>Content-Range</x:ref>, to replace all instances of the1004 corresponding header fields in the stored response.</t>1005 </list>1006 </t>1007 </section>1008 1009 </section> 1009 1010
Note: See TracChangeset
for help on using the changeset viewer.