Nathan Lutchansky wrote:
> Err... Since HTTP/1.1 specifies that keepalive is enabled by default, the
> proxy should *always* expect it to be on. Unless, of course, it sends a
> "Connection: close" header in the request.
Exactly - but when there are bugs it doesn't do that :)
> If I had to make a guess, I'd say that the proxy is waiting for the server
> to send the data associated with the reply, but according to HTTP/1.1
> spec, the 304 code is "special" and explicitly has no data. This should
> probably be a special case in the proxy code then... -Nathan
This was exactly the problem - the original proxy code didn't
distinguish between responses that returned entities and responses that
didn't because all responses ended with EOF.
The latest CVS has this fixed - can you check this for me to see if it
works for you?
Regards,
Graham
--
-----------------------------------------
[EMAIL PROTECTED] "There's a moon
over Bourbon Street
tonight..."
