Changeset 1543 for draft-ietf-httpbis/latest

Timestamp:

Feb 20, 2012, 10:08:57 AM (8 years ago)

Author:

julian.reschke@…

Message:

tune changes for [1542] (see #311)

Location:

draft-ietf-httpbis/latest

Files:

• p5-range.html (modified) (2 diffs)
• p5-range.xml (modified) (3 diffs)

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

@@ -826 +826 @@
       <p id="rfc.section.3.2.p.2">When this status code is returned for a byte-range request, the response <em class="bcp14">SHOULD</em> include a Content-Range header field specifying the current length of the representation (see <a href="#header.content-range" id="rfc.xref.header.content-range.3" title="Content-Range">Section&nbsp;5.2</a>). This response <em class="bcp14">MUST NOT</em> use the multipart/byteranges content-type. For example,
       </p>
-      <div id="rfc.figure.u.4"></div><pre class="text">  HTTP/1.1 416 Requested Range Not Satisfiable
-  Date: Mon, 20 Jan 2012 15:41:54 GMT
-  Content-Range: bytes */47022
-  Content-Type: image/gif
+      <div id="rfc.figure.u.4"></div><pre class="text">HTTP/1.1 416 Requested Range Not Satisfiable
+Date: Mon, 20 Jan 2012 15:41:54 GMT
+Content-Range: bytes */47022
+Content-Type: image/gif
 </pre><div class="note" id="rfc.section.3.2.p.4"> 
          <p> <b>Note:</b> Clients cannot depend on servers to send a 416 (Requested range not satisfiable) response instead of a 200 (OK) response for
@@ -843 +843 @@
          and a Content-Length header field showing the number of bytes actually transferred. For example,
       </p>
-      <div id="rfc.figure.u.5"></div><pre class="text">  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
+      <div id="rfc.figure.u.5"></div><pre class="text">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
 </pre><p id="rfc.section.4.1.p.3">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 <a href="#internet.media.type.multipart.byteranges" title="Internet Media Type multipart/byteranges">Appendix&nbsp;A</a>.
       </p>
-      <p id="rfc.section.4.1.p.4">A server can combine requested ranges when those ranges are overlapping (See <a href="#security.considerations" title="Security Considerations">Section&nbsp;7</a>).
+      <p id="rfc.section.4.1.p.4">A server <em class="bcp14">MAY</em> combine requested ranges when those ranges are overlapping (see <a href="#security.considerations" title="Security Considerations">Section&nbsp;7</a>).
       </p>
       <p id="rfc.section.4.1.p.5">A response to a request for a single range <em class="bcp14">MUST NOT</em> be sent using the multipart/byteranges media type. A response to a request for multiple ranges, whose result is a single range, <em class="bcp14">MAY</em> be sent as a multipart/byteranges media type with one part. A client that cannot decode a multipart/byteranges message <em class="bcp14">MUST NOT</em> ask for multiple ranges in a single request.

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

@@ -458 +458 @@
    This response &MUST-NOT; use the multipart/byteranges content-type. For example,
 </t>
-<figure><artwork type="example">
-  HTTP/1.1 416 Requested Range Not Satisfiable
-  Date: Mon, 20 Jan 2012 15:41:54 GMT
-  Content-Range: bytes */47022
-  Content-Type: image/gif
+<figure><artwork type="message/http; msgtype=&#34;response&#34;" x:indent-with="  ">
+HTTP/1.1 416 Requested Range Not Satisfiable
+Date: Mon, 20 Jan 2012 15:41:54 GMT
+Content-Range: bytes */47022
+Content-Type: image/gif
 </artwork></figure>
 <x:note>
@@ -484 +484 @@
    field showing the number of bytes actually transferred. For example,
 </t>
-<figure><artwork type="example">
-  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
+<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>
@@ -501 +501 @@
 <t>
    A server &MAY; combine requested ranges when those ranges are overlapping
-   (See <xref target="security.considerations"/>).
+   (see <xref target="security.considerations"/>).
 </t>
 <t>