Ignore:
Timestamp:
Jul 22, 2010, 10:43:26 PM (9 years ago)
Author:
fielding@…
Message:

Addresses #109: Clarify entity / representation / variant terminology

Replace more entity, entities, and entity-body, as appropriate.

Addresses #183: "requested resource" in content-encoding definition

Fixed.

Clarifies #178: Content-MD5 and partial responses

New terminology makes it easier to understand what is digested.

File:
1 edited

Legend:

Unmodified
Added
Removed
  • draft-ietf-httpbis/latest/p5-range.xml

    r866 r874  
    316316<t>
    317317   HTTP/1.1 allows a client to request that only part (a range of) the
    318    response entity be included within the response. HTTP/1.1 uses range
     318   representation be included within the response. HTTP/1.1 uses range
    319319   units in the Range (<xref target="header.range"/>) and Content-Range (<xref target="header.content-range"/>)
    320    header fields. An entity can be broken down into subranges according
     320   header fields. A representation can be broken down into subranges according
    321321   to various structural units.
    322322</t>
     
    412412<section title="Combining Ranges" anchor="combining.byte.ranges">
    413413<t>
    414    A response might transfer only a subrange of an entity-body, either because
     414   A response might transfer only a subrange of a representation, either because
    415415   the request included one or more Range specifications, or because
    416    a connection was broken prematurely.
     416   a connection closed prematurely.
    417417   After several such transfers, a cache might have received several
    418    ranges of the same entity-body.
     418   ranges of the same representation.
    419419</t>
    420420<t>
     
    498498  <x:anchor-alias value="other-range-resp-spec"/>
    499499<t>
    500    The "Content-Range" entity-header field is sent with a partial entity-body to
    501    specify where in the full entity-body the partial body should be
     500   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
    502502   applied. Range units are defined in <xref target="range.units"/>.
    503503</t>
     
    522522</artwork></figure>
    523523<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,
    525525   unless this length is unknown or difficult to determine. The asterisk
    526526   "*" character means that the instance-length is unknown at the time
     
    617617   invalid, the server &SHOULD; treat the request as if the invalid Range
    618618   header field did not exist. (Normally, this means return a 200
    619    response containing the full entity).
     619   response containing the full representation).
    620620</t>
    621621<t>
     
    643643  <x:anchor-alias value="If-Range-v"/>
    644644<t>
    645    If a client has a partial copy of an entity in its cache, and wishes
    646    to have an up-to-date copy of the entire entity in its cache, it
     645   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
    647647   could use the Range request-header with a conditional GET (using
    648648   either or both of If-Unmodified-Since and If-Match.) However, if the
     
    662662</artwork></figure>
    663663<t>
    664    If the client has no entity tag for a representation, but does have a Last-Modified
     664   If the client has no entity-tag for a representation, but does have a Last-Modified
    665665   date, it &MAY; use that date in an If-Range header. (The
    666666   server can distinguish between a valid HTTP-date and any form of
     
    671671</t>
    672672<t>
    673    If the entity tag given in the If-Range header matches the current
     673   If the entity-tag given in the If-Range header matches the current
    674674   cache validator for the representation, then the server &SHOULD; provide the
    675675   specified sub-range of the representation using a 206 (Partial Content)
     
    744744   A suffix-byte-range-spec is used to specify the suffix of the
    745745   representation body, of a length given by the suffix-length value. (That is,
    746    this form specifies the last N bytes of an entity-body.) If the
     746   this form specifies the last N bytes of a representation.) If the
    747747   representation is shorter than the specified suffix-length, the entire
    748748   representation is used.
     
    751751   If a syntactically valid byte-range-set includes at least one byte-range-spec
    752752   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-zero
     753   the representation, or at least one suffix-byte-range-spec with a non-zero
    754754   suffix-length, then the byte-range-set is satisfiable.
    755755   Otherwise, the byte-range-set is unsatisfiable. If the byte-range-set
     
    760760</t>
    761761<t>
    762    Examples of byte-ranges-specifier values (assuming an entity-body of
     762   Examples of byte-ranges-specifier values (assuming a representation of
    763763   length 10000):
    764764  <list style="symbols">
     
    820820   possible, since Range supports efficient recovery from partially
    821821   failed transfers, and supports efficient partial retrieval of large
    822    entities.
     822   representations.
    823823</t>
    824824<t>
    825825   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:
    827827  <list style="symbols">
    828828     <t>The presence of a Range header in an unconditional GET modifies
     
    845845<t>
    846846   If a proxy that supports ranges receives a Range request, forwards
    847    the request to an inbound server, and receives an entire entity in
     847   the request to an inbound server, and receives an entire representation in
    848848   reply, it &SHOULD; only return the requested range to its client. It
    849849   &SHOULD; store the entire received response in its cache if that is
Note: See TracChangeset for help on using the changeset viewer.