> Just consider balancing the load on source IP, or NATing the Squid > servers, as there are a number of websites that don't like a single HTTP > "session" originating from multiple IPs. > Long ago, far away, when I owned a managed server hosting company... We used Foundry load balancers to balance web requests, and just "round robin + quickest" instead of "sticky". We set them up for "Direct Server Return". So even though the balancer was at .254, the server might be at .10, or .22, etc. The number of emails we'd get from people telling us we were trying to hack their machines with our servers was outrageous in the beginning, but soon trailed off. Not sure if the webmaster decided to handle it, or people didn't pay as much attention. Tuc/TBOH
