Changeset 1708 for draft-ietf-httpbis/latest/p5-range.xml
- Timestamp:
- 03/07/12 18:26:11 (10 years ago)
- File:
-
- 1 edited
Legend:
- Unmodified
- Added
- Removed
-
draft-ietf-httpbis/latest/p5-range.xml
r1697 r1708 312 312 <iref primary="true" item="206 Partial Content (status code)" x:for-anchor=""/> 313 313 <iref primary="true" item="Status Codes" subitem="206 Partial Content" x:for-anchor=""/> 314 <x:anchor-alias value="206 (Partial Content)"/> 314 315 <t> 315 316 The server has fulfilled the partial GET request for the resource. … … 354 355 <iref primary="true" item="416 Requested Range Not Satisfiable (status code)" x:for-anchor=""/> 355 356 <iref primary="true" item="Status Codes" subitem="416 Requested Range Not Satisfiable" x:for-anchor=""/> 357 <x:anchor-alias value="416 (Requested Range Not Satisfiable)"/> 356 358 <t> 357 359 A server &SHOULD; return a response with this status code if a request … … 377 379 <x:note> 378 380 <t> 379 &Note; Clients cannot depend on servers to send a 416 (Requested380 range not satisfiable)response instead of a 200 (OK) response for381 &Note; Clients cannot depend on servers to send a <x:ref>416 (Requested 382 Range Not Satisfiable)</x:ref> response instead of a 200 (OK) response for 381 383 an unsatisfiable Range header field, since not all servers 382 384 implement this header field. … … 442 444 </t> 443 445 <t> 444 When a client receives an incomplete 200 (OK) or 206 (Partial Content)446 When a client receives an incomplete 200 (OK) or <x:ref>206 (Partial Content)</x:ref> 445 447 response and already has one or more stored responses for the same method 446 448 and effective request URI, all of the stored responses with the same … … 456 458 </t> 457 459 <t> 458 If the new response is a 206 (Partial Content)response and at least one460 If the new response is a <x:ref>206 (Partial Content)</x:ref> response and at least one 459 461 of the matching stored responses is a 200 (OK), then the combined response 460 462 header fields consist of the most recent 200 response's header fields. … … 578 580 <t> 579 581 In the case of a byte range request: 580 A server sending a response with status code 416 (Requested range not581 satisfiable)&SHOULD; include a Content-Range field with a byte-range-resp-spec582 A server sending a response with status code <x:ref>416 (Requested Range Not 583 Satisfiable)</x:ref> &SHOULD; include a Content-Range field with a byte-range-resp-spec 582 584 of "*". The instance-length specifies the current length of 583 the selected resource. A response with status code 206 (Partial584 Content)&MUST-NOT; include a Content-Range field with a byte-range-resp-spec of "*".585 the selected resource. A response with status code <x:ref>206 (Partial Content)</x:ref> 586 &MUST-NOT; include a Content-Range field with a byte-range-resp-spec of "*". 585 587 </t> 586 588 <t> 587 589 The "Content-Range" header field has no meaning for status codes that do not 588 590 explicitly describe its semantic. Currently, only status codes 589 206 (Partial Content) and 416 (Requested range not satisfiable)describe591 <x:ref>206 (Partial Content)</x:ref> and <x:ref>416 (Requested Range Not Satisfiable)</x:ref> describe 590 592 the meaning of this header field. 591 593 </t> … … 678 680 validator for the selected representation of the target resource, then 679 681 the server &SHOULD; send the specified sub-range of the representation 680 using a 206 (Partial Content)response. If the validator does not match,682 using a <x:ref>206 (Partial Content)</x:ref> response. If the validator does not match, 681 683 then the server &SHOULD; send the entire representation using a 200 (OK) 682 684 response. … … 760 762 Otherwise, the byte-range-set is unsatisfiable. If the byte-range-set 761 763 is unsatisfiable, the server &SHOULD; return a response with a 762 416 (Requested range not satisfiable)status code. Otherwise, the server763 &SHOULD; return a response with a 206 (Partial Content)status code764 <x:ref>416 (Requested Range Not Satisfiable)</x:ref> status code. Otherwise, the server 765 &SHOULD; return a response with a <x:ref>206 (Partial Content)</x:ref> status code 764 766 containing the satisfiable ranges of the representation. 765 767 </t> … … 830 832 <t>The presence of a Range header field in an unconditional GET modifies 831 833 what is returned if the GET is otherwise successful. In other 832 words, the response carries a status code of 206 (Partial833 Content)instead of 200 (OK).</t>834 words, the response carries a status code of <x:ref>206 (Partial Content)</x:ref> 835 instead of 200 (OK).</t> 834 836 835 837 <t>The presence of a Range header field in a conditional GET (a request … … 1221 1223 <iref item="multipart/byteranges Media Type" primary="true"/> 1222 1224 <t> 1223 When an HTTP 206 (Partial Content)response message includes the1225 When an HTTP <x:ref>206 (Partial Content)</x:ref> response message includes the 1224 1226 content of multiple ranges (a response to a request for multiple 1225 1227 non-overlapping ranges), these are transmitted as a multipart
Note: See TracChangeset
for help on using the changeset viewer.