Changeset 643 for draft-ietf-httpbis/latest

Timestamp:

28/07/09 12:18:05 (13 years ago)

Author:

ylafon@…

Message:

sync

File:

• draft-ietf-httpbis/latest/p5-range.html (modified) (4 diffs)

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

@@ -371 +371 @@
       <link rel="Appendix" title="C Collected ABNF" href="#rfc.section.C">
       <link rel="Appendix" title="D Change Log (to be removed by RFC Editor before publication)" href="#rfc.section.D">
-      <meta name="generator" content="http://greenbytes.de/tech/webdav/rfc2629.xslt, Revision 1.439, 2009-06-09 18:43:39, XSLT vendor: SAXON 8.9 from Saxonica http://www.saxonica.com/">
+      <meta name="generator" content="http://greenbytes.de/tech/webdav/rfc2629.xslt, Revision 1.439, 2009-06-09 18:43:39, XSLT vendor: SAXON 8.9.0.4 from Saxonica http://www.saxonica.com/">
       <link rel="schema.DC" href="http://purl.org/dc/elements/1.1/">
       <meta name="DC.Creator" content="Fielding, R.">
@@ -467 +467 @@
          <tr>
             <td class="header left"></td>
-            <td class="header right">July 27, 2009</td>
+            <td class="header right">July 28, 2009</td>
          </tr>
       </table>
@@ -856 +856 @@
   <a href="#range.retrieval.requests" class="smpl">Range-v</a> = <a href="#rule.ranges-specifier" class="smpl">byte-ranges-specifier</a>
           / <a href="#range.retrieval.requests" class="smpl">other-ranges-specifier</a>
-  <a href="#range.retrieval.requests" class="smpl">other-ranges-specifier</a> = 1*<a href="#notation" class="smpl">CHAR</a>
+  <a href="#range.retrieval.requests" class="smpl">other-ranges-specifier</a> = <a href="#range.units" class="smpl">other-range-unit</a> "=" <a href="#range.retrieval.requests" class="smpl">other-range-set</a>
+  <a href="#range.retrieval.requests" class="smpl">other-range-set</a> = 1*<a href="#notation" class="smpl">CHAR</a>
 </pre><p id="rfc.section.5.4.2.p.3">A server <em class="bcp14">MAY</em> ignore the Range header. However, HTTP/1.1 origin servers and intermediate caches ought to support byte ranges when possible,
          since Range supports efficient recovery from partially failed transfers, and supports efficient partial retrieval of large
@@ -1235 +1236 @@
       <ul>
          <li>Fixed discrepancy in the If-Range definition about allowed validators.</li>
+         <li> &lt;<a href="http://trac.tools.ietf.org/wg/httpbis/trac/ticket/151">http://trac.tools.ietf.org/wg/httpbis/trac/ticket/151</a>&gt;: "range unit missing from other-ranges-specifier in Range header"
+         </li>
       </ul>
       <h1 id="rfc.index"><a href="#rfc.index">Index</a></h1>