Re: Pipelined requests

Adrian Chadd wrote:

> > The problem is in clientSendMoreData(), or actually the fact that the
> > second reply isn't deferred until clientSendMoreData() is invoked on it
> > by the store.. storeClientSendMoreData() then notices this is not the
> > current reply for the connection, forgets the data it got and assumes it
> > is OK to just ask for the data again when the reply can be forwarded by
> > restarting the store_client_copy() call in
> > clientKeepaliveNextRequest()...
> >
> > This is only one of the bugs in how Squid deals with pipelined requests..
> > that whole section of the code is bit of mess. There is also some
> > suspect timing problems in clientReadRequests() and how/when/why the
> > processing of pipelined requests are deferred, and access.log..
>
> has it ever worked ? has anyone ever defined it it should work
> so an/the implementation can be checked?

The first does work in 2.5 and earlier, as there one is allowed to ask again
for the same data as many times as is neeede.

The second mess exists in all versions but is not critical to the function..

Note: Processing of pipelined request has been very fragile over the years.
The deferred replies seems to push some of the other Squid code into paths
rarely reached on "normal" request/reply processing..

Regards
Henrik
Received on Mon Jul 15 2002 - 07:13:06 MDT