RE: [Chicken-users] Spiffy crashes occasionally

[Dominique Boucher]

> The output is just the standard error messages of a failed 
> write. It seems that the socket is closed unexpectedly. I get 
> this error from time to time, but mostly with a single 
> newline ("can not write to socket: (5 "\n")"). So it's likely 
> that spiffy tries to write one byte too much. Is it possible 
> that the client communicating with spiffy in this case closes 
> the connection too early? The server should handle this 
> problem more gracefully, though.
> I will try to address this.

I noticed that, too. I use Firefox and get such an exception following each
request. That does not happen with Internet Explorer, though (or wget). So
the problem seems to be with Firefox.

> I have not experienced any lockups with spiffy. The only 
> other problem I found is with broken clients: for example 
> wget sends a keep-alive header, even if retrieving a single 
> file. Since spiffy doesn't handle timeout, the connection 
> stays open until the client is forced to quit.

Try "wget --no-http-keep-alive"

Dominique