Ignore:
Timestamp:
May 6, 2009, 12:11:26 AM (11 years ago)
Author:
julian.reschke@…
Message:

Make spec consistent in not stating "decimal" when it's already clear from the ABNF (related to #161)

File:
1 edited

Legend:

Unmodified
Added
Removed
  • draft-ietf-httpbis/latest/p5-range.html

    r573 r576  
    467467         <tr>
    468468            <td class="header left"></td>
    469             <td class="header right">May 1, 2009</td>
     469            <td class="header right">May 6, 2009</td>
    470470         </tr>
    471471      </table>
     
    724724      </p>
    725725      <p id="rfc.section.5.2.p.6">In the case of a byte range request: A server sending a response with status code 416 (Requested range not satisfiable) <em class="bcp14">SHOULD</em> include a Content-Range field with a byte-range-resp-spec of "*". The instance-length specifies the current length of the
    726          selected resource as a decimal number. A response with status code 206 (Partial Content) <em class="bcp14">MUST NOT</em> include a Content-Range field with a byte-range-resp-spec of "*".
     726         selected resource. A response with status code 206 (Partial Content) <em class="bcp14">MUST NOT</em> include a Content-Range field with a byte-range-resp-spec of "*".
    727727      </p>
    728728      <p id="rfc.section.5.2.p.7">Examples of byte-content-range-spec values, assuming that the entity contains a total of 1234 bytes: </p>
     
    808808  <a href="#rule.ranges-specifier" class="smpl">last-byte-pos</a>   = 1*<a href="#notation" class="smpl">DIGIT</a>
    809809</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
    810          gives the byte-offset of the last byte in the range; that is, the byte positions specified are inclusive. Byte offsets are
    811          decimal and start at zero.
     810         gives the byte-offset of the last byte in the range; that is, the byte positions specified are inclusive. Byte offsets start
     811         at zero.
    812812      </p>
    813813      <p id="rfc.section.5.4.1.p.6">If the last-byte-pos value is present, it <em class="bcp14">MUST</em> be greater than or equal to the first-byte-pos in that byte-range-spec, or the byte-range-spec is syntactically invalid. The
     
    820820      <div id="rfc.figure.u.16"></div><pre class="inline"><span id="rfc.iref.g.21"></span><span id="rfc.iref.g.22"></span>  <a href="#rule.ranges-specifier" class="smpl">suffix-byte-range-spec</a> = "-" <a href="#rule.ranges-specifier" class="smpl">suffix-length</a>
    821821  <a href="#rule.ranges-specifier" class="smpl">suffix-length</a> = 1*<a href="#notation" class="smpl">DIGIT</a>
    822 </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 decimal suffix-length
    823          value. (That is, this form specifies the last N bytes of an entity-body.) If the entity is shorter than the specified suffix-length,
    824          the entire entity-body is used.
     822</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
     823         is, this form specifies the last N bytes of an entity-body.) If the entity is shorter than the specified suffix-length, the
     824         entire entity-body is used.
    825825      </p>
    826826      <p id="rfc.section.5.4.1.p.11">If a syntactically valid byte-range-set includes at least one byte-range-spec whose first-byte-pos is less than the current
     
    12271227      </ul>
    12281228      <h2 id="rfc.section.D.8"><a href="#rfc.section.D.8">D.8</a>&nbsp;<a id="changes.since.06" href="#changes.since.06">Since draft-ietf-httpbis-p5-range-06</a></h2>
     1229      <p id="rfc.section.D.8.p.1">Closed issues: </p>
     1230      <ul>
     1231         <li> &lt;<a href="http://tools.ietf.org/wg/httpbis/trac/ticket/161">http://tools.ietf.org/wg/httpbis/trac/ticket/161</a>&gt;: "base for numeric protocol elements"
     1232         </li>
     1233      </ul>
    12291234      <h1 id="rfc.index"><a href="#rfc.index">Index</a></h1>
    12301235      <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.C">C</a> <a href="#rfc.index.G">G</a> <a href="#rfc.index.H">H</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> <a href="#rfc.index.S">S</a>
Note: See TracChangeset for help on using the changeset viewer.