From: ludo@gnu.org (Ludovic Courtès)
To: Ricardo Wurmus <ricardo.wurmus@mdc-berlin.de>
Cc: 23421-done@debbugs.gnu.org
Subject: bug#23421: parse-rfc-822-date is too strict
Date: Sun, 08 May 2016 22:02:13 +0200 [thread overview]
Message-ID: <87posw2u9m.fsf@gnu.org> (raw)
In-Reply-To: <idjlh3s6chi.fsf@bimsb-sys02.mdc-berlin.net> (Ricardo Wurmus's message of "Mon, 2 May 2016 11:22:17 +0200")
Ricardo Wurmus <ricardo.wurmus@mdc-berlin.de> skribis:
> The procedure “parse-rfc-822-date” in the module (web http) is a bit too
> strict as it rejects dates in which the hour field is a single digit
> without zero-padding.
>
> A date like this will be rejected:
>
> Sun, 06 Nov 1994 8:49:37 GMT
>
> Whereas a date like this is accepted:
>
> Sun, 06 Nov 1994 08:49:37 GMT
>
> The only difference is the leading zero in the timestamp.
Fixed in 16050431f29d56f80c4a8253506fc851b8441840, thanks!
Ludo’.
prev parent reply other threads:[~2016-05-08 20:02 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-05-02 9:22 bug#23421: parse-rfc-822-date is too strict Ricardo Wurmus
2016-05-08 20:02 ` Ludovic Courtès [this message]
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=87posw2u9m.fsf@gnu.org \
--to=ludo@gnu.org \
--cc=23421-done@debbugs.gnu.org \
--cc=ricardo.wurmus@mdc-berlin.de \
/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).