Changeset 1767
- Timestamp:
- 13/07/12 15:49:46 (10 years ago)
- Location:
- draft-ietf-httpbis/latest
- Files:
-
- 2 edited
Legend:
- Unmodified
- Added
- Removed
-
draft-ietf-httpbis/latest/p5-range.html
r1764 r1767 944 944 is 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 <a href="#status.416" class="smpl">416 (Requested Range Not Satisfiable)</a> status code. Otherwise, the server <em class="bcp14">SHOULD</em> return a response with a <a href="#status.206" class="smpl">206 (Partial Content)</a> status code containing the satisfiable ranges of the representation. 945 945 </p> 946 <p id="rfc.section.5.4.1.p.12">Examples of byte-ranges-specifier values (assuming a representation of length 10000): </p> 946 <p id="rfc.section.5.4.1.p.12">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 an HTTP payload, recipients <em class="bcp14">SHOULD</em> anticipate potentially large decimal numerals and prevent parsing errors due to integer conversion overflows. 947 </p> 948 <p id="rfc.section.5.4.1.p.13">Examples of byte-ranges-specifier values (assuming a representation of length 10000): </p> 947 949 <ul> 948 950 <li>The first 500 bytes (byte offsets 0-499, inclusive): … … 1495 1497 </li> 1496 1498 <li> <<a href="http://tools.ietf.org/wg/httpbis/trac/ticket/368">http://tools.ietf.org/wg/httpbis/trac/ticket/368</a>>: "note introduction of new IANA registries as normative changes" 1499 </li> 1500 <li> <<a href="http://tools.ietf.org/wg/httpbis/trac/ticket/369">http://tools.ietf.org/wg/httpbis/trac/ticket/369</a>>: "range units vs leading zeroes vs size" 1497 1501 </li> 1498 1502 </ul> -
draft-ietf-httpbis/latest/p5-range.xml
r1764 r1767 720 720 <x:anchor-alias value="suffix-byte-range-spec"/> 721 721 <x:anchor-alias value="suffix-length"/> 722 723 722 A byte range operation &MAY; specify a single range of bytes, or a set 724 723 of ranges within a single representation. … … 775 774 &SHOULD; return a response with a <x:ref>206 (Partial Content)</x:ref> status code 776 775 containing the satisfiable ranges of the representation. 776 </t> 777 <t> 778 In the byte range syntax, <x:ref>first-byte-pos</x:ref>, 779 <x:ref>last-byte-pos</x:ref>, and <x:ref>suffix-length</x:ref> are 780 expressed as decimal number of octets. Since there is no predefined limit 781 to the length of an HTTP payload, recipients &SHOULD; anticipate 782 potentially large decimal numerals and prevent parsing errors due to integer 783 conversion overflows. 777 784 </t> 778 785 <t> … … 1771 1778 "note introduction of new IANA registries as normative changes" 1772 1779 </t> 1780 <t> 1781 <eref target="http://tools.ietf.org/wg/httpbis/trac/ticket/369"/>: 1782 "range units vs leading zeroes vs size" 1783 </t> 1773 1784 </list> 1774 1785 </t>
Note: See TracChangeset
for help on using the changeset viewer.