On Mon, Jul 10, 2006 at 03:30:44PM +0200, Luigi Gangitano wrote: > Hi Steinar, > I forwarded this bug to the upstream developers, who asked for more > informations: > > A somewhat odd server sending back the response before the entire > request have > been sent..
Ah, yes. I've looked around a bit, and I think I know what happens: For some reason, Apache starts sending back the _beginning_ of the response as soon as it gets the headers -- but at some point, it runs out of buffer or something and waits for the body. Only when the body arrives, it sends out the end. (AFAIK it's fully entitled to do this if it likes.) Squid, OTOH, isn't much better: As soon as it receives the header in the request, it sends it on to Apache -- but it seems to simply ignore the body. (Perhaps it doesn't know that PROPFIND can have a body?) Since it never sends the body, Apache never ends the request, and after a while it simply seems to time out, leaving the Squid with only a partial response to send back. IMO Squid should be fixed to read the body and pass it on, even though the server starts sending out responses. > Please collect etheral traces of the traffic between Squid and the > web server > and attach the saved packet dump to this bug report for further > analysis. Note: > Raw packet dump, not decoded data.. Attached. I took the liberty to blank out the passwords in the dump, so don't worry if some of the checksums are suddenly off. /* Steinar */ -- Homepage: http://www.sesse.net/
dump2
Description: Binary data
