Changeset 2021

Timestamp:

29/11/12 03:32:34 (10 years ago)

Author:

mnot@…

Message:

Update Changes from RFC2616 from issues list.

Location:

draft-ietf-httpbis/latest

Files:

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

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

@@ -1229 +1229 @@
       </ol>
       <h1 id="rfc.section.B"><a href="#rfc.section.B">B.</a>&nbsp;<a id="changes.from.rfc.2616" href="#changes.from.rfc.2616">Changes from RFC 2616</a></h1>
-      <p id="rfc.section.B.p.1">This specification introduces a Range Specifier Registry. (<a href="#range.specifier.registry" title="Range Specifier Registry">Section&nbsp;2.1</a>)
-      </p>
-      <p id="rfc.section.B.p.2">A weak validator cannot be used in a <a href="#status.206" class="smpl">206</a> response. (<a href="#status.206" id="rfc.xref.status.206.2" title="206 Partial Content">Section&nbsp;3.1</a>)
-      </p>
-      <p id="rfc.section.B.p.3">multipart/byteranges can consist of a single part. (<a href="#internet.media.type.multipart.byteranges" title="Internet Media Type multipart/byteranges">Appendix&nbsp;A</a>)
+      <p id="rfc.section.B.p.1">A weak validator cannot be used in a <a href="#status.206" class="smpl">206</a> response. (<a href="#status.206" id="rfc.xref.status.206.2" title="206 Partial Content">Section&nbsp;3.1</a>)
+      </p>
+      <p id="rfc.section.B.p.2">The Content-Range header field only has meaning when the status code explicitly defines its use. (<a href="#header.content-range" id="rfc.xref.header.content-range.5" title="Content-Range">Section&nbsp;5.2</a>)
+      </p>
+      <p id="rfc.section.B.p.3">Servers are given more leeway in what they return to a range request, in order to mitigate malicious (or just greedy) clients.</p>
+      <p id="rfc.section.B.p.4">multipart/byteranges can consist of a single part. (<a href="#internet.media.type.multipart.byteranges" title="Internet Media Type multipart/byteranges">Appendix&nbsp;A</a>)
+      </p>
+      <p id="rfc.section.B.p.5">This specification introduces a Range Specifier Registry. (<a href="#range.specifier.registry" title="Range Specifier Registry">Section&nbsp;2.1</a>)
       </p>
       <h1 id="rfc.section.C"><a href="#rfc.section.C">C.</a>&nbsp;<a id="imported.abnf" href="#imported.abnf">Imported ABNF</a></h1>
@@ -1337 +1340 @@
             </li>
             <li><a id="rfc.index.C" href="#rfc.index.C"><b>C</b></a><ul>
-                  <li>Content-Range header field&nbsp;&nbsp;<a href="#rfc.xref.header.content-range.1">2</a>, <a href="#rfc.xref.header.content-range.2">3.1</a>, <a href="#rfc.xref.header.content-range.3">3.2</a>, <a href="#rfc.iref.c.1"><b>5.2</b></a>, <a href="#rfc.xref.header.content-range.4">6.2</a></li>
+                  <li>Content-Range header field&nbsp;&nbsp;<a href="#rfc.xref.header.content-range.1">2</a>, <a href="#rfc.xref.header.content-range.2">3.1</a>, <a href="#rfc.xref.header.content-range.3">3.2</a>, <a href="#rfc.iref.c.1"><b>5.2</b></a>, <a href="#rfc.xref.header.content-range.4">6.2</a>, <a href="#rfc.xref.header.content-range.5">B</a></li>
                </ul>
             </li>

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

@@ -1296 +1296 @@
 
 <section title="Changes from RFC 2616" anchor="changes.from.rfc.2616">
+
+<t>
+  A weak validator cannot be used in a <x:ref>206</x:ref> response.
+  (<xref target="status.206"/>)
+</t>
+<t>
+  The Content-Range header field only has meaning when the status code
+  explicitly defines its use.
+  (<xref target="header.content-range" />)
+</t>
+<t>
+  Servers are given more leeway in what they return to a range request,
+  in order to mitigate malicious (or just greedy) clients.
+</t>
+<t>
+  multipart/byteranges can consist of a single part.
+  (<xref target="internet.media.type.multipart.byteranges"/>)
+</t>
 <t>
   This specification introduces a Range Specifier Registry.
   (<xref target="range.specifier.registry"/>)
-</t>
-<t>
-  A weak validator cannot be used in a <x:ref>206</x:ref> response.
-  (<xref target="status.206"/>)
-</t>
-<t>
-  multipart/byteranges can consist of a single part.
-  (<xref target="internet.media.type.multipart.byteranges"/>)
 </t>
 </section>