Changeset 829 for draft-ietf-httpbis
- Timestamp:
- 25/06/10 13:01:53 (12 years ago)
- Location:
- draft-ietf-httpbis/latest
- Files:
-
- 2 edited
Legend:
- Unmodified
- Added
- Removed
-
draft-ietf-httpbis/latest/p5-range.html
r824 r829 400 400 <meta name="dct.creator" content="Reschke, J. F."> 401 401 <meta name="dct.identifier" content="urn:ietf:id:draft-ietf-httpbis-p5-range-latest"> 402 <meta name="dct.issued" scheme="ISO8601" content="2010-06- 02">402 <meta name="dct.issued" scheme="ISO8601" content="2010-06-25"> 403 403 <meta name="dct.replaces" content="urn:ietf:rfc:2616"> 404 404 <meta name="dct.abstract" content="The Hypertext Transfer Protocol (HTTP) is an application-level protocol for distributed, collaborative, hypermedia information systems. HTTP has been in use by the World Wide Web global information initiative since 1990. This document is Part 5 of the seven-part specification that defines the protocol referred to as "HTTP/1.1" and, taken together, obsoletes RFC 2616. Part 5 defines range-specific requests and the rules for constructing and combining responses to those requests."> … … 426 426 </tr> 427 427 <tr> 428 <td class="left">Expires: December 4, 2010</td>428 <td class="left">Expires: December 27, 2010</td> 429 429 <td class="right">J. Mogul</td> 430 430 </tr> … … 483 483 <tr> 484 484 <td class="left"></td> 485 <td class="right">June 2 , 2010</td>485 <td class="right">June 25, 2010</td> 486 486 </tr> 487 487 </tbody> … … 509 509 in progress”. 510 510 </p> 511 <p>This Internet-Draft will expire in December 4, 2010.</p>511 <p>This Internet-Draft will expire in December 27, 2010.</p> 512 512 <h1><a id="rfc.copyrightnotice" href="#rfc.copyrightnotice">Copyright Notice</a></h1> 513 513 <p>Copyright © 2010 IETF Trust and the persons identified as the document authors. All rights reserved.</p> … … 669 669 <h2 id="rfc.section.3.2"><a href="#rfc.section.3.2">3.2</a> <a id="status.416" href="#status.416">416 Requested Range Not Satisfiable</a></h2> 670 670 <p id="rfc.section.3.2.p.1">A server <em class="bcp14">SHOULD</em> return a response with this status code if a request included a Range request-header field (<a href="#header.range" id="rfc.xref.header.range.4" title="Range">Section 5.4</a>), and none of the ranges-specifier values in this field overlap the current extent of the selected resource, and the request 671 did not include an If-Range request-header field . (For byte-ranges, this means that the first-byte-pos of all of the byte-range-spec672 values were greater than the currentlength of the selected resource.)671 did not include an If-Range request-header field (<a href="#header.if-range" id="rfc.xref.header.if-range.2" title="If-Range">Section 5.3</a>). (For byte-ranges, this means that the first-byte-pos of all of the byte-range-spec values were greater than the current 672 length of the selected resource.) 673 673 </p> 674 674 <p id="rfc.section.3.2.p.2">When this status code is returned for a byte-range request, the response <em class="bcp14">SHOULD</em> include a Content-Range entity-header field specifying the current length of the selected resource (see <a href="#header.content-range" id="rfc.xref.header.content-range.3" title="Content-Range">Section 5.2</a>). This response <em class="bcp14">MUST NOT</em> use the multipart/byteranges content-type. … … 890 890 </li> 891 891 </ul> 892 <p id="rfc.section.5.4.2.p.5">In some cases, it might be more appropriate to use the If-Range header (see <a href="#header.if-range" id="rfc.xref.header.if-range. 2" title="If-Range">Section 5.3</a>) in addition to the Range header.892 <p id="rfc.section.5.4.2.p.5">In some cases, it might be more appropriate to use the If-Range header (see <a href="#header.if-range" id="rfc.xref.header.if-range.3" title="If-Range">Section 5.3</a>) in addition to the Range header. 893 893 </p> 894 894 <p id="rfc.section.5.4.2.p.6">If a proxy that supports ranges receives a Range request, forwards the request to an inbound server, and receives an entire … … 958 958 <td class="left">http</td> 959 959 <td class="left">standard</td> 960 <td class="left"> <a href="#header.if-range" id="rfc.xref.header.if-range. 3" title="If-Range">Section 5.3</a>960 <td class="left"> <a href="#header.if-range" id="rfc.xref.header.if-range.4" title="If-Range">Section 5.3</a> 961 961 </td> 962 962 </tr> … … 1164 1164 </p> 1165 1165 <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 1166 needed headers in a 206 response, this problem can be avoided. (Section <a href="#status.206" id="rfc.xref.status.206.2" title="206 Partial Content">3.1</a> and <a href="#header.if-range" id="rfc.xref.header.if-range. 4" title="If-Range">5.3</a>)1166 needed headers in a 206 response, this problem can be avoided. (Section <a href="#status.206" id="rfc.xref.status.206.2" title="206 Partial Content">3.1</a> and <a href="#header.if-range" id="rfc.xref.header.if-range.5" title="If-Range">5.3</a>) 1167 1167 </p> 1168 1168 <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. … … 1374 1374 <li class="indline1">Accept-Ranges <a class="iref" href="#rfc.iref.h.1"><b>5.1</b></a>, <a class="iref" href="#rfc.xref.header.accept-ranges.1">6.2</a></li> 1375 1375 <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">6.2</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> 1376 <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>, <a class="iref" href="#rfc.xref.header.if-range.3">6.2</a>, <a class="iref" href="#rfc.xref.header.if-range.4">B.1</a></li>1376 <li class="indline1">If-Range <a class="iref" href="#rfc.xref.header.if-range.1">3.1</a>, <a class="iref" href="#rfc.xref.header.if-range.2">3.2</a>, <a class="iref" href="#rfc.iref.h.3"><b>5.3</b></a>, <a class="iref" href="#rfc.xref.header.if-range.3">5.4.2</a>, <a class="iref" href="#rfc.xref.header.if-range.4">6.2</a>, <a class="iref" href="#rfc.xref.header.if-range.5">B.1</a></li> 1377 1377 <li class="indline1">Range <a class="iref" href="#rfc.xref.header.range.1">2</a>, <a class="iref" href="#rfc.xref.header.range.2">2</a>, <a class="iref" href="#rfc.xref.header.range.3">3.1</a>, <a class="iref" href="#rfc.xref.header.range.4">3.2</a>, <a class="iref" href="#rfc.iref.h.4"><b>5.4</b></a>, <a class="iref" href="#rfc.xref.header.range.5">6.2</a></li> 1378 1378 </ul> … … 1381 1381 </li> 1382 1382 <li class="indline0"><a id="rfc.index.I" href="#rfc.index.I"><b>I</b></a><ul class="ind"> 1383 <li class="indline1">If-Range header <a class="iref" href="#rfc.xref.header.if-range.1">3.1</a>, <a class="iref" href="#rfc. iref.i.1"><b>5.3</b></a>, <a class="iref" href="#rfc.xref.header.if-range.2">5.4.2</a>, <a class="iref" href="#rfc.xref.header.if-range.3">6.2</a>, <a class="iref" href="#rfc.xref.header.if-range.4">B.1</a></li>1383 <li class="indline1">If-Range header <a class="iref" href="#rfc.xref.header.if-range.1">3.1</a>, <a class="iref" href="#rfc.xref.header.if-range.2">3.2</a>, <a class="iref" href="#rfc.iref.i.1"><b>5.3</b></a>, <a class="iref" href="#rfc.xref.header.if-range.3">5.4.2</a>, <a class="iref" href="#rfc.xref.header.if-range.4">6.2</a>, <a class="iref" href="#rfc.xref.header.if-range.5">B.1</a></li> 1384 1384 </ul> 1385 1385 </li> -
draft-ietf-httpbis/latest/p5-range.xml
r824 r829 401 401 the ranges-specifier values in this field overlap the current extent 402 402 of the selected resource, and the request did not include an If-Range 403 request-header field . (For byte-ranges, this means that the first-byte-pos404 of all of the byte-range-spec values were greater than the405 current length of the selected resource.)403 request-header field (<xref target="header.if-range"/>). (For byte-ranges, 404 this means that the first-byte-pos of all of the byte-range-spec values were 405 greater than the current length of the selected resource.) 406 406 </t> 407 407 <t>
Note: See TracChangeset
for help on using the changeset viewer.