From: ludo@gnu.org (Ludovic Courtès)
To: Daniel Hartwig <mandyke@gmail.com>
Cc: 12827@debbugs.gnu.org
Subject: bug#12827: [2.0.6] web client: fails to parse 404 header
Date: Mon, 26 Nov 2012 01:15:52 +0100 [thread overview]
Message-ID: <87lidpxlqf.fsf@gnu.org> (raw)
In-Reply-To: <CAN3veRdJ_Qo1=r75f3NAT7++_a0ASFAVdKWFfuFOegRL32E+tQ@mail.gmail.com> (Daniel Hartwig's message of "Sat, 24 Nov 2012 23:34:41 +0800")
[-- Attachment #1: Type: text/plain, Size: 489 bytes --]
Hi!
Daniel Hartwig <mandyke@gmail.com> skribis:
> The API seems less clean, and it is not immediately clear
> that uri? is not the top of the URI-like type hierarchy. The other
> functions only indicate “uri” in their name. I did not
> wish to introduce parallel “build-uri-reference”, etc. for each of
> these, and did consider adding #:reference? on some to select
> weaker validation.
OK.
So for now, I’d go with this patch, which fixes the bug at hand:
[-- Warning: decoded text below may be mangled, UTF-8 assumed --]
[-- Attachment #2: Type: text/x-patch, Size: 1396 bytes --]
diff --git a/module/web/http.scm b/module/web/http.scm
index 342f435..65ebe7d 100644
--- a/module/web/http.scm
+++ b/module/web/http.scm
@@ -1185,6 +1185,17 @@ treated specially, and is just returned as a plain string."
uri?
write-uri))
+;; emacs: (put 'declare-relative-uri-header! 'scheme-indent-function 1)
+(define (declare-relative-uri-header! name)
+ (declare-header! name
+ (lambda (str)
+ (or (string->uri str) ; absolute URI
+ (build-uri #f ; relative URI
+ #:path str
+ #:validate? #f)))
+ uri?
+ write-uri))
+
;; emacs: (put 'declare-quality-list-header! 'scheme-indent-function 1)
(define (declare-quality-list-header! name)
(declare-header! name
@@ -1437,7 +1448,7 @@ treated specially, and is just returned as a plain string."
;; Content-Location = ( absoluteURI | relativeURI )
;;
-(declare-uri-header! "Content-Location")
+(declare-relative-uri-header! "Content-Location")
;; Content-MD5 = <base64 of 128 bit MD5 digest as per RFC 1864>
;;
@@ -1726,7 +1737,7 @@ treated specially, and is just returned as a plain string."
;; Referer = ( absoluteURI | relativeURI )
;;
-(declare-uri-header! "Referer")
+(declare-relative-uri-header! "Referer")
;; TE = #( t-codings )
;; t-codings = "trailers" | ( transfer-extension [ accept-params ] )
[-- Attachment #3: Type: text/plain, Size: 115 bytes --]
Once 2.0.7 is out, when you have more time, we can fix it cleanly.
How does that sound?
Thanks,
Ludo’.
next prev parent reply other threads:[~2012-11-26 0:15 UTC|newest]
Thread overview: 18+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-11-07 20:40 bug#12827: [2.0.6] web client: fails to parse 404 header Ludovic Courtès
2012-11-08 5:52 ` Daniel Hartwig
2012-11-08 20:10 ` Ludovic Courtès
2012-11-09 0:39 ` Daniel Hartwig
2012-11-09 20:52 ` Ludovic Courtès
2012-11-10 1:45 ` Daniel Hartwig
2012-11-10 13:52 ` Ludovic Courtès
2012-11-23 22:19 ` Ludovic Courtès
2012-11-24 11:23 ` Daniel Hartwig
2012-11-24 15:10 ` Ludovic Courtès
2012-11-24 15:34 ` Daniel Hartwig
2012-11-26 0:15 ` Ludovic Courtès [this message]
2012-11-26 23:13 ` Ludovic Courtès
2012-11-27 1:06 ` Daniel Hartwig
2012-11-27 12:50 ` Ludovic Courtès
2012-11-27 15:18 ` Daniel Hartwig
2012-11-27 21:43 ` Ludovic Courtès
2013-02-23 8:11 ` bug#12827: [PATCH] Tweak web modules, support relative URIs (was: bug#12827: [2.0.6] web client: fails to parse 404 header) Daniel Hartwig
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
List information: https://www.gnu.org/software/guile/
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=87lidpxlqf.fsf@gnu.org \
--to=ludo@gnu.org \
--cc=12827@debbugs.gnu.org \
--cc=mandyke@gmail.com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).