Changeset 1047 for draft-ietf-httpbis/latest

Timestamp:

Oct 22, 2010, 2:55:14 AM (9 years ago)

Author:

julian.reschke@…

Message:

rephrase client requirements for Date header field (addresses #248)

Location:

draft-ietf-httpbis/latest

Files:

• p1-messaging.html (modified) (2 diffs)
• p1-messaging.xml (modified) (2 diffs)

draft-ietf-httpbis/latest/p1-messaging.html

@@ -2072 +2072 @@
          a Date.
       </p>
-      <p id="rfc.section.9.3.p.7">Clients <em class="bcp14">SHOULD</em> only send a Date header field in messages that include a payload, as is usually the case for PUT and POST requests, and even
-         then it is optional. A client without a clock <em class="bcp14">MUST NOT</em> send a Date header field in a request.
+      <p id="rfc.section.9.3.p.7">Clients can use the Date header field as well; in order to keep request messages small, they are advised not to include it
+         when it doesn't convey any useful information (as it is usually the case for requests that do not contain a payload).
       </p>
       <p id="rfc.section.9.3.p.8">The HTTP-date sent in a Date header field <em class="bcp14">SHOULD NOT</em> represent a date and time subsequent to the generation of the message. It <em class="bcp14">SHOULD</em> represent the best available approximation of the date and time of message generation, unless the implementation has no means
@@ -3458 +3458 @@
          </li>
          <li> &lt;<a href="http://tools.ietf.org/wg/httpbis/trac/ticket/221">http://tools.ietf.org/wg/httpbis/trac/ticket/221</a>&gt;: "effective request URI: handling of missing host in HTTP/1.0"
+         </li>
+         <li> &lt;<a href="http://tools.ietf.org/wg/httpbis/trac/ticket/248">http://tools.ietf.org/wg/httpbis/trac/ticket/248</a>&gt;: "confusing Date requirements for clients"
          </li>
       </ul>

draft-ietf-httpbis/latest/p1-messaging.xml

@@ -3005 +3005 @@
 </t>
 <t>
-   Clients &SHOULD; only send a Date header field in messages that include
-   a payload, as is usually the case for PUT and POST requests, and even
-   then it is optional. A client without a clock &MUST-NOT; send a Date
-   header field in a request.
+   Clients can use the Date header field as well; in order to keep request
+   messages small, they are advised not to include it when it doesn't convey
+   any useful information (as it is usually the case for requests that do not
+   contain a payload).
 </t>
 <t>
@@ -5664 +5664 @@
       "effective request URI: handling of missing host in HTTP/1.0"
     </t>
+    <t>
+      <eref target="http://tools.ietf.org/wg/httpbis/trac/ticket/248"/>:
+      "confusing Date requirements for clients"
+    </t>
   </list>
 </t>