Changeset 2217 for draft-ietf-httpbis/latest
- Timestamp:
- 31/03/13 16:23:11 (10 years ago)
- Location:
- draft-ietf-httpbis/latest
- Files:
-
- 2 edited
Legend:
- Unmodified
- Added
- Removed
-
draft-ietf-httpbis/latest/p5-range.html
r2208 r2217 449 449 } 450 450 @bottom-center { 451 content: "Expires September 19, 2013";451 content: "Expires October 2, 2013"; 452 452 } 453 453 @bottom-right { … … 492 492 <meta name="dct.creator" content="Reschke, J. F."> 493 493 <meta name="dct.identifier" content="urn:ietf:id:draft-ietf-httpbis-p5-range-latest"> 494 <meta name="dct.issued" scheme="ISO8601" content="2013-03- 18">494 <meta name="dct.issued" scheme="ISO8601" content="2013-03-31"> 495 495 <meta name="dct.replaces" content="urn:ietf:rfc:2616"> 496 496 <meta name="dct.abstract" content="The Hypertext Transfer Protocol (HTTP) is an application-level protocol for distributed, collaborative, hypertext information systems. This document defines range requests and the rules for constructing and combining responses to those requests."> … … 518 518 </tr> 519 519 <tr> 520 <td class="left">Expires: September 19, 2013</td>520 <td class="left">Expires: October 2, 2013</td> 521 521 <td class="right">J. Reschke, Editor</td> 522 522 </tr> … … 527 527 <tr> 528 528 <td class="left"></td> 529 <td class="right">March 18, 2013</td>529 <td class="right">March 31, 2013</td> 530 530 </tr> 531 531 </tbody> … … 552 552 in progress”. 553 553 </p> 554 <p>This Internet-Draft will expire on September 19, 2013.</p>554 <p>This Internet-Draft will expire on October 2, 2013.</p> 555 555 <h1><a id="rfc.copyrightnotice" href="#rfc.copyrightnotice">Copyright Notice</a></h1> 556 556 <p>Copyright © 2013 IETF Trust and the persons identified as the document authors. All rights reserved.</p> … … 634 634 or the dimensions of an embedded image. 635 635 </p> 636 <p id="rfc.section.1.p.2">This document defines HTTP/1.1 range requests, partial responses, and the multipart/byteranges media type , obsoleting those637 parts previously defined in <a href="#RFC2616" id="rfc.xref.RFC2616.1"><cite title="Hypertext Transfer Protocol -- HTTP/1.1">[RFC2616]</cite></a>. Range requestsare an <em class="bcp14">OPTIONAL</em> feature of HTTP, designed so that recipients not implementing this feature (or not supporting it for the target resource)636 <p id="rfc.section.1.p.2">This document defines HTTP/1.1 range requests, partial responses, and the multipart/byteranges media type. Range requests 637 are an <em class="bcp14">OPTIONAL</em> feature of HTTP, designed so that recipients not implementing this feature (or not supporting it for the target resource) 638 638 can respond as if it is a normal GET request without impacting interoperability. Partial responses are indicated by a distinct 639 639 status code to not be mistaken for full responses by caches that might not implement the feature. … … 692 692 <div id="rfc.figure.u.6"></div><pre class="inline"><span id="rfc.iref.g.11"></span><span id="rfc.iref.g.12"></span> <a href="#rule.ranges-specifier" class="smpl">suffix-byte-range-spec</a> = "-" <a href="#rule.ranges-specifier" class="smpl">suffix-length</a> 693 693 <a href="#rule.ranges-specifier" class="smpl">suffix-length</a> = 1*<a href="#imported.abnf" class="smpl">DIGIT</a> 694 </pre><p id="rfc.section.2.1.p.11">If the selected representation is shorter than the specified <a href="#rule.ranges-specifier" class="smpl">suffix-length</a>, the entire representation is used. For example (assuming a representation of length 10000): 695 </p> 694 </pre><p id="rfc.section.2.1.p.11">If the selected representation is shorter than the specified <a href="#rule.ranges-specifier" class="smpl">suffix-length</a>, the entire representation is used. 695 </p> 696 <p id="rfc.section.2.1.p.12">Additional examples, assuming a representation of length 10000: </p> 696 697 <ul> 697 698 <li>The final 500 bytes (byte offsets 9500-9999, inclusive): … … 707 708 </pre> </li> 708 709 </ul> 709 <p id="rfc.section.2.1.p.1 2">If a valid <a href="#rule.ranges-specifier" class="smpl">byte-range-set</a> includes at least one <a href="#rule.ranges-specifier" class="smpl">byte-range-spec</a> with a <a href="#rule.ranges-specifier" class="smpl">first-byte-pos</a> that is less than the current length of the representation, or at least one <a href="#rule.ranges-specifier" class="smpl">suffix-byte-range-spec</a> with a non-zero <a href="#rule.ranges-specifier" class="smpl">suffix-length</a>, then the <a href="#rule.ranges-specifier" class="smpl">byte-range-set</a> is satisfiable. Otherwise, the <a href="#rule.ranges-specifier" class="smpl">byte-range-set</a> is unsatisfiable.710 </p> 711 <p id="rfc.section.2.1.p.1 3">In the byte range syntax, <a href="#rule.ranges-specifier" class="smpl">first-byte-pos</a>, <a href="#rule.ranges-specifier" class="smpl">last-byte-pos</a>, and <a href="#rule.ranges-specifier" class="smpl">suffix-length</a> are expressed as decimal number of octets. Since there is no predefined limit to the length of a payload, recipients ought710 <p id="rfc.section.2.1.p.13">If a valid <a href="#rule.ranges-specifier" class="smpl">byte-range-set</a> includes at least one <a href="#rule.ranges-specifier" class="smpl">byte-range-spec</a> with a <a href="#rule.ranges-specifier" class="smpl">first-byte-pos</a> that is less than the current length of the representation, or at least one <a href="#rule.ranges-specifier" class="smpl">suffix-byte-range-spec</a> with a non-zero <a href="#rule.ranges-specifier" class="smpl">suffix-length</a>, then the <a href="#rule.ranges-specifier" class="smpl">byte-range-set</a> is satisfiable. Otherwise, the <a href="#rule.ranges-specifier" class="smpl">byte-range-set</a> is unsatisfiable. 711 </p> 712 <p id="rfc.section.2.1.p.14">In the byte range syntax, <a href="#rule.ranges-specifier" class="smpl">first-byte-pos</a>, <a href="#rule.ranges-specifier" class="smpl">last-byte-pos</a>, and <a href="#rule.ranges-specifier" class="smpl">suffix-length</a> are expressed as decimal number of octets. Since there is no predefined limit to the length of a payload, recipients ought 712 713 to anticipate potentially large decimal numerals and prevent parsing errors due to integer conversion overflows. 713 714 </p> … … 933 934 Content-Range: bytes */47022 934 935 </pre><div class="note" id="rfc.section.4.4.p.4"> 935 <p> <b>Note:</b> Because servers are free to ignore <a href="#header.range" class="smpl">Range</a>, many implementations will simply respond with <a href="p2-semantics.html#status.200" class="smpl">200 (OK)</a> if the requested ranges are invalid or not satisfiable. That is partly because most clients are prepared to receive a <a href="p2-semantics.html#status.200" class="smpl">200 (OK)</a> to complete the task (albeit less efficiently) and partly because clients might not stop making an invalid partial request 936 <p> <b>Note:</b> Because servers are free to ignore <a href="#header.range" class="smpl">Range</a>, many implementations will simply respond with the entire selected representation in a <a href="p2-semantics.html#status.200" class="smpl">200 (OK)</a> response if the requested ranges are invalid or not satisfiable. That is partly because most clients are prepared to receive 937 a <a href="p2-semantics.html#status.200" class="smpl">200 (OK)</a> to complete the task (albeit less efficiently) and partly because clients might not stop making an invalid partial request 936 938 until they have received a complete representation. Thus, clients cannot depend on receiving a <a href="#status.416" class="smpl">416 (Range Not Satisfiable)</a> response even when it is most appropriate. 937 939 </p> … … 1448 1450 </li> 1449 1451 <li><em>RFC2119</em> <a href="#rfc.xref.RFC2119.1">1.1</a>, <a href="#RFC2119"><b>8.1</b></a></li> 1450 <li><em>RFC2616</em> <a href="# rfc.xref.RFC2616.1">1</a>, <a href="#RFC2616"><b>8.2</b></a></li>1452 <li><em>RFC2616</em> <a href="#RFC2616"><b>8.2</b></a></li> 1451 1453 <li><em>RFC5226</em> <a href="#rfc.xref.RFC5226.1">5.1.1</a>, <a href="#RFC5226"><b>8.2</b></a><ul> 1452 1454 <li><em>Section 4.1</em> <a href="#rfc.xref.RFC5226.1">5.1.1</a></li> -
draft-ietf-httpbis/latest/p5-range.xml
r2208 r2217 141 141 <t> 142 142 This document defines HTTP/1.1 range requests, partial responses, and the 143 multipart/byteranges media type, obsoleting those parts previously defined 144 in <xref target="RFC2616"/>. Range requests are an &OPTIONAL; feature 143 multipart/byteranges media type. Range requests are an &OPTIONAL; feature 145 144 of HTTP, designed so that recipients not implementing this feature (or not 146 145 supporting it for the target resource) can respond as if it is a normal … … 275 274 If the selected representation is shorter than the specified 276 275 <x:ref>suffix-length</x:ref>, the entire representation is used. 277 For example (assuming a representation of length 10000): 276 </t> 277 <t> 278 Additional examples, assuming a representation of length 10000: 278 279 <list style="symbols"> 279 280 <t>The final 500 bytes (byte offsets 9500-9999, inclusive): … … 823 824 <t> 824 825 &Note; Because servers are free to ignore <x:ref>Range</x:ref>, many 825 implementations will simply respond with <x:ref>200 (OK)</x:ref> if the 826 implementations will simply respond with the entire selected representation 827 in a <x:ref>200 (OK)</x:ref> response if the 826 828 requested ranges are invalid or not satisfiable. That is partly because 827 829 most clients are prepared to receive a <x:ref>200 (OK)</x:ref> to
Note: See TracChangeset
for help on using the changeset viewer.