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
problem.
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.
-Robin
--
Lojban Reason #17: http://en.wikipedia.org/wiki/Buffalo_buffalo
Proud Supporter of the Singularity Institute - http://singinst.org/
http://www.digitalkingdom.org/~rlpowell/ *** http://www.lojban.org/
_______________________________________________
Chicken-users mailing list
[email protected]
http://lists.nongnu.org/mailman/listinfo/chicken-users
