Changeset 99 for draft-ietf-httpbis/latest/p5-range.html
- Timestamp:
- 23/12/07 17:00:13 (15 years ago)
- File:
-
- 1 edited
Legend:
- Unmodified
- Added
- Removed
-
draft-ietf-httpbis/latest/p5-range.html
r97 r99 342 342 <link rel="Chapter" href="#rfc.section.9" title="9 References"> 343 343 <link rel="Appendix" title="A Internet Media Type multipart/byteranges" href="#rfc.section.A"> 344 <link rel="Appendix" title="B C hanges from RFC 2068" href="#rfc.section.B">344 <link rel="Appendix" title="B Compatibility with Previous Versions" href="#rfc.section.B"> 345 345 <meta name="generator" content="http://greenbytes.de/tech/webdav/rfc2629.xslt, Revision 1.353, 2007/12/11 23:20:44, XSLT vendor: SAXON 8.9 from Saxonica http://www.saxonica.com/"> 346 346 <link rel="schema.DC" href="http://purl.org/dc/elements/1.1/"> … … 512 512 <li class="tocline0"><a href="#rfc.authors">Authors' Addresses</a></li> 513 513 <li class="tocline0">A. <a href="#internet.media.type.multipart.byteranges">Internet Media Type multipart/byteranges</a></li> 514 <li class="tocline0">B. <a href="#changes.from.rfc.2068">Changes from RFC 2068</a></li> 514 <li class="tocline0">B. <a href="#compatibility">Compatibility with Previous Versions</a><ul class="toc"> 515 <li class="tocline1">B.1 <a href="#changes.from.rfc.2068">Changes from RFC 2068</a></li> 516 <li class="tocline1">B.2 <a href="#changes.from.rfc.2616">Changes from RFC 2616</a></li> 517 </ul> 518 </li> 515 519 <li class="tocline0"><a href="#rfc.ipr">Intellectual Property and Copyright Statements</a></li> 516 520 <li class="tocline0"><a href="#rfc.index">Index</a></li> … … 659 663 </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 660 664 ranges), these are transmitted as a multipart message. The multipart media type used for this purpose is "multipart/byteranges" 661 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 </a> for a compatibility issue.665 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. 662 666 </p> 663 667 <p id="rfc.section.5.2.p.11">A response to a request for a single range <em class="bcp14">MUST NOT</em> be sent using the multipart/byteranges media type. A response to a request for multiple ranges, whose result is a single range, <em class="bcp14">MAY</em> be sent as a multipart/byteranges media type with one part. A client that cannot decode a multipart/byteranges message <em class="bcp14">MUST NOT</em> ask for multiple byte-ranges in a single request. … … 869 873 </li> 870 874 </ol> 871 <h1 id="rfc.section.B"><a href="#rfc.section.B">B.</a> <a id="changes.from.rfc.2068" href="#changes.from.rfc.2068">Changes from RFC 2068</a></h1> 872 <p id="rfc.section.B.p.1">There are situations where a server (especially a proxy) does not know the full length of a response but is capable of serving 875 <h1 id="rfc.section.B"><a href="#rfc.section.B">B.</a> <a id="compatibility" href="#compatibility">Compatibility with Previous Versions</a></h1> 876 <h2 id="rfc.section.B.1"><a href="#rfc.section.B.1">B.1</a> <a id="changes.from.rfc.2068" href="#changes.from.rfc.2068">Changes from RFC 2068</a></h2> 877 <p id="rfc.section.B.1.p.1">There are situations where a server (especially a proxy) does not know the full length of a response but is capable of serving 873 878 a byterange request. We therefore need a mechanism to allow byteranges with a content-range not indicating the full length 874 879 of the message. (<a href="#header.content-range" id="rfc.xref.header.content-range.4" title="Content-Range">Section 5.2</a>) 875 880 </p> 876 <p id="rfc.section.B. p.2">Range request responses would become very verbose if all meta-data were always returned; by allowing the server to only send881 <p id="rfc.section.B.1.p.2">Range request responses would become very verbose if all meta-data were always returned; by allowing the server to only send 877 882 needed headers in a 206 response, this problem can be avoided. 878 883 </p> 879 <p id="rfc.section.B. p.3">Fix problem with unsatisfiable range requests; there are two cases: syntactic problems, and range doesn't exist in the document.884 <p id="rfc.section.B.1.p.3">Fix problem with unsatisfiable range requests; there are two cases: syntactic problems, and range doesn't exist in the document. 880 885 The 416 status code was needed to resolve this ambiguity needed to indicate an error for a byte range request that falls outside 881 886 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.5" title="Content-Range">5.2</a>) 882 887 </p> 888 <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> 883 889 <h1><a id="rfc.copyright" href="#rfc.copyright">Full Copyright Statement</a></h1> 884 890 <p>Copyright © The IETF Trust (2007).</p> … … 918 924 </li> 919 925 <li class="indline0"><a id="rfc.index.4" href="#rfc.index.4"><b>4</b></a><ul class="ind"> 920 <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 </a></li>926 <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> 921 927 </ul> 922 928 </li> … … 926 932 </li> 927 933 <li class="indline0"><a id="rfc.index.C" href="#rfc.index.C"><b>C</b></a><ul class="ind"> 928 <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">B </a>, <a class="iref" href="#rfc.xref.header.content-range.5">B</a></li>934 <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">B.1</a>, <a class="iref" href="#rfc.xref.header.content-range.5">B.1</a></li> 929 935 </ul> 930 936 </li> … … 960 966 <ul class="ind"> 961 967 <li class="indline1">Accept-Ranges <a class="iref" href="#rfc.iref.h.1"><b>5.1</b></a></li> 962 <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">B </a>, <a class="iref" href="#rfc.xref.header.content-range.5">B</a></li>968 <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">B.1</a>, <a class="iref" href="#rfc.xref.header.content-range.5">B.1</a></li> 963 969 <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></li> 964 970 <li class="indline1">Range <a class="iref" href="#rfc.xref.header.range.1">2</a>, <a class="iref" href="#rfc.xref.header.range.2">3.1</a>, <a class="iref" href="#rfc.xref.header.range.3">3.2</a>, <a class="iref" href="#rfc.iref.h.4"><b>5.4</b></a></li> … … 1001 1007 <ul class="ind"> 1002 1008 <li class="indline1">206 Partial Content <a class="iref" href="#rfc.iref.s.1"><b>3.1</b></a></li> 1003 <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 </a></li>1009 <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> 1004 1010 </ul> 1005 1011 </li>
Note: See TracChangeset
for help on using the changeset viewer.