Changeset 424 for draft-ietf-httpbis/latest/p5-range.html
- Timestamp:
- 21/11/08 17:39:20 (13 years ago)
- File:
-
- 1 edited
Legend:
- Unmodified
- Added
- Removed
-
draft-ietf-httpbis/latest/p5-range.html
r421 r424 365 365 <link rel="Index" href="#rfc.index"> 366 366 <link rel="Chapter" title="1 Introduction" href="#rfc.section.1"> 367 <link rel="Chapter" title="2 Notational Conventions and Generic Grammar" href="#rfc.section.2"> 368 <link rel="Chapter" title="3 Range Units" href="#rfc.section.3"> 369 <link rel="Chapter" title="4 Status Code Definitions" href="#rfc.section.4"> 370 <link rel="Chapter" title="5 Combining Ranges" href="#rfc.section.5"> 371 <link rel="Chapter" title="6 Header Field Definitions" href="#rfc.section.6"> 372 <link rel="Chapter" title="7 IANA Considerations" href="#rfc.section.7"> 373 <link rel="Chapter" title="8 Security Considerations" href="#rfc.section.8"> 374 <link rel="Chapter" title="9 Acknowledgments" href="#rfc.section.9"> 375 <link rel="Chapter" href="#rfc.section.10" title="10 References"> 367 <link rel="Chapter" title="2 Range Units" href="#rfc.section.2"> 368 <link rel="Chapter" title="3 Status Code Definitions" href="#rfc.section.3"> 369 <link rel="Chapter" title="4 Combining Ranges" href="#rfc.section.4"> 370 <link rel="Chapter" title="5 Header Field Definitions" href="#rfc.section.5"> 371 <link rel="Chapter" title="6 IANA Considerations" href="#rfc.section.6"> 372 <link rel="Chapter" title="7 Security Considerations" href="#rfc.section.7"> 373 <link rel="Chapter" title="8 Acknowledgments" href="#rfc.section.8"> 374 <link rel="Chapter" href="#rfc.section.9" title="9 References"> 376 375 <link rel="Appendix" title="A Internet Media Type multipart/byteranges" href="#rfc.section.A"> 377 376 <link rel="Appendix" title="B Compatibility with Previous Versions" href="#rfc.section.B"> … … 512 511 <li class="tocline0">1. <a href="#introduction">Introduction</a><ul class="toc"> 513 512 <li class="tocline1">1.1 <a href="#intro.requirements">Requirements</a></li> 514 </ul> 515 </li> 516 <li class="tocline0">2. <a href="#notation">Notational Conventions and Generic Grammar</a></li> 517 <li class="tocline0">3. <a href="#range.units">Range Units</a></li> 518 <li class="tocline0">4. <a href="#rfc.section.4">Status Code Definitions</a><ul class="toc"> 519 <li class="tocline1">4.1 <a href="#status.206">206 Partial Content</a></li> 520 <li class="tocline1">4.2 <a href="#status.416">416 Requested Range Not Satisfiable</a></li> 521 </ul> 522 </li> 523 <li class="tocline0">5. <a href="#combining.byte.ranges">Combining Ranges</a></li> 524 <li class="tocline0">6. <a href="#header.fields">Header Field Definitions</a><ul class="toc"> 525 <li class="tocline1">6.1 <a href="#header.accept-ranges">Accept-Ranges</a></li> 526 <li class="tocline1">6.2 <a href="#header.content-range">Content-Range</a></li> 527 <li class="tocline1">6.3 <a href="#header.if-range">If-Range</a></li> 528 <li class="tocline1">6.4 <a href="#header.range">Range</a><ul class="toc"> 529 <li class="tocline1">6.4.1 <a href="#byte.ranges">Byte Ranges</a></li> 530 <li class="tocline1">6.4.2 <a href="#range.retrieval.requests">Range Retrieval Requests</a></li> 513 <li class="tocline1">1.2 <a href="#notation">Syntax Notation</a><ul class="toc"> 514 <li class="tocline1">1.2.1 <a href="#core.rules">Core Rules</a></li> 515 <li class="tocline1">1.2.2 <a href="#abnf.dependencies">ABNF Rules defined in other Parts of the Specification</a></li> 531 516 </ul> 532 517 </li> 533 518 </ul> 534 519 </li> 535 <li class="tocline0">7. <a href="#IANA.considerations">IANA Considerations</a><ul class="toc"> 536 <li class="tocline1">7.1 <a href="#message.header.registration">Message Header Registration</a></li> 520 <li class="tocline0">2. <a href="#range.units">Range Units</a></li> 521 <li class="tocline0">3. <a href="#rfc.section.3">Status Code Definitions</a><ul class="toc"> 522 <li class="tocline1">3.1 <a href="#status.206">206 Partial Content</a></li> 523 <li class="tocline1">3.2 <a href="#status.416">416 Requested Range Not Satisfiable</a></li> 537 524 </ul> 538 525 </li> 539 <li class="tocline0">8. <a href="#security.considerations">Security Considerations</a></li> 540 <li class="tocline0">9. <a href="#ack">Acknowledgments</a></li> 541 <li class="tocline0">10. <a href="#rfc.references">References</a><ul class="toc"> 542 <li class="tocline1">10.1 <a href="#rfc.references.1">Normative References</a></li> 543 <li class="tocline1">10.2 <a href="#rfc.references.2">Informative References</a></li> 526 <li class="tocline0">4. <a href="#combining.byte.ranges">Combining Ranges</a></li> 527 <li class="tocline0">5. <a href="#header.fields">Header Field Definitions</a><ul class="toc"> 528 <li class="tocline1">5.1 <a href="#header.accept-ranges">Accept-Ranges</a></li> 529 <li class="tocline1">5.2 <a href="#header.content-range">Content-Range</a></li> 530 <li class="tocline1">5.3 <a href="#header.if-range">If-Range</a></li> 531 <li class="tocline1">5.4 <a href="#header.range">Range</a><ul class="toc"> 532 <li class="tocline1">5.4.1 <a href="#byte.ranges">Byte Ranges</a></li> 533 <li class="tocline1">5.4.2 <a href="#range.retrieval.requests">Range Retrieval Requests</a></li> 534 </ul> 535 </li> 536 </ul> 537 </li> 538 <li class="tocline0">6. <a href="#IANA.considerations">IANA Considerations</a><ul class="toc"> 539 <li class="tocline1">6.1 <a href="#message.header.registration">Message Header Registration</a></li> 540 </ul> 541 </li> 542 <li class="tocline0">7. <a href="#security.considerations">Security Considerations</a></li> 543 <li class="tocline0">8. <a href="#ack">Acknowledgments</a></li> 544 <li class="tocline0">9. <a href="#rfc.references">References</a><ul class="toc"> 545 <li class="tocline1">9.1 <a href="#rfc.references.1">Normative References</a></li> 546 <li class="tocline1">9.2 <a href="#rfc.references.2">Informative References</a></li> 544 547 </ul> 545 548 </li> … … 586 589 <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." 587 590 </p> 588 <h1 id="rfc.section.2"><a href="#rfc.section.2">2.</a> <a id="notation" href="#notation">Notational Conventions and Generic Grammar</a></h1> 589 <p id="rfc.section.2.p.1">This specification uses the ABNF syntax defined in <a href="p1-messaging.html#notation.abnf" title="ABNF Extension: #rule">Section 1.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 1.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>: 590 </p> 591 <div id="rfc.figure.u.1"></div><pre class="inline"> <a href="#notation" class="smpl">CHAR</a> = <CHAR, 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 1.2.2</a>> 592 <a href="#notation" class="smpl">DIGIT</a> = <DIGIT, 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 1.2.2</a>> 593 <a href="#notation" class="smpl">SP</a> = <SP, 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 1.2.2</a>> 594 </pre><div id="rfc.figure.u.2"></div><pre class="inline"> <a href="#notation" class="smpl">token</a> = <token, 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#basic.rules" title="Basic Rules">Section 1.2.2</a>> 595 <a href="#notation" class="smpl">OWS</a> = <OWS, defined in <a href="#Part1" id="rfc.xref.Part1.7"><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 1.2.2</a>> 596 </pre><div id="abnf.dependencies"> 597 <p id="rfc.section.2.p.4"> The ABNF rules below are defined in other parts:</p> 598 </div> 591 <h2 id="rfc.section.1.2"><a href="#rfc.section.1.2">1.2</a> <a id="notation" href="#notation">Syntax Notation</a></h2> 592 <p id="rfc.section.1.2.p.1">This specification uses the ABNF syntax defined in <a href="p1-messaging.html#notation" title="Syntax Notation">Section 1.2</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>. 593 </p> 594 <h3 id="rfc.section.1.2.1"><a href="#rfc.section.1.2.1">1.2.1</a> <a id="core.rules" href="#core.rules">Core Rules</a></h3> 595 <p id="rfc.section.1.2.1.p.1">The core rules below are defined in <a href="p1-messaging.html#basic.rules" title="Basic Rules">Section 1.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>: 596 </p> 597 <div id="rfc.figure.u.1"></div><pre class="inline"> <a href="#core.rules" class="smpl">CHAR</a> = <CHAR, 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 1.2.2</a>> 598 <a href="#core.rules" class="smpl">DIGIT</a> = <DIGIT, 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 1.2.2</a>> 599 <a href="#core.rules" class="smpl">SP</a> = <SP, 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 1.2.2</a>> 600 </pre><div id="rfc.figure.u.2"></div><pre class="inline"> <a href="#core.rules" class="smpl">token</a> = <token, 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#basic.rules" title="Basic Rules">Section 1.2.2</a>> 601 <a href="#core.rules" class="smpl">OWS</a> = <OWS, defined in <a href="#Part1" id="rfc.xref.Part1.7"><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 1.2.2</a>> 602 </pre><h3 id="rfc.section.1.2.2"><a href="#rfc.section.1.2.2">1.2.2</a> <a id="abnf.dependencies" href="#abnf.dependencies">ABNF Rules defined in other Parts of the Specification</a></h3> 603 <p id="rfc.section.1.2.2.p.1">The ABNF rules below are defined in other parts:</p> 599 604 <div id="rfc.figure.u.3"></div><pre class="inline"> <a href="#abnf.dependencies" class="smpl">HTTP-date</a> = <HTTP-date, defined in <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="p1-messaging.html#full.date" title="Full Date">Section 3.2.1</a>> 600 </pre><div id="rfc.figure.u.4"></div><pre class="inline"> <a href="#abnf.dependencies" class="smpl">entity-tag</a> = <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>>601 </pre><h1 id="rfc.section. 3"><a href="#rfc.section.3">3.</a> <a id="range.units" href="#range.units">Range Units</a></h1>602 <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.1603 uses range units in the Range (<a href="#header.range" id="rfc.xref.header.range.1" title="Range">Section 6.4</a>) and Content-Range (<a href="#header.content-range" id="rfc.xref.header.content-range.1" title="Content-Range">Section 6.2</a>) header fields. An entity can be broken down into subranges according to various structural units.605 </pre><div id="rfc.figure.u.4"></div><pre class="inline"> <a href="#abnf.dependencies" class="smpl">entity-tag</a> = <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 2</a>> 606 </pre><h1 id="rfc.section.2"><a href="#rfc.section.2">2.</a> <a id="range.units" href="#range.units">Range Units</a></h1> 607 <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 608 uses range units in the Range (<a href="#header.range" id="rfc.xref.header.range.1" title="Range">Section 5.4</a>) and Content-Range (<a href="#header.content-range" id="rfc.xref.header.content-range.1" title="Content-Range">Section 5.2</a>) header fields. An entity can be broken down into subranges according to various structural units. 604 609 </p> 605 610 <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> <a href="#range.units" class="smpl">range-unit</a> = <a href="#range.units" class="smpl">bytes-unit</a> / <a href="#range.units" class="smpl">other-range-unit</a> 606 611 <a href="#range.units" class="smpl">bytes-unit</a> = "bytes" 607 <a href="#range.units" class="smpl">other-range-unit</a> = <a href="# notation" class="smpl">token</a>608 </pre><p id="rfc.section. 3.p.3">HTTP/1.1 has been designed to allow implementations of applications that do not depend on knowledge of ranges. The only range612 <a href="#range.units" class="smpl">other-range-unit</a> = <a href="#core.rules" class="smpl">token</a> 613 </pre><p id="rfc.section.2.p.3">HTTP/1.1 has been designed to allow implementations of applications that do not depend on knowledge of ranges. The only range 609 614 unit defined by HTTP/1.1 is "bytes". 610 615 </p> 611 <p id="rfc.section. 3.p.4">If a range unit is not understood in a request, a server <em class="bcp14">MUST</em> ignore the whole Range header (<a href="#header.range" id="rfc.xref.header.range.2" title="Range">Section 6.4</a>). If a range unit is not understood in a response, an intermediary <em class="bcp14">SHOULD</em> pass the response to the client; a client <em class="bcp14">MUST</em> fail.612 </p> 613 <h1 id="rfc.section. 4"><a href="#rfc.section.4">4.</a> Status Code Definitions616 <p id="rfc.section.2.p.4">If a range unit is not understood in a request, a server <em class="bcp14">MUST</em> ignore the whole Range header (<a href="#header.range" id="rfc.xref.header.range.2" title="Range">Section 5.4</a>). If a range unit is not understood in a response, an intermediary <em class="bcp14">SHOULD</em> pass the response to the client; a client <em class="bcp14">MUST</em> fail. 617 </p> 618 <h1 id="rfc.section.3"><a href="#rfc.section.3">3.</a> Status Code Definitions 614 619 </h1> 615 620 <div id="rfc.iref.3"></div> 616 621 <div id="rfc.iref.s.1"></div> 617 <h2 id="rfc.section. 4.1"><a href="#rfc.section.4.1">4.1</a> <a id="status.206" href="#status.206">206 Partial Content</a></h2>618 <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.3" title="Range">Section 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 6.3</a>) to make the request conditional.619 </p> 620 <p id="rfc.section. 4.1.p.2">The response <em class="bcp14">MUST</em> include the following header fields:622 <h2 id="rfc.section.3.1"><a href="#rfc.section.3.1">3.1</a> <a id="status.206" href="#status.206">206 Partial Content</a></h2> 623 <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.3" title="Range">Section 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 5.3</a>) to make the request conditional. 624 </p> 625 <p id="rfc.section.3.1.p.2">The response <em class="bcp14">MUST</em> include the following header fields: 621 626 </p> 622 627 <ul> 623 <li>Either a Content-Range header field (<a href="#header.content-range" id="rfc.xref.header.content-range.2" title="Content-Range">Section 6.2</a>) indicating the range included with this response, or a multipart/byteranges Content-Type including Content-Range fields628 <li>Either a Content-Range header field (<a href="#header.content-range" id="rfc.xref.header.content-range.2" title="Content-Range">Section 5.2</a>) indicating the range included with this response, or a multipart/byteranges Content-Type including Content-Range fields 624 629 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. 625 630 </li> … … 630 635 </li> 631 636 </ul> 632 <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.633 </p> 634 <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 Ranges">Section 5</a>.635 </p> 636 <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. Furthermore, if a response uses a range unit that is not understood by the cache, then637 <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. 638 </p> 639 <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 Ranges">Section 4</a>. 640 </p> 641 <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. Furthermore, if a response uses a range unit that is not understood by the cache, then 637 642 it <em class="bcp14">MUST NOT</em> be cached either. 638 643 </p> 639 644 <div id="rfc.iref.4"></div> 640 645 <div id="rfc.iref.s.2"></div> 641 <h2 id="rfc.section. 4.2"><a href="#rfc.section.4.2">4.2</a> <a id="status.416" href="#status.416">416 Requested Range Not Satisfiable</a></h2>642 <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.4" title="Range">Section 6.4</a>), and none of the ranges-specifier values in this field overlap the current extent of the selected resource, and the request646 <h2 id="rfc.section.3.2"><a href="#rfc.section.3.2">3.2</a> <a id="status.416" href="#status.416">416 Requested Range Not Satisfiable</a></h2> 647 <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.4" title="Range">Section 5.4</a>), and none of the ranges-specifier values in this field overlap the current extent of the selected resource, and the request 643 648 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 644 649 values were greater than the current length of the selected resource.) 645 650 </p> 646 <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 6.2</a>). This response <em class="bcp14">MUST NOT</em> use the multipart/byteranges content-type.647 </p> 648 <h1 id="rfc.section. 5"><a href="#rfc.section.5">5.</a> <a id="combining.byte.ranges" href="#combining.byte.ranges">Combining Ranges</a></h1>649 <p id="rfc.section. 5.p.1">A response might transfer only a subrange of an entity-body, either the request included one or more Range specifications,651 <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 5.2</a>). This response <em class="bcp14">MUST NOT</em> use the multipart/byteranges content-type. 652 </p> 653 <h1 id="rfc.section.4"><a href="#rfc.section.4">4.</a> <a id="combining.byte.ranges" href="#combining.byte.ranges">Combining Ranges</a></h1> 654 <p id="rfc.section.4.p.1">A response might transfer only a subrange of an entity-body, either the request included one or more Range specifications, 650 655 or because a connection was broken prematurely. After several such transfers, a cache might have received several ranges of 651 656 the same entity-body. 652 657 </p> 653 <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, the658 <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 654 659 cache <em class="bcp14">MAY</em> combine the new subrange with the existing set if both the following conditions are met: 655 660 </p> 656 661 <ul> 657 662 <li>Both the incoming response and the cache entry have a cache validator.</li> 658 <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>).663 <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.2"><cite title="HTTP/1.1, part 4: Conditional Requests">[Part4]</cite></a>). 659 664 </li> 660 665 </ul> 661 <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 incoming666 <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 662 667 response if these values are equal or missing), and <em class="bcp14">MUST</em> discard the other partial information. 663 668 </p> 664 <h1 id="rfc.section. 6"><a href="#rfc.section.6">6.</a> <a id="header.fields" href="#header.fields">Header Field Definitions</a></h1>665 <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>666 <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 who669 <h1 id="rfc.section.5"><a href="#rfc.section.5">5.</a> <a id="header.fields" href="#header.fields">Header Field Definitions</a></h1> 670 <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> 671 <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 667 672 receives the entity. 668 673 </p> 669 674 <div id="rfc.iref.a.1"></div> 670 675 <div id="rfc.iref.h.1"></div> 671 <h2 id="rfc.section. 6.1"><a href="#rfc.section.6.1">6.1</a> <a id="header.accept-ranges" href="#header.accept-ranges">Accept-Ranges</a></h2>672 <p id="rfc.section. 6.1.p.1">The response-header "Accept-Ranges" field allows the server to indicate its acceptance of range requests for a resource:</p>673 <div id="rfc.figure.u.6"></div><pre class="inline"><span id="rfc.iref.g.4"></span><span id="rfc.iref.g.5"></span><span id="rfc.iref.g.6"></span> <a href="#header.accept-ranges" class="smpl">Accept-Ranges</a> = "Accept-Ranges" ":" <a href="# notation" class="smpl">OWS</a> <a href="#header.accept-ranges" class="smpl">Accept-Ranges-v</a>676 <h2 id="rfc.section.5.1"><a href="#rfc.section.5.1">5.1</a> <a id="header.accept-ranges" href="#header.accept-ranges">Accept-Ranges</a></h2> 677 <p id="rfc.section.5.1.p.1">The response-header "Accept-Ranges" field allows the server to indicate its acceptance of range requests for a resource:</p> 678 <div id="rfc.figure.u.6"></div><pre class="inline"><span id="rfc.iref.g.4"></span><span id="rfc.iref.g.5"></span><span id="rfc.iref.g.6"></span> <a href="#header.accept-ranges" class="smpl">Accept-Ranges</a> = "Accept-Ranges" ":" <a href="#core.rules" class="smpl">OWS</a> <a href="#header.accept-ranges" class="smpl">Accept-Ranges-v</a> 674 679 <a href="#header.accept-ranges" class="smpl">Accept-Ranges-v</a> = <a href="#header.accept-ranges" class="smpl">acceptable-ranges</a> 675 680 <a href="#header.accept-ranges" class="smpl">acceptable-ranges</a> = 1#<a href="#range.units" class="smpl">range-unit</a> / "none" 676 </pre><p id="rfc.section. 6.1.p.3">Origin servers that accept byte-range requests <em class="bcp14">MAY</em> send681 </pre><p id="rfc.section.5.1.p.3">Origin servers that accept byte-range requests <em class="bcp14">MAY</em> send 677 682 </p> 678 683 <div id="rfc.figure.u.7"></div><pre class="text"> Accept-Ranges: bytes 679 </pre><p id="rfc.section. 6.1.p.5">but are not required to do so. Clients <em class="bcp14">MAY</em> generate range requests without having received this header for the resource involved. Range units are defined in <a href="#range.units" title="Range Units">Section 3</a>.680 </p> 681 <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> send684 </pre><p id="rfc.section.5.1.p.5">but are not required to do so. Clients <em class="bcp14">MAY</em> generate range requests without having received this header for the resource involved. Range units are defined in <a href="#range.units" title="Range Units">Section 2</a>. 685 </p> 686 <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 682 687 </p> 683 688 <div id="rfc.figure.u.8"></div><pre class="text"> Accept-Ranges: none 684 </pre><p id="rfc.section. 6.1.p.8">to advise the client not to attempt a range request.</p>689 </pre><p id="rfc.section.5.1.p.8">to advise the client not to attempt a range request.</p> 685 690 <div id="rfc.iref.c.1"></div> 686 691 <div id="rfc.iref.h.2"></div> 687 <h2 id="rfc.section. 6.2"><a href="#rfc.section.6.2">6.2</a> <a id="header.content-range" href="#header.content-range">Content-Range</a></h2>688 <p id="rfc.section. 6.2.p.1">The entity-header "Content-Range" is sent with a partial entity-body to specify where in the full entity-body the partial689 body should be applied. Range units are defined in <a href="#range.units" title="Range Units">Section 3</a>.690 </p> 691 <div id="rfc.figure.u.9"></div><pre class="inline"><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><span id="rfc.iref.g.11"></span><span id="rfc.iref.g.12"></span> <a href="#header.content-range" class="smpl">Content-Range</a> = "Content-Range" ":" <a href="# notation" class="smpl">OWS</a> <a href="#header.content-range" class="smpl">Content-Range-v</a>692 <h2 id="rfc.section.5.2"><a href="#rfc.section.5.2">5.2</a> <a id="header.content-range" href="#header.content-range">Content-Range</a></h2> 693 <p id="rfc.section.5.2.p.1">The entity-header "Content-Range" is sent with a partial entity-body to specify where in the full entity-body the partial 694 body should be applied. Range units are defined in <a href="#range.units" title="Range Units">Section 2</a>. 695 </p> 696 <div id="rfc.figure.u.9"></div><pre class="inline"><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><span id="rfc.iref.g.11"></span><span id="rfc.iref.g.12"></span> <a href="#header.content-range" class="smpl">Content-Range</a> = "Content-Range" ":" <a href="#core.rules" class="smpl">OWS</a> <a href="#header.content-range" class="smpl">Content-Range-v</a> 692 697 <a href="#header.content-range" class="smpl">Content-Range-v</a> = <a href="#header.content-range" class="smpl">content-range-spec</a> 693 698 694 699 <a href="#header.content-range" class="smpl">content-range-spec</a> = <a href="#header.content-range" class="smpl">byte-content-range-spec</a> 695 700 / <a href="#header.content-range" class="smpl">other-content-range-spec</a> 696 <a href="#header.content-range" class="smpl">byte-content-range-spec</a> = <a href="#range.units" class="smpl">bytes-unit</a> <a href="# notation" class="smpl">SP</a>701 <a href="#header.content-range" class="smpl">byte-content-range-spec</a> = <a href="#range.units" class="smpl">bytes-unit</a> <a href="#core.rules" class="smpl">SP</a> 697 702 <a href="#header.content-range" class="smpl">byte-range-resp-spec</a> "/" 698 703 ( <a href="#header.content-range" class="smpl">instance-length</a> / "*" ) … … 701 706 / "*" 702 707 703 <a href="#header.content-range" class="smpl">instance-length</a> = 1*<a href="# notation" class="smpl">DIGIT</a>708 <a href="#header.content-range" class="smpl">instance-length</a> = 1*<a href="#core.rules" class="smpl">DIGIT</a> 704 709 705 <a href="#header.content-range" class="smpl">other-content-range-spec</a> = <a href="#range.units" class="smpl">other-range-unit</a> <a href="# notation" class="smpl">SP</a>710 <a href="#header.content-range" class="smpl">other-content-range-spec</a> = <a href="#range.units" class="smpl">other-range-unit</a> <a href="#core.rules" class="smpl">SP</a> 706 711 <a href="#header.content-range" class="smpl">other-range-resp-spec</a> 707 <a href="#header.content-range" class="smpl">other-range-resp-spec</a> = *<a href="# notation" class="smpl">CHAR</a>708 </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 "*"712 <a href="#header.content-range" class="smpl">other-range-resp-spec</a> = *<a href="#core.rules" class="smpl">CHAR</a> 713 </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 "*" 709 714 character means that the instance-length is unknown at the time when the response was generated. 710 715 </p> 711 <p id="rfc.section. 6.2.p.4">Unlike byte-ranges-specifier values (see <a href="#byte.ranges" title="Byte Ranges">Section 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.712 </p> 713 <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, or716 <p id="rfc.section.5.2.p.4">Unlike byte-ranges-specifier values (see <a href="#byte.ranges" title="Byte Ranges">Section 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. 717 </p> 718 <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 714 719 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. 715 720 </p> 716 <p id="rfc.section. 6.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 the721 <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 717 722 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 "*". 718 723 </p> 719 <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>724 <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> 720 725 <ul> 721 726 <li>The first 500 bytes: … … 732 737 </pre> </li> 733 738 </ul> 734 <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 to739 <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 735 740 a request for a set of ranges that overlap without any holes), this content is transmitted with a Content-Range header, and 736 741 a Content-Length header showing the number of bytes actually transferred. For example, … … 742 747 Content-Length: 26012 743 748 Content-Type: image/gif 744 </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-overlapping749 </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 745 750 ranges), these are transmitted as a multipart message. The multipart media type used for this purpose is "multipart/byteranges" 746 751 as defined in <a href="#internet.media.type.multipart.byteranges" title="Internet Media Type multipart/byteranges">Appendix A</a>. See <a href="#changes.from.rfc.2068" title="Changes from RFC 2068">Appendix B.1</a> for a compatibility issue. 747 752 </p> 748 <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 ranges in a single request.749 </p> 750 <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.751 </p> 752 <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 containing753 <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 ranges in a single request. 754 </p> 755 <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. 756 </p> 757 <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 753 758 the full entity). 754 759 </p> 755 <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-header760 <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 756 761 field (that is, all of whose byte-range-spec values have a first-byte-pos value greater than the current length of the selected 757 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 4.2</a>).762 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 3.2</a>). 758 763 </p> 759 764 <dl class="empty"> … … 764 769 <div id="rfc.iref.i.1"></div> 765 770 <div id="rfc.iref.h.3"></div> 766 <h2 id="rfc.section. 6.3"><a href="#rfc.section.6.3">6.3</a> <a id="header.if-range" href="#header.if-range">If-Range</a></h2>767 <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 its771 <h2 id="rfc.section.5.3"><a href="#rfc.section.5.3">5.3</a> <a id="header.if-range" href="#header.if-range">If-Range</a></h2> 772 <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 768 773 cache, it could use the Range request-header with a conditional GET (using either or both of If-Unmodified-Since and If-Match.) 769 774 However, if the condition fails because the entity has been modified, the client would then have to make a second request 770 775 to obtain the entire current entity-body. 771 776 </p> 772 <p id="rfc.section. 6.3.p.2">The request header "If-Range" allows a client to "short-circuit" the second request. Informally, its meaning is `if the entity777 <p id="rfc.section.5.3.p.2">The request header "If-Range" allows a client to "short-circuit" the second request. Informally, its meaning is `if the entity 773 778 is unchanged, send me the part(s) that I am missing; otherwise, send me the entire new entity'. 774 779 </p> 775 <div id="rfc.figure.u.15"></div><pre class="inline"><span id="rfc.iref.g.13"></span><span id="rfc.iref.g.14"></span> <a href="#header.if-range" class="smpl">If-Range</a> = "If-Range" ":" <a href="# notation" class="smpl">OWS</a> <a href="#header.if-range" class="smpl">If-Range-v</a>780 <div id="rfc.figure.u.15"></div><pre class="inline"><span id="rfc.iref.g.13"></span><span id="rfc.iref.g.14"></span> <a href="#header.if-range" class="smpl">If-Range</a> = "If-Range" ":" <a href="#core.rules" class="smpl">OWS</a> <a href="#header.if-range" class="smpl">If-Range-v</a> 776 781 <a href="#header.if-range" class="smpl">If-Range-v</a> = <a href="#abnf.dependencies" class="smpl">entity-tag</a> / <a href="#abnf.dependencies" class="smpl">HTTP-date</a> 777 </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 examining782 </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 778 783 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. 779 784 </p> 780 <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, then785 <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 781 786 the server <em class="bcp14">SHOULD</em> return the entire entity using a 200 (OK) response. 782 787 </p> 783 788 <div id="rfc.iref.r.1"></div> 784 789 <div id="rfc.iref.h.4"></div> 785 <h2 id="rfc.section. 6.4"><a href="#rfc.section.6.4">6.4</a> <a id="header.range" href="#header.range">Range</a></h2>786 <h3 id="rfc.section. 6.4.1"><a href="#rfc.section.6.4.1">6.4.1</a> <a id="byte.ranges" href="#byte.ranges">Byte Ranges</a></h3>787 <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 meaningful790 <h2 id="rfc.section.5.4"><a href="#rfc.section.5.4">5.4</a> <a id="header.range" href="#header.range">Range</a></h2> 791 <h3 id="rfc.section.5.4.1"><a href="#rfc.section.5.4.1">5.4.1</a> <a id="byte.ranges" href="#byte.ranges">Byte Ranges</a></h3> 792 <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 788 793 for any HTTP entity. (However, not all clients and servers need to support byte-range operations.) 789 794 </p> 790 <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>795 <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> 791 796 <div id="rule.ranges-specifier"> 792 <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.797 <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. 793 798 </p> 794 799 </div> … … 796 801 <a href="#rule.ranges-specifier" class="smpl">byte-range-set</a> = 1#( <a href="#rule.ranges-specifier" class="smpl">byte-range-spec</a> / <a href="#rule.ranges-specifier" class="smpl">suffix-byte-range-spec</a> ) 797 802 <a href="#rule.ranges-specifier" class="smpl">byte-range-spec</a> = <a href="#rule.ranges-specifier" class="smpl">first-byte-pos</a> "-" [<a href="#rule.ranges-specifier" class="smpl">last-byte-pos</a>] 798 <a href="#rule.ranges-specifier" class="smpl">first-byte-pos</a> = 1*<a href="# notation" class="smpl">DIGIT</a>799 <a href="#rule.ranges-specifier" class="smpl">last-byte-pos</a> = 1*<a href="# notation" class="smpl">DIGIT</a>800 </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 value803 <a href="#rule.ranges-specifier" class="smpl">first-byte-pos</a> = 1*<a href="#core.rules" class="smpl">DIGIT</a> 804 <a href="#rule.ranges-specifier" class="smpl">last-byte-pos</a> = 1*<a href="#core.rules" class="smpl">DIGIT</a> 805 </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 801 806 gives the byte-offset of the last byte in the range; that is, the byte positions specified are inclusive. Byte offsets start 802 807 at zero. 803 808 </p> 804 <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. The809 <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 805 810 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. 806 811 </p> 807 <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-pos812 <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 808 813 is taken to be equal to one less than the current length of the entity-body in bytes. 809 814 </p> 810 <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>815 <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> 811 816 <div id="rfc.figure.u.17"></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> 812 <a href="#rule.ranges-specifier" class="smpl">suffix-length</a> = 1*<a href="# notation" class="smpl">DIGIT</a>813 </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. (That817 <a href="#rule.ranges-specifier" class="smpl">suffix-length</a> = 1*<a href="#core.rules" class="smpl">DIGIT</a> 818 </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 814 819 is, this form specifies the last N bytes of an entity-body.) If the entity is shorter than the specified suffix-length, the 815 820 entire entity-body is used. 816 821 </p> 817 <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 current822 <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 818 823 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 819 824 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. 820 825 </p> 821 <p id="rfc.section. 6.4.1.p.12">Examples of byte-ranges-specifier values (assuming an entity-body of length 10000): </p>826 <p id="rfc.section.5.4.1.p.12">Examples of byte-ranges-specifier values (assuming an entity-body of length 10000): </p> 822 827 <ul> 823 828 <li>The first 500 bytes (byte offsets 0-499, inclusive): bytes=0-499</li> … … 829 834 </li> 830 835 </ul> 831 <h3 id="rfc.section. 6.4.2"><a href="#rfc.section.6.4.2">6.4.2</a> <a id="range.retrieval.requests" href="#range.retrieval.requests">Range Retrieval Requests</a></h3>832 <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 applies836 <h3 id="rfc.section.5.4.2"><a href="#rfc.section.5.4.2">5.4.2</a> <a id="range.retrieval.requests" href="#range.retrieval.requests">Range Retrieval Requests</a></h3> 837 <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 833 838 to the entity returned as the result of the request: 834 839 </p> … … 836 841 <a href="#rule.ranges-specifier" class="smpl">ranges-specifier</a> = <a href="#rule.ranges-specifier" class="smpl">byte-ranges-specifier</a> 837 842 / <a href="#rule.ranges-specifier" class="smpl">other-ranges-specifier</a> 838 <a href="#rule.ranges-specifier" class="smpl">other-ranges-specifier</a> = 1*<a href="# notation" class="smpl">CHAR</a>839 </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,843 <a href="#rule.ranges-specifier" class="smpl">other-ranges-specifier</a> = 1*<a href="#core.rules" class="smpl">CHAR</a> 844 </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, 840 845 since Range supports efficient recovery from partially failed transfers, and supports efficient partial retrieval of large 841 846 entities. 842 847 </p> 843 <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>848 <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> 844 849 <ul> 845 850 <li>The presence of a Range header in an unconditional GET modifies what is returned if the GET is otherwise successful. In other … … 851 856 </li> 852 857 </ul> 853 <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 6.3</a>) in addition to the Range header.854 </p> 855 <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 entire858 <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 5.3</a>) in addition to the Range header. 859 </p> 860 <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 856 861 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. 857 862 </p> 858 <h1 id="rfc.section. 7"><a href="#rfc.section.7">7.</a> <a id="IANA.considerations" href="#IANA.considerations">IANA Considerations</a></h1>859 <h2 id="rfc.section. 7.1"><a href="#rfc.section.7.1">7.1</a> <a id="message.header.registration" href="#message.header.registration">Message Header Registration</a></h2>860 <p id="rfc.section. 7.1.p.1">The Message Header Registry located at <<a href="http://www.iana.org/assignments/message-headers/message-header-index.html">http://www.iana.org/assignments/message-headers/message-header-index.html</a>> should be updated with the permanent registrations below (see <a href="#RFC3864" id="rfc.xref.RFC3864.1"><cite title="Registration Procedures for Message Header Fields">[RFC3864]</cite></a>):863 <h1 id="rfc.section.6"><a href="#rfc.section.6">6.</a> <a id="IANA.considerations" href="#IANA.considerations">IANA Considerations</a></h1> 864 <h2 id="rfc.section.6.1"><a href="#rfc.section.6.1">6.1</a> <a id="message.header.registration" href="#message.header.registration">Message Header Registration</a></h2> 865 <p id="rfc.section.6.1.p.1">The Message Header Registry located at <<a href="http://www.iana.org/assignments/message-headers/message-header-index.html">http://www.iana.org/assignments/message-headers/message-header-index.html</a>> should be updated with the permanent registrations below (see <a href="#RFC3864" id="rfc.xref.RFC3864.1"><cite title="Registration Procedures for Message Header Fields">[RFC3864]</cite></a>): 861 866 </p> 862 867 <div id="rfc.table.1"> … … 876 881 <td>http</td> 877 882 <td>standard</td> 878 <td> <a href="#header.accept-ranges" id="rfc.xref.header.accept-ranges.1" title="Accept-Ranges">Section 6.1</a>883 <td> <a href="#header.accept-ranges" id="rfc.xref.header.accept-ranges.1" title="Accept-Ranges">Section 5.1</a> 879 884 </td> 880 885 </tr> … … 883 888 <td>http</td> 884 889 <td>standard</td> 885 <td> <a href="#header.content-range" id="rfc.xref.header.content-range.4" title="Content-Range">Section 6.2</a>890 <td> <a href="#header.content-range" id="rfc.xref.header.content-range.4" title="Content-Range">Section 5.2</a> 886 891 </td> 887 892 </tr> … … 890 895 <td>http</td> 891 896 <td>standard</td> 892 <td> <a href="#header.if-range" id="rfc.xref.header.if-range.3" title="If-Range">Section 6.3</a>897 <td> <a href="#header.if-range" id="rfc.xref.header.if-range.3" title="If-Range">Section 5.3</a> 893 898 </td> 894 899 </tr> … … 897 902 <td>http</td> 898 903 <td>standard</td> 899 <td> <a href="#header.range" id="rfc.xref.header.range.5" title="Range">Section 6.4</a>904 <td> <a href="#header.range" id="rfc.xref.header.range.5" title="Range">Section 5.4</a> 900 905 </td> 901 906 </tr> … … 903 908 </table> 904 909 </div> 905 <p id="rfc.section. 7.1.p.2">The change controller is: "IETF (iesg@ietf.org) - Internet Engineering Task Force".</p>906 <h1 id="rfc.section. 8"><a href="#rfc.section.8">8.</a> <a id="security.considerations" href="#security.considerations">Security Considerations</a></h1>907 <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.9"><cite title="HTTP/1.1, part 1: URIs, Connections, and Message Parsing">[Part1]</cite></a>.908 </p> 909 <h1 id="rfc.section. 9"><a href="#rfc.section.9">9.</a> <a id="ack" href="#ack">Acknowledgments</a></h1>910 <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 input910 <p id="rfc.section.6.1.p.2">The change controller is: "IETF (iesg@ietf.org) - Internet Engineering Task Force".</p> 911 <h1 id="rfc.section.7"><a href="#rfc.section.7">7.</a> <a id="security.considerations" href="#security.considerations">Security Considerations</a></h1> 912 <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.9"><cite title="HTTP/1.1, part 1: URIs, Connections, and Message Parsing">[Part1]</cite></a>. 913 </p> 914 <h1 id="rfc.section.8"><a href="#rfc.section.8">8.</a> <a id="ack" href="#ack">Acknowledgments</a></h1> 915 <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 911 916 from Steve Zilles, Daniel W. Connolly, Roy T. Fielding, Jim Gettys, Martin Hamilton, Koen Holtman, Shel Kaplan, Paul Leach, 912 917 Alex Lopez-Ortiz, Larry Masinter, Jeff Mogul, Lou Montulli, David W. Morris, Luigi Rizzo, and Bill Weihl. 913 918 </p> 914 <h1 id="rfc.references"><a id="rfc.section. 10" href="#rfc.section.10">10.</a> References919 <h1 id="rfc.references"><a id="rfc.section.9" href="#rfc.section.9">9.</a> References 915 920 </h1> 916 <h2 id="rfc.references.1"><a href="#rfc.section. 10.1" id="rfc.section.10.1">10.1</a> Normative References921 <h2 id="rfc.references.1"><a href="#rfc.section.9.1" id="rfc.section.9.1">9.1</a> Normative References 917 922 </h2> 918 923 <table summary="Normative References"> … … 948 953 </tr> 949 954 </table> 950 <h2 id="rfc.references.2"><a href="#rfc.section. 10.2" id="rfc.section.10.2">10.2</a> Informative References955 <h2 id="rfc.references.2"><a href="#rfc.section.9.2" id="rfc.section.9.2">9.2</a> Informative References 951 956 </h2> 952 957 <table summary="Informative References"> … … 1061 1066 <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 1062 1067 for transfer encoding that may not be self delimiting); it was important to straighten out exactly how message lengths are 1063 computed. (<a href="#header.content-range" id="rfc.xref.header.content-range.5" title="Content-Range">Section 6.2</a>, see also <a href="#Part1" id="rfc.xref.Part1.10"><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>)1068 computed. (<a href="#header.content-range" id="rfc.xref.header.content-range.5" title="Content-Range">Section 5.2</a>, see also <a href="#Part1" id="rfc.xref.Part1.10"><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>) 1064 1069 </p> 1065 1070 <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 1066 1071 a byterange request. We therefore need a mechanism to allow byteranges with a content-range not indicating the full length 1067 of the message. (<a href="#header.content-range" id="rfc.xref.header.content-range.6" title="Content-Range">Section 6.2</a>)1072 of the message. (<a href="#header.content-range" id="rfc.xref.header.content-range.6" title="Content-Range">Section 5.2</a>) 1068 1073 </p> 1069 1074 <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 1070 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.4" title="If-Range">6.3</a>)1075 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.4" title="If-Range">5.3</a>) 1071 1076 </p> 1072 1077 <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. 1073 1078 The 416 status code was needed to resolve this ambiguity needed to indicate an error for a byte range request that falls outside 1074 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.7" title="Content-Range">6.2</a>)1079 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.7" title="Content-Range">5.2</a>) 1075 1080 </p> 1076 1081 <h2 id="rfc.section.B.2"><a href="#rfc.section.B.2">B.2</a> <a id="changes.from.rfc.2616" href="#changes.from.rfc.2616">Changes from RFC 2616</a></h2> 1077 <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 4.1</a>)1082 <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 3.1</a>) 1078 1083 </p> 1079 1084 <p id="rfc.section.B.2.p.2">Clarify that multipart/byteranges can consist of a single part. (<a href="#internet.media.type.multipart.byteranges" title="Internet Media Type multipart/byteranges">Appendix A</a>) … … 1105 1110 content-range-spec = byte-content-range-spec / 1106 1111 other-content-range-spec 1107 entity-tag = <entity-tag, defined in [Part4], Section 3>1112 entity-tag = <entity-tag, defined in [Part4], Section 2> 1108 1113 first-byte-pos = 1*DIGIT 1109 1114 instance-length = 1*DIGIT … … 1179 1184 </p> 1180 1185 <ul> 1181 <li>Add appendix containing collected and expanded ABNF .</li>1186 <li>Add appendix containing collected and expanded ABNF, reorganize ABNF introduction.</li> 1182 1187 </ul> 1183 1188 <h1><a id="rfc.copyright" href="#rfc.copyright">Full Copyright Statement</a></h1> … … 1211 1216 <ul class="ind"> 1212 1217 <li class="indline0"><a id="rfc.index.2" href="#rfc.index.2"><b>2</b></a><ul class="ind"> 1213 <li class="indline1">206 Partial Content (status code) <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>1218 <li class="indline1">206 Partial Content (status code) <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> 1214 1219 </ul> 1215 1220 </li> 1216 1221 <li class="indline0"><a id="rfc.index.4" href="#rfc.index.4"><b>4</b></a><ul class="ind"> 1217 <li class="indline1">416 Requested Range Not Satisfiable (status code) <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>1222 <li class="indline1">416 Requested Range Not Satisfiable (status code) <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> 1218 1223 </ul> 1219 1224 </li> 1220 1225 <li class="indline0"><a id="rfc.index.A" href="#rfc.index.A"><b>A</b></a><ul class="ind"> 1221 <li class="indline1">Accept-Ranges header <a class="iref" href="#rfc.iref.a.1"><b> 6.1</b></a>, <a class="iref" href="#rfc.xref.header.accept-ranges.1">7.1</a></li>1226 <li class="indline1">Accept-Ranges header <a class="iref" href="#rfc.iref.a.1"><b>5.1</b></a>, <a class="iref" href="#rfc.xref.header.accept-ranges.1">6.1</a></li> 1222 1227 </ul> 1223 1228 </li> 1224 1229 <li class="indline0"><a id="rfc.index.C" href="#rfc.index.C"><b>C</b></a><ul class="ind"> 1225 <li class="indline1">Content-Range header <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">7.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>, <a class="iref" href="#rfc.xref.header.content-range.7">B.1</a></li>1230 <li class="indline1">Content-Range header <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">6.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>, <a class="iref" href="#rfc.xref.header.content-range.7">B.1</a></li> 1226 1231 </ul> 1227 1232 </li> … … 1229 1234 <li class="indline1"><tt>Grammar</tt> 1230 1235 <ul class="ind"> 1231 <li class="indline1"><tt>Accept-Ranges</tt> <a class="iref" href="#rfc.iref.g.4"><b> 6.1</b></a></li>1232 <li class="indline1"><tt>Accept-Ranges-v</tt> <a class="iref" href="#rfc.iref.g.5"><b> 6.1</b></a></li>1233 <li class="indline1"><tt>acceptable-ranges</tt> <a class="iref" href="#rfc.iref.g.6"><b> 6.1</b></a></li>1234 <li class="indline1"><tt>byte-content-range-spec</tt> <a class="iref" href="#rfc.iref.g.10"><b> 6.2</b></a></li>1235 <li class="indline1"><tt>byte-range-resp-spec</tt> <a class="iref" href="#rfc.iref.g.11"><b> 6.2</b></a></li>1236 <li class="indline1"><tt>byte-range-set</tt> <a class="iref" href="#rfc.iref.g.17"><b> 6.4.1</b></a></li>1237 <li class="indline1"><tt>byte-range-spec</tt> <a class="iref" href="#rfc.iref.g.18"><b> 6.4.1</b></a></li>1238 <li class="indline1"><tt>byte-ranges-specifier</tt> <a class="iref" href="#rfc.iref.g.16"><b> 6.4.1</b></a></li>1239 <li class="indline1"><tt>bytes-unit</tt> <a class="iref" href="#rfc.iref.g.2"><b> 3</b></a></li>1240 <li class="indline1"><tt>Content-Range</tt> <a class="iref" href="#rfc.iref.g.7"><b> 6.2</b></a></li>1241 <li class="indline1"><tt>content-range-spec</tt> <a class="iref" href="#rfc.iref.g.9"><b> 6.2</b></a></li>1242 <li class="indline1"><tt>Content-Range-v</tt> <a class="iref" href="#rfc.iref.g.8"><b> 6.2</b></a></li>1243 <li class="indline1"><tt>first-byte-pos</tt> <a class="iref" href="#rfc.iref.g.19"><b> 6.4.1</b></a></li>1244 <li class="indline1"><tt>If-Range</tt> <a class="iref" href="#rfc.iref.g.13"><b> 6.3</b></a></li>1245 <li class="indline1"><tt>If-Range-v</tt> <a class="iref" href="#rfc.iref.g.14"><b> 6.3</b></a></li>1246 <li class="indline1"><tt>instance-length</tt> <a class="iref" href="#rfc.iref.g.12"><b> 6.2</b></a></li>1247 <li class="indline1"><tt>last-byte-pos</tt> <a class="iref" href="#rfc.iref.g.20"><b> 6.4.1</b></a></li>1248 <li class="indline1"><tt>other-range-unit</tt> <a class="iref" href="#rfc.iref.g.3"><b> 3</b></a></li>1249 <li class="indline1"><tt>Range</tt> <a class="iref" href="#rfc.iref.g.23"><b> 6.4.2</b></a></li>1250 <li class="indline1"><tt>range-unit</tt> <a class="iref" href="#rfc.iref.g.1"><b> 3</b></a></li>1251 <li class="indline1"><tt>ranges-specifier</tt> <a class="iref" href="#rfc.iref.g.15"><b> 6.4.1</b></a></li>1252 <li class="indline1"><tt>suffix-byte-range-spec</tt> <a class="iref" href="#rfc.iref.g.21"><b> 6.4.1</b></a></li>1253 <li class="indline1"><tt>suffix-length</tt> <a class="iref" href="#rfc.iref.g.22"><b> 6.4.1</b></a></li>1236 <li class="indline1"><tt>Accept-Ranges</tt> <a class="iref" href="#rfc.iref.g.4"><b>5.1</b></a></li> 1237 <li class="indline1"><tt>Accept-Ranges-v</tt> <a class="iref" href="#rfc.iref.g.5"><b>5.1</b></a></li> 1238 <li class="indline1"><tt>acceptable-ranges</tt> <a class="iref" href="#rfc.iref.g.6"><b>5.1</b></a></li> 1239 <li class="indline1"><tt>byte-content-range-spec</tt> <a class="iref" href="#rfc.iref.g.10"><b>5.2</b></a></li> 1240 <li class="indline1"><tt>byte-range-resp-spec</tt> <a class="iref" href="#rfc.iref.g.11"><b>5.2</b></a></li> 1241 <li class="indline1"><tt>byte-range-set</tt> <a class="iref" href="#rfc.iref.g.17"><b>5.4.1</b></a></li> 1242 <li class="indline1"><tt>byte-range-spec</tt> <a class="iref" href="#rfc.iref.g.18"><b>5.4.1</b></a></li> 1243 <li class="indline1"><tt>byte-ranges-specifier</tt> <a class="iref" href="#rfc.iref.g.16"><b>5.4.1</b></a></li> 1244 <li class="indline1"><tt>bytes-unit</tt> <a class="iref" href="#rfc.iref.g.2"><b>2</b></a></li> 1245 <li class="indline1"><tt>Content-Range</tt> <a class="iref" href="#rfc.iref.g.7"><b>5.2</b></a></li> 1246 <li class="indline1"><tt>content-range-spec</tt> <a class="iref" href="#rfc.iref.g.9"><b>5.2</b></a></li> 1247 <li class="indline1"><tt>Content-Range-v</tt> <a class="iref" href="#rfc.iref.g.8"><b>5.2</b></a></li> 1248 <li class="indline1"><tt>first-byte-pos</tt> <a class="iref" href="#rfc.iref.g.19"><b>5.4.1</b></a></li> 1249 <li class="indline1"><tt>If-Range</tt> <a class="iref" href="#rfc.iref.g.13"><b>5.3</b></a></li> 1250 <li class="indline1"><tt>If-Range-v</tt> <a class="iref" href="#rfc.iref.g.14"><b>5.3</b></a></li> 1251 <li class="indline1"><tt>instance-length</tt> <a class="iref" href="#rfc.iref.g.12"><b>5.2</b></a></li> 1252 <li class="indline1"><tt>last-byte-pos</tt> <a class="iref" href="#rfc.iref.g.20"><b>5.4.1</b></a></li> 1253 <li class="indline1"><tt>other-range-unit</tt> <a class="iref" href="#rfc.iref.g.3"><b>2</b></a></li> 1254 <li class="indline1"><tt>Range</tt> <a class="iref" href="#rfc.iref.g.23"><b>5.4.2</b></a></li> 1255 <li class="indline1"><tt>range-unit</tt> <a class="iref" href="#rfc.iref.g.1"><b>2</b></a></li> 1256 <li class="indline1"><tt>ranges-specifier</tt> <a class="iref" href="#rfc.iref.g.15"><b>5.4.1</b></a></li> 1257 <li class="indline1"><tt>suffix-byte-range-spec</tt> <a class="iref" href="#rfc.iref.g.21"><b>5.4.1</b></a></li> 1258 <li class="indline1"><tt>suffix-length</tt> <a class="iref" href="#rfc.iref.g.22"><b>5.4.1</b></a></li> 1254 1259 </ul> 1255 1260 </li> … … 1259 1264 <li class="indline1">Headers 1260 1265 <ul class="ind"> 1261 <li class="indline1">Accept-Ranges <a class="iref" href="#rfc.iref.h.1"><b> 6.1</b></a>, <a class="iref" href="#rfc.xref.header.accept-ranges.1">7.1</a></li>1262 <li class="indline1">Content-Range <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">7.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>, <a class="iref" href="#rfc.xref.header.content-range.7">B.1</a></li>1263 <li class="indline1">If-Range <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">7.1</a>, <a class="iref" href="#rfc.xref.header.if-range.4">B.1</a></li>1264 <li class="indline1">Range <a class="iref" href="#rfc.xref.header.range.1"> 3</a>, <a class="iref" href="#rfc.xref.header.range.2">3</a>, <a class="iref" href="#rfc.xref.header.range.3">4.1</a>, <a class="iref" href="#rfc.xref.header.range.4">4.2</a>, <a class="iref" href="#rfc.iref.h.4"><b>6.4</b></a>, <a class="iref" href="#rfc.xref.header.range.5">7.1</a></li>1266 <li class="indline1">Accept-Ranges <a class="iref" href="#rfc.iref.h.1"><b>5.1</b></a>, <a class="iref" href="#rfc.xref.header.accept-ranges.1">6.1</a></li> 1267 <li class="indline1">Content-Range <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">6.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>, <a class="iref" href="#rfc.xref.header.content-range.7">B.1</a></li> 1268 <li class="indline1">If-Range <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">6.1</a>, <a class="iref" href="#rfc.xref.header.if-range.4">B.1</a></li> 1269 <li class="indline1">Range <a class="iref" href="#rfc.xref.header.range.1">2</a>, <a class="iref" href="#rfc.xref.header.range.2">2</a>, <a class="iref" href="#rfc.xref.header.range.3">3.1</a>, <a class="iref" href="#rfc.xref.header.range.4">3.2</a>, <a class="iref" href="#rfc.iref.h.4"><b>5.4</b></a>, <a class="iref" href="#rfc.xref.header.range.5">6.1</a></li> 1265 1270 </ul> 1266 1271 </li> … … 1268 1273 </li> 1269 1274 <li class="indline0"><a id="rfc.index.I" href="#rfc.index.I"><b>I</b></a><ul class="ind"> 1270 <li class="indline1">If-Range header <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">7.1</a>, <a class="iref" href="#rfc.xref.header.if-range.4">B.1</a></li>1275 <li class="indline1">If-Range header <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">6.1</a>, <a class="iref" href="#rfc.xref.header.if-range.4">B.1</a></li> 1271 1276 </ul> 1272 1277 </li> … … 1283 1288 </li> 1284 1289 <li class="indline0"><a id="rfc.index.P" href="#rfc.index.P"><b>P</b></a><ul class="ind"> 1285 <li class="indline1"><em>Part1</em> <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">2</a>, <a class="iref" href="#rfc.xref.Part1.8">2</a>, <a class="iref" href="#rfc.xref.Part1.9">8</a>, <a class="iref" href="#Part1"><b>10.1</b></a>, <a class="iref" href="#rfc.xref.Part1.10">B.1</a><ul class="ind">1286 <li class="indline1"><em>Section 1.2 .1</em> <a class="iref" href="#rfc.xref.Part1.1">2</a></li>1287 <li class="indline1"><em>Section 1.2.2</em> <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">2</a></li>1288 <li class="indline1"><em>Section 3.2.1</em> <a class="iref" href="#rfc.xref.Part1.8"> 2</a></li>1290 <li class="indline1"><em>Part1</em> <a class="iref" href="#rfc.xref.Part1.1">1.2</a>, <a class="iref" href="#rfc.xref.Part1.2">1.2.1</a>, <a class="iref" href="#rfc.xref.Part1.3">1.2.1</a>, <a class="iref" href="#rfc.xref.Part1.4">1.2.1</a>, <a class="iref" href="#rfc.xref.Part1.5">1.2.1</a>, <a class="iref" href="#rfc.xref.Part1.6">1.2.1</a>, <a class="iref" href="#rfc.xref.Part1.7">1.2.1</a>, <a class="iref" href="#rfc.xref.Part1.8">1.2.2</a>, <a class="iref" href="#rfc.xref.Part1.9">7</a>, <a class="iref" href="#Part1"><b>9.1</b></a>, <a class="iref" href="#rfc.xref.Part1.10">B.1</a><ul class="ind"> 1291 <li class="indline1"><em>Section 1.2</em> <a class="iref" href="#rfc.xref.Part1.1">1.2</a></li> 1292 <li class="indline1"><em>Section 1.2.2</em> <a class="iref" href="#rfc.xref.Part1.2">1.2.1</a>, <a class="iref" href="#rfc.xref.Part1.3">1.2.1</a>, <a class="iref" href="#rfc.xref.Part1.4">1.2.1</a>, <a class="iref" href="#rfc.xref.Part1.5">1.2.1</a>, <a class="iref" href="#rfc.xref.Part1.6">1.2.1</a>, <a class="iref" href="#rfc.xref.Part1.7">1.2.1</a></li> 1293 <li class="indline1"><em>Section 3.2.1</em> <a class="iref" href="#rfc.xref.Part1.8">1.2.2</a></li> 1289 1294 </ul> 1290 1295 </li> 1291 <li class="indline1"><em>Part3</em> <a class="iref" href="#Part3"><b> 10.1</b></a>, <a class="iref" href="#rfc.xref.Part3.1">B.1</a></li>1292 <li class="indline1"><em>Part4</em> <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">1293 <li class="indline1"><em>Section 3</em> <a class="iref" href="#rfc.xref.Part4.1">2</a></li>1294 <li class="indline1"><em>Section 5</em> <a class="iref" href="#rfc.xref.Part4.2">5</a></li>1296 <li class="indline1"><em>Part3</em> <a class="iref" href="#Part3"><b>9.1</b></a>, <a class="iref" href="#rfc.xref.Part3.1">B.1</a></li> 1297 <li class="indline1"><em>Part4</em> <a class="iref" href="#rfc.xref.Part4.1">1.2.2</a>, <a class="iref" href="#rfc.xref.Part4.2">4</a>, <a class="iref" href="#Part4"><b>9.1</b></a><ul class="ind"> 1298 <li class="indline1"><em>Section 2</em> <a class="iref" href="#rfc.xref.Part4.1">1.2.2</a></li> 1299 <li class="indline1"><em>Section 4</em> <a class="iref" href="#rfc.xref.Part4.2">4</a></li> 1295 1300 </ul> 1296 1301 </li> 1297 <li class="indline1"><em>Part6</em> <a class="iref" href="#Part6"><b> 10.1</b></a>, <a class="iref" href="#rfc.xref.Part6.1">B.1</a></li>1302 <li class="indline1"><em>Part6</em> <a class="iref" href="#Part6"><b>9.1</b></a>, <a class="iref" href="#rfc.xref.Part6.1">B.1</a></li> 1298 1303 </ul> 1299 1304 </li> 1300 1305 <li class="indline0"><a id="rfc.index.R" href="#rfc.index.R"><b>R</b></a><ul class="ind"> 1301 <li class="indline1">Range header <a class="iref" href="#rfc.xref.header.range.1"> 3</a>, <a class="iref" href="#rfc.xref.header.range.2">3</a>, <a class="iref" href="#rfc.xref.header.range.3">4.1</a>, <a class="iref" href="#rfc.xref.header.range.4">4.2</a>, <a class="iref" href="#rfc.iref.r.1"><b>6.4</b></a>, <a class="iref" href="#rfc.xref.header.range.5">7.1</a></li>1302 <li class="indline1"><em>RFC2046</em> <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><ul class="ind">1306 <li class="indline1">Range header <a class="iref" href="#rfc.xref.header.range.1">2</a>, <a class="iref" href="#rfc.xref.header.range.2">2</a>, <a class="iref" href="#rfc.xref.header.range.3">3.1</a>, <a class="iref" href="#rfc.xref.header.range.4">3.2</a>, <a class="iref" href="#rfc.iref.r.1"><b>5.4</b></a>, <a class="iref" href="#rfc.xref.header.range.5">6.1</a></li> 1307 <li class="indline1"><em>RFC2046</em> <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><ul class="ind"> 1303 1308 <li class="indline1"><em>Section 5.1</em> <a class="iref" href="#rfc.xref.RFC2046.1">A</a></li> 1304 1309 </ul> 1305 1310 </li> 1306 <li class="indline1"><em>RFC2119</em> <a class="iref" href="#rfc.xref.RFC2119.1">1.1</a>, <a class="iref" href="#RFC2119"><b> 10.1</b></a></li>1307 <li class="indline1"><em>RFC2616</em> <a class="iref" href="#RFC2616"><b> 10.2</b></a>, <a class="iref" href="#rfc.xref.RFC2616.1">D.1</a></li>1308 <li class="indline1"><em>RFC3864</em> <a class="iref" href="#rfc.xref.RFC3864.1"> 7.1</a>, <a class="iref" href="#RFC3864"><b>10.2</b></a></li>1309 <li class="indline1"><em>RFC4288</em> <a class="iref" href="#RFC4288"><b> 10.2</b></a>, <a class="iref" href="#rfc.xref.RFC4288.1">A</a></li>1311 <li class="indline1"><em>RFC2119</em> <a class="iref" href="#rfc.xref.RFC2119.1">1.1</a>, <a class="iref" href="#RFC2119"><b>9.1</b></a></li> 1312 <li class="indline1"><em>RFC2616</em> <a class="iref" href="#RFC2616"><b>9.2</b></a>, <a class="iref" href="#rfc.xref.RFC2616.1">D.1</a></li> 1313 <li class="indline1"><em>RFC3864</em> <a class="iref" href="#rfc.xref.RFC3864.1">6.1</a>, <a class="iref" href="#RFC3864"><b>9.2</b></a></li> 1314 <li class="indline1"><em>RFC4288</em> <a class="iref" href="#RFC4288"><b>9.2</b></a>, <a class="iref" href="#rfc.xref.RFC4288.1">A</a></li> 1310 1315 </ul> 1311 1316 </li> … … 1313 1318 <li class="indline1">Status Codes 1314 1319 <ul class="ind"> 1315 <li class="indline1">206 Partial Content <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>1316 <li class="indline1">416 Requested Range Not Satisfiable <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>1320 <li class="indline1">206 Partial Content <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> 1321 <li class="indline1">416 Requested Range Not Satisfiable <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> 1317 1322 </ul> 1318 1323 </li>
Note: See TracChangeset
for help on using the changeset viewer.