[Top][All Lists]

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

Spiffy relies on content-length (was Re: [Chicken-users] Spiffy relies o

From: Robin Lee Powell
Subject: Spiffy relies on content-length (was Re: [Chicken-users] Spiffy relies on removed proc.)
Date: Sun, 16 Mar 2008 13:06:54 -0700
User-agent: Mutt/1.5.17+20080114 (2008-01-14)

On Sun, Mar 16, 2008 at 03:20:11PM +0100, Peter Bex wrote:
> Thanks for the error report!  I've fixed the bug and added a
> testcase for it so it will not happen again.  I've also pushed a
> new release which should be available shortly (3.8).

It seems to work now, but this leads to a more general Spiffy

Run spiffy with:

(define-http-resource ("/test") "test html, sort of")

and then access /test in any browser.  You will find (I hope) that
the browser hangs until timeout or until you kill Spiffy; I
certainly do.

Sending a Content-Length header, which define-http-resource doesn't,
solves the problem.

The issue is *probably* that Spiffy does keep-alive connections by
default, and without Content-Length, there's no way to know when the
server is done talking.

I'm not sure that keep-alive by default is the right thing (I mean
I'm genuinely not sure: I don't know much at all about how
keep-alive works), and even if it is, there should be a way to turn
it off, and there doesn't seem to be.


Lojban Reason #17:
Proud Supporter of the Singularity Institute - ***

reply via email to

[Prev in Thread] Current Thread [Next in Thread]