Changeset 2559

Timestamp:

18/01/14 08:29:56 (8 years ago)

Author:

fielding@…

Message:

(editorial) clarify that If-Range uses an exact match comparison even for HTTP-date, unlike If-Unmodified-Since; see #534 comment from Richard Barnes

Location:

draft-ietf-httpbis/latest

Files:

• p5-range.html (modified) (6 diffs)
• p5-range.xml (modified) (1 diff)

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

@@ -448 +448 @@
   }
   @bottom-center {
-       content: "Expires July 21, 2014";
+       content: "Expires July 22, 2014";
   }
   @bottom-right {
@@ -491 +491 @@
       <meta name="dct.creator" content="Reschke, J. F.">
       <meta name="dct.identifier" content="urn:ietf:id:draft-ietf-httpbis-p5-range-latest">
-      <meta name="dct.issued" scheme="ISO8601" content="2014-01-17">
+      <meta name="dct.issued" scheme="ISO8601" content="2014-01-18">
       <meta name="dct.replaces" content="urn:ietf:rfc:2616">
       <meta name="dct.abstract" content="The Hypertext Transfer Protocol (HTTP) is a stateless application-level protocol for distributed, collaborative, hypertext information systems. This document defines range requests and the rules for constructing and combining responses to those requests.">
@@ -517 +517 @@
             </tr>
             <tr>
-               <td class="left">Expires: July 21, 2014</td>
+               <td class="left">Expires: July 22, 2014</td>
                <td class="right">J. Reschke, Editor</td>
             </tr>
@@ -526 +526 @@
             <tr>
                <td class="left"></td>
-               <td class="right">January 17, 2014</td>
+               <td class="right">January 18, 2014</td>
             </tr>
          </tbody>
@@ -553 +553 @@
             in progress”.
          </p>
-         <p>This Internet-Draft will expire on July 21, 2014.</p>
+         <p>This Internet-Draft will expire on July 22, 2014.</p>
       </div>
       <div id="rfc.copyrightnotice">
@@ -807 +807 @@
             </p>
             <p id="rfc.section.3.2.p.7">If the validator given in the If-Range header field matches the current validator for the selected representation of the target
-               resource, then the server <em class="bcp14">SHOULD</em> process the <a href="#header.range" class="smpl">Range</a> header field as requested. If the validator does not match, the server <em class="bcp14">MUST</em> ignore the <a href="#header.range" class="smpl">Range</a> header field.
+               resource, then the server <em class="bcp14">SHOULD</em> process the <a href="#header.range" class="smpl">Range</a> header field as requested. If the validator does not match, the server <em class="bcp14">MUST</em> ignore the <a href="#header.range" class="smpl">Range</a> header field. Note that this comparison by exact match, including when the validator is an <a href="#imported.abnf" class="smpl">HTTP-date</a>, differs from the "earlier than or equal to" comparison used when evaluating an <a href="p4-conditional.html#header.if-unmodified-since" class="smpl">If-Unmodified-Since</a> conditional.
             </p>
          </div>

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

@@ -500 +500 @@
    the server &SHOULD; process the <x:ref>Range</x:ref> header field as
    requested. If the validator does not match, the server &MUST; ignore the
-   <x:ref>Range</x:ref> header field.
+   <x:ref>Range</x:ref> header field. Note that this comparison by exact
+   match, including when the validator is an <x:ref>HTTP-date</x:ref>, differs
+   from the "earlier than or equal to" comparison used when evaluating an
+   <x:ref>If-Unmodified-Since</x:ref> conditional.
 </t>
 </section>