Changeset 2297 for draft-ietf-httpbis/latest
- Timestamp:
- 20/06/13 16:41:11 (10 years ago)
- Location:
- draft-ietf-httpbis/latest
- Files:
-
- 2 edited
Legend:
- Unmodified
- Added
- Removed
-
draft-ietf-httpbis/latest/p5-range.html
r2296 r2297 918 918 </p> 919 919 <p id="rfc.section.4.3.p.5">The combined response message body consists of the union of partial content ranges in the new response and each of the selected 920 responses. If the union consists of the entire range of the representation, then the client <em class="bcp14">MUST</em> record the combined response as if it were a complete <a href="p2-semantics.html#status.200" class="smpl">200 (OK)</a> response, including a <a href="p1-messaging.html#header.content-length" class="smpl">Content-Length</a> header field that reflects the complete length. Otherwise, the client <em class="bcp14">MUST</em> recordthe set of continuous ranges as one of the following: an incomplete <a href="p2-semantics.html#status.200" class="smpl">200 (OK)</a> response if the combined response is a prefix of the representation, a single <a href="#status.206" class="smpl">206 (Partial Content)</a> response containing a multipart/byteranges body, or multiple <a href="#status.206" class="smpl">206 (Partial Content)</a> responses, each with one continuous range that is indicated by a <a href="#header.content-range" class="smpl">Content-Range</a> header field.920 responses. If the union consists of the entire range of the representation, then the client <em class="bcp14">MUST</em> process the combined response as if it were a complete <a href="p2-semantics.html#status.200" class="smpl">200 (OK)</a> response, including a <a href="p1-messaging.html#header.content-length" class="smpl">Content-Length</a> header field that reflects the complete length. Otherwise, the client <em class="bcp14">MUST</em> process the set of continuous ranges as one of the following: an incomplete <a href="p2-semantics.html#status.200" class="smpl">200 (OK)</a> response if the combined response is a prefix of the representation, a single <a href="#status.206" class="smpl">206 (Partial Content)</a> response containing a multipart/byteranges body, or multiple <a href="#status.206" class="smpl">206 (Partial Content)</a> responses, each with one continuous range that is indicated by a <a href="#header.content-range" class="smpl">Content-Range</a> header field. 921 921 </p> 922 922 <div id="rfc.iref.29"></div> … … 933 933 Content-Range: bytes */47022 934 934 </pre><div class="note" id="rfc.section.4.4.p.4"> 935 <p> <b>Note:</b> Because servers are free to ignore <a href="#header.range" class="smpl">Range</a>, many implementations will simply respond with the entire selected representation in a <a href="p2-semantics.html#status.200" class="smpl">200 (OK)</a> response if the requested ranges are invalid or not satisfiable. That is partly because most clients are prepared to receive 936 a <a href="p2-semantics.html#status.200" class="smpl">200 (OK)</a> to complete the task (albeit less efficiently) and partly because clients might not stop making an invalid partial request 935 <p> <b>Note:</b> Because servers are free to ignore <a href="#header.range" class="smpl">Range</a>, many implementations will simply respond with the entire selected representation in a <a href="p2-semantics.html#status.200" class="smpl">200 (OK)</a> response. That is partly because most clients are prepared to receive a <a href="p2-semantics.html#status.200" class="smpl">200 (OK)</a> to complete the task (albeit less efficiently) and partly because clients might not stop making an invalid partial request 937 936 until they have received a complete representation. Thus, clients cannot depend on receiving a <a href="#status.416" class="smpl">416 (Range Not Satisfiable)</a> response even when it is most appropriate. 938 937 </p> -
draft-ietf-httpbis/latest/p5-range.xml
r2296 r2297 781 781 content ranges in the new response and each of the selected responses. 782 782 If the union consists of the entire range of the representation, then the 783 client &MUST; recordthe combined response as if it were a complete783 client &MUST; process the combined response as if it were a complete 784 784 <x:ref>200 (OK)</x:ref> response, including a <x:ref>Content-Length</x:ref> 785 785 header field that reflects the complete length. 786 Otherwise, the client &MUST; recordthe set of continuous ranges as one of786 Otherwise, the client &MUST; process the set of continuous ranges as one of 787 787 the following: 788 788 an incomplete <x:ref>200 (OK)</x:ref> response if the combined response is … … 826 826 &Note; Because servers are free to ignore <x:ref>Range</x:ref>, many 827 827 implementations will simply respond with the entire selected representation 828 in a <x:ref>200 (OK)</x:ref> response if the 829 requested ranges are invalid or not satisfiable. That is partly because 828 in a <x:ref>200 (OK)</x:ref> response. That is partly because 830 829 most clients are prepared to receive a <x:ref>200 (OK)</x:ref> to 831 830 complete the task (albeit less efficiently) and partly because clients
Note: See TracChangeset
for help on using the changeset viewer.