GNU bug report logs -
#12827
[2.0.6] web client: fails to parse 404 header
Previous Next
Reported by: ludo <at> gnu.org (Ludovic Courtès)
Date: Wed, 7 Nov 2012 20:42:02 UTC
Severity: normal
Done: Andy Wingo <wingo <at> pobox.com>
Bug is archived. No further changes may be made.
Full log
View this message in rfc822 format
[Message part 1 (text/plain, inline)]
On 27 November 2012 20:50, Ludovic Courtès <ludo <at> gnu.org> wrote:
> Sure. But then again, the goal was just to have a hack that would solve
> the problem initially reported here, while waiting for a proper fix.
Avoiding an obvious parser error, but introducing subtle problems with
the objects. The reported bug has been present since always with (web
uri).
>
> I’m open to suggestions. It seems to me that it’s either this or your
> patches against (web uri). WDYT?
I still don't like the API in those patches, and don't think it is
tested enough against, e.g., reading and writing all combinations of
headers and idempotent (?) across read-write cycles (a quick check
just showed that it wasn't, due to write-uri in (web http)).
Anyway, if you like to fix this bug, I have isolated the changes to
string->uri, just enough to handle these headers without introducing
any API changes (which can come later, after refinement).
Attached a patch against current stable-2.0.
Regards
[0001-web-client-correctly-handle-uri-query-etc.-in-relati.patch (application/octet-stream, attachment)]
This bug report was last modified 8 years and 80 days ago.
Previous Next
GNU bug tracking system
Copyright (C) 1999 Darren O. Benham,
1997,2003 nCipher Corporation Ltd,
1994-97 Ian Jackson.