Ignore:
Timestamp:
Mar 27, 2009, 8:25:20 AM (11 years ago)
Author:
julian.reschke@…
Message:

enhance readability of byte range examples

File:
1 edited

Legend:

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

    r564 r565  
    729729      <ul>
    730730         <li>The first 500 bytes:
    731             <div id="rfc.figure.u.9"></div><pre class="text">   bytes 0-499/1234
     731            <div id="rfc.figure.u.9"></div><pre class="text">  bytes 0-499/1234
    732732</pre> </li>
    733733         <li>The second 500 bytes:
    734             <div id="rfc.figure.u.10"></div><pre class="text">   bytes 500-999/1234
     734            <div id="rfc.figure.u.10"></div><pre class="text">  bytes 500-999/1234
    735735</pre> </li>
    736736         <li>All except for the first 500 bytes:
    737             <div id="rfc.figure.u.11"></div><pre class="text">   bytes 500-1233/1234
     737            <div id="rfc.figure.u.11"></div><pre class="text">  bytes 500-1233/1234
    738738</pre> </li>
    739739         <li>The last 500 bytes:
    740             <div id="rfc.figure.u.12"></div><pre class="text">   bytes 734-1233/1234
     740            <div id="rfc.figure.u.12"></div><pre class="text">  bytes 734-1233/1234
    741741</pre> </li>
    742742      </ul>
     
    830830      <p id="rfc.section.5.4.1.p.12">Examples of byte-ranges-specifier values (assuming an entity-body of length 10000): </p>
    831831      <ul>
    832          <li>The first 500 bytes (byte offsets 0-499, inclusive): bytes=0-499</li>
    833          <li>The second 500 bytes (byte offsets 500-999, inclusive): bytes=500-999</li>
    834          <li>The final 500 bytes (byte offsets 9500-9999, inclusive): bytes=-500</li>
    835          <li>Or bytes=9500-</li>
    836          <li>The first and last bytes only (bytes 0 and 9999): bytes=0-0,-1</li>
    837          <li>Several legal but not canonical specifications of the second 500 bytes (byte offsets 500-999, inclusive): <br> bytes=500-600,601-999<br> bytes=500-700,601-999
    838          </li>
     832         <li>The first 500 bytes (byte offsets 0-499, inclusive):
     833            <div id="rfc.figure.u.17"></div><pre class="text">  bytes=0-499
     834</pre> </li>
     835         <li>The second 500 bytes (byte offsets 500-999, inclusive):
     836            <div id="rfc.figure.u.18"></div><pre class="text">  bytes=500-999
     837</pre> </li>
     838         <li>The final 500 bytes (byte offsets 9500-9999, inclusive):
     839            <div id="rfc.figure.u.19"></div><pre class="text">  bytes=-500
     840</pre> Or: <div id="rfc.figure.u.20"></div><pre class="text">  bytes=9500-
     841</pre> </li>
     842         <li>The first and last bytes only (bytes 0 and 9999):
     843            <div id="rfc.figure.u.21"></div><pre class="text">  bytes=0-0,-1
     844</pre> </li>
     845         <li>Several legal but not canonical specifications of the second 500 bytes (byte offsets 500-999, inclusive):
     846            <div id="rfc.figure.u.22"></div><pre class="text">  bytes=500-600,601-999
     847  bytes=500-700,601-999
     848</pre> </li>
    839849      </ul>
    840850      <h3 id="rfc.section.5.4.2"><a href="#rfc.section.5.4.2">5.4.2</a>&nbsp;<a id="range.retrieval.requests" href="#range.retrieval.requests">Range Retrieval Requests</a></h3>
     
    842852         to the entity returned as the result of the request:
    843853      </p>
    844       <div id="rfc.figure.u.17"></div><pre class="inline"><span id="rfc.iref.g.23"></span>  <a href="#range.retrieval.requests" class="smpl">Range</a>   = "Range" ":" <a href="#core.rules" class="smpl">OWS</a> <a href="#range.retrieval.requests" class="smpl">Range-v</a>
     854      <div id="rfc.figure.u.23"></div><pre class="inline"><span id="rfc.iref.g.23"></span>  <a href="#range.retrieval.requests" class="smpl">Range</a>   = "Range" ":" <a href="#core.rules" class="smpl">OWS</a> <a href="#range.retrieval.requests" class="smpl">Range-v</a>
    845855  <a href="#range.retrieval.requests" class="smpl">Range-v</a> = <a href="#rule.ranges-specifier" class="smpl">byte-ranges-specifier</a>
    846856          / <a href="#range.retrieval.requests" class="smpl">other-ranges-specifier</a>
     
    10461056         <dd>IESG</dd>
    10471057      </dl>
    1048       <div id="rfc.figure.u.18"></div>
     1058      <div id="rfc.figure.u.24"></div>
    10491059      <p>For example:</p><pre class="text">  HTTP/1.1 206 Partial Content
    10501060  Date: Wed, 15 Nov 1995 06:25:24 GMT
     
    10941104      </p>
    10951105      <h1 id="rfc.section.C"><a href="#rfc.section.C">C.</a>&nbsp;<a id="collected.abnf" href="#collected.abnf">Collected ABNF</a></h1>
    1096       <div id="rfc.figure.u.19"></div> <pre class="inline"><a href="#header.accept-ranges" class="smpl">Accept-Ranges</a> = "Accept-Ranges:" OWS Accept-Ranges-v
     1106      <div id="rfc.figure.u.25"></div> <pre class="inline"><a href="#header.accept-ranges" class="smpl">Accept-Ranges</a> = "Accept-Ranges:" OWS Accept-Ranges-v
    10971107<a href="#header.accept-ranges" class="smpl">Accept-Ranges-v</a> = acceptable-ranges
    10981108
     
    11471157
    11481158
    1149 </pre> <div id="rfc.figure.u.20"></div>
     1159</pre> <div id="rfc.figure.u.26"></div>
    11501160      <p>ABNF diagnostics:</p><pre class="inline">; Accept-Ranges defined but not used
    11511161; Content-Range defined but not used
Note: See TracChangeset for help on using the changeset viewer.