[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
bug#12827: [2.0.6] web client: fails to parse 404 header
From: |
Daniel Hartwig |
Subject: |
bug#12827: [2.0.6] web client: fails to parse 404 header |
Date: |
Thu, 8 Nov 2012 13:52:29 +0800 |
On 8 November 2012 04:40, Ludovic Courtès <address@hidden> wrote:
> scheme@(guile-user)> (use-modules (web client) (web uri))
> scheme@(guile-user)> (http-get (string->uri
> "http://www.gnu.org/does-not-exist"))
> web/http.scm:191:11: In procedure read-header:
> web/http.scm:191:11: Bad uri header component: gnu-404.html
Some headers are supposed to support these “URI-references”.
I have just updated a patch I worked on a while back that adds support
for such things, including “partial-refs”. It is not yet ready for
inclusion, some points to consider:
* DONE (web uri) support for relative-refs
* DONE (web http) support for relative-refs in headers
* TODO (resolve-ref uri uri-reference) → absolute-uri
* TODO documentation
* TODO maybe use more scheme-ish names instead of RFC 3986
This latest RFC makes a clear distinction between an actual URI
and a reference to such. I thought it best to reflect that
distinction, but maybe it does pollute the namespace a bit:
- absolute-uri? → uri-absolute?
- relative-ref? → uri-relative?
* TODO build-uri validation is broken/less strict and will now pass
relative-refs, so maybe introduce build-uri-reference instead
Anyway, this may provide a useful base to work from, if not something
suitable for inclusion almost immediately.
Regards
0001-uri-reference-support.patch
Description: Binary data
- bug#12827: [2.0.6] web client: fails to parse 404 header, Ludovic Courtès, 2012/11/07
- bug#12827: [2.0.6] web client: fails to parse 404 header,
Daniel Hartwig <=
- bug#12827: [2.0.6] web client: fails to parse 404 header, Ludovic Courtès, 2012/11/23
- bug#12827: [2.0.6] web client: fails to parse 404 header, Daniel Hartwig, 2012/11/24
- bug#12827: [2.0.6] web client: fails to parse 404 header, Ludovic Courtès, 2012/11/24
- bug#12827: [2.0.6] web client: fails to parse 404 header, Daniel Hartwig, 2012/11/24
- bug#12827: [2.0.6] web client: fails to parse 404 header, Ludovic Courtès, 2012/11/25