Changeset 253 for draft-ietf-httpbis/latest/p5-range.html
- Timestamp:
- 31/05/08 14:54:09 (14 years ago)
- File:
-
- 1 edited
Legend:
- Unmodified
- Added
- Removed
-
draft-ietf-httpbis/latest/p5-range.html
r252 r253 133 133 table { 134 134 margin-left: 2em; 135 } 136 table.tt { 137 vertical-align: top; 138 } 139 table.full { 140 border-style: outset; 141 border-width: 1px; 142 } 143 table.headers { 144 border-style: outset; 145 border-width: 1px; 146 } 147 table.tt td { 148 vertical-align: top; 149 } 150 table.full td { 151 border-style: inset; 152 border-width: 1px; 153 } 154 table.tt th { 155 vertical-align: top; 156 } 157 table.full th { 158 border-style: inset; 159 border-width: 1px; 160 } 161 table.headers th { 162 border-style: none none inset none; 163 border-width: 1px; 135 164 } 136 165 table.header { … … 444 473 <tr> 445 474 <td class="header left"></td> 446 <td class="header right">May 3 0, 2008</td>475 <td class="header right">May 31, 2008</td> 447 476 </tr> 448 477 </table> … … 503 532 </ul> 504 533 </li> 505 <li class="tocline0">7. <a href="#IANA.considerations">IANA Considerations</a></li> 534 <li class="tocline0">7. <a href="#IANA.considerations">IANA Considerations</a><ul class="toc"> 535 <li class="tocline1">7.1 <a href="#message.header.registration">Message Header Registration</a></li> 536 </ul> 537 </li> 506 538 <li class="tocline0">8. <a href="#security.considerations">Security Considerations</a></li> 507 539 <li class="tocline0">9. <a href="#ack">Acknowledgments</a></li> … … 804 836 </p> 805 837 <h1 id="rfc.section.7"><a href="#rfc.section.7">7.</a> <a id="IANA.considerations" href="#IANA.considerations">IANA Considerations</a></h1> 806 <p id="rfc.section.7.p.1"> <span class="comment">[rfc.comment.1: TBD.]</span> 807 </p> 838 <h2 id="rfc.section.7.1"><a href="#rfc.section.7.1">7.1</a> <a id="message.header.registration" href="#message.header.registration">Message Header Registration</a></h2> 839 <p id="rfc.section.7.1.p.1">The Message Header Registry located at <<a href="http://www.iana.org/assignments/message-headers/message-header-index.html">http://www.iana.org/assignments/message-headers/message-header-index.html</a>> should be updated with the permanent registrations below (see <a href="#RFC3864" id="rfc.xref.RFC3864.1"><cite title="Registration Procedures for Message Header Fields">[RFC3864]</cite></a>): 840 </p> 841 <div id="rfc.table.u.1"> 842 <table summary="" class="tt full" cellpadding="3" cellspacing="0"> 843 <thead> 844 <tr> 845 <th>Header Field Name</th> 846 <th>Protocol</th> 847 <th>Status</th> 848 <th>Reference</th> 849 </tr> 850 </thead> 851 <tbody> 852 <tr> 853 <td>Accept-Ranges</td> 854 <td>http</td> 855 <td>standard</td> 856 <td> <a href="#header.accept-ranges" id="rfc.xref.header.accept-ranges.1" title="Accept-Ranges">Section 6.1</a> 857 </td> 858 </tr> 859 <tr> 860 <td>Content-Range</td> 861 <td>http</td> 862 <td>standard</td> 863 <td> <a href="#header.content-range" id="rfc.xref.header.content-range.4" title="Content-Range">Section 6.2</a> 864 </td> 865 </tr> 866 <tr> 867 <td>If-Range</td> 868 <td>http</td> 869 <td>standard</td> 870 <td> <a href="#header.if-range" id="rfc.xref.header.if-range.3" title="If-Range">Section 6.3</a> 871 </td> 872 </tr> 873 <tr> 874 <td>Range</td> 875 <td>http</td> 876 <td>standard</td> 877 <td> <a href="#header.range" id="rfc.xref.header.range.4" title="Range">Section 6.4</a> 878 </td> 879 </tr> 880 </tbody> 881 </table> 882 </div> 883 <p id="rfc.section.7.1.p.2">The change controller is: "IETF (iesg@ietf.org) - Internet Engineering Task Force".</p> 808 884 <h1 id="rfc.section.8"><a href="#rfc.section.8">8.</a> <a id="security.considerations" href="#security.considerations">Security Considerations</a></h1> 809 885 <p id="rfc.section.8.p.1">No additional security considerations have been identified beyond those applicable to HTTP in general <a href="#Part1" id="rfc.xref.Part1.7"><cite title="HTTP/1.1, part 1: URIs, Connections, and Message Parsing">[Part1]</cite></a>. … … 852 928 <h2 id="rfc.references.2"><a href="#rfc.section.10.2" id="rfc.section.10.2">10.2</a> Informative References 853 929 </h2> 854 <table summary="Informative References"> 930 <table summary="Informative References"> 855 931 <tr> 856 932 <td class="reference"><b id="RFC2616">[RFC2616]</b></td> 857 933 <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. 934 </td> 935 </tr> 936 <tr> 937 <td class="reference"><b id="RFC3864">[RFC3864]</b></td> 938 <td class="top"><a title="Nine by Nine">Klyne, G.</a>, <a title="BEA Systems">Nottingham, M.</a>, and <a title="HP Labs">J. Mogul</a>, “<a href="http://tools.ietf.org/html/rfc3864">Registration Procedures for Message Header Fields</a>”, BCP 90, RFC 3864, September 2004. 858 939 </td> 859 940 </tr> … … 958 1039 <p id="rfc.section.B.1.p.1">Transfer-coding and message lengths all interact in ways that required fixing exactly when chunked encoding is used (to allow 959 1040 for transfer encoding that may not be self delimiting); it was important to straighten out exactly how message lengths are 960 computed. (<a href="#header.content-range" id="rfc.xref.header.content-range. 4" title="Content-Range">Section 6.2</a>, see also <a href="#Part1" id="rfc.xref.Part1.8"><cite title="HTTP/1.1, part 1: URIs, Connections, and Message Parsing">[Part1]</cite></a>, <a href="#Part3" id="rfc.xref.Part3.1"><cite title="HTTP/1.1, part 3: Message Payload and Content Negotiation">[Part3]</cite></a> and <a href="#Part6" id="rfc.xref.Part6.1"><cite title="HTTP/1.1, part 6: Caching">[Part6]</cite></a>)1041 computed. (<a href="#header.content-range" id="rfc.xref.header.content-range.5" title="Content-Range">Section 6.2</a>, see also <a href="#Part1" id="rfc.xref.Part1.8"><cite title="HTTP/1.1, part 1: URIs, Connections, and Message Parsing">[Part1]</cite></a>, <a href="#Part3" id="rfc.xref.Part3.1"><cite title="HTTP/1.1, part 3: Message Payload and Content Negotiation">[Part3]</cite></a> and <a href="#Part6" id="rfc.xref.Part6.1"><cite title="HTTP/1.1, part 6: Caching">[Part6]</cite></a>) 961 1042 </p> 962 1043 <p id="rfc.section.B.1.p.2">There are situations where a server (especially a proxy) does not know the full length of a response but is capable of serving 963 1044 a byterange request. We therefore need a mechanism to allow byteranges with a content-range not indicating the full length 964 of the message. (<a href="#header.content-range" id="rfc.xref.header.content-range. 5" title="Content-Range">Section 6.2</a>)1045 of the message. (<a href="#header.content-range" id="rfc.xref.header.content-range.6" title="Content-Range">Section 6.2</a>) 965 1046 </p> 966 1047 <p id="rfc.section.B.1.p.3">Range request responses would become very verbose if all meta-data were always returned; by allowing the server to only send 967 needed headers in a 206 response, this problem can be avoided. (Section <a href="#status.206" id="rfc.xref.status.206.1" title="206 Partial Content">4.1</a> and <a href="#header.if-range" id="rfc.xref.header.if-range. 3" title="If-Range">6.3</a>)1048 needed headers in a 206 response, this problem can be avoided. (Section <a href="#status.206" id="rfc.xref.status.206.1" title="206 Partial Content">4.1</a> and <a href="#header.if-range" id="rfc.xref.header.if-range.4" title="If-Range">6.3</a>) 968 1049 </p> 969 1050 <p id="rfc.section.B.1.p.4">Fix problem with unsatisfiable range requests; there are two cases: syntactic problems, and range doesn't exist in the document. 970 1051 The 416 status code was needed to resolve this ambiguity needed to indicate an error for a byte range request that falls outside 971 of the actual contents of a document. (Section <a href="#status.416" id="rfc.xref.status.416.2" title="416 Requested Range Not Satisfiable">4.2</a>, <a href="#header.content-range" id="rfc.xref.header.content-range. 6" title="Content-Range">6.2</a>)1052 of the actual contents of a document. (Section <a href="#status.416" id="rfc.xref.status.416.2" title="416 Requested Range Not Satisfiable">4.2</a>, <a href="#header.content-range" id="rfc.xref.header.content-range.7" title="Content-Range">6.2</a>) 972 1053 </p> 973 1054 <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> … … 1003 1084 </ul> 1004 1085 <h2 id="rfc.section.C.4"><a href="#rfc.section.C.4">C.4</a> <a id="changes.since.02" href="#changes.since.02">Since draft-ietf-httpbis-p5-range-02</a></h2> 1005 <p id="rfc.section.C.4.p.1">None.</p> 1086 <p id="rfc.section.C.4.p.1">Ongoing work on IANA Message Header Registration (<<a href="http://www3.tools.ietf.org/wg/httpbis/trac/ticket/40">http://www3.tools.ietf.org/wg/httpbis/trac/ticket/40</a>>): 1087 </p> 1088 <ul> 1089 <li>Reference RFC 3984, and update header registrations for headers defined in this document.</li> 1090 </ul> 1006 1091 <h1><a id="rfc.copyright" href="#rfc.copyright">Full Copyright Statement</a></h1> 1007 1092 <p>This document is subject to the rights, licenses and restrictions contained in BCP 78, and except as set forth therein, the … … 1042 1127 </li> 1043 1128 <li class="indline0"><a id="rfc.index.A" href="#rfc.index.A"><b>A</b></a><ul class="ind"> 1044 <li class="indline1">Accept-Ranges header <a class="iref" href="#rfc.iref.a.1"><b>6.1</b></a> </li>1129 <li class="indline1">Accept-Ranges header <a class="iref" href="#rfc.iref.a.1"><b>6.1</b></a>, <a class="iref" href="#rfc.xref.header.accept-ranges.1">7.1</a></li> 1045 1130 </ul> 1046 1131 </li> 1047 1132 <li class="indline0"><a id="rfc.index.C" href="#rfc.index.C"><b>C</b></a><ul class="ind"> 1048 <li class="indline1">Content-Range header <a class="iref" href="#rfc.xref.header.content-range.1">3</a>, <a class="iref" href="#rfc.xref.header.content-range.2">4.1</a>, <a class="iref" href="#rfc.xref.header.content-range.3">4.2</a>, <a class="iref" href="#rfc.iref.c.1"><b>6.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>, <a class="iref" href="#rfc.xref.header.content-range.6">B.1</a></li>1133 <li class="indline1">Content-Range header <a class="iref" href="#rfc.xref.header.content-range.1">3</a>, <a class="iref" href="#rfc.xref.header.content-range.2">4.1</a>, <a class="iref" href="#rfc.xref.header.content-range.3">4.2</a>, <a class="iref" href="#rfc.iref.c.1"><b>6.2</b></a>, <a class="iref" href="#rfc.xref.header.content-range.4">7.1</a>, <a class="iref" href="#rfc.xref.header.content-range.5">B.1</a>, <a class="iref" href="#rfc.xref.header.content-range.6">B.1</a>, <a class="iref" href="#rfc.xref.header.content-range.7">B.1</a></li> 1049 1134 </ul> 1050 1135 </li> … … 1079 1164 <li class="indline1">Headers 1080 1165 <ul class="ind"> 1081 <li class="indline1">Accept-Ranges <a class="iref" href="#rfc.iref.h.1"><b>6.1</b></a> </li>1082 <li class="indline1">Content-Range <a class="iref" href="#rfc.xref.header.content-range.1">3</a>, <a class="iref" href="#rfc.xref.header.content-range.2">4.1</a>, <a class="iref" href="#rfc.xref.header.content-range.3">4.2</a>, <a class="iref" href="#rfc.iref.h.2"><b>6.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>, <a class="iref" href="#rfc.xref.header.content-range.6">B.1</a></li>1083 <li class="indline1">If-Range <a class="iref" href="#rfc.xref.header.if-range.1">4.1</a>, <a class="iref" href="#rfc.iref.h.3"><b>6.3</b></a>, <a class="iref" href="#rfc.xref.header.if-range.2">6.4.2</a>, <a class="iref" href="#rfc.xref.header.if-range.3"> B.1</a></li>1084 <li class="indline1">Range <a class="iref" href="#rfc.xref.header.range.1">3</a>, <a class="iref" href="#rfc.xref.header.range.2">4.1</a>, <a class="iref" href="#rfc.xref.header.range.3">4.2</a>, <a class="iref" href="#rfc.iref.h.4"><b>6.4</b></a> </li>1166 <li class="indline1">Accept-Ranges <a class="iref" href="#rfc.iref.h.1"><b>6.1</b></a>, <a class="iref" href="#rfc.xref.header.accept-ranges.1">7.1</a></li> 1167 <li class="indline1">Content-Range <a class="iref" href="#rfc.xref.header.content-range.1">3</a>, <a class="iref" href="#rfc.xref.header.content-range.2">4.1</a>, <a class="iref" href="#rfc.xref.header.content-range.3">4.2</a>, <a class="iref" href="#rfc.iref.h.2"><b>6.2</b></a>, <a class="iref" href="#rfc.xref.header.content-range.4">7.1</a>, <a class="iref" href="#rfc.xref.header.content-range.5">B.1</a>, <a class="iref" href="#rfc.xref.header.content-range.6">B.1</a>, <a class="iref" href="#rfc.xref.header.content-range.7">B.1</a></li> 1168 <li class="indline1">If-Range <a class="iref" href="#rfc.xref.header.if-range.1">4.1</a>, <a class="iref" href="#rfc.iref.h.3"><b>6.3</b></a>, <a class="iref" href="#rfc.xref.header.if-range.2">6.4.2</a>, <a class="iref" href="#rfc.xref.header.if-range.3">7.1</a>, <a class="iref" href="#rfc.xref.header.if-range.4">B.1</a></li> 1169 <li class="indline1">Range <a class="iref" href="#rfc.xref.header.range.1">3</a>, <a class="iref" href="#rfc.xref.header.range.2">4.1</a>, <a class="iref" href="#rfc.xref.header.range.3">4.2</a>, <a class="iref" href="#rfc.iref.h.4"><b>6.4</b></a>, <a class="iref" href="#rfc.xref.header.range.4">7.1</a></li> 1085 1170 </ul> 1086 1171 </li> … … 1088 1173 </li> 1089 1174 <li class="indline0"><a id="rfc.index.I" href="#rfc.index.I"><b>I</b></a><ul class="ind"> 1090 <li class="indline1">If-Range header <a class="iref" href="#rfc.xref.header.if-range.1">4.1</a>, <a class="iref" href="#rfc.iref.i.1"><b>6.3</b></a>, <a class="iref" href="#rfc.xref.header.if-range.2">6.4.2</a>, <a class="iref" href="#rfc.xref.header.if-range.3"> B.1</a></li>1175 <li class="indline1">If-Range header <a class="iref" href="#rfc.xref.header.if-range.1">4.1</a>, <a class="iref" href="#rfc.iref.i.1"><b>6.3</b></a>, <a class="iref" href="#rfc.xref.header.if-range.2">6.4.2</a>, <a class="iref" href="#rfc.xref.header.if-range.3">7.1</a>, <a class="iref" href="#rfc.xref.header.if-range.4">B.1</a></li> 1091 1176 </ul> 1092 1177 </li> … … 1119 1204 </li> 1120 1205 <li class="indline0"><a id="rfc.index.R" href="#rfc.index.R"><b>R</b></a><ul class="ind"> 1121 <li class="indline1">Range header <a class="iref" href="#rfc.xref.header.range.1">3</a>, <a class="iref" href="#rfc.xref.header.range.2">4.1</a>, <a class="iref" href="#rfc.xref.header.range.3">4.2</a>, <a class="iref" href="#rfc.iref.r.1"><b>6.4</b></a> </li>1206 <li class="indline1">Range header <a class="iref" href="#rfc.xref.header.range.1">3</a>, <a class="iref" href="#rfc.xref.header.range.2">4.1</a>, <a class="iref" href="#rfc.xref.header.range.3">4.2</a>, <a class="iref" href="#rfc.iref.r.1"><b>6.4</b></a>, <a class="iref" href="#rfc.xref.header.range.4">7.1</a></li> 1122 1207 <li class="indline1"><em>RFC2046</em> <a class="iref" href="#RFC2046"><b>10.1</b></a>, <a class="iref" href="#rfc.xref.RFC2046.1">A</a>, <a class="iref" href="#rfc.xref.RFC2046.2">A</a></li> 1123 1208 <li class="indline1"><em>RFC2119</em> <a class="iref" href="#rfc.xref.RFC2119.1">1.1</a>, <a class="iref" href="#RFC2119"><b>10.1</b></a></li> 1124 1209 <li class="indline1"><em>RFC2616</em> <a class="iref" href="#RFC2616"><b>10.2</b></a>, <a class="iref" href="#rfc.xref.RFC2616.1">C.1</a></li> 1210 <li class="indline1"><em>RFC3864</em> <a class="iref" href="#rfc.xref.RFC3864.1">7.1</a>, <a class="iref" href="#RFC3864"><b>10.2</b></a></li> 1125 1211 <li class="indline1"><em>RFC4288</em> <a class="iref" href="#RFC4288"><b>10.2</b></a>, <a class="iref" href="#rfc.xref.RFC4288.1">A</a></li> 1126 1212 </ul>
Note: See TracChangeset
for help on using the changeset viewer.