Subject: Re: bug#13544: (web http) fails to parse numeric timezones in Date header

From: Andy Wingo <[email-masked]>
Date: Sat, 09 Mar 2013 09:21:49 +0100

On Sat 09 Mar 2013 02:41, Daniel Hartwig <[email-masked]> writes:

> Interpretting ‘+0000’ timezone is sensible in a robust implementation,

Yes, I agree, this makes sense.

> though what to do if a numeric timezone is given other than this?

I would continue to raise an error I think.  Timezones get complicated,
fast, and there is little hope that we could preserve correctness.
WDYT?

Andy
-- 
http://wingolog.org/