Changeset 135 for draft-ietf-httpbis/latest/p5-range.html

Timestamp:

Jan 1, 2008, 9:15:17 AM (12 years ago)

Author:

julian.reschke@…

Message:

Consistent indentation for all ABNF rules (addresses #36)

File:

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

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

@@ -537 +537 @@
          uses range units in the Range (<a href="#header.range" id="rfc.xref.header.range.1" title="Range">Section&nbsp;5.4</a>) and Content-Range (<a href="#header.content-range" id="rfc.xref.header.content-range.1" title="Content-Range">Section&nbsp;5.2</a>) header fields. An entity can be broken down into subranges according to various structural units.
       </p>
-      <div id="rfc.figure.u.1"></div><pre class="inline"><span id="rfc.iref.g.1"></span><span id="rfc.iref.g.2"></span><span id="rfc.iref.g.3"></span>   range-unit       = bytes-unit | other-range-unit
-   bytes-unit       = "bytes"
-   other-range-unit = token
+      <div id="rfc.figure.u.1"></div><pre class="inline"><span id="rfc.iref.g.1"></span><span id="rfc.iref.g.2"></span><span id="rfc.iref.g.3"></span>  range-unit       = bytes-unit | other-range-unit
+  bytes-unit       = "bytes"
+  other-range-unit = token
 </pre><p id="rfc.section.2.p.3">The only range unit defined by HTTP/1.1 is "bytes". HTTP/1.1 implementations <em class="bcp14">MAY</em> ignore ranges specified using other units.
       </p>
@@ -602 +602 @@
       <h2 id="rfc.section.5.1"><a href="#rfc.section.5.1">5.1</a>&nbsp;<a id="header.accept-ranges" href="#header.accept-ranges">Accept-Ranges</a></h2>
       <p id="rfc.section.5.1.p.1">The Accept-Ranges response-header field allows the server to indicate its acceptance of range requests for a resource:</p>
-      <div id="rfc.figure.u.2"></div><pre class="inline"><span id="rfc.iref.g.4"></span><span id="rfc.iref.g.5"></span>       Accept-Ranges     = "Accept-Ranges" ":" acceptable-ranges
-       acceptable-ranges = 1#range-unit | "none"
+      <div id="rfc.figure.u.2"></div><pre class="inline"><span id="rfc.iref.g.4"></span><span id="rfc.iref.g.5"></span>  Accept-Ranges     = "Accept-Ranges" ":" acceptable-ranges
+  acceptable-ranges = 1#range-unit | "none"
 </pre><p id="rfc.section.5.1.p.3">Origin servers that accept byte-range requests <em class="bcp14">MAY</em> send
       </p>
@@ -619 +619 @@
          should be applied. Range units are defined in <a href="#range.units" title="Range Units">Section&nbsp;2</a>.
       </p>
-      <div id="rfc.figure.u.5"></div><pre class="inline"><span id="rfc.iref.g.6"></span><span id="rfc.iref.g.7"></span><span id="rfc.iref.g.8"></span><span id="rfc.iref.g.9"></span><span id="rfc.iref.g.10"></span>    Content-Range = "Content-Range" ":" content-range-spec
-
-    content-range-spec      = byte-content-range-spec
-    byte-content-range-spec = bytes-unit SP
-                              byte-range-resp-spec "/"
-                              ( instance-length | "*" )
-
-    byte-range-resp-spec = (first-byte-pos "-" last-byte-pos)
-                                   | "*"
-    instance-length           = 1*DIGIT
+      <div id="rfc.figure.u.5"></div><pre class="inline"><span id="rfc.iref.g.6"></span><span id="rfc.iref.g.7"></span><span id="rfc.iref.g.8"></span><span id="rfc.iref.g.9"></span><span id="rfc.iref.g.10"></span>  Content-Range = "Content-Range" ":" content-range-spec
+  
+  content-range-spec      = byte-content-range-spec
+  byte-content-range-spec = bytes-unit SP
+                            byte-range-resp-spec "/"
+                            ( instance-length | "*" )
+  
+  byte-range-resp-spec = (first-byte-pos "-" last-byte-pos)
+                                 | "*"
+  instance-length           = 1*DIGIT
 </pre><p id="rfc.section.5.2.p.3">The header <em class="bcp14">SHOULD</em> indicate the total length of the full entity-body, unless this length is unknown or difficult to determine. The asterisk "*"
          character means that the instance-length is unknown at the time when the response was generated.
@@ -696 +696 @@
          send me the part(s) that I am missing; otherwise, send me the entire new entity'.
       </p>
-      <div id="rfc.figure.u.11"></div><pre class="inline"><span id="rfc.iref.g.11"></span>     If-Range = "If-Range" ":" ( entity-tag | HTTP-date )
+      <div id="rfc.figure.u.11"></div><pre class="inline"><span id="rfc.iref.g.11"></span>  If-Range = "If-Range" ":" ( entity-tag | HTTP-date )
 </pre><p id="rfc.section.5.3.p.4">If the client has no entity tag for an entity, but does have a Last-Modified date, it <em class="bcp14">MAY</em> use that date in an If-Range header. (The server can distinguish between a valid HTTP-date and any form of entity-tag by examining
          no more than two characters.) The If-Range header <em class="bcp14">SHOULD</em> only be used together with a Range header, and <em class="bcp14">MUST</em> be ignored if the request does not include a Range header, or if the server does not support the sub-range operation.
@@ -713 +713 @@
       <p id="rfc.section.5.4.1.p.3">A byte range operation <em class="bcp14">MAY</em> specify a single range of bytes, or a set of ranges within a single entity.
       </p>
-      <div id="rfc.figure.u.12"></div><pre class="inline"><span id="rfc.iref.g.12"></span><span id="rfc.iref.g.13"></span><span id="rfc.iref.g.14"></span><span id="rfc.iref.g.15"></span><span id="rfc.iref.g.16"></span><span id="rfc.iref.g.17"></span>    ranges-specifier = byte-ranges-specifier
-    byte-ranges-specifier = bytes-unit "=" byte-range-set
-    byte-range-set  = 1#( byte-range-spec | suffix-byte-range-spec )
-    byte-range-spec = first-byte-pos "-" [last-byte-pos]
-    first-byte-pos  = 1*DIGIT
-    last-byte-pos   = 1*DIGIT
+      <div id="rfc.figure.u.12"></div><pre class="inline"><span id="rfc.iref.g.12"></span><span id="rfc.iref.g.13"></span><span id="rfc.iref.g.14"></span><span id="rfc.iref.g.15"></span><span id="rfc.iref.g.16"></span><span id="rfc.iref.g.17"></span>  ranges-specifier = byte-ranges-specifier
+  byte-ranges-specifier = bytes-unit "=" byte-range-set
+  byte-range-set  = 1#( byte-range-spec | suffix-byte-range-spec )
+  byte-range-spec = first-byte-pos "-" [last-byte-pos]
+  first-byte-pos  = 1*DIGIT
+  last-byte-pos   = 1*DIGIT
 </pre><p id="rfc.section.5.4.1.p.5">The first-byte-pos value in a byte-range-spec gives the byte-offset of the first byte in a range. The last-byte-pos value
          gives the byte-offset of the last byte in the range; that is, the byte positions specified are inclusive. Byte offsets start
@@ -730 +730 @@
       </p>
       <p id="rfc.section.5.4.1.p.8">By its choice of last-byte-pos, a client can limit the number of bytes retrieved without knowing the size of the entity.</p>
-      <div id="rfc.figure.u.13"></div><pre class="inline"><span id="rfc.iref.g.18"></span><span id="rfc.iref.g.19"></span>    suffix-byte-range-spec = "-" suffix-length
-    suffix-length = 1*DIGIT
+      <div id="rfc.figure.u.13"></div><pre class="inline"><span id="rfc.iref.g.18"></span><span id="rfc.iref.g.19"></span>  suffix-byte-range-spec = "-" suffix-length
+  suffix-length = 1*DIGIT
 </pre><p id="rfc.section.5.4.1.p.10">A suffix-byte-range-spec is used to specify the suffix of the entity-body, of a length given by the suffix-length value. (That
          is, this form specifies the last N bytes of an entity-body.) If the entity is shorter than the specified suffix-length, the
@@ -754 +754 @@
          to the entity returned as the result of the request:
       </p>
-      <div id="rfc.figure.u.14"></div><pre class="inline"><span id="rfc.iref.g.20"></span>   Range = "Range" ":" ranges-specifier
+      <div id="rfc.figure.u.14"></div><pre class="inline"><span id="rfc.iref.g.20"></span>  Range = "Range" ":" ranges-specifier
 </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