Ignore:
Timestamp:
Mar 27, 2009, 6:55:35 AM (11 years ago)
Author:
julian.reschke@…
Message:

move anchor for other-ranges-specifier to correct subsection

File:
1 edited

Legend:

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

    r563 r564  
    467467         <tr>
    468468            <td class="header left"></td>
    469             <td class="header right">March 24, 2009</td>
     469            <td class="header right">March 27, 2009</td>
    470470         </tr>
    471471      </table>
     
    799799      <p id="rfc.section.5.4.1.p.2">Byte range specifications in HTTP apply to the sequence of bytes in the entity-body (not necessarily the same as the message-body).</p>
    800800      <div id="rule.ranges-specifier">
    801          <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.
     801         <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.
    802802         </p>
    803803      </div>
     
    844844      <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>
    845845  <a href="#range.retrieval.requests" class="smpl">Range-v</a> = <a href="#rule.ranges-specifier" class="smpl">byte-ranges-specifier</a>
    846           / <a href="#rule.ranges-specifier" class="smpl">other-ranges-specifier</a>
    847   <a href="#rule.ranges-specifier" class="smpl">other-ranges-specifier</a> = 1*<a href="#notation" class="smpl">CHAR</a>
     846          / <a href="#range.retrieval.requests" class="smpl">other-ranges-specifier</a>
     847  <a href="#range.retrieval.requests" class="smpl">other-ranges-specifier</a> = 1*<a href="#notation" class="smpl">CHAR</a>
    848848</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,
    849849         since Range supports efficient recovery from partially failed transfers, and supports efficient partial retrieval of large
     
    11371137<a href="#header.content-range" class="smpl">other-range-resp-spec</a> = *CHAR
    11381138<a href="#range.units" class="smpl">other-range-unit</a> = token
    1139 <a href="#rule.ranges-specifier" class="smpl">other-ranges-specifier</a> = 1*CHAR
     1139<a href="#range.retrieval.requests" class="smpl">other-ranges-specifier</a> = 1*CHAR
    11401140
    11411141<a href="#range.units" class="smpl">range-unit</a> = bytes-unit / other-range-unit
Note: See TracChangeset for help on using the changeset viewer.