Ignore:
Timestamp:
Apr 5, 2011, 3:49:27 PM (9 years ago)
Author:
fielding@…
Message:

editorial: rearrange p4 a bit more to split discussion of last-modified
from that of entity-tags, move entity-tags definition within the ETag
header field, and introduce sections for requirements on generation
and comparison of each (separately). This roughly halves the
cognitive complexity of the existing descriptions and allows us
to get rid of a lot of duplication (with more to come).

Moved some stray requirements on range requests to p5.

File:
1 edited

Legend:

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

    r1258 r1260  
    2020  <!ENTITY full-date                  "<xref target='Part1' x:rel='#date.time.formats.full.date' xmlns:x='http://purl.org/net/xml2rfc/ext'/>">
    2121  <!ENTITY messaging                  "<xref target='Part1' xmlns:x='http://purl.org/net/xml2rfc/ext'/>">
    22   <!ENTITY entity-tags                "<xref target='Part4' x:rel='#entity.tags' xmlns:x='http://purl.org/net/xml2rfc/ext'/>">
     22  <!ENTITY entity-tags                "<xref target='Part4' x:rel='#header.etag' xmlns:x='http://purl.org/net/xml2rfc/ext'/>">
    2323  <!ENTITY weak-and-strong-validators "<xref target='Part4' x:rel='#weak.and.strong.validators' xmlns:x='http://purl.org/net/xml2rfc/ext'/>">
     24  <!ENTITY lastmod-comparison         "<xref target='Part4' x:rel='#lastmod.comparison' xmlns:x='http://purl.org/net/xml2rfc/ext'/>">
    2425]>
    2526<?rfc toc="yes" ?>
     
    313314  <x:anchor-alias value="range-unit"/>
    314315<t>
    315    HTTP/1.1 allows a client to request that only part (a range of) the
     316   HTTP/1.1 allows a client to request that only part (a range) of the
    316317   representation be included within the response. HTTP/1.1 uses range
    317318   units in the Range (<xref target="header.range"/>) and Content-Range (<xref target="header.content-range"/>)
     
    339340<section title="Range Specifier Registry" anchor="range.specifier.registry">
    340341<t>
    341    The HTTP Ranger Specifier Registry defines the name space for the range
     342   The HTTP Range Specifier Registry defines the name space for the range
    342343   specifier names.
    343344</t>
     
    678679</artwork></figure>
    679680<t>
     681   Only a strong validator (&weak-and-strong-validators;) is usable for
     682   range retrieval, since otherwise the client might end up with an
     683   internally inconsistent representation.
     684   Clients &MUST-NOT; use weak validators in range requests.
     685   A cache or origin server receiving a conditional range request
     686   &MUST; use the strong comparison function to evaluate the condition.
     687</t>
     688<t>
    680689   If the client has no entity-tag for a representation, but does have a Last-Modified
    681690   date, it &MAY; use that date in an If-Range header field. (The
     
    685694   ignored if the request does not include a Range header field, or if the
    686695   server does not support the sub-range operation.
     696</t>
     697<t>
     698   If a client wishes to perform a sub-range retrieval on a value for
     699   which it has only a Last-Modified time and no opaque validator, it
     700   &MAY; do this only if the Last-Modified time is strong in the sense
     701   described in &lastmod-comparison;.
    687702</t>
    688703<t>
Note: See TracChangeset for help on using the changeset viewer.