Changeset 2238 for draft-ietf-httpbis/latest/p6-cache.xml

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:

• draft-ietf-httpbis/latest/p6-cache.xml (modified) (3 diffs)

draft-ietf-httpbis/latest/p6-cache.xml

@@ -465 +465 @@
 </t>
 </section>
+
+<section anchor="combining.responses" title="Combining Partial Content">
+<t>
+   A response might transfer only a partial representation if the
+   connection closed prematurely or if the request used one or more Range
+   specifiers (&partial;).  After several such transfers, a cache might have
+   received several ranges of the same representation.  A cache &MAY; combine
+   these ranges into a single stored response, and reuse that response to
+   satisfy later requests, if they all share the same strong validator and
+   the cache complies with the client requirements in &combining-byte-ranges;.
+</t>
+<t>
+   When combining the new response with one or more stored responses, a
+   cache &MUST;:
+   <list style="symbols">
+      <t>delete any <x:ref>Warning</x:ref> header fields in the stored response
+         with warn-code 1xx (see <xref target="header.warning" />);</t>
+      <t>retain any <x:ref>Warning</x:ref> header fields in the stored response
+         with warn-code 2xx; and,</t>
+      <t>use other header fields provided in the new response, aside
+         from <x:ref>Content-Range</x:ref>, to replace all instances of the
+         corresponding header fields in the stored response.</t>
+   </list>
+</t>
+</section>
+
 </section>
 
@@ -875 +901 @@
 </t>
 
-<section anchor="freshening.responses" title="Freshening Responses with 304 Not Modified">
+<section anchor="freshening.responses" title="Freshening Stored Responses upon Validation">
 <t>
    When a cache receives a <x:ref>304 (Not Modified)</x:ref> response and
@@ -981 +1007 @@
 </section>
 
-
-<section anchor="combining.responses" title="Combining Partial Content">
-<t>
-   A response might transfer only a partial representation if the
-   connection closed prematurely or if the request used one or more Range
-   specifiers (&partial;).  After several such transfers, a cache might have
-   received several ranges of the same representation.  A cache &MAY; combine
-   these ranges into a single stored response, and reuse that response to
-   satisfy later requests, if they all share the same strong validator and
-   the cache complies with the client requirements in &combining-byte-ranges;.
-</t>
-<t>
-   When combining the new response with one or more stored responses, a
-   cache &MUST;:
-   <list style="symbols">
-      <t>delete any <x:ref>Warning</x:ref> header fields in the stored response
-         with warn-code 1xx (see <xref target="header.warning" />);</t>
-      <t>retain any <x:ref>Warning</x:ref> header fields in the stored response
-         with warn-code 2xx; and,</t>
-      <t>use other header fields provided in the new response, aside
-         from <x:ref>Content-Range</x:ref>, to replace all instances of the
-         corresponding header fields in the stored response.</t>
-   </list>
-</t>
-</section>
 </section>