Changeset 438 for draft-ietf-httpbis/latest/p5-range.html
- Timestamp:
- 24/12/08 10:28:17 (13 years ago)
- File:
-
- 1 edited
Legend:
- Unmodified
- Added
- Removed
-
draft-ietf-httpbis/latest/p5-range.html
r435 r438 473 473 <tr> 474 474 <td class="header left"></td> 475 <td class="header right">December 1, 2008</td>475 <td class="header right">December 24, 2008</td> 476 476 </tr> 477 477 </table> … … 719 719 </p> 720 720 <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 721 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 "*".721 selected resource as a decimal number. 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 "*". 722 722 </p> 723 723 <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> … … 803 803 <a href="#rule.ranges-specifier" class="smpl">last-byte-pos</a> = 1*<a href="#notation" class="smpl">DIGIT</a> 804 804 </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 805 gives the byte-offset of the last byte in the range; that is, the byte positions specified are inclusive. Byte offsets start806 at zero.805 gives the byte-offset of the last byte in the range; that is, the byte positions specified are inclusive. Byte offsets are 806 decimal and start at zero. 807 807 </p> 808 808 <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 … … 815 815 <div id="rfc.figure.u.16"></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> 816 816 <a href="#rule.ranges-specifier" class="smpl">suffix-length</a> = 1*<a href="#notation" class="smpl">DIGIT</a> 817 </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. (That818 is, this form specifies the last N bytes of an entity-body.) If the entity is shorter than the specified suffix-length, the819 entire entity-body is used.817 </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 decimal suffix-length 818 value. (That is, this form specifies the last N bytes of an entity-body.) If the entity is shorter than the specified suffix-length, 819 the entire entity-body is used. 820 820 </p> 821 821 <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 … … 1196 1196 </ul> 1197 1197 <h2 id="rfc.section.D.7"><a href="#rfc.section.D.7">D.7</a> <a id="changes.since.05" href="#changes.since.05">Since draft-ietf-httpbis-p5-range-05</a></h2> 1198 <p id="rfc.section.D.7.p.1">Ongoing work on Custom Ranges (<<a href="http://tools.ietf.org/wg/httpbis/trac/ticket/85">http://tools.ietf.org/wg/httpbis/trac/ticket/85</a>>): 1198 <p id="rfc.section.D.7.p.1">Closed issues: </p> 1199 <ul> 1200 <li> <<a href="http://tools.ietf.org/wg/httpbis/trac/ticket/142">http://tools.ietf.org/wg/httpbis/trac/ticket/142</a>>: "State base for *-byte-pos and suffix-length" 1201 </li> 1202 </ul> 1203 <p id="rfc.section.D.7.p.2">Ongoing work on Custom Ranges (<<a href="http://tools.ietf.org/wg/httpbis/trac/ticket/85">http://tools.ietf.org/wg/httpbis/trac/ticket/85</a>>): 1199 1204 </p> 1200 1205 <ul> 1201 1206 <li>Remove bias in favor of byte ranges; allow custom ranges in ABNF.</li> 1202 1207 </ul> 1203 <p id="rfc.section.D.7.p. 2">Ongoing work on ABNF conversion (<<a href="http://tools.ietf.org/wg/httpbis/trac/ticket/36">http://tools.ietf.org/wg/httpbis/trac/ticket/36</a>>):1208 <p id="rfc.section.D.7.p.3">Ongoing work on ABNF conversion (<<a href="http://tools.ietf.org/wg/httpbis/trac/ticket/36">http://tools.ietf.org/wg/httpbis/trac/ticket/36</a>>): 1204 1209 </p> 1205 1210 <ul>
Note: See TracChangeset
for help on using the changeset viewer.