From: Thien-Thi Nguyen <ttn@surf.glug.org>
Cc: bug-guile@gnu.org
Subject: Re: Bug in http module of guile-www
Date: Thu, 15 Jul 2004 00:41:59 +0200 [thread overview]
Message-ID: <E1BksRr-0006w2-00@surf.glug.org> (raw)
In-Reply-To: <1089790696.598.19.camel@venkman> (message from Robert Marlow on Wed, 14 Jul 2004 15:38:17 +0800)
From: Robert Marlow <bobstopper@bobturf.org>
Date: Wed, 14 Jul 2004 15:38:17 +0800
I happened accross a bug in the HTTP module of guile-www which seemed to
trigger when I visited a page which gave no headers and just whitespace
in the body. In such a case the variable "second" of parse-status-line
gets bound to #f which messes up the later make-shared-substrings which
use it.
in the status line (which has the form: VERSION CODE TEXT), i believe
TEXT is optional, but i don't have the http spec (RFC 2616) handy to
confirm this. if TEXT is actually optional, that indicates a bug in
http.scm. if TEXT is required, that indicates a bug in the server's
http implementation.
note that the status line cannot be omitted altogether; the most minimal
valid HTTP response a server can send is STATUS-LINE, CRLF, CRLF. you
may wish to check the server response for conformance using a command
like "w3m -dump_head" or similar.
[patch]
unfortunately the patch is incorrect because it allows the possibility
to derive #f for CODE, which is illegal (CODE must be a 3-digit sequence
like "404" or "200"). assuming TEXT is indeed optional, i have changed
`parse-status-line' (in cvs) to handle a missing TEXT component by
returning the empty string. the proc now reads as follows:
(define (parse-status-line statline)
;; Handle: VERSION CODE
;; as well as: VERSION CODE TEXT
;; For the former, use the null string for TEXT.
(let* ((first (string-index statline #\space))
(second (string-index statline #\space (1+ first))))
(list (make-shared-substring statline 0 first)
(make-shared-substring statline (1+ first)
(or second (string-length statline)))
(if second
(make-shared-substring statline (1+ second))
""))))
and will appear in guile-www 2.6 (to be released shortly).
thi
_______________________________________________
Bug-guile mailing list
Bug-guile@gnu.org
http://lists.gnu.org/mailman/listinfo/bug-guile
next prev parent reply other threads:[~2004-07-14 22:41 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-07-14 7:38 Bug in http module of guile-www Robert Marlow
2004-07-14 22:41 ` Thien-Thi Nguyen [this message]
2004-07-15 1:37 ` Kevin Ryde
2004-07-14 22:58 ` Kevin Ryde
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=E1BksRr-0006w2-00@surf.glug.org \
--to=ttn@surf.glug.org \
--cc=bug-guile@gnu.org \
--cc=ttn@glug.org \
/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).