Changeset 2363

Timestamp:

28/08/13 14:03:43 (9 years ago)

Author:

julian.reschke@…

Message:

Tune language about proxies forwarding unknown range units; for overlapping excessive ranges, change the "ought to reject" to a "MAY" (because it's really purely optional)
(see #490)

Location:

draft-ietf-httpbis/latest

Files:

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

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

@@ -449 +449 @@
   }
   @bottom-center {
-       content: "Expires February 13, 2014";
+       content: "Expires March 1, 2014";
   }
   @bottom-right {
@@ -492 +492 @@
       <meta name="dct.creator" content="Reschke, J. F.">
       <meta name="dct.identifier" content="urn:ietf:id:draft-ietf-httpbis-p5-range-latest">
-      <meta name="dct.issued" scheme="ISO8601" content="2013-08-12">
+      <meta name="dct.issued" scheme="ISO8601" content="2013-08-28">
       <meta name="dct.replaces" content="urn:ietf:rfc:2616">
       <meta name="dct.abstract" content="The Hypertext Transfer Protocol (HTTP) is an application-level protocol for distributed, collaborative, hypertext information systems. This document defines range requests and the rules for constructing and combining responses to those requests.">
@@ -518 +518 @@
             </tr>
             <tr>
-               <td class="left">Expires: February 13, 2014</td>
+               <td class="left">Expires: March 1, 2014</td>
                <td class="right">J. Reschke, Editor</td>
             </tr>
@@ -527 +527 @@
             <tr>
                <td class="left"></td>
-               <td class="right">August 12, 2013</td>
+               <td class="right">August 28, 2013</td>
             </tr>
          </tbody>
@@ -552 +552 @@
          in progress”.
       </p>
-      <p>This Internet-Draft will expire on February 13, 2014.</p>
+      <p>This Internet-Draft will expire on March 1, 2014.</p>
       <h1><a id="rfc.copyrightnotice" href="#rfc.copyrightnotice">Copyright Notice</a></h1>
       <p>Copyright © 2013 IETF Trust and the persons identified as the document authors. All rights reserved.</p>
@@ -744 +744 @@
          server <em class="bcp14">MUST</em> ignore a Range header field received with a request method other than GET.
       </p>
-      <p id="rfc.section.3.1.p.4">An origin server <em class="bcp14">MUST</em> ignore a Range header field that contains a range unit it does not understand. A proxy <em class="bcp14">MAY</em> either discard a Range header field that contains a range unit it does not understand or pass it to the next inbound server
-         when forwarding the request.
-      </p>
-      <p id="rfc.section.3.1.p.5">A server that supports range requests ought to ignore or reject a <a href="#header.range" class="smpl">Range</a> header field that consists of more than two overlapping ranges, or a set of many small ranges that are not listed in ascending
+      <p id="rfc.section.3.1.p.4">An origin server <em class="bcp14">MUST</em> ignore a Range header field that contains a range unit it does not understand. A proxy <em class="bcp14">MAY</em> discard a Range header field that contains a range unit it does not understand.
+      </p>
+      <p id="rfc.section.3.1.p.5">A server that supports range requests <em class="bcp14">MAY</em> ignore or reject a <a href="#header.range" class="smpl">Range</a> header field that consists of more than two overlapping ranges, or a set of many small ranges that are not listed in ascending
          order, since both are indications of either a broken client or a deliberate denial of service attack (<a href="#overlapping.ranges" title="Denial of Service Attacks using Range">Section&nbsp;6.1</a>). A client <em class="bcp14">SHOULD NOT</em> request multiple ranges that are inherently less efficient to process and transfer than a single range that encompasses the
          same data.
@@ -1354 +1353 @@
       </ul>
       <h2 id="rfc.section.E.5"><a href="#rfc.section.E.5">E.5</a>&nbsp;<a id="changes.since.23" href="#changes.since.23">Since draft-ietf-httpbis-p5-range-23</a></h2>
-      <p id="rfc.section.E.5.p.1">None yet.</p>
+      <p id="rfc.section.E.5.p.1">Closed issues: </p>
+      <ul>
+         <li>&lt;<a href="http://tools.ietf.org/wg/httpbis/trac/ticket/490">http://tools.ietf.org/wg/httpbis/trac/ticket/490</a>&gt;: "p5 editorial comments"
+         </li>
+      </ul>
       <h1 id="rfc.index"><a href="#rfc.index">Index</a></h1>
       <p class="noprint"><a href="#rfc.index.2">2</a> <a href="#rfc.index.4">4</a> <a href="#rfc.index.A">A</a> <a href="#rfc.index.B">B</a> <a href="#rfc.index.C">C</a> <a href="#rfc.index.G">G</a> <a href="#rfc.index.I">I</a> <a href="#rfc.index.M">M</a> <a href="#rfc.index.P">P</a> <a href="#rfc.index.R">R</a> 

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

@@ -392 +392 @@
 <t>
    An origin server &MUST; ignore a Range header field that contains a range
-   unit it does not understand. A proxy &MAY; either discard a Range header
-   field that contains a range unit it does not understand or pass it to the
-   next inbound server when forwarding the request.
-</t>
-<t>
-   A server that supports range requests ought to ignore or reject a
+   unit it does not understand. A proxy &MAY; discard a Range header
+   field that contains a range unit it does not understand.
+</t>
+<t>
+   A server that supports range requests &MAY; ignore or reject a
    <x:ref>Range</x:ref> header field that consists of more than two
    overlapping ranges, or a set of many small ranges that are not listed
@@ -1585 +1584 @@
 <section title="Since draft-ietf-httpbis-p5-range-23" anchor="changes.since.23">
 <t>
-  None yet.
+  Closed issues:
+  <list style="symbols">
+    <t>
+      <eref target="http://tools.ietf.org/wg/httpbis/trac/ticket/490"/>:
+      "p5 editorial comments"
+    </t>
+  </list>
 </t>
 </section>