From: Ian Price <ianprice90@googlemail.com>
To: Nikita Karetnikov <nikita.karetnikov@gmail.com>
Cc: 13095@debbugs.gnu.org, "Ludovic Courtès" <ludo@gnu.org>
Subject: bug#13095: http-get: Throw to key `bad-response' with args `("EOF while reading response body: ...)'
Date: Sat, 08 Dec 2012 19:59:50 +0000 [thread overview]
Message-ID: <871uf0b9hl.fsf@Kagami.home> (raw)
In-Reply-To: <CAD15K4u2H5HETmEqvRGyoPW+ArYpo-XYQ3X=EyMeuTyE1h0PcA@mail.gmail.com> (Nikita Karetnikov's message of "Thu, 6 Dec 2012 02:20:45 +0300")
Nikita Karetnikov <nikita.karetnikov@gmail.com> writes:
> Hi,
>
> I'm using Guile 2.0.7. 'http-get' fails to download the file.
>
> scheme@(guile-user)> (http-get (string->uri
> "http://citylan.dl.sourceforge.net/project/libusb/libusb-1.0/libusb-1.0.9/libusb-1.0.9.tar.bz2"))
> ERROR: In procedure get-bytevector-all:
> ERROR: Throw to key `bad-response' with args `("EOF while reading
> response body: ~a bytes of ~a" (12731 421971))'.
This will run correctly if you call http-get with the #:keep-alive?
keyword set to #t. If you don't run it with that, the connection gets
closed automatically, and so you'll get an EOF down the line when it
tries to read from the port.
I think this is a bug. The intended semantics of keep-alive? (I believe)
is to keep it alive _after_ the request (including the body) is
finished, not just the request headers.
Strange though, I never noticed this come up when adding the chunked
support in the first place.
--
Ian Price -- shift-reset.com
"Programming is like pinball. The reward for doing it well is
the opportunity to do it again" - from "The Wizardy Compiled"
next prev parent reply other threads:[~2012-12-08 19:59 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-12-05 23:20 bug#13095: http-get: Throw to key `bad-response' with args `("EOF while reading response body: ...)' Nikita Karetnikov
2012-12-08 19:59 ` Ian Price [this message]
2012-12-08 20:06 ` Ian Price
2012-12-08 20:47 ` Ian Price
[not found] ` <87d2ykqkiy.fsf@zigzag.favinet>
2012-12-08 23:39 ` Ludovic Courtès
2012-12-10 13:45 ` dsmich
2013-01-12 14:47 ` Ian Price
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=871uf0b9hl.fsf@Kagami.home \
--to=ianprice90@googlemail.com \
--cc=13095@debbugs.gnu.org \
--cc=ludo@gnu.org \
--cc=nikita.karetnikov@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).