bug#12827: [2.0.6] web client: fails to parse 404 header

[Ludovic Courtès]

Hi,

Daniel Hartwig <address@hidden> skribis:

> 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)).

Fair enough.

> 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).

Applied, thanks!

Ludo’.