Amos, Many thanks, I upgraded to 3.1.18 and that seems to have done the trick. Weird as no other parameters were changed. Not sure why 2.6 ( the default for the version of rhel that we have) did not work but no need to investigate now,
Thanks again, Rob On Dec 5, 2011, at 9:42 PM, Amos Jeffries <[email protected]> wrote: > On Mon, 5 Dec 2011 09:14:40 -0500, rob yates wrote: >> Sorry for the bump, could someone let me know if this is supported? If >> it's not supported I'll need to look at something other than squid and >> am far enough along that I would rather not, > > It is supported. Ensure that you have server_persistent_connections ON > (default setting) in squid.conf. > > > The word for today is "upgrade" anyway. > > There are some behaviour and traffic conditions required to make persistent > connections actually work. It appears that one of these conditions is not met > in your system. Probably the server is emitting unknown-length headers or > explicitly requesting connection closure. > > The amount of persistence you can get is up to the particular software > HTTP/1.1 compliance in both Squid and the backend server. So upgrading Squid > to the latest stable release you can will mean a better chance of > persistence happening. > > Amos >
