Changeset 1544 for draft-ietf-httpbis/latest/p5-range.xml
- Timestamp:
- 21/02/12 02:12:49 (9 years ago)
- File:
-
- 1 edited
Legend:
- Unmodified
- Added
- Removed
-
draft-ietf-httpbis/latest/p5-range.xml
r1543 r1544 416 416 Content-Length header field is present in the response, its 417 417 value &MUST; match the actual number of octets transmitted in the 418 message -body.418 message body. 419 419 </t> 420 420 <t> … … 556 556 </t> 557 557 <t> 558 The combined response message -body consists of the union of partial558 The combined response message body consists of the union of partial 559 559 content ranges in the new response and each of the selected responses. 560 560 If the union consists of the entire range of the representation, then the … … 786 786 <t> 787 787 Byte range specifications in HTTP apply to the sequence of bytes in 788 the representation body (not necessarily the same as the message -body).788 the representation body (not necessarily the same as the message body). 789 789 </t> 790 790 <t anchor="rule.ranges-specifier"> … … 1409 1409 content of multiple ranges (a response to a request for multiple 1410 1410 non-overlapping ranges), these are transmitted as a multipart 1411 message -body (<xref target="RFC2046" x:fmt="," x:sec="5.1"/>). The media type for this purpose is called1411 message body (<xref target="RFC2046" x:fmt="," x:sec="5.1"/>). The media type for this purpose is called 1412 1412 "multipart/byteranges". The following is to be registered with IANA <xref target="RFC4288"/>. 1413 1413 </t>
Note: See TracChangeset
for help on using the changeset viewer.