Changeset 2143 for draft-ietf-httpbis/latest/p5-range.xml

Timestamp:

20/01/13 14:57:02 (10 years ago)

Author:

fielding@…

Message:

(editorial) move status codes to where they are used; no text changes

File:

• draft-ietf-httpbis/latest/p5-range.xml (modified) (2 diffs)

draft-ietf-httpbis/latest/p5-range.xml

@@ -475 +475 @@
 
 
-<section title="Status Code Definitions" anchor="status.code.definitions">
+<section title="Responses to a Range Request" anchor="range.response">
+<section title="Response to a Single and Multiple Ranges Request">
+<t>
+   When an HTTP message includes the content of a single range (for
+   example, a response to a request for a single range, or to a request
+   for a set of ranges that overlap without any holes), this content is
+   transmitted with a <x:ref>Content-Range</x:ref> header field, and a
+   <x:ref>Content-Length</x:ref> header field showing the number of bytes
+   actually transferred. For example,
+</t>
+<figure><artwork type="message/http; msgtype=&#34;response&#34;" x:indent-with="  ">
+HTTP/1.1 206 Partial Content
+Date: Wed, 15 Nov 1995 06:25:24 GMT
+Last-Modified: Wed, 15 Nov 1995 04:58:08 GMT
+Content-Range: bytes 21010-47021/47022
+Content-Length: 26012
+Content-Type: image/gif
+</artwork></figure>
+<t>
+   When an HTTP message includes the content of multiple ranges (for
+   example, a response to a request for multiple non-overlapping
+   ranges), these are transmitted as a multipart message. The multipart
+   media type used for this purpose is "multipart/byteranges" as defined
+   in <xref target="internet.media.type.multipart.byteranges"/>.
+</t>
+<t>
+   A server &MAY; combine requested ranges when those ranges are overlapping
+   (see <xref target="overlapping.ranges"/>).
+</t>
+<t>
+   A response to a request for a single range &MUST-NOT; be sent using the
+   multipart/byteranges media type.  A response to a request for
+   multiple ranges, whose result is a single range, &MAY; be sent as a
+   multipart/byteranges media type with one part. A client that cannot
+   decode a multipart/byteranges message &MUST-NOT; ask for multiple
+   ranges in a single request.
+</t>
+<t>
+   When a client asks for multiple ranges in one request, the
+   server &SHOULD; send them in the order that they appeared in the
+   request.
+</t>
+</section>
+
 <section title="206 Partial Content" anchor="status.206">
   <iref primary="true" item="206 Partial Content (status code)" x:for-anchor=""/>
@@ -562 +605 @@
   </t>
 </x:note>
-</section>
-</section>
-
-<section title="Responses to a Range Request" anchor="range.response">
-<section title="Response to a Single and Multiple Ranges Request">
-<t>
-   When an HTTP message includes the content of a single range (for
-   example, a response to a request for a single range, or to a request
-   for a set of ranges that overlap without any holes), this content is
-   transmitted with a <x:ref>Content-Range</x:ref> header field, and a
-   <x:ref>Content-Length</x:ref> header field showing the number of bytes
-   actually transferred. For example,
-</t>
-<figure><artwork type="message/http; msgtype=&#34;response&#34;" x:indent-with="  ">
-HTTP/1.1 206 Partial Content
-Date: Wed, 15 Nov 1995 06:25:24 GMT
-Last-Modified: Wed, 15 Nov 1995 04:58:08 GMT
-Content-Range: bytes 21010-47021/47022
-Content-Length: 26012
-Content-Type: image/gif
-</artwork></figure>
-<t>
-   When an HTTP message includes the content of multiple ranges (for
-   example, a response to a request for multiple non-overlapping
-   ranges), these are transmitted as a multipart message. The multipart
-   media type used for this purpose is "multipart/byteranges" as defined
-   in <xref target="internet.media.type.multipart.byteranges"/>.
-</t>
-<t>
-   A server &MAY; combine requested ranges when those ranges are overlapping
-   (see <xref target="overlapping.ranges"/>).
-</t>
-<t>
-   A response to a request for a single range &MUST-NOT; be sent using the
-   multipart/byteranges media type.  A response to a request for
-   multiple ranges, whose result is a single range, &MAY; be sent as a
-   multipart/byteranges media type with one part. A client that cannot
-   decode a multipart/byteranges message &MUST-NOT; ask for multiple
-   ranges in a single request.
-</t>
-<t>
-   When a client asks for multiple ranges in one request, the
-   server &SHOULD; send them in the order that they appeared in the
-   request.
-</t>
 </section>