Changeset 2052 for draft-ietf-httpbis/latest/p5-range.xml
- Timestamp:
- 16/12/12 03:46:23 (9 years ago)
- File:
-
- 1 edited
Legend:
- Unmodified
- Added
- Removed
-
draft-ietf-httpbis/latest/p5-range.xml
r2046 r2052 273 273 header field, it &SHOULD-NOT; include other representation header fields. 274 274 Otherwise, the response &MUST; include all of the representation header 275 fields that would have been returnedwith a <x:ref>200 (OK)</x:ref> response275 fields that would have been sent with a <x:ref>200 (OK)</x:ref> response 276 276 to the same request. 277 277 </t> … … 286 286 <x:anchor-alias value="416 (Requested Range Not Satisfiable)"/> 287 287 <t> 288 A server &SHOULD; returna response with this status code if a request288 A server &SHOULD; send a response with this status code if a request 289 289 included a <x:ref>Range</x:ref> header field (<xref target="header.range"/>), 290 290 and none of the ranges-specifier values in this field overlap the current … … 296 296 </t> 297 297 <t> 298 When this status code is returnedfor a byte-range request, the298 When this status code is sent for a byte-range request, the 299 299 response &SHOULD; include a <x:ref>Content-Range</x:ref> header field 300 300 specifying the current length of the representation (see <xref target="header.content-range"/>). … … 359 359 <t> 360 360 When a client asks for multiple ranges in one request, the 361 server &SHOULD; returnthem in the order that they appeared in the361 server &SHOULD; send them in the order that they appeared in the 362 362 request. 363 363 </t> … … 558 558 syntactically invalid, or if it might be seen as a denial-of-service 559 559 attack), the server &SHOULD; treat the request as if the invalid <x:ref>Range</x:ref> 560 header field did not exist. (Normally, this means returna <x:ref>200 (OK)</x:ref>560 header field did not exist. (Normally, this means send a <x:ref>200 (OK)</x:ref> 561 561 response containing the full representation). 562 562 </t> … … 690 690 suffix-length, then the byte-range-set is satisfiable. 691 691 Otherwise, the byte-range-set is unsatisfiable. If the byte-range-set 692 is unsatisfiable, the server &SHOULD; returna response with a692 is unsatisfiable, the server &SHOULD; send a response with a 693 693 <x:ref>416 (Requested Range Not Satisfiable)</x:ref> status code. Otherwise, the server 694 &SHOULD; returna response with a <x:ref>206 (Partial Content)</x:ref> status code694 &SHOULD; send a response with a <x:ref>206 (Partial Content)</x:ref> status code 695 695 containing the satisfiable ranges of the representation. 696 696 </t> … … 768 768 <list style="symbols"> 769 769 <t>The presence of a Range header field in an unconditional GET modifies 770 what is returnedif the GET is otherwise successful. In other770 what is sent if the GET is otherwise successful. In other 771 771 words, the response carries a status code of <x:ref>206 (Partial Content)</x:ref> 772 772 instead of <x:ref>200 (OK)</x:ref>.</t> … … 776 776 <x:ref>If-None-Match</x:ref>, or one or both of 777 777 <x:ref>If-Unmodified-Since</x:ref> and <x:ref>If-Match</x:ref>) modifies 778 what is returnedif the GET is otherwise successful and the778 what is sent if the GET is otherwise successful and the 779 779 condition is true. It does not affect the <x:ref>304 (Not Modified)</x:ref> 780 response returnedif the conditional is false.</t>780 response sent if the conditional is false.</t> 781 781 </list> 782 782 </t> … … 789 789 If a proxy that supports ranges receives a Range request, forwards 790 790 the request to an inbound server, and receives an entire representation in 791 reply, it &MAY; only returnthe requested range to its client.791 reply, it &MAY; only send the requested range to its client. 792 792 </t> 793 793 </section> … … 1307 1307 </t> 1308 1308 <t> 1309 Servers are given more leeway in what they returnto a range request,1309 Servers are given more leeway in what they send to a range request, 1310 1310 in order to mitigate malicious (or just greedy) clients. 1311 1311 </t> … … 1371 1371 <x:ref>Content-Range</x:ref> = byte-content-range-spec / other-content-range-spec 1372 1372 1373 <x:ref>HTTP-date</x:ref> = <HTTP-date, defined in [Part2], Section 8.1.1.1>1373 <x:ref>HTTP-date</x:ref> = <HTTP-date, defined in [Part2], Section 7.1.1.1> 1374 1374 1375 1375 <x:ref>If-Range</x:ref> = entity-tag / HTTP-date
Note: See TracChangeset
for help on using the changeset viewer.