On Tue, 28 Dec 2004, Stefan Wiederoder wrote:
we have an issue with client/server persistent connections - oneapplication is fine with the current default (client/server on) and another is saying "zero sized reply". If we set client/server to off - application two is fine. But we're too chicken to risk trouble with the other applications, therefore I�ve thought about enhancing Squid to make this possible.
my idea is to transform this server_persistent_connections { on | off } client_persistent_connections { on | off }
to something like this:
pconn pconn-name source destination client-persistent server-persistent example: pconn app1 any server.app1 on on pconn app2 any server.app2 on off pconn app3 any server.app3 off off pconn any any any on on (to enable a default like today)
it would be better and in fact desireabele to extend the existing directives to be acl driven similar to how tcp_outgoing_address/tcp_outgoing_tos/access_log and many other acl driven directives work.
server/client_persistent_connections on/off [acl ...]
It would not be good to merge the two into a single directive as what these address is a hop by hop property affecting either client<->squid or squid<->server communication. If you have problems you most likely have problems either with a specific client (client_persistent_connections) or a specific server (server_persistent_connections) and trying to apply the same rule on both does not make much sense.
Regards Henrik
