W3C home > Mailing lists > Public > ietf-http-wg-old@w3.org > September to December 1997

Re: This is not "this is not a date"

From: Roy T. Fielding <fielding@kiwi.ics.uci.edu>
Date: Fri, 12 Dec 1997 21:31:06 -0800
To: Jeffrey Mogul <mogul@pa.dec.com>
Cc: http-wg%cuckoo.hpl.hp.com@hplb.hpl.hp.com
Message-Id: <9712122130.aa28613@paris.ics.uci.edu>
X-Mailing-List: <http-wg@cuckoo.hpl.hp.com> archive/latest/4939
>I have a suggestion: instead of coming up with a new syntax
>for "this is not a date" (when the existing date syntax, horribly
>inefficient and hard-to-parse as it is, has at least more or
>less been tamed by implementors) perhaps we can get by with
>something a little simpler.
>For example, we could say
>	If the sender is required to send a Date header
>	by some part of this specification, and is unable
>	to generate a current HTTP-date value, it SHOULD
>	send a legal HTTP-date value that is provably in
>	the past.
>For example, send
>	Date: Thu, 01 Jan 1970 00:0:01 GMT
>As far as I can tell, this will not lead to any more trouble
>than simply omitting the Date header.  It also seems to be
>legal according to section 14.19 of -rev-01.

Ummm, we already have a syntax for "this is not a date"  -- the lack
of a Date header field.  Why should we send garbage on the wire?
I think we should just change the specification so that it properly
handles the case where there is no Date header field.  That would be
the more robust way of specifying it in any case.

Received on Friday, 12 December 1997 21:36:47 UTC

This archive was generated by hypermail 2.3.1 : Wednesday, 7 January 2015 14:40:21 UTC