Ignore:
Timestamp:
Feb 6, 2008, 11:15:29 AM (12 years ago)
Author:
julian.reschke@…
Message:

Add sections that for now normatively reference the ABNF syntax and basic rules from Part1, also start work on referencing ABNF rules adopted from other parts (ongoing); relates to #36.

File:
1 edited

Legend:

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

    r204 r205  
    333333      <link rel="Index" href="#rfc.index">
    334334      <link rel="Chapter" title="1 Introduction" href="#rfc.section.1">
    335       <link rel="Chapter" title="2 Range Units" href="#rfc.section.2">
    336       <link rel="Chapter" title="3 Status Code Definitions" href="#rfc.section.3">
    337       <link rel="Chapter" title="4 Combining Byte Ranges" href="#rfc.section.4">
    338       <link rel="Chapter" title="5 Header Field Definitions" href="#rfc.section.5">
    339       <link rel="Chapter" title="6 IANA Considerations" href="#rfc.section.6">
    340       <link rel="Chapter" title="7 Security Considerations" href="#rfc.section.7">
    341       <link rel="Chapter" title="8 Acknowledgments" href="#rfc.section.8">
    342       <link rel="Chapter" href="#rfc.section.9" title="9 References">
     335      <link rel="Chapter" title="2 Notational Conventions and Generic Grammar" href="#rfc.section.2">
     336      <link rel="Chapter" title="3 Range Units" href="#rfc.section.3">
     337      <link rel="Chapter" title="4 Status Code Definitions" href="#rfc.section.4">
     338      <link rel="Chapter" title="5 Combining Byte Ranges" href="#rfc.section.5">
     339      <link rel="Chapter" title="6 Header Field Definitions" href="#rfc.section.6">
     340      <link rel="Chapter" title="7 IANA Considerations" href="#rfc.section.7">
     341      <link rel="Chapter" title="8 Security Considerations" href="#rfc.section.8">
     342      <link rel="Chapter" title="9 Acknowledgments" href="#rfc.section.9">
     343      <link rel="Chapter" href="#rfc.section.10" title="10 References">
    343344      <link rel="Appendix" title="A Internet Media Type multipart/byteranges" href="#rfc.section.A">
    344345      <link rel="Appendix" title="B Compatibility with Previous Versions" href="#rfc.section.B">
     
    482483            </ul>
    483484         </li>
    484          <li class="tocline0">2.&nbsp;&nbsp;&nbsp;<a href="#range.units">Range Units</a></li>
    485          <li class="tocline0">3.&nbsp;&nbsp;&nbsp;<a href="#rfc.section.3">Status Code Definitions</a><ul class="toc">
    486                <li class="tocline1">3.1&nbsp;&nbsp;&nbsp;<a href="#status.206">206 Partial Content</a></li>
    487                <li class="tocline1">3.2&nbsp;&nbsp;&nbsp;<a href="#status.416">416 Requested Range Not Satisfiable</a></li>
     485         <li class="tocline0">2.&nbsp;&nbsp;&nbsp;<a href="#notation">Notational Conventions and Generic Grammar</a></li>
     486         <li class="tocline0">3.&nbsp;&nbsp;&nbsp;<a href="#range.units">Range Units</a></li>
     487         <li class="tocline0">4.&nbsp;&nbsp;&nbsp;<a href="#rfc.section.4">Status Code Definitions</a><ul class="toc">
     488               <li class="tocline1">4.1&nbsp;&nbsp;&nbsp;<a href="#status.206">206 Partial Content</a></li>
     489               <li class="tocline1">4.2&nbsp;&nbsp;&nbsp;<a href="#status.416">416 Requested Range Not Satisfiable</a></li>
    488490            </ul>
    489491         </li>
    490          <li class="tocline0">4.&nbsp;&nbsp;&nbsp;<a href="#combining.byte.ranges">Combining Byte Ranges</a></li>
    491          <li class="tocline0">5.&nbsp;&nbsp;&nbsp;<a href="#header.fields">Header Field Definitions</a><ul class="toc">
    492                <li class="tocline1">5.1&nbsp;&nbsp;&nbsp;<a href="#header.accept-ranges">Accept-Ranges</a></li>
    493                <li class="tocline1">5.2&nbsp;&nbsp;&nbsp;<a href="#header.content-range">Content-Range</a></li>
    494                <li class="tocline1">5.3&nbsp;&nbsp;&nbsp;<a href="#header.if-range">If-Range</a></li>
    495                <li class="tocline1">5.4&nbsp;&nbsp;&nbsp;<a href="#header.range">Range</a><ul class="toc">
    496                      <li class="tocline1">5.4.1&nbsp;&nbsp;&nbsp;<a href="#byte.ranges">Byte Ranges</a></li>
    497                      <li class="tocline1">5.4.2&nbsp;&nbsp;&nbsp;<a href="#range.retrieval.requests">Range Retrieval Requests</a></li>
     492         <li class="tocline0">5.&nbsp;&nbsp;&nbsp;<a href="#combining.byte.ranges">Combining Byte Ranges</a></li>
     493         <li class="tocline0">6.&nbsp;&nbsp;&nbsp;<a href="#header.fields">Header Field Definitions</a><ul class="toc">
     494               <li class="tocline1">6.1&nbsp;&nbsp;&nbsp;<a href="#header.accept-ranges">Accept-Ranges</a></li>
     495               <li class="tocline1">6.2&nbsp;&nbsp;&nbsp;<a href="#header.content-range">Content-Range</a></li>
     496               <li class="tocline1">6.3&nbsp;&nbsp;&nbsp;<a href="#header.if-range">If-Range</a></li>
     497               <li class="tocline1">6.4&nbsp;&nbsp;&nbsp;<a href="#header.range">Range</a><ul class="toc">
     498                     <li class="tocline1">6.4.1&nbsp;&nbsp;&nbsp;<a href="#byte.ranges">Byte Ranges</a></li>
     499                     <li class="tocline1">6.4.2&nbsp;&nbsp;&nbsp;<a href="#range.retrieval.requests">Range Retrieval Requests</a></li>
    498500                  </ul>
    499501               </li>
    500502            </ul>
    501503         </li>
    502          <li class="tocline0">6.&nbsp;&nbsp;&nbsp;<a href="#IANA.considerations">IANA Considerations</a></li>
    503          <li class="tocline0">7.&nbsp;&nbsp;&nbsp;<a href="#security.considerations">Security Considerations</a></li>
    504          <li class="tocline0">8.&nbsp;&nbsp;&nbsp;<a href="#ack">Acknowledgments</a></li>
    505          <li class="tocline0">9.&nbsp;&nbsp;&nbsp;<a href="#rfc.references">References</a><ul class="toc">
    506                <li class="tocline1">9.1&nbsp;&nbsp;&nbsp;<a href="#rfc.references.1">Normative References</a></li>
    507                <li class="tocline1">9.2&nbsp;&nbsp;&nbsp;<a href="#rfc.references.2">Informative References</a></li>
     504         <li class="tocline0">7.&nbsp;&nbsp;&nbsp;<a href="#IANA.considerations">IANA Considerations</a></li>
     505         <li class="tocline0">8.&nbsp;&nbsp;&nbsp;<a href="#security.considerations">Security Considerations</a></li>
     506         <li class="tocline0">9.&nbsp;&nbsp;&nbsp;<a href="#ack">Acknowledgments</a></li>
     507         <li class="tocline0">10.&nbsp;&nbsp;&nbsp;<a href="#rfc.references">References</a><ul class="toc">
     508               <li class="tocline1">10.1&nbsp;&nbsp;&nbsp;<a href="#rfc.references.1">Normative References</a></li>
     509               <li class="tocline1">10.2&nbsp;&nbsp;&nbsp;<a href="#rfc.references.2">Informative References</a></li>
    508510            </ul>
    509511         </li>
     
    545547      <p id="rfc.section.1.1.p.2">An implementation is not compliant if it fails to satisfy one or more of the <em class="bcp14">MUST</em> or <em class="bcp14">REQUIRED</em> level requirements for the protocols it implements. An implementation that satisfies all the <em class="bcp14">MUST</em> or <em class="bcp14">REQUIRED</em> level and all the <em class="bcp14">SHOULD</em> level requirements for its protocols is said to be "unconditionally compliant"; one that satisfies all the <em class="bcp14">MUST</em> level requirements but not all the <em class="bcp14">SHOULD</em> level requirements for its protocols is said to be "conditionally compliant."
    546548      </p>
    547       <h1 id="rfc.section.2"><a href="#rfc.section.2">2.</a>&nbsp;<a id="range.units" href="#range.units">Range Units</a></h1>
    548       <p id="rfc.section.2.p.1">HTTP/1.1 allows a client to request that only part (a range of) the response entity be included within the response. HTTP/1.1
    549          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.
    550       </p>
    551       <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
     549      <h1 id="rfc.section.2"><a href="#rfc.section.2">2.</a>&nbsp;<a id="notation" href="#notation">Notational Conventions and Generic Grammar</a></h1>
     550      <p id="rfc.section.2.p.1">This specification uses the ABNF syntax defined in <a href="p1-messaging.html#notation.abnf" title="Augmented BNF">Section 2.1</a> of <a href="#Part1" id="rfc.xref.Part1.1"><cite title="HTTP/1.1, part 1: URIs, Connections, and Message Parsing">[Part1]</cite></a> and the core rules defined in <a href="p1-messaging.html#basic.rules" title="Basic Rules">Section 2.2</a> of <a href="#Part1" id="rfc.xref.Part1.2"><cite title="HTTP/1.1, part 1: URIs, Connections, and Message Parsing">[Part1]</cite></a>: <span class="comment">[abnf.dep: ABNF syntax and basic rules will be adopted from RFC 5234, see &lt;<a href="http://tools.ietf.org/wg/httpbis/trac/ticket/36">http://tools.ietf.org/wg/httpbis/trac/ticket/36</a>&gt;.]</span>
     551      </p>
     552      <div id="rfc.figure.u.1"></div><pre class="inline">  DIGIT      = &lt;DIGIT, defined in <a href="#Part1" id="rfc.xref.Part1.3"><cite title="HTTP/1.1, part 1: URIs, Connections, and Message Parsing">[Part1]</cite></a>, <a href="p1-messaging.html#basic.rules" title="Basic Rules">Section 2.2</a>&gt;
     553  SP         = &lt;SP, defined in <a href="#Part1" id="rfc.xref.Part1.4"><cite title="HTTP/1.1, part 1: URIs, Connections, and Message Parsing">[Part1]</cite></a>, <a href="p1-messaging.html#basic.rules" title="Basic Rules">Section 2.2</a>&gt;
     554</pre><div id="rfc.figure.u.2"></div><pre class="inline">  token      = &lt;token, defined in <a href="#Part1" id="rfc.xref.Part1.5"><cite title="HTTP/1.1, part 1: URIs, Connections, and Message Parsing">[Part1]</cite></a>, <a href="p1-messaging.html#basic.rules" title="Basic Rules">Section 2.2</a>&gt;
     555</pre><p id="rfc.section.2.p.4">The ABNF rules below are defined in other parts:</p>
     556      <div id="rfc.figure.u.3"></div><pre class="inline">  HTTP-date  = &lt;HTTP-date, defined in <a href="#Part1" id="rfc.xref.Part1.6"><cite title="HTTP/1.1, part 1: URIs, Connections, and Message Parsing">[Part1]</cite></a>, <a href="p1-messaging.html#full.date" title="Full Date">Section 3.3.1</a>&gt;
     557</pre><div id="rfc.figure.u.4"></div><pre class="inline">  entity-tag = &lt;entity-tag, defined in <a href="#Part4" id="rfc.xref.Part4.1"><cite title="HTTP/1.1, part 4: Conditional Requests">[Part4]</cite></a>, <a href="p4-conditional.html#entity.tags" title="Entity Tags">Section 3</a>&gt;
     558</pre><h1 id="rfc.section.3"><a href="#rfc.section.3">3.</a>&nbsp;<a id="range.units" href="#range.units">Range Units</a></h1>
     559      <p id="rfc.section.3.p.1">HTTP/1.1 allows a client to request that only part (a range of) the response entity be included within the response. HTTP/1.1
     560         uses range units in the Range (<a href="#header.range" id="rfc.xref.header.range.1" title="Range">Section&nbsp;6.4</a>) and Content-Range (<a href="#header.content-range" id="rfc.xref.header.content-range.1" title="Content-Range">Section&nbsp;6.2</a>) header fields. An entity can be broken down into subranges according to various structural units.
     561      </p>
     562      <div id="rfc.figure.u.5"></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
    552563  bytes-unit       = "bytes"
    553564  other-range-unit = token
    554 </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.
    555       </p>
    556       <p id="rfc.section.2.p.4">HTTP/1.1 has been designed to allow implementations of applications that do not depend on knowledge of ranges.</p>
    557       <h1 id="rfc.section.3"><a href="#rfc.section.3">3.</a>&nbsp;Status Code Definitions
     565</pre><p id="rfc.section.3.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.
     566      </p>
     567      <p id="rfc.section.3.p.4">HTTP/1.1 has been designed to allow implementations of applications that do not depend on knowledge of ranges.</p>
     568      <h1 id="rfc.section.4"><a href="#rfc.section.4">4.</a>&nbsp;Status Code Definitions
    558569      </h1>
    559570      <div id="rfc.iref.3"></div>
    560571      <div id="rfc.iref.s.1"></div>
    561       <h2 id="rfc.section.3.1"><a href="#rfc.section.3.1">3.1</a>&nbsp;<a id="status.206" href="#status.206">206 Partial Content</a></h2>
    562       <p id="rfc.section.3.1.p.1">The server has fulfilled the partial GET request for the resource. The request <em class="bcp14">MUST</em> have included a Range header field (<a href="#header.range" id="rfc.xref.header.range.2" title="Range">Section&nbsp;5.4</a>) indicating the desired range, and <em class="bcp14">MAY</em> have included an If-Range header field (<a href="#header.if-range" id="rfc.xref.header.if-range.1" title="If-Range">Section&nbsp;5.3</a>) to make the request conditional.
    563       </p>
    564       <p id="rfc.section.3.1.p.2">The response <em class="bcp14">MUST</em> include the following header fields:
     572      <h2 id="rfc.section.4.1"><a href="#rfc.section.4.1">4.1</a>&nbsp;<a id="status.206" href="#status.206">206 Partial Content</a></h2>
     573      <p id="rfc.section.4.1.p.1">The server has fulfilled the partial GET request for the resource. The request <em class="bcp14">MUST</em> have included a Range header field (<a href="#header.range" id="rfc.xref.header.range.2" title="Range">Section&nbsp;6.4</a>) indicating the desired range, and <em class="bcp14">MAY</em> have included an If-Range header field (<a href="#header.if-range" id="rfc.xref.header.if-range.1" title="If-Range">Section&nbsp;6.3</a>) to make the request conditional.
     574      </p>
     575      <p id="rfc.section.4.1.p.2">The response <em class="bcp14">MUST</em> include the following header fields:
    565576      </p>
    566577      <ul>
    567          <li>Either a Content-Range header field (<a href="#header.content-range" id="rfc.xref.header.content-range.2" title="Content-Range">Section&nbsp;5.2</a>) indicating the range included with this response, or a multipart/byteranges Content-Type including Content-Range fields
     578         <li>Either a Content-Range header field (<a href="#header.content-range" id="rfc.xref.header.content-range.2" title="Content-Range">Section&nbsp;6.2</a>) indicating the range included with this response, or a multipart/byteranges Content-Type including Content-Range fields
    568579            for each part. If a Content-Length header field is present in the response, its value <em class="bcp14">MUST</em> match the actual number of OCTETs transmitted in the message-body.
    569580         </li>
     
    574585         </li>
    575586      </ul>
    576       <p id="rfc.section.3.1.p.3">If the 206 response is the result of an If-Range request, the response <em class="bcp14">SHOULD NOT</em> include other entity-headers. Otherwise, the response <em class="bcp14">MUST</em> include all of the entity-headers that would have been returned with a 200 (OK) response to the same request.
    577       </p>
    578       <p id="rfc.section.3.1.p.4">A cache <em class="bcp14">MUST NOT</em> combine a 206 response with other previously cached content if the ETag or Last-Modified headers do not match exactly, see <a href="#combining.byte.ranges" title="Combining Byte Ranges">Section&nbsp;4</a>.
    579       </p>
    580       <p id="rfc.section.3.1.p.5">A cache that does not support the Range and Content-Range headers <em class="bcp14">MUST NOT</em> cache 206 (Partial Content) responses.
     587      <p id="rfc.section.4.1.p.3">If the 206 response is the result of an If-Range request, the response <em class="bcp14">SHOULD NOT</em> include other entity-headers. Otherwise, the response <em class="bcp14">MUST</em> include all of the entity-headers that would have been returned with a 200 (OK) response to the same request.
     588      </p>
     589      <p id="rfc.section.4.1.p.4">A cache <em class="bcp14">MUST NOT</em> combine a 206 response with other previously cached content if the ETag or Last-Modified headers do not match exactly, see <a href="#combining.byte.ranges" title="Combining Byte Ranges">Section&nbsp;5</a>.
     590      </p>
     591      <p id="rfc.section.4.1.p.5">A cache that does not support the Range and Content-Range headers <em class="bcp14">MUST NOT</em> cache 206 (Partial Content) responses.
    581592      </p>
    582593      <div id="rfc.iref.4"></div>
    583594      <div id="rfc.iref.s.2"></div>
    584       <h2 id="rfc.section.3.2"><a href="#rfc.section.3.2">3.2</a>&nbsp;<a id="status.416" href="#status.416">416 Requested Range Not Satisfiable</a></h2>
    585       <p id="rfc.section.3.2.p.1">A server <em class="bcp14">SHOULD</em> return a response with this status code if a request included a Range request-header field (<a href="#header.range" id="rfc.xref.header.range.3" title="Range">Section&nbsp;5.4</a>), and none of the range-specifier values in this field overlap the current extent of the selected resource, and the request
     595      <h2 id="rfc.section.4.2"><a href="#rfc.section.4.2">4.2</a>&nbsp;<a id="status.416" href="#status.416">416 Requested Range Not Satisfiable</a></h2>
     596      <p id="rfc.section.4.2.p.1">A server <em class="bcp14">SHOULD</em> return a response with this status code if a request included a Range request-header field (<a href="#header.range" id="rfc.xref.header.range.3" title="Range">Section&nbsp;6.4</a>), and none of the range-specifier values in this field overlap the current extent of the selected resource, and the request
    586597         did not include an If-Range request-header field. (For byte-ranges, this means that the first-byte-pos of all of the byte-range-spec
    587598         values were greater than the current length of the selected resource.)
    588599      </p>
    589       <p id="rfc.section.3.2.p.2">When this status code is returned for a byte-range request, the response <em class="bcp14">SHOULD</em> include a Content-Range entity-header field specifying the current length of the selected resource (see <a href="#header.content-range" id="rfc.xref.header.content-range.3" title="Content-Range">Section&nbsp;5.2</a>). This response <em class="bcp14">MUST NOT</em> use the multipart/byteranges content-type.
    590       </p>
    591       <h1 id="rfc.section.4"><a href="#rfc.section.4">4.</a>&nbsp;<a id="combining.byte.ranges" href="#combining.byte.ranges">Combining Byte Ranges</a></h1>
    592       <p id="rfc.section.4.p.1">A response might transfer only a subrange of the bytes of an entity-body, either because the request included one or more
     600      <p id="rfc.section.4.2.p.2">When this status code is returned for a byte-range request, the response <em class="bcp14">SHOULD</em> include a Content-Range entity-header field specifying the current length of the selected resource (see <a href="#header.content-range" id="rfc.xref.header.content-range.3" title="Content-Range">Section&nbsp;6.2</a>). This response <em class="bcp14">MUST NOT</em> use the multipart/byteranges content-type.
     601      </p>
     602      <h1 id="rfc.section.5"><a href="#rfc.section.5">5.</a>&nbsp;<a id="combining.byte.ranges" href="#combining.byte.ranges">Combining Byte Ranges</a></h1>
     603      <p id="rfc.section.5.p.1">A response might transfer only a subrange of the bytes of an entity-body, either because the request included one or more
    593604         Range specifications, or because a connection was broken prematurely. After several such transfers, a cache might have received
    594605         several ranges of the same entity-body.
    595606      </p>
    596       <p id="rfc.section.4.p.2">If a cache has a stored non-empty set of subranges for an entity, and an incoming response transfers another subrange, the
     607      <p id="rfc.section.5.p.2">If a cache has a stored non-empty set of subranges for an entity, and an incoming response transfers another subrange, the
    597608         cache <em class="bcp14">MAY</em> combine the new subrange with the existing set if both the following conditions are met:
    598609      </p>
    599610      <ul>
    600611         <li>Both the incoming response and the cache entry have a cache validator.</li>
    601          <li>The two cache validators match using the strong comparison function (see <a href="p4-conditional.html#weak.and.strong.validators" title="Weak and Strong Validators">Section 4</a> of <a href="#Part4" id="rfc.xref.Part4.1"><cite title="HTTP/1.1, part 4: Conditional Requests">[Part4]</cite></a>).
     612         <li>The two cache validators match using the strong comparison function (see <a href="p4-conditional.html#weak.and.strong.validators" title="Weak and Strong Validators">Section 5</a> of <a href="#Part4" id="rfc.xref.Part4.2"><cite title="HTTP/1.1, part 4: Conditional Requests">[Part4]</cite></a>).
    602613         </li>
    603614      </ul>
    604       <p id="rfc.section.4.p.3">If either requirement is not met, the cache <em class="bcp14">MUST</em> use only the most recent partial response (based on the Date values transmitted with every response, and using the incoming
     615      <p id="rfc.section.5.p.3">If either requirement is not met, the cache <em class="bcp14">MUST</em> use only the most recent partial response (based on the Date values transmitted with every response, and using the incoming
    605616         response if these values are equal or missing), and <em class="bcp14">MUST</em> discard the other partial information.
    606617      </p>
    607       <h1 id="rfc.section.5"><a href="#rfc.section.5">5.</a>&nbsp;<a id="header.fields" href="#header.fields">Header Field Definitions</a></h1>
    608       <p id="rfc.section.5.p.1">This section defines the syntax and semantics of HTTP/1.1 header fields related to range requests and partial responses.</p>
    609       <p id="rfc.section.5.p.2">For entity-header fields, both sender and recipient refer to either the client or the server, depending on who sends and who
     618      <h1 id="rfc.section.6"><a href="#rfc.section.6">6.</a>&nbsp;<a id="header.fields" href="#header.fields">Header Field Definitions</a></h1>
     619      <p id="rfc.section.6.p.1">This section defines the syntax and semantics of HTTP/1.1 header fields related to range requests and partial responses.</p>
     620      <p id="rfc.section.6.p.2">For entity-header fields, both sender and recipient refer to either the client or the server, depending on who sends and who
    610621         receives the entity.
    611622      </p>
    612623      <div id="rfc.iref.a.1"></div>
    613624      <div id="rfc.iref.h.1"></div>
    614       <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>
    615       <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>
    616       <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
     625      <h2 id="rfc.section.6.1"><a href="#rfc.section.6.1">6.1</a>&nbsp;<a id="header.accept-ranges" href="#header.accept-ranges">Accept-Ranges</a></h2>
     626      <p id="rfc.section.6.1.p.1">The Accept-Ranges response-header field allows the server to indicate its acceptance of range requests for a resource:</p>
     627      <div id="rfc.figure.u.6"></div><pre class="inline"><span id="rfc.iref.g.4"></span><span id="rfc.iref.g.5"></span>  Accept-Ranges     = "Accept-Ranges" ":" acceptable-ranges
    617628  acceptable-ranges = 1#range-unit | "none"
    618 </pre><p id="rfc.section.5.1.p.3">Origin servers that accept byte-range requests <em class="bcp14">MAY</em> send
    619       </p>
    620       <div id="rfc.figure.u.3"></div><pre class="text">       Accept-Ranges: bytes
    621 </pre><p id="rfc.section.5.1.p.5">but are not required to do so. Clients <em class="bcp14">MAY</em> generate byte-range requests without having received this header for the resource involved. Range units are defined in <a href="#range.units" title="Range Units">Section&nbsp;2</a>.
    622       </p>
    623       <p id="rfc.section.5.1.p.6">Servers that do not accept any kind of range request for a resource <em class="bcp14">MAY</em> send
    624       </p>
    625       <div id="rfc.figure.u.4"></div><pre class="text">       Accept-Ranges: none
    626 </pre><p id="rfc.section.5.1.p.8">to advise the client not to attempt a range request.</p>
     629</pre><p id="rfc.section.6.1.p.3">Origin servers that accept byte-range requests <em class="bcp14">MAY</em> send
     630      </p>
     631      <div id="rfc.figure.u.7"></div><pre class="text">       Accept-Ranges: bytes
     632</pre><p id="rfc.section.6.1.p.5">but are not required to do so. Clients <em class="bcp14">MAY</em> generate byte-range requests without having received this header for the resource involved. Range units are defined in <a href="#range.units" title="Range Units">Section&nbsp;3</a>.
     633      </p>
     634      <p id="rfc.section.6.1.p.6">Servers that do not accept any kind of range request for a resource <em class="bcp14">MAY</em> send
     635      </p>
     636      <div id="rfc.figure.u.8"></div><pre class="text">       Accept-Ranges: none
     637</pre><p id="rfc.section.6.1.p.8">to advise the client not to attempt a range request.</p>
    627638      <div id="rfc.iref.c.1"></div>
    628639      <div id="rfc.iref.h.2"></div>
    629       <h2 id="rfc.section.5.2"><a href="#rfc.section.5.2">5.2</a>&nbsp;<a id="header.content-range" href="#header.content-range">Content-Range</a></h2>
    630       <p id="rfc.section.5.2.p.1">The Content-Range entity-header is sent with a partial entity-body to specify where in the full entity-body the partial body
    631          should be applied. Range units are defined in <a href="#range.units" title="Range Units">Section&nbsp;2</a>.
    632       </p>
    633       <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
     640      <h2 id="rfc.section.6.2"><a href="#rfc.section.6.2">6.2</a>&nbsp;<a id="header.content-range" href="#header.content-range">Content-Range</a></h2>
     641      <p id="rfc.section.6.2.p.1">The Content-Range entity-header is sent with a partial entity-body to specify where in the full entity-body the partial body
     642         should be applied. Range units are defined in <a href="#range.units" title="Range Units">Section&nbsp;3</a>.
     643      </p>
     644      <div id="rfc.figure.u.9"></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
    634645 
    635646  content-range-spec      = byte-content-range-spec
     
    641652                                 | "*"
    642653  instance-length           = 1*DIGIT
    643 </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 "*"
     654</pre><p id="rfc.section.6.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 "*"
    644655         character means that the instance-length is unknown at the time when the response was generated.
    645656      </p>
    646       <p id="rfc.section.5.2.p.4">Unlike byte-ranges-specifier values (see <a href="#byte.ranges" title="Byte Ranges">Section&nbsp;5.4.1</a>), a byte-range-resp-spec <em class="bcp14">MUST</em> only specify one range, and <em class="bcp14">MUST</em> contain absolute byte positions for both the first and last byte of the range.
    647       </p>
    648       <p id="rfc.section.5.2.p.5">A byte-content-range-spec with a byte-range-resp-spec whose last-byte-pos value is less than its first-byte-pos value, or
     657      <p id="rfc.section.6.2.p.4">Unlike byte-ranges-specifier values (see <a href="#byte.ranges" title="Byte Ranges">Section&nbsp;6.4.1</a>), a byte-range-resp-spec <em class="bcp14">MUST</em> only specify one range, and <em class="bcp14">MUST</em> contain absolute byte positions for both the first and last byte of the range.
     658      </p>
     659      <p id="rfc.section.6.2.p.5">A byte-content-range-spec with a byte-range-resp-spec whose last-byte-pos value is less than its first-byte-pos value, or
    649660         whose instance-length value is less than or equal to its last-byte-pos value, is invalid. The recipient of an invalid byte-content-range-spec <em class="bcp14">MUST</em> ignore it and any content transferred along with it.
    650661      </p>
    651       <p id="rfc.section.5.2.p.6">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
     662      <p id="rfc.section.6.2.p.6">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
    652663         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 "*".
    653664      </p>
    654       <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>
     665      <p id="rfc.section.6.2.p.7">Examples of byte-content-range-spec values, assuming that the entity contains a total of 1234 bytes: </p>
    655666      <ul>
    656667         <li>The first 500 bytes:
    657             <div id="rfc.figure.u.6"></div><pre class="text">   bytes 0-499/1234
     668            <div id="rfc.figure.u.10"></div><pre class="text">   bytes 0-499/1234
    658669</pre> </li>
    659670         <li>The second 500 bytes:
    660             <div id="rfc.figure.u.7"></div><pre class="text">   bytes 500-999/1234
     671            <div id="rfc.figure.u.11"></div><pre class="text">   bytes 500-999/1234
    661672</pre> </li>
    662673         <li>All except for the first 500 bytes:
    663             <div id="rfc.figure.u.8"></div><pre class="text">   bytes 500-1233/1234
     674            <div id="rfc.figure.u.12"></div><pre class="text">   bytes 500-1233/1234
    664675</pre> </li>
    665676         <li>The last 500 bytes:
    666             <div id="rfc.figure.u.9"></div><pre class="text">   bytes 734-1233/1234
     677            <div id="rfc.figure.u.13"></div><pre class="text">   bytes 734-1233/1234
    667678</pre> </li>
    668679      </ul>
    669       <p id="rfc.section.5.2.p.8">When an HTTP message includes the content of a single range (for example, a response to a request for a single range, or to
     680      <p id="rfc.section.6.2.p.8">When an HTTP message includes the content of a single range (for example, a response to a request for a single range, or to
    670681         a request for a set of ranges that overlap without any holes), this content is transmitted with a Content-Range header, and
    671682         a Content-Length header showing the number of bytes actually transferred. For example,
    672683      </p>
    673       <div id="rfc.figure.u.10"></div><pre class="text">    HTTP/1.1 206 Partial Content
     684      <div id="rfc.figure.u.14"></div><pre class="text">    HTTP/1.1 206 Partial Content
    674685    Date: Wed, 15 Nov 1995 06:25:24 GMT
    675686    Last-Modified: Wed, 15 Nov 1995 04:58:08 GMT
     
    677688    Content-Length: 26012
    678689    Content-Type: image/gif
    679 </pre><p id="rfc.section.5.2.p.10">When an HTTP message includes the content of multiple ranges (for example, a response to a request for multiple non-overlapping
     690</pre><p id="rfc.section.6.2.p.10">When an HTTP message includes the content of multiple ranges (for example, a response to a request for multiple non-overlapping
    680691         ranges), these are transmitted as a multipart message. The multipart media type used for this purpose is "multipart/byteranges"
    681692         as defined in <a href="#internet.media.type.multipart.byteranges" title="Internet Media Type multipart/byteranges">Appendix&nbsp;A</a>. See <a href="#changes.from.rfc.2068" title="Changes from RFC 2068">Appendix&nbsp;B.1</a> for a compatibility issue.
    682693      </p>
    683       <p id="rfc.section.5.2.p.11">A response to a request for a single range <em class="bcp14">MUST NOT</em> be sent using the multipart/byteranges media type. A response to a request for multiple ranges, whose result is a single range, <em class="bcp14">MAY</em> be sent as a multipart/byteranges media type with one part. A client that cannot decode a multipart/byteranges message <em class="bcp14">MUST NOT</em> ask for multiple byte-ranges in a single request.
    684       </p>
    685       <p id="rfc.section.5.2.p.12">When a client requests multiple byte-ranges in one request, the server <em class="bcp14">SHOULD</em> return them in the order that they appeared in the request.
    686       </p>
    687       <p id="rfc.section.5.2.p.13">If the server ignores a byte-range-spec because it is syntactically invalid, the server <em class="bcp14">SHOULD</em> treat the request as if the invalid Range header field did not exist. (Normally, this means return a 200 response containing
     694      <p id="rfc.section.6.2.p.11">A response to a request for a single range <em class="bcp14">MUST NOT</em> be sent using the multipart/byteranges media type. A response to a request for multiple ranges, whose result is a single range, <em class="bcp14">MAY</em> be sent as a multipart/byteranges media type with one part. A client that cannot decode a multipart/byteranges message <em class="bcp14">MUST NOT</em> ask for multiple byte-ranges in a single request.
     695      </p>
     696      <p id="rfc.section.6.2.p.12">When a client requests multiple byte-ranges in one request, the server <em class="bcp14">SHOULD</em> return them in the order that they appeared in the request.
     697      </p>
     698      <p id="rfc.section.6.2.p.13">If the server ignores a byte-range-spec because it is syntactically invalid, the server <em class="bcp14">SHOULD</em> treat the request as if the invalid Range header field did not exist. (Normally, this means return a 200 response containing
    688699         the full entity).
    689700      </p>
    690       <p id="rfc.section.5.2.p.14">If the server receives a request (other than one including an If-Range request-header field) with an unsatisfiable Range request-header
     701      <p id="rfc.section.6.2.p.14">If the server receives a request (other than one including an If-Range request-header field) with an unsatisfiable Range request-header
    691702         field (that is, all of whose byte-range-spec values have a first-byte-pos value greater than the current length of the selected
    692          resource), it <em class="bcp14">SHOULD</em> return a response code of 416 (Requested range not satisfiable) (<a href="#status.416" id="rfc.xref.status.416.1" title="416 Requested Range Not Satisfiable">Section&nbsp;3.2</a>).
     703         resource), it <em class="bcp14">SHOULD</em> return a response code of 416 (Requested range not satisfiable) (<a href="#status.416" id="rfc.xref.status.416.1" title="416 Requested Range Not Satisfiable">Section&nbsp;4.2</a>).
    693704      </p>
    694705      <dl class="empty">
     
    699710      <div id="rfc.iref.i.1"></div>
    700711      <div id="rfc.iref.h.3"></div>
    701       <h2 id="rfc.section.5.3"><a href="#rfc.section.5.3">5.3</a>&nbsp;<a id="header.if-range" href="#header.if-range">If-Range</a></h2>
    702       <p id="rfc.section.5.3.p.1">If a client has a partial copy of an entity in its cache, and wishes to have an up-to-date copy of the entire entity in its
     712      <h2 id="rfc.section.6.3"><a href="#rfc.section.6.3">6.3</a>&nbsp;<a id="header.if-range" href="#header.if-range">If-Range</a></h2>
     713      <p id="rfc.section.6.3.p.1">If a client has a partial copy of an entity in its cache, and wishes to have an up-to-date copy of the entire entity in its
    703714         cache, it could use the Range request-header with a conditional GET (using either or both of If-Unmodified-Since and If-Match.)
    704715         However, if the condition fails because the entity has been modified, the client would then have to make a second request
    705716         to obtain the entire current entity-body.
    706717      </p>
    707       <p id="rfc.section.5.3.p.2">The If-Range header allows a client to "short-circuit" the second request. Informally, its meaning is `if the entity is unchanged,
     718      <p id="rfc.section.6.3.p.2">The If-Range header allows a client to "short-circuit" the second request. Informally, its meaning is `if the entity is unchanged,
    708719         send me the part(s) that I am missing; otherwise, send me the entire new entity'.
    709720      </p>
    710       <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 )
    711 </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
     721      <div id="rfc.figure.u.15"></div><pre class="inline"><span id="rfc.iref.g.11"></span>  If-Range = "If-Range" ":" ( entity-tag | HTTP-date )
     722</pre><p id="rfc.section.6.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
    712723         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.
    713724      </p>
    714       <p id="rfc.section.5.3.p.5">If the entity tag given in the If-Range header matches the current entity tag for the entity, then the server <em class="bcp14">SHOULD</em> provide the specified sub-range of the entity using a 206 (Partial Content) response. If the entity tag does not match, then
     725      <p id="rfc.section.6.3.p.5">If the entity tag given in the If-Range header matches the current entity tag for the entity, then the server <em class="bcp14">SHOULD</em> provide the specified sub-range of the entity using a 206 (Partial Content) response. If the entity tag does not match, then
    715726         the server <em class="bcp14">SHOULD</em> return the entire entity using a 200 (OK) response.
    716727      </p>
    717728      <div id="rfc.iref.r.1"></div>
    718729      <div id="rfc.iref.h.4"></div>
    719       <h2 id="rfc.section.5.4"><a href="#rfc.section.5.4">5.4</a>&nbsp;<a id="header.range" href="#header.range">Range</a></h2>
    720       <h3 id="rfc.section.5.4.1"><a href="#rfc.section.5.4.1">5.4.1</a>&nbsp;<a id="byte.ranges" href="#byte.ranges">Byte Ranges</a></h3>
    721       <p id="rfc.section.5.4.1.p.1">Since all HTTP entities are represented in HTTP messages as sequences of bytes, the concept of a byte range is meaningful
     730      <h2 id="rfc.section.6.4"><a href="#rfc.section.6.4">6.4</a>&nbsp;<a id="header.range" href="#header.range">Range</a></h2>
     731      <h3 id="rfc.section.6.4.1"><a href="#rfc.section.6.4.1">6.4.1</a>&nbsp;<a id="byte.ranges" href="#byte.ranges">Byte Ranges</a></h3>
     732      <p id="rfc.section.6.4.1.p.1">Since all HTTP entities are represented in HTTP messages as sequences of bytes, the concept of a byte range is meaningful
    722733         for any HTTP entity. (However, not all clients and servers need to support byte-range operations.)
    723734      </p>
    724       <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>
    725       <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.
    726       </p>
    727       <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
     735      <p id="rfc.section.6.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>
     736      <p id="rfc.section.6.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.
     737      </p>
     738      <div id="rfc.figure.u.16"></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
    728739  byte-ranges-specifier = bytes-unit "=" byte-range-set
    729740  byte-range-set  = 1#( byte-range-spec | suffix-byte-range-spec )
     
    731742  first-byte-pos  = 1*DIGIT
    732743  last-byte-pos   = 1*DIGIT
    733 </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
     744</pre><p id="rfc.section.6.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
    734745         gives the byte-offset of the last byte in the range; that is, the byte positions specified are inclusive. Byte offsets start
    735746         at zero.
    736747      </p>
    737       <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
     748      <p id="rfc.section.6.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
    738749         recipient of a byte-range-set that includes one or more syntactically invalid byte-range-spec values <em class="bcp14">MUST</em> ignore the header field that includes that byte-range-set.
    739750      </p>
    740       <p id="rfc.section.5.4.1.p.7">If the last-byte-pos value is absent, or if the value is greater than or equal to the current length of the entity-body, last-byte-pos
     751      <p id="rfc.section.6.4.1.p.7">If the last-byte-pos value is absent, or if the value is greater than or equal to the current length of the entity-body, last-byte-pos
    741752         is taken to be equal to one less than the current length of the entity-body in bytes.
    742753      </p>
    743       <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>
    744       <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
     754      <p id="rfc.section.6.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>
     755      <div id="rfc.figure.u.17"></div><pre class="inline"><span id="rfc.iref.g.18"></span><span id="rfc.iref.g.19"></span>  suffix-byte-range-spec = "-" suffix-length
    745756  suffix-length = 1*DIGIT
    746 </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
     757</pre><p id="rfc.section.6.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
    747758         is, this form specifies the last N bytes of an entity-body.) If the entity is shorter than the specified suffix-length, the
    748759         entire entity-body is used.
    749760      </p>
    750       <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
     761      <p id="rfc.section.6.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
    751762         length of the entity-body, or at least one suffix-byte-range-spec with a non-zero suffix-length, then the byte-range-set is
    752763         satisfiable. Otherwise, the byte-range-set is unsatisfiable. If the byte-range-set is unsatisfiable, the server <em class="bcp14">SHOULD</em> return a response with a status of 416 (Requested range not satisfiable). Otherwise, the server <em class="bcp14">SHOULD</em> return a response with a status of 206 (Partial Content) containing the satisfiable ranges of the entity-body.
    753764      </p>
    754       <p id="rfc.section.5.4.1.p.12">Examples of byte-ranges-specifier values (assuming an entity-body of length 10000): </p>
     765      <p id="rfc.section.6.4.1.p.12">Examples of byte-ranges-specifier values (assuming an entity-body of length 10000): </p>
    755766      <ul>
    756767         <li>The first 500 bytes (byte offsets 0-499, inclusive): bytes=0-499</li>
     
    762773         </li>
    763774      </ul>
    764       <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>
    765       <p id="rfc.section.5.4.2.p.1">HTTP retrieval requests using conditional or unconditional GET methods <em class="bcp14">MAY</em> request one or more sub-ranges of the entity, instead of the entire entity, using the Range request header, which applies
     775      <h3 id="rfc.section.6.4.2"><a href="#rfc.section.6.4.2">6.4.2</a>&nbsp;<a id="range.retrieval.requests" href="#range.retrieval.requests">Range Retrieval Requests</a></h3>
     776      <p id="rfc.section.6.4.2.p.1">HTTP retrieval requests using conditional or unconditional GET methods <em class="bcp14">MAY</em> request one or more sub-ranges of the entity, instead of the entire entity, using the Range request header, which applies
    766777         to the entity returned as the result of the request:
    767778      </p>
    768       <div id="rfc.figure.u.14"></div><pre class="inline"><span id="rfc.iref.g.20"></span>  Range = "Range" ":" ranges-specifier
    769 </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,
     779      <div id="rfc.figure.u.18"></div><pre class="inline"><span id="rfc.iref.g.20"></span>  Range = "Range" ":" ranges-specifier
     780</pre><p id="rfc.section.6.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,
    770781         since Range supports efficient recovery from partially failed transfers, and supports efficient partial retrieval of large
    771782         entities.
    772783      </p>
    773       <p id="rfc.section.5.4.2.p.4">If the server supports the Range header and the specified range or ranges are appropriate for the entity: </p>
     784      <p id="rfc.section.6.4.2.p.4">If the server supports the Range header and the specified range or ranges are appropriate for the entity: </p>
    774785      <ul>
    775786         <li>The presence of a Range header in an unconditional GET modifies what is returned if the GET is otherwise successful. In other
     
    781792         </li>
    782793      </ul>
    783       <p id="rfc.section.5.4.2.p.5">In some cases, it might be more appropriate to use the If-Range header (see <a href="#header.if-range" id="rfc.xref.header.if-range.2" title="If-Range">Section&nbsp;5.3</a>) in addition to the Range header.
    784       </p>
    785       <p id="rfc.section.5.4.2.p.6">If a proxy that supports ranges receives a Range request, forwards the request to an inbound server, and receives an entire
     794      <p id="rfc.section.6.4.2.p.5">In some cases, it might be more appropriate to use the If-Range header (see <a href="#header.if-range" id="rfc.xref.header.if-range.2" title="If-Range">Section&nbsp;6.3</a>) in addition to the Range header.
     795      </p>
     796      <p id="rfc.section.6.4.2.p.6">If a proxy that supports ranges receives a Range request, forwards the request to an inbound server, and receives an entire
    786797         entity in reply, it <em class="bcp14">SHOULD</em> only return the requested range to its client. It <em class="bcp14">SHOULD</em> store the entire received response in its cache if that is consistent with its cache allocation policies.
    787798      </p>
    788       <h1 id="rfc.section.6"><a href="#rfc.section.6">6.</a>&nbsp;<a id="IANA.considerations" href="#IANA.considerations">IANA Considerations</a></h1>
    789       <p id="rfc.section.6.p.1"> <span class="comment">[rfc.comment.1: TBD.]</span>
    790       </p>
    791       <h1 id="rfc.section.7"><a href="#rfc.section.7">7.</a>&nbsp;<a id="security.considerations" href="#security.considerations">Security Considerations</a></h1>
    792       <p id="rfc.section.7.p.1">No additional security considerations have been identified beyond those applicable to HTTP in general <a href="#Part1" id="rfc.xref.Part1.1"><cite title="HTTP/1.1, part 1: URIs, Connections, and Message Parsing">[Part1]</cite></a>.
    793       </p>
    794       <h1 id="rfc.section.8"><a href="#rfc.section.8">8.</a>&nbsp;<a id="ack" href="#ack">Acknowledgments</a></h1>
    795       <p id="rfc.section.8.p.1">Most of the specification of ranges is based on work originally done by Ari Luotonen and John Franks, with additional input
     799      <h1 id="rfc.section.7"><a href="#rfc.section.7">7.</a>&nbsp;<a id="IANA.considerations" href="#IANA.considerations">IANA Considerations</a></h1>
     800      <p id="rfc.section.7.p.1"> <span class="comment">[rfc.comment.1: TBD.]</span>
     801      </p>
     802      <h1 id="rfc.section.8"><a href="#rfc.section.8">8.</a>&nbsp;<a id="security.considerations" href="#security.considerations">Security Considerations</a></h1>
     803      <p id="rfc.section.8.p.1">No additional security considerations have been identified beyond those applicable to HTTP in general <a href="#Part1" id="rfc.xref.Part1.7"><cite title="HTTP/1.1, part 1: URIs, Connections, and Message Parsing">[Part1]</cite></a>.
     804      </p>
     805      <h1 id="rfc.section.9"><a href="#rfc.section.9">9.</a>&nbsp;<a id="ack" href="#ack">Acknowledgments</a></h1>
     806      <p id="rfc.section.9.p.1">Most of the specification of ranges is based on work originally done by Ari Luotonen and John Franks, with additional input
    796807         from Steve Zilles, Daniel W. Connolly, Roy T. Fielding, Jim Gettys, Martin Hamilton, Koen Holtman, Shel Kaplan, Paul Leach,
    797808         Alex Lopez-Ortiz, Larry Masinter, Jeff Mogul, Lou Montulli, David W. Morris, Luigi Rizzo, and Bill Weihl.
    798809      </p>
    799       <h1 id="rfc.references"><a id="rfc.section.9" href="#rfc.section.9">9.</a> References
     810      <h1 id="rfc.references"><a id="rfc.section.10" href="#rfc.section.10">10.</a> References
    800811      </h1>
    801       <h2 id="rfc.references.1"><a href="#rfc.section.9.1" id="rfc.section.9.1">9.1</a> Normative References
     812      <h2 id="rfc.references.1"><a href="#rfc.section.10.1" id="rfc.section.10.1">10.1</a> Normative References
    802813      </h2>
    803814      <table summary="Normative References">           
     
    833844         </tr>
    834845      </table>
    835       <h2 id="rfc.references.2"><a href="#rfc.section.9.2" id="rfc.section.9.2">9.2</a> Informative References
     846      <h2 id="rfc.references.2"><a href="#rfc.section.10.2" id="rfc.section.10.2">10.2</a> Informative References
    836847      </h2>
    837848      <table summary="Informative References">   
     
    912923         <dd>IESG</dd>
    913924      </dl>
    914       <div id="rfc.figure.u.15"></div>
     925      <div id="rfc.figure.u.19"></div>
    915926      <p>For example:</p><pre class="text">   HTTP/1.1 206 Partial Content
    916927   Date: Wed, 15 Nov 1995 06:25:24 GMT
     
    941952      <p id="rfc.section.B.1.p.1">Transfer-coding and message lengths all interact in ways that required fixing exactly when chunked encoding is used (to allow
    942953         for transfer encoding that may not be self delimiting); it was important to straighten out exactly how message lengths are
    943          computed. (<a href="#header.content-range" id="rfc.xref.header.content-range.4" title="Content-Range">Section&nbsp;5.2</a>, see also <a href="#Part1" id="rfc.xref.Part1.2"><cite title="HTTP/1.1, part 1: URIs, Connections, and Message Parsing">[Part1]</cite></a>, <a href="#Part3" id="rfc.xref.Part3.1"><cite title="HTTP/1.1, part 3: Message Payload and Content Negotiation">[Part3]</cite></a> and <a href="#Part6" id="rfc.xref.Part6.1"><cite title="HTTP/1.1, part 6: Caching">[Part6]</cite></a>)
     954         computed. (<a href="#header.content-range" id="rfc.xref.header.content-range.4" title="Content-Range">Section&nbsp;6.2</a>, see also <a href="#Part1" id="rfc.xref.Part1.8"><cite title="HTTP/1.1, part 1: URIs, Connections, and Message Parsing">[Part1]</cite></a>, <a href="#Part3" id="rfc.xref.Part3.1"><cite title="HTTP/1.1, part 3: Message Payload and Content Negotiation">[Part3]</cite></a> and <a href="#Part6" id="rfc.xref.Part6.1"><cite title="HTTP/1.1, part 6: Caching">[Part6]</cite></a>)
    944955      </p>
    945956      <p id="rfc.section.B.1.p.2">There are situations where a server (especially a proxy) does not know the full length of a response but is capable of serving
    946957         a byterange request. We therefore need a mechanism to allow byteranges with a content-range not indicating the full length
    947          of the message. (<a href="#header.content-range" id="rfc.xref.header.content-range.5" title="Content-Range">Section&nbsp;5.2</a>)
     958         of the message. (<a href="#header.content-range" id="rfc.xref.header.content-range.5" title="Content-Range">Section&nbsp;6.2</a>)
    948959      </p>
    949960      <p id="rfc.section.B.1.p.3">Range request responses would become very verbose if all meta-data were always returned; by allowing the server to only send
    950          needed headers in a 206 response, this problem can be avoided. (Section <a href="#status.206" id="rfc.xref.status.206.1" title="206 Partial Content">3.1</a> and <a href="#header.if-range" id="rfc.xref.header.if-range.3" title="If-Range">5.3</a>)
     961         needed headers in a 206 response, this problem can be avoided. (Section <a href="#status.206" id="rfc.xref.status.206.1" title="206 Partial Content">4.1</a> and <a href="#header.if-range" id="rfc.xref.header.if-range.3" title="If-Range">6.3</a>)
    951962      </p>
    952963      <p id="rfc.section.B.1.p.4">Fix problem with unsatisfiable range requests; there are two cases: syntactic problems, and range doesn't exist in the document.
    953964         The 416 status code was needed to resolve this ambiguity needed to indicate an error for a byte range request that falls outside
    954          of the actual contents of a document. (Section <a href="#status.416" id="rfc.xref.status.416.2" title="416 Requested Range Not Satisfiable">3.2</a>, <a href="#header.content-range" id="rfc.xref.header.content-range.6" title="Content-Range">5.2</a>)
     965         of the actual contents of a document. (Section <a href="#status.416" id="rfc.xref.status.416.2" title="416 Requested Range Not Satisfiable">4.2</a>, <a href="#header.content-range" id="rfc.xref.header.content-range.6" title="Content-Range">6.2</a>)
    955966      </p>
    956967      <h2 id="rfc.section.B.2"><a href="#rfc.section.B.2">B.2</a>&nbsp;<a id="changes.from.rfc.2616" href="#changes.from.rfc.2616">Changes from RFC 2616</a></h2>
    957       <p id="rfc.section.B.2.p.1">Clarify that it is not ok to use a weak cache validator in a 206 response. (<a href="#status.206" id="rfc.xref.status.206.2" title="206 Partial Content">Section&nbsp;3.1</a>)
     968      <p id="rfc.section.B.2.p.1">Clarify that it is not ok to use a weak cache validator in a 206 response. (<a href="#status.206" id="rfc.xref.status.206.2" title="206 Partial Content">Section&nbsp;4.1</a>)
    958969      </p>
    959970      <h1 id="rfc.section.C"><a href="#rfc.section.C">C.</a>&nbsp;Change Log (to be removed by RFC Editor before publication)
     
    981992         </li>
    982993      </ul>
     994      <p id="rfc.section.C.3.p.2">Ongoing work on ABNF conversion (&lt;<a href="http://www3.tools.ietf.org/wg/httpbis/trac/ticket/36">http://www3.tools.ietf.org/wg/httpbis/trac/ticket/36</a>&gt;):
     995      </p>
     996      <ul>
     997         <li>Add explicit references to BNF syntax and rules imported from other parts of the specification.</li>
     998      </ul>
    983999      <h1><a id="rfc.copyright" href="#rfc.copyright">Full Copyright Statement</a></h1>
    9841000      <p>Copyright © The IETF Trust (2008).</p>
     
    10141030         <ul class="ind">
    10151031            <li class="indline0"><a id="rfc.index.2" href="#rfc.index.2"><b>2</b></a><ul class="ind">
    1016                   <li class="indline1">206 Partial Content (status code)&nbsp;&nbsp;<a class="iref" href="#rfc.iref.3"><b>3.1</b></a>, <a class="iref" href="#rfc.xref.status.206.1">B.1</a>, <a class="iref" href="#rfc.xref.status.206.2">B.2</a></li>
     1032                  <li class="indline1">206 Partial Content (status code)&nbsp;&nbsp;<a class="iref" href="#rfc.iref.3"><b>4.1</b></a>, <a class="iref" href="#rfc.xref.status.206.1">B.1</a>, <a class="iref" href="#rfc.xref.status.206.2">B.2</a></li>
    10171033               </ul>
    10181034            </li>
    10191035            <li class="indline0"><a id="rfc.index.4" href="#rfc.index.4"><b>4</b></a><ul class="ind">
    1020                   <li class="indline1">416 Requested Range Not Satisfiable (status code)&nbsp;&nbsp;<a class="iref" href="#rfc.iref.4"><b>3.2</b></a>, <a class="iref" href="#rfc.xref.status.416.1">5.2</a>, <a class="iref" href="#rfc.xref.status.416.2">B.1</a></li>
     1036                  <li class="indline1">416 Requested Range Not Satisfiable (status code)&nbsp;&nbsp;<a class="iref" href="#rfc.iref.4"><b>4.2</b></a>, <a class="iref" href="#rfc.xref.status.416.1">6.2</a>, <a class="iref" href="#rfc.xref.status.416.2">B.1</a></li>
    10211037               </ul>
    10221038            </li>
    10231039            <li class="indline0"><a id="rfc.index.A" href="#rfc.index.A"><b>A</b></a><ul class="ind">
    1024                   <li class="indline1">Accept-Ranges header&nbsp;&nbsp;<a class="iref" href="#rfc.iref.a.1"><b>5.1</b></a></li>
     1040                  <li class="indline1">Accept-Ranges header&nbsp;&nbsp;<a class="iref" href="#rfc.iref.a.1"><b>6.1</b></a></li>
    10251041               </ul>
    10261042            </li>
    10271043            <li class="indline0"><a id="rfc.index.C" href="#rfc.index.C"><b>C</b></a><ul class="ind">
    1028                   <li class="indline1">Content-Range header&nbsp;&nbsp;<a class="iref" href="#rfc.xref.header.content-range.1">2</a>, <a class="iref" href="#rfc.xref.header.content-range.2">3.1</a>, <a class="iref" href="#rfc.xref.header.content-range.3">3.2</a>, <a class="iref" href="#rfc.iref.c.1"><b>5.2</b></a>, <a class="iref" href="#rfc.xref.header.content-range.4">B.1</a>, <a class="iref" href="#rfc.xref.header.content-range.5">B.1</a>, <a class="iref" href="#rfc.xref.header.content-range.6">B.1</a></li>
     1044                  <li class="indline1">Content-Range header&nbsp;&nbsp;<a class="iref" href="#rfc.xref.header.content-range.1">3</a>, <a class="iref" href="#rfc.xref.header.content-range.2">4.1</a>, <a class="iref" href="#rfc.xref.header.content-range.3">4.2</a>, <a class="iref" href="#rfc.iref.c.1"><b>6.2</b></a>, <a class="iref" href="#rfc.xref.header.content-range.4">B.1</a>, <a class="iref" href="#rfc.xref.header.content-range.5">B.1</a>, <a class="iref" href="#rfc.xref.header.content-range.6">B.1</a></li>
    10291045               </ul>
    10301046            </li>
     
    10321048                  <li class="indline1"><tt>Grammar</tt>&nbsp;&nbsp;
    10331049                     <ul class="ind">
    1034                         <li class="indline1"><tt>Accept-Ranges</tt>&nbsp;&nbsp;<a class="iref" href="#rfc.iref.g.4"><b>5.1</b></a></li>
    1035                         <li class="indline1"><tt>acceptable-ranges</tt>&nbsp;&nbsp;<a class="iref" href="#rfc.iref.g.5"><b>5.1</b></a></li>
    1036                         <li class="indline1"><tt>byte-content-range-spec</tt>&nbsp;&nbsp;<a class="iref" href="#rfc.iref.g.8"><b>5.2</b></a></li>
    1037                         <li class="indline1"><tt>byte-range-resp-spec</tt>&nbsp;&nbsp;<a class="iref" href="#rfc.iref.g.9"><b>5.2</b></a></li>
    1038                         <li class="indline1"><tt>byte-range-set</tt>&nbsp;&nbsp;<a class="iref" href="#rfc.iref.g.14"><b>5.4.1</b></a></li>
    1039                         <li class="indline1"><tt>byte-range-spec</tt>&nbsp;&nbsp;<a class="iref" href="#rfc.iref.g.15"><b>5.4.1</b></a></li>
    1040                         <li class="indline1"><tt>byte-ranges-specifier</tt>&nbsp;&nbsp;<a class="iref" href="#rfc.iref.g.13"><b>5.4.1</b></a></li>
    1041                         <li class="indline1"><tt>bytes-unit</tt>&nbsp;&nbsp;<a class="iref" href="#rfc.iref.g.2"><b>2</b></a></li>
    1042                         <li class="indline1"><tt>Content-Range</tt>&nbsp;&nbsp;<a class="iref" href="#rfc.iref.g.6"><b>5.2</b></a></li>
    1043                         <li class="indline1"><tt>content-range-spec</tt>&nbsp;&nbsp;<a class="iref" href="#rfc.iref.g.7"><b>5.2</b></a></li>
    1044                         <li class="indline1"><tt>first-byte-pos</tt>&nbsp;&nbsp;<a class="iref" href="#rfc.iref.g.16"><b>5.4.1</b></a></li>
    1045                         <li class="indline1"><tt>If-Range</tt>&nbsp;&nbsp;<a class="iref" href="#rfc.iref.g.11"><b>5.3</b></a></li>
    1046                         <li class="indline1"><tt>instance-length</tt>&nbsp;&nbsp;<a class="iref" href="#rfc.iref.g.10"><b>5.2</b></a></li>
    1047                         <li class="indline1"><tt>last-byte-pos</tt>&nbsp;&nbsp;<a class="iref" href="#rfc.iref.g.17"><b>5.4.1</b></a></li>
    1048                         <li class="indline1"><tt>other-range-unit</tt>&nbsp;&nbsp;<a class="iref" href="#rfc.iref.g.3"><b>2</b></a></li>
    1049                         <li class="indline1"><tt>Range</tt>&nbsp;&nbsp;<a class="iref" href="#rfc.iref.g.20"><b>5.4.2</b></a></li>
    1050                         <li class="indline1"><tt>range-unit</tt>&nbsp;&nbsp;<a class="iref" href="#rfc.iref.g.1"><b>2</b></a></li>
    1051                         <li class="indline1"><tt>ranges-specifier</tt>&nbsp;&nbsp;<a class="iref" href="#rfc.iref.g.12"><b>5.4.1</b></a></li>
    1052                         <li class="indline1"><tt>suffix-byte-range-spec</tt>&nbsp;&nbsp;<a class="iref" href="#rfc.iref.g.18"><b>5.4.1</b></a></li>
    1053                         <li class="indline1"><tt>suffix-length</tt>&nbsp;&nbsp;<a class="iref" href="#rfc.iref.g.19"><b>5.4.1</b></a></li>
     1050                        <li class="indline1"><tt>Accept-Ranges</tt>&nbsp;&nbsp;<a class="iref" href="#rfc.iref.g.4"><b>6.1</b></a></li>
     1051                        <li class="indline1"><tt>acceptable-ranges</tt>&nbsp;&nbsp;<a class="iref" href="#rfc.iref.g.5"><b>6.1</b></a></li>
     1052                        <li class="indline1"><tt>byte-content-range-spec</tt>&nbsp;&nbsp;<a class="iref" href="#rfc.iref.g.8"><b>6.2</b></a></li>
     1053                        <li class="indline1"><tt>byte-range-resp-spec</tt>&nbsp;&nbsp;<a class="iref" href="#rfc.iref.g.9"><b>6.2</b></a></li>
     1054                        <li class="indline1"><tt>byte-range-set</tt>&nbsp;&nbsp;<a class="iref" href="#rfc.iref.g.14"><b>6.4.1</b></a></li>
     1055                        <li class="indline1"><tt>byte-range-spec</tt>&nbsp;&nbsp;<a class="iref" href="#rfc.iref.g.15"><b>6.4.1</b></a></li>
     1056                        <li class="indline1"><tt>byte-ranges-specifier</tt>&nbsp;&nbsp;<a class="iref" href="#rfc.iref.g.13"><b>6.4.1</b></a></li>
     1057                        <li class="indline1"><tt>bytes-unit</tt>&nbsp;&nbsp;<a class="iref" href="#rfc.iref.g.2"><b>3</b></a></li>
     1058                        <li class="indline1"><tt>Content-Range</tt>&nbsp;&nbsp;<a class="iref" href="#rfc.iref.g.6"><b>6.2</b></a></li>
     1059                        <li class="indline1"><tt>content-range-spec</tt>&nbsp;&nbsp;<a class="iref" href="#rfc.iref.g.7"><b>6.2</b></a></li>
     1060                        <li class="indline1"><tt>first-byte-pos</tt>&nbsp;&nbsp;<a class="iref" href="#rfc.iref.g.16"><b>6.4.1</b></a></li>
     1061                        <li class="indline1"><tt>If-Range</tt>&nbsp;&nbsp;<a class="iref" href="#rfc.iref.g.11"><b>6.3</b></a></li>
     1062                        <li class="indline1"><tt>instance-length</tt>&nbsp;&nbsp;<a class="iref" href="#rfc.iref.g.10"><b>6.2</b></a></li>
     1063                        <li class="indline1"><tt>last-byte-pos</tt>&nbsp;&nbsp;<a class="iref" href="#rfc.iref.g.17"><b>6.4.1</b></a></li>
     1064                        <li class="indline1"><tt>other-range-unit</tt>&nbsp;&nbsp;<a class="iref" href="#rfc.iref.g.3"><b>3</b></a></li>
     1065                        <li class="indline1"><tt>Range</tt>&nbsp;&nbsp;<a class="iref" href="#rfc.iref.g.20"><b>6.4.2</b></a></li>
     1066                        <li class="indline1"><tt>range-unit</tt>&nbsp;&nbsp;<a class="iref" href="#rfc.iref.g.1"><b>3</b></a></li>
     1067                        <li class="indline1"><tt>ranges-specifier</tt>&nbsp;&nbsp;<a class="iref" href="#rfc.iref.g.12"><b>6.4.1</b></a></li>
     1068                        <li class="indline1"><tt>suffix-byte-range-spec</tt>&nbsp;&nbsp;<a class="iref" href="#rfc.iref.g.18"><b>6.4.1</b></a></li>
     1069                        <li class="indline1"><tt>suffix-length</tt>&nbsp;&nbsp;<a class="iref" href="#rfc.iref.g.19"><b>6.4.1</b></a></li>
    10541070                     </ul>
    10551071                  </li>
     
    10591075                  <li class="indline1">Headers&nbsp;&nbsp;
    10601076                     <ul class="ind">
    1061                         <li class="indline1">Accept-Ranges&nbsp;&nbsp;<a class="iref" href="#rfc.iref.h.1"><b>5.1</b></a></li>
    1062                         <li class="indline1">Content-Range&nbsp;&nbsp;<a class="iref" href="#rfc.xref.header.content-range.1">2</a>, <a class="iref" href="#rfc.xref.header.content-range.2">3.1</a>, <a class="iref" href="#rfc.xref.header.content-range.3">3.2</a>, <a class="iref" href="#rfc.iref.h.2"><b>5.2</b></a>, <a class="iref" href="#rfc.xref.header.content-range.4">B.1</a>, <a class="iref" href="#rfc.xref.header.content-range.5">B.1</a>, <a class="iref" href="#rfc.xref.header.content-range.6">B.1</a></li>
    1063                         <li class="indline1">If-Range&nbsp;&nbsp;<a class="iref" href="#rfc.xref.header.if-range.1">3.1</a>, <a class="iref" href="#rfc.iref.h.3"><b>5.3</b></a>, <a class="iref" href="#rfc.xref.header.if-range.2">5.4.2</a>, <a class="iref" href="#rfc.xref.header.if-range.3">B.1</a></li>
    1064                         <li class="indline1">Range&nbsp;&nbsp;<a class="iref" href="#rfc.xref.header.range.1">2</a>, <a class="iref" href="#rfc.xref.header.range.2">3.1</a>, <a class="iref" href="#rfc.xref.header.range.3">3.2</a>, <a class="iref" href="#rfc.iref.h.4"><b>5.4</b></a></li>
     1077                        <li class="indline1">Accept-Ranges&nbsp;&nbsp;<a class="iref" href="#rfc.iref.h.1"><b>6.1</b></a></li>
     1078                        <li class="indline1">Content-Range&nbsp;&nbsp;<a class="iref" href="#rfc.xref.header.content-range.1">3</a>, <a class="iref" href="#rfc.xref.header.content-range.2">4.1</a>, <a class="iref" href="#rfc.xref.header.content-range.3">4.2</a>, <a class="iref" href="#rfc.iref.h.2"><b>6.2</b></a>, <a class="iref" href="#rfc.xref.header.content-range.4">B.1</a>, <a class="iref" href="#rfc.xref.header.content-range.5">B.1</a>, <a class="iref" href="#rfc.xref.header.content-range.6">B.1</a></li>
     1079                        <li class="indline1">If-Range&nbsp;&nbsp;<a class="iref" href="#rfc.xref.header.if-range.1">4.1</a>, <a class="iref" href="#rfc.iref.h.3"><b>6.3</b></a>, <a class="iref" href="#rfc.xref.header.if-range.2">6.4.2</a>, <a class="iref" href="#rfc.xref.header.if-range.3">B.1</a></li>
     1080                        <li class="indline1">Range&nbsp;&nbsp;<a class="iref" href="#rfc.xref.header.range.1">3</a>, <a class="iref" href="#rfc.xref.header.range.2">4.1</a>, <a class="iref" href="#rfc.xref.header.range.3">4.2</a>, <a class="iref" href="#rfc.iref.h.4"><b>6.4</b></a></li>
    10651081                     </ul>
    10661082                  </li>
     
    10681084            </li>
    10691085            <li class="indline0"><a id="rfc.index.I" href="#rfc.index.I"><b>I</b></a><ul class="ind">
    1070                   <li class="indline1">If-Range header&nbsp;&nbsp;<a class="iref" href="#rfc.xref.header.if-range.1">3.1</a>, <a class="iref" href="#rfc.iref.i.1"><b>5.3</b></a>, <a class="iref" href="#rfc.xref.header.if-range.2">5.4.2</a>, <a class="iref" href="#rfc.xref.header.if-range.3">B.1</a></li>
     1086                  <li class="indline1">If-Range header&nbsp;&nbsp;<a class="iref" href="#rfc.xref.header.if-range.1">4.1</a>, <a class="iref" href="#rfc.iref.i.1"><b>6.3</b></a>, <a class="iref" href="#rfc.xref.header.if-range.2">6.4.2</a>, <a class="iref" href="#rfc.xref.header.if-range.3">B.1</a></li>
    10711087               </ul>
    10721088            </li>
     
    10831099            </li>
    10841100            <li class="indline0"><a id="rfc.index.P" href="#rfc.index.P"><b>P</b></a><ul class="ind">
    1085                   <li class="indline1"><em>Part1</em>&nbsp;&nbsp;<a class="iref" href="#rfc.xref.Part1.1">7</a>, <a class="iref" href="#Part1"><b>9.1</b></a>, <a class="iref" href="#rfc.xref.Part1.2">B.1</a></li>
    1086                   <li class="indline1"><em>Part3</em>&nbsp;&nbsp;<a class="iref" href="#Part3"><b>9.1</b></a>, <a class="iref" href="#rfc.xref.Part3.1">B.1</a></li>
    1087                   <li class="indline1"><em>Part4</em>&nbsp;&nbsp;<a class="iref" href="#rfc.xref.Part4.1">4</a>, <a class="iref" href="#Part4"><b>9.1</b></a><ul class="ind">
    1088                         <li class="indline1"><em>Section 4</em>&nbsp;&nbsp;<a class="iref" href="#rfc.xref.Part4.1">4</a></li>
     1101                  <li class="indline1"><em>Part1</em>&nbsp;&nbsp;<a class="iref" href="#rfc.xref.Part1.1">2</a>, <a class="iref" href="#rfc.xref.Part1.2">2</a>, <a class="iref" href="#rfc.xref.Part1.3">2</a>, <a class="iref" href="#rfc.xref.Part1.4">2</a>, <a class="iref" href="#rfc.xref.Part1.5">2</a>, <a class="iref" href="#rfc.xref.Part1.6">2</a>, <a class="iref" href="#rfc.xref.Part1.7">8</a>, <a class="iref" href="#Part1"><b>10.1</b></a>, <a class="iref" href="#rfc.xref.Part1.8">B.1</a><ul class="ind">
     1102                        <li class="indline1"><em>Section 2.1</em>&nbsp;&nbsp;<a class="iref" href="#rfc.xref.Part1.1">2</a></li>
     1103                        <li class="indline1"><em>Section 2.2</em>&nbsp;&nbsp;<a class="iref" href="#rfc.xref.Part1.2">2</a>, <a class="iref" href="#rfc.xref.Part1.3">2</a>, <a class="iref" href="#rfc.xref.Part1.4">2</a>, <a class="iref" href="#rfc.xref.Part1.5">2</a></li>
     1104                        <li class="indline1"><em>Section 3.3.1</em>&nbsp;&nbsp;<a class="iref" href="#rfc.xref.Part1.6">2</a></li>
    10891105                     </ul>
    10901106                  </li>
    1091                   <li class="indline1"><em>Part6</em>&nbsp;&nbsp;<a class="iref" href="#Part6"><b>9.1</b></a>, <a class="iref" href="#rfc.xref.Part6.1">B.1</a></li>
     1107                  <li class="indline1"><em>Part3</em>&nbsp;&nbsp;<a class="iref" href="#Part3"><b>10.1</b></a>, <a class="iref" href="#rfc.xref.Part3.1">B.1</a></li>
     1108                  <li class="indline1"><em>Part4</em>&nbsp;&nbsp;<a class="iref" href="#rfc.xref.Part4.1">2</a>, <a class="iref" href="#rfc.xref.Part4.2">5</a>, <a class="iref" href="#Part4"><b>10.1</b></a><ul class="ind">
     1109                        <li class="indline1"><em>Section 3</em>&nbsp;&nbsp;<a class="iref" href="#rfc.xref.Part4.1">2</a></li>
     1110                        <li class="indline1"><em>Section 5</em>&nbsp;&nbsp;<a class="iref" href="#rfc.xref.Part4.2">5</a></li>
     1111                     </ul>
     1112                  </li>
     1113                  <li class="indline1"><em>Part6</em>&nbsp;&nbsp;<a class="iref" href="#Part6"><b>10.1</b></a>, <a class="iref" href="#rfc.xref.Part6.1">B.1</a></li>
    10921114               </ul>
    10931115            </li>
    10941116            <li class="indline0"><a id="rfc.index.R" href="#rfc.index.R"><b>R</b></a><ul class="ind">
    1095                   <li class="indline1">Range header&nbsp;&nbsp;<a class="iref" href="#rfc.xref.header.range.1">2</a>, <a class="iref" href="#rfc.xref.header.range.2">3.1</a>, <a class="iref" href="#rfc.xref.header.range.3">3.2</a>, <a class="iref" href="#rfc.iref.r.1"><b>5.4</b></a></li>
    1096                   <li class="indline1"><em>RFC2046</em>&nbsp;&nbsp;<a class="iref" href="#RFC2046"><b>9.1</b></a>, <a class="iref" href="#rfc.xref.RFC2046.1">A</a>, <a class="iref" href="#rfc.xref.RFC2046.2">A</a></li>
    1097                   <li class="indline1"><em>RFC2119</em>&nbsp;&nbsp;<a class="iref" href="#rfc.xref.RFC2119.1">1.1</a>, <a class="iref" href="#RFC2119"><b>9.1</b></a></li>
    1098                   <li class="indline1"><em>RFC2616</em>&nbsp;&nbsp;<a class="iref" href="#RFC2616"><b>9.2</b></a>, <a class="iref" href="#rfc.xref.RFC2616.1">C.1</a></li>
    1099                   <li class="indline1"><em>RFC4288</em>&nbsp;&nbsp;<a class="iref" href="#RFC4288"><b>9.2</b></a>, <a class="iref" href="#rfc.xref.RFC4288.1">A</a></li>
     1117                  <li class="indline1">Range header&nbsp;&nbsp;<a class="iref" href="#rfc.xref.header.range.1">3</a>, <a class="iref" href="#rfc.xref.header.range.2">4.1</a>, <a class="iref" href="#rfc.xref.header.range.3">4.2</a>, <a class="iref" href="#rfc.iref.r.1"><b>6.4</b></a></li>
     1118                  <li class="indline1"><em>RFC2046</em>&nbsp;&nbsp;<a class="iref" href="#RFC2046"><b>10.1</b></a>, <a class="iref" href="#rfc.xref.RFC2046.1">A</a>, <a class="iref" href="#rfc.xref.RFC2046.2">A</a></li>
     1119                  <li class="indline1"><em>RFC2119</em>&nbsp;&nbsp;<a class="iref" href="#rfc.xref.RFC2119.1">1.1</a>, <a class="iref" href="#RFC2119"><b>10.1</b></a></li>
     1120                  <li class="indline1"><em>RFC2616</em>&nbsp;&nbsp;<a class="iref" href="#RFC2616"><b>10.2</b></a>, <a class="iref" href="#rfc.xref.RFC2616.1">C.1</a></li>
     1121                  <li class="indline1"><em>RFC4288</em>&nbsp;&nbsp;<a class="iref" href="#RFC4288"><b>10.2</b></a>, <a class="iref" href="#rfc.xref.RFC4288.1">A</a></li>
    11001122               </ul>
    11011123            </li>
     
    11031125                  <li class="indline1">Status Codes&nbsp;&nbsp;
    11041126                     <ul class="ind">
    1105                         <li class="indline1">206 Partial Content&nbsp;&nbsp;<a class="iref" href="#rfc.iref.s.1"><b>3.1</b></a>, <a class="iref" href="#rfc.xref.status.206.1">B.1</a>, <a class="iref" href="#rfc.xref.status.206.2">B.2</a></li>
    1106                         <li class="indline1">416 Requested Range Not Satisfiable&nbsp;&nbsp;<a class="iref" href="#rfc.iref.s.2"><b>3.2</b></a>, <a class="iref" href="#rfc.xref.status.416.1">5.2</a>, <a class="iref" href="#rfc.xref.status.416.2">B.1</a></li>
     1127                        <li class="indline1">206 Partial Content&nbsp;&nbsp;<a class="iref" href="#rfc.iref.s.1"><b>4.1</b></a>, <a class="iref" href="#rfc.xref.status.206.1">B.1</a>, <a class="iref" href="#rfc.xref.status.206.2">B.2</a></li>
     1128                        <li class="indline1">416 Requested Range Not Satisfiable&nbsp;&nbsp;<a class="iref" href="#rfc.iref.s.2"><b>4.2</b></a>, <a class="iref" href="#rfc.xref.status.416.1">6.2</a>, <a class="iref" href="#rfc.xref.status.416.2">B.1</a></li>
    11071129                     </ul>
    11081130                  </li>
Note: See TracChangeset for help on using the changeset viewer.