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

[Daniel Hartwig]

On 9 March 2013 16:21, Andy Wingo <address@hidden> wrote:
> On Sat 09 Mar 2013 02:41, Daniel Hartwig <address@hidden> 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?

Ok.  What about Ludo's original comment, about the extra space in the
sqlite header?