On 23/04/11 14:09, Yang Zhang wrote:
We've been wresting with using Squid as a forward caching proxy for web service calls from our application where we're caching as much as possible. Some of the web service responses don't contain a Content-Length, preventing client-side persistent connections (Squid has no problem persisting connections as long as responses have Content-Length set). Rapid TCP connections/teardowns are dramatically impacting the performance of our application. How do we make Squid specify the content length (which it knows) and thus use persistent connections? Thanks in advance.
This is an open bug. http://bugs.squid-cache.org/show_bug.cgi?id=2824 Amos -- Please be using Current Stable Squid 2.7.STABLE9 or 3.1.12 Beta testers wanted for 3.2.0.7 and 3.1.12.1
