Changeset 874 for draft-ietf-httpbis/latest/p5-range.xml
- Timestamp:
- 23/07/10 05:43:26 (12 years ago)
- File:
-
- 1 edited
Legend:
- Unmodified
- Added
- Removed
-
draft-ietf-httpbis/latest/p5-range.xml
r866 r874 316 316 <t> 317 317 HTTP/1.1 allows a client to request that only part (a range of) the 318 re sponse entitybe included within the response. HTTP/1.1 uses range318 representation be included within the response. HTTP/1.1 uses range 319 319 units in the Range (<xref target="header.range"/>) and Content-Range (<xref target="header.content-range"/>) 320 header fields. A n entitycan be broken down into subranges according320 header fields. A representation can be broken down into subranges according 321 321 to various structural units. 322 322 </t> … … 412 412 <section title="Combining Ranges" anchor="combining.byte.ranges"> 413 413 <t> 414 A response might transfer only a subrange of a n entity-body, either because414 A response might transfer only a subrange of a representation, either because 415 415 the request included one or more Range specifications, or because 416 a connection was brokenprematurely.416 a connection closed prematurely. 417 417 After several such transfers, a cache might have received several 418 ranges of the same entity-body.418 ranges of the same representation. 419 419 </t> 420 420 <t> … … 498 498 <x:anchor-alias value="other-range-resp-spec"/> 499 499 <t> 500 The "Content-Range" entity-header field is sent with a partial entity-bodyto501 specify where in the full entity-bodythe partial body should be500 The "Content-Range" entity-header field is sent with a partial representation to 501 specify where in the full representation the partial body should be 502 502 applied. Range units are defined in <xref target="range.units"/>. 503 503 </t> … … 522 522 </artwork></figure> 523 523 <t> 524 The header &SHOULD; indicate the total length of the full entity-body,524 The header &SHOULD; indicate the total length of the full representation, 525 525 unless this length is unknown or difficult to determine. The asterisk 526 526 "*" character means that the instance-length is unknown at the time … … 617 617 invalid, the server &SHOULD; treat the request as if the invalid Range 618 618 header field did not exist. (Normally, this means return a 200 619 response containing the full entity).619 response containing the full representation). 620 620 </t> 621 621 <t> … … 643 643 <x:anchor-alias value="If-Range-v"/> 644 644 <t> 645 If a client has a partial copy of a n entityin its cache, and wishes646 to have an up-to-date copy of the entire entityin its cache, it645 If a client has a partial copy of a representation in its cache, and wishes 646 to have an up-to-date copy of the entire representation in its cache, it 647 647 could use the Range request-header with a conditional GET (using 648 648 either or both of If-Unmodified-Since and If-Match.) However, if the … … 662 662 </artwork></figure> 663 663 <t> 664 If the client has no entity 664 If the client has no entity-tag for a representation, but does have a Last-Modified 665 665 date, it &MAY; use that date in an If-Range header. (The 666 666 server can distinguish between a valid HTTP-date and any form of … … 671 671 </t> 672 672 <t> 673 If the entity 673 If the entity-tag given in the If-Range header matches the current 674 674 cache validator for the representation, then the server &SHOULD; provide the 675 675 specified sub-range of the representation using a 206 (Partial Content) … … 744 744 A suffix-byte-range-spec is used to specify the suffix of the 745 745 representation body, of a length given by the suffix-length value. (That is, 746 this form specifies the last N bytes of a n entity-body.) If the746 this form specifies the last N bytes of a representation.) If the 747 747 representation is shorter than the specified suffix-length, the entire 748 748 representation is used. … … 751 751 If a syntactically valid byte-range-set includes at least one byte-range-spec 752 752 whose first-byte-pos is less than the current length of 753 the entity-body, or at least one suffix-byte-range-spec with a non-zero753 the representation, or at least one suffix-byte-range-spec with a non-zero 754 754 suffix-length, then the byte-range-set is satisfiable. 755 755 Otherwise, the byte-range-set is unsatisfiable. If the byte-range-set … … 760 760 </t> 761 761 <t> 762 Examples of byte-ranges-specifier values (assuming a n entity-bodyof762 Examples of byte-ranges-specifier values (assuming a representation of 763 763 length 10000): 764 764 <list style="symbols"> … … 820 820 possible, since Range supports efficient recovery from partially 821 821 failed transfers, and supports efficient partial retrieval of large 822 entities.822 representations. 823 823 </t> 824 824 <t> 825 825 If the server supports the Range header and the specified range or 826 ranges are appropriate for the entity:826 ranges are appropriate for the representation: 827 827 <list style="symbols"> 828 828 <t>The presence of a Range header in an unconditional GET modifies … … 845 845 <t> 846 846 If a proxy that supports ranges receives a Range request, forwards 847 the request to an inbound server, and receives an entire entityin847 the request to an inbound server, and receives an entire representation in 848 848 reply, it &SHOULD; only return the requested range to its client. It 849 849 &SHOULD; store the entire received response in its cache if that is
Note: See TracChangeset
for help on using the changeset viewer.