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

[Ludovic Courtès]

Hi Daniel,

Daniel Hartwig <address@hidden> skribis:

> On 24 November 2012 06:19, Ludovic Courtès <address@hidden> wrote:
>> Any update on that?  The plan is to release 2.0.7 next week, so it’d be
>> great if this could be in.
>
> I have made a first attempt at the doc strings and manual.  This
> involved first syncronizing the two, as only the manual had been
> receiving updates.
>
> Some more tweaking to the code.

Thanks.  I applied the first two patches, and passed the source files
through:

  sed -e"s/@var{\([a-z0-9?!-]\+\)}/\U\1/g ; s/@code{\([^}]\+\)}/‘\1’/g"

because docstrings should not contain Texinfo markup.

> Personally I am not 100% on this, but I attach it for comment anyway.
> I will not be able to work on it again for a short while.
>
> A quick solution may be to silently introduce just enough to fix the
> current bug, and worry about the extra predicates, uri-record-type vs.
> rfc-definition-of-uri, etc. later.

I could come up with a ‘declare-relative-uri-header!’ that would use
(build-uri xxx #:validate? #f) as a quick fix.

However, it seems to me that your patch is actually fine, and doesn’t
break compatibility, so I’d rather apply it directly.  Did you have
other concerns?

Thanks,
Ludo’.