Changeset 196 for draft-ietf-httpbis/latest/p5-range.html
- Timestamp:
- 05/02/08 00:57:41 (14 years ago)
- File:
-
- 1 edited
Legend:
- Unmodified
- Added
- Removed
-
draft-ietf-httpbis/latest/p5-range.html
r189 r196 834 834 <h2 id="rfc.references.2"><a href="#rfc.section.9.2" id="rfc.section.9.2">9.2</a> Informative References 835 835 </h2> 836 <table summary="Informative References"> 836 <table summary="Informative References"> 837 837 <tr> 838 838 <td class="reference"><b id="RFC2616">[RFC2616]</b></td> 839 839 <td class="top"><a title="University of California, Irvine">Fielding, R.</a>, <a title="W3C">Gettys, J.</a>, <a title="Compaq Computer Corporation">Mogul, J.</a>, <a title="MIT Laboratory for Computer Science">Frystyk, H.</a>, <a title="Xerox Corporation">Masinter, L.</a>, <a title="Microsoft Corporation">Leach, P.</a>, and <a title="W3C">T. Berners-Lee</a>, “<a href="http://tools.ietf.org/html/rfc2616">Hypertext Transfer Protocol -- HTTP/1.1</a>”, RFC 2616, June 1999. 840 </td> 841 </tr> 842 <tr> 843 <td class="reference"><b id="RFC4288">[RFC4288]</b></td> 844 <td class="top"><a title="Sun Microsystems">Freed, N.</a> and <a>J. Klensin</a>, “<a href="http://tools.ietf.org/html/rfc4288">Media Type Specifications and Registration Procedures</a>”, BCP 13, RFC 4288, December 2005. 840 845 </td> 841 846 </tr> … … 861 866 <h1 id="rfc.section.A"><a href="#rfc.section.A">A.</a> <a id="internet.media.type.multipart.byteranges" href="#internet.media.type.multipart.byteranges">Internet Media Type multipart/byteranges</a></h1> 862 867 <p id="rfc.section.A.p.1">When an HTTP 206 (Partial Content) response message includes the content of multiple ranges (a response to a request for multiple 863 non-overlapping ranges), these are transmitted as a multipart message-body . The media type for this purpose is called "multipart/byteranges".868 non-overlapping ranges), these are transmitted as a multipart message-body <a href="#RFC2046" id="rfc.xref.RFC2046.1"><cite title="Multipurpose Internet Mail Extensions (MIME) Part Two: Media Types">[RFC2046]</cite></a>. The media type for this purpose is called "multipart/byteranges". The following is to be registered with IANA <a href="#RFC4288" id="rfc.xref.RFC4288.1"><cite title="Media Type Specifications and Registration Procedures">[RFC4288]</cite></a>. 864 869 </p> 865 870 <p id="rfc.section.A.p.2">The multipart/byteranges media type includes two or more parts, each with its own Content-Type and Content-Range fields. The … … 868 873 <p id="rfc.section.A.p.3"> </p> 869 874 <dl> 870 <dt> MediaType name:</dt>875 <dt>Type name:</dt> 871 876 <dd>multipart</dd> 872 <dt> Media subtype name:</dt>877 <dt>Subtype name:</dt> 873 878 <dd>byteranges</dd> 874 879 <dt>Required parameters:</dt> … … 880 885 <dt>Security considerations:</dt> 881 886 <dd>none</dd> 887 <dt>Interoperability considerations:</dt> 888 <dd>none</dd> 889 <dt>Published specification:</dt> 890 <dd>This specification (see <a href="#internet.media.type.multipart.byteranges" title="Internet Media Type multipart/byteranges">Appendix A</a>). 891 </dd> 892 <dt>Applications that use this media type:</dt> 893 <dt>Additional information:</dt> 894 <dd> 895 <dl> 896 <dt>Magic number(s):</dt> 897 <dd>none</dd> 898 <dt>File extension(s):</dt> 899 <dd>none</dd> 900 <dt>Macintosh file type code(s):</dt> 901 <dd>none</dd> 902 </dl> 903 </dd> 904 <dt>Person and email address to contact for further information:</dt> 905 <dd>See Authors Section.</dd> 906 <dt>Intended usage:</dt> 907 <dd>COMMON</dd> 908 <dt>Restrictions on usage:</dt> 909 <dd>none</dd> 910 <dt>Author/Change controller:</dt> 911 <dd>IESG</dd> 882 912 </dl> 883 913 <div id="rfc.figure.u.15"></div> … … 901 931 <ol> 902 932 <li>Additional CRLFs may precede the first boundary string in the entity.</li> 903 <li>Although <a href="#RFC2046" id="rfc.xref.RFC2046. 1"><cite title="Multipurpose Internet Mail Extensions (MIME) Part Two: Media Types">[RFC2046]</cite></a> permits the boundary string to be quoted, some existing implementations handle a quoted boundary string incorrectly.933 <li>Although <a href="#RFC2046" id="rfc.xref.RFC2046.2"><cite title="Multipurpose Internet Mail Extensions (MIME) Part Two: Media Types">[RFC2046]</cite></a> permits the boundary string to be quoted, some existing implementations handle a quoted boundary string incorrectly. 904 934 </li> 905 935 <li>A number of browsers and servers were coded to an early draft of the byteranges specification to use a media type of multipart/x-byteranges<span id="rfc.iref.m.3"></span><span id="rfc.iref.m.4"></span>, which is almost, but not quite compatible with the version documented in HTTP/1.1. … … 945 975 <h2 id="rfc.section.C.3"><a href="#rfc.section.C.3">C.3</a> Since draft-ietf-httpbis-p5-range-01 946 976 </h2> 977 <p id="rfc.section.C.3.p.1">Updated media type registrations to use RFC4288 template.</p> 947 978 <h1><a id="rfc.copyright" href="#rfc.copyright">Full Copyright Statement</a></h1> 948 979 <p>Copyright © The IETF Trust (2008).</p> … … 1058 1089 <li class="indline0"><a id="rfc.index.R" href="#rfc.index.R"><b>R</b></a><ul class="ind"> 1059 1090 <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">3.1</a>, <a class="iref" href="#rfc.xref.header.range.3">3.2</a>, <a class="iref" href="#rfc.iref.r.1"><b>5.4</b></a></li> 1060 <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> </li>1091 <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></li> 1061 1092 <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> 1062 1093 <li class="indline1"><em>RFC2616</em> <a class="iref" href="#RFC2616"><b>9.2</b></a>, <a class="iref" href="#rfc.xref.RFC2616.1">C.1</a></li> 1094 <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> 1063 1095 </ul> 1064 1096 </li>
Note: See TracChangeset
for help on using the changeset viewer.