Thanks for the tips! Was my cache_peer line OK? The possibility of hitting an item from a different port could be disastrous, however. Are they identified by both host and URI, or if the URI is the same (say, both /index.html) could you get the wrong one? If this cannot be fixed through configuration, we might have to have hundreds of instances of squid to keep things truly separate, but that would be a huge pain in the neck to manage. -- View this message in context: http://squid-web-proxy-cache.1019090.n4.nabble.com/Squid-3-2-0-9-problems-and-special-reverse-proxy-configuration-tp3665862p3667773.html Sent from the Squid - Users mailing list archive at Nabble.com.
