Changeset 1260 for draft-ietf-httpbis/latest/p5-range.xml

Timestamp:

05/04/11 22:49:27 (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:

• draft-ietf-httpbis/latest/p5-range.xml (modified) (5 diffs)

draft-ietf-httpbis/latest/p5-range.xml

@@ -20 +20 @@
   <!ENTITY full-date                  "<xref target='Part1' x:rel='#date.time.formats.full.date' xmlns:x='http://purl.org/net/xml2rfc/ext'/>">
   <!ENTITY messaging                  "<xref target='Part1' xmlns:x='http://purl.org/net/xml2rfc/ext'/>">
-  <!ENTITY entity-tags                "<xref target='Part4' x:rel='#entity.tags' xmlns:x='http://purl.org/net/xml2rfc/ext'/>">
+  <!ENTITY entity-tags                "<xref target='Part4' x:rel='#header.etag' xmlns:x='http://purl.org/net/xml2rfc/ext'/>">
   <!ENTITY weak-and-strong-validators "<xref target='Part4' x:rel='#weak.and.strong.validators' xmlns:x='http://purl.org/net/xml2rfc/ext'/>">
+  <!ENTITY lastmod-comparison         "<xref target='Part4' x:rel='#lastmod.comparison' xmlns:x='http://purl.org/net/xml2rfc/ext'/>">
 ]>
 <?rfc toc="yes" ?>
@@ -313 +314 @@
   <x:anchor-alias value="range-unit"/>
 <t>
-   HTTP/1.1 allows a client to request that only part (a range of) the
+   HTTP/1.1 allows a client to request that only part (a range) of the
    representation be included within the response. HTTP/1.1 uses range
    units in the Range (<xref target="header.range"/>) and Content-Range (<xref target="header.content-range"/>)
@@ -339 +340 @@
 <section title="Range Specifier Registry" anchor="range.specifier.registry">
 <t>
-   The HTTP Ranger Specifier Registry defines the name space for the range
+   The HTTP Range Specifier Registry defines the name space for the range
    specifier names.
 </t>
@@ -678 +679 @@
 </artwork></figure>
 <t>
+   Only a strong validator (&weak-and-strong-validators;) is usable for
+   range retrieval, since otherwise the client might end up with an
+   internally inconsistent representation.
+   Clients &MUST-NOT; use weak validators in range requests.
+   A cache or origin server receiving a conditional range request
+   &MUST; use the strong comparison function to evaluate the condition.
+</t>
+<t>
    If the client has no entity-tag for a representation, but does have a Last-Modified
    date, it &MAY; use that date in an If-Range header field. (The
@@ -685 +694 @@
    ignored if the request does not include a Range header field, or if the
    server does not support the sub-range operation.
+</t>
+<t>
+   If a client wishes to perform a sub-range retrieval on a value for
+   which it has only a Last-Modified time and no opaque validator, it
+   &MAY; do this only if the Last-Modified time is strong in the sense
+   described in &lastmod-comparison;.
 </t>
 <t>