From: Andy Wingo <wingo@pobox.com>
To: Daniel Hartwig <mandyke@gmail.com>
Cc: "Ludovic Courtès" <ludo@gnu.org>,
13544@debbugs.gnu.org, "Cyril Roelandt" <tipecaml@gmail.com>
Subject: bug#13544: (web http) fails to parse numeric timezones in Date header
Date: Sun, 10 Mar 2013 19:31:56 +0100 [thread overview]
Message-ID: <87r4jnw1gj.fsf@pobox.com> (raw)
In-Reply-To: <CAN3veRez=k6vRo4QiH5KRbQm_f=w6TNeF0D1eLiz3nYRnNz5ww@mail.gmail.com> (Daniel Hartwig's message of "Sun, 10 Mar 2013 07:50:56 +0800")
On Sun 10 Mar 2013 00:50, Daniel Hartwig <mandyke@gmail.com> writes:
> On 9 March 2013 16:21, Andy Wingo <wingo@pobox.com> wrote:
>> On Sat 09 Mar 2013 02:41, Daniel Hartwig <mandyke@gmail.com> 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?
Dunno. Is it common? In this particular case I would mail and try to
get them to fix their server, given that it is run by hackers. Let us
leave that particular issue for another bug.
Andy
--
http://wingolog.org/
next prev parent reply other threads:[~2013-03-10 18:31 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-01-24 22:13 bug#13544: (web http) fails to parse numeric timezones in Date header Ludovic Courtès
2013-03-07 22:28 ` Andy Wingo
2013-03-09 1:41 ` Daniel Hartwig
2013-03-09 2:08 ` Daniel Hartwig
2013-03-09 8:21 ` Andy Wingo
2013-03-09 23:50 ` Daniel Hartwig
2013-03-10 18:31 ` Andy Wingo [this message]
2013-03-14 13:34 ` Ludovic Courtès
2013-03-14 15:00 ` Andy Wingo
2013-03-14 16:07 ` Ludovic Courtès
2013-03-15 7:08 ` Daniel Hartwig
2013-03-15 7:17 ` Daniel Hartwig
2013-03-15 14:40 ` Daniel Hartwig
2013-03-15 23:04 ` Ludovic Courtès
2013-03-27 15:25 ` Ludovic Courtès
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
List information: https://www.gnu.org/software/guile/
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=87r4jnw1gj.fsf@pobox.com \
--to=wingo@pobox.com \
--cc=13544@debbugs.gnu.org \
--cc=ludo@gnu.org \
--cc=mandyke@gmail.com \
--cc=tipecaml@gmail.com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).