Ignore:
Timestamp:
Oct 22, 2010, 2:55:14 AM (9 years ago)
Author:
julian.reschke@…
Message:

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

File:
1 edited

Legend:

Unmodified
Added
Removed
  • draft-ietf-httpbis/latest/p1-messaging.html

    r1045 r1047  
    20722072         a Date.
    20732073      </p>
    2074       <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
    2075          then it is optional. A client without a clock <em class="bcp14">MUST NOT</em> send a Date header field in a request.
     2074      <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
     2075         when it doesn't convey any useful information (as it is usually the case for requests that do not contain a payload).
    20762076      </p>
    20772077      <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
     
    34583458         </li>
    34593459         <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"
     3460         </li>
     3461         <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"
    34603462         </li>
    34613463      </ul>
Note: See TracChangeset for help on using the changeset viewer.