On 27 November 2012 20:50, Ludovic Courtès <ludo@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