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.xml

    r1045 r1047  
    30053005</t>
    30063006<t>
    3007    Clients &SHOULD; only send a Date header field in messages that include
    3008    a payload, as is usually the case for PUT and POST requests, and even
    3009    then it is optional. A client without a clock &MUST-NOT; send a Date
    3010    header field in a request.
     3007   Clients can use the Date header field as well; in order to keep request
     3008   messages small, they are advised not to include it when it doesn't convey
     3009   any useful information (as it is usually the case for requests that do not
     3010   contain a payload).
    30113011</t>
    30123012<t>
     
    56645664      "effective request URI: handling of missing host in HTTP/1.0"
    56655665    </t>
     5666    <t>
     5667      <eref target="http://tools.ietf.org/wg/httpbis/trac/ticket/248"/>:
     5668      "confusing Date requirements for clients"
     5669    </t>
    56665670  </list>
    56675671</t>
Note: See TracChangeset for help on using the changeset viewer.