bug#14128: web/http.scm: bad-header date check (UTC?)

2013-11-19 Thread Mark H Weaver
Andy Wingo agreed on IRC to accepting UTC, since we've since discovered that not only various web servers, but also some transparent web proxies put UTC in the date header, which was causing problems for many people. So, I've pushed a change to stable-2.0 to accept UTC.

bug#14128: web/http.scm: bad-header date check (UTC?)

2013-04-04 Thread Andy Wingo
On Wed 03 Apr 2013 09:59, Aleix Conchillo Flaqué aconchi...@gmail.com writes: = 184: 1 [read-header #input-output: gnutls-session-port 2e94c30] 754: 0 [parse-asctime-date Wed, 03 Apr 2013 07:29:49 UTC] web/http.scm:754:6: In procedure parse-asctime-date: web/http.scm:754:6:

bug#14128: web/http.scm: bad-header date check (UTC?)

2013-04-04 Thread Daniel Hartwig
On 3 April 2013 20:32, Thien-Thi Nguyen t...@gnuvola.org wrote: () Daniel Hartwig mand...@gmail.com () Wed, 3 Apr 2013 18:47:22 +0800 Interesting. Though this does gradually erode the type barrier erected by the web module. I am reluctant to cede this territory. I suppose playing

bug#14128: web/http.scm: bad-header date check (UTC?)

2013-04-03 Thread Aleix Conchillo Flaqué
Hi, I was doing a test using gnutls and connecting to twitter api services. Example attached. I successfully passed the TLS/SSL part, but then I got this HTTP bad header issue. I am running Guile 2.0.5 from Debian/unstable but current stable-2.0 branch also suffers from the safe problem (I

bug#14128: web/http.scm: bad-header date check (UTC?)

2013-04-03 Thread Daniel Hartwig
On 3 April 2013 15:59, Aleix Conchillo Flaqué aconchi...@gmail.com wrote: Hi, I was doing a test using gnutls and connecting to twitter api services. Example attached. I successfully passed the TLS/SSL part, but then I got this HTTP bad header issue. I am running Guile 2.0.5 from

bug#14128: web/http.scm: bad-header date check (UTC?)

2013-04-03 Thread Thien-Thi Nguyen
() Daniel Hartwig mand...@gmail.com () Wed, 3 Apr 2013 17:47:01 +0800 Apparently we are supposed to do this a bit more and accomodate yet another non-compliant service? Maybe that stuff should be exposed to the user. Do a best effort conversion and if not successful, return a pair

bug#14128: web/http.scm: bad-header date check (UTC?)

2013-04-03 Thread Daniel Hartwig
On 3 April 2013 18:33, Thien-Thi Nguyen t...@gnuvola.org wrote: () Daniel Hartwig mand...@gmail.com () Wed, 3 Apr 2013 17:47:01 +0800 Apparently we are supposed to do this a bit more and accomodate yet another non-compliant service? Maybe that stuff should be exposed to the user. Do

bug#14128: web/http.scm: bad-header date check (UTC?)

2013-04-03 Thread Ludovic Courtès
Daniel Hartwig mand...@gmail.com skribis: RFC 2616 _requires_ http date values have a suffix of GMT What about adding an exception for “UTC”? :-) It’s the same timezone, only with a different name, so it shouldn’t cost us much. WDYT? Ludo’.

bug#14128: web/http.scm: bad-header date check (UTC?)

2013-04-03 Thread Aleix Conchillo Flaqué
On Wed, Apr 3, 2013 at 5:34 AM, Ludovic Courtès l...@gnu.org wrote: Daniel Hartwig mand...@gmail.com skribis: RFC 2616 _requires_ http date values have a suffix of GMT What about adding an exception for “UTC”? :-) It’s the same timezone, only with a different name, so it shouldn’t cost

bug#14128: web/http.scm: bad-header date check (UTC?)

2013-04-03 Thread Aleix Conchillo Flaqué
On Wed, Apr 3, 2013 at 7:57 AM, Aleix Conchillo Flaqué aconchi...@gmail.com wrote: This is what I did locally so I could continue testing. But unfortunately, it's is very likely that there are more broken servers around. The permissive flag seems like an all-or-nothing, so I think Thien-Thi's