W3C home > Mailing lists > Public > ietf-http-wg@w3.org > July to September 2012

Re: #375: Most Conservative (caching and date parsing)

From: Poul-Henning Kamp <phk@phk.freebsd.dk>
Date: Mon, 16 Jul 2012 14:23:14 +0000
To: Yutaka OIWA <y.oiwa@aist.go.jp>
cc: Mark Nottingham <mnot@mnot.net>, HTTP Working Group <ietf-http-wg@w3.org>
Message-ID: <59061.1342448594@critter.freebsd.dk>
In message <CAMeZVwscuX986t9KMD0eXou-fgHUG8DBBkx2++AbJAt0gDs+Ng@mail.gmail.com>
, Yutaka OIWA writes:

>>> If an HTTP header field incorrectly carries a date value with a time zone other than GMT, it must be converted into GMT using the most conservative possible conversion.
>>
>> What does "most conservative" mean?


>My personal proposal is instead of adding any examples, state it like "it may be
>converted to GMT using whatever methods they think appropriate", 

As a time-geek, I would caution against that, because names of timezones
are politically chosen and both their definition and naming is highly
fragile in various parts of the world.

Given that it is a class-A fuckup to send wrong dates, I will advocate
that such timestamps SHOULD be ignored, but CAN be interpreted on a
best-effort basis.

Ohh, and also:  GMT is (maybe!) what parliament decides in the UK, the
correct "independent" timescale is called UTC.

-- 
Poul-Henning Kamp       | UNIX since Zilog Zeus 3.20
phk@FreeBSD.ORG         | TCP/IP since RFC 956
FreeBSD committer       | BSD since 4.3-tahoe    
Never attribute to malice what can adequately be explained by incompetence.
Received on Monday, 16 July 2012 14:23:44 GMT

This archive was generated by hypermail 2.2.0+W3C-0.50 : Monday, 16 July 2012 14:23:50 GMT