W3C home > Mailing lists > Public > ietf-http-wg@w3.org > October to December 2010

Issue 248: client "Date" requirements

From: Julian Reschke <julian.reschke@gmx.de>
Date: Mon, 11 Oct 2010 18:46:03 +0200
Message-ID: <4CB33F4B.7090602@gmx.de>
To: HTTP Working Group <ietf-http-wg@w3.org>

the spec currently says:

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

(this comes from RFC 2616).

This is very wrong:

"SHOULD only .. and even then it is optional".

So, if it's optional, it's MAY. I don't believe we need to say that 
clients "MAY" send a Date header :-).

Can we simplify that, or even remove it?

(see <http://trac.tools.ietf.org/wg/httpbis/trac/ticket/248>)

Best regards, Julian
Received on Monday, 11 October 2010 16:46:39 UTC

This archive was generated by hypermail 2.3.1 : Tuesday, 1 March 2016 11:10:55 UTC