On 15 jun, 15:10, [EMAIL PROTECTED] (Jerry D. Hedden) wrote: > Arno Velds wrote: > > As I mentioned in my somewhat lengthy post I have already worked > > around the problem by not starting new threads from the connection > > All I would like to know is that if I want to be a HTTP/1.0 > > server and only serve 1 request per connection why isn't the second > > request from the same client answered even though they can be 20 > > seconds apart and separated by a $c->close on the server side. > > If you want to be HTTP/1.0, then you need to tell the browser that. > You do this by setting: > $HTTP::Daemon::PROTO = "HTTP/1.0"; > This is then sent with the response so that the browser knows you're > not going to service another request on this socket.
Check....Now I feel silly.... Still, I don't even remotely understand why the exiting of the image thread has any relation with the browser timeout on this weird form of HTTP/1.0 - HTTP/1.1 miscommunication. Oh well... Thanks!
