Philip Kaplan wrote:
I am not a squid user...yet...but I may be if it can do what I need.
Can any of you kind souls tell if the following is possible...and not
extremely difficult to setup by a neophyte:
What I need:
- Squid acts as a proxy server for HTTP traffic. It accepts HTTP
traffic and forwards the traffic to either:
1) HTTP proxy server A if the destination host in the URL matches a
list of local values
2) HTTP proxy server B if the destination host in the URL matches a
different list of local values
3) the actual destination if the destination host in the URL is
unmatched in either list
...where proxy A and B are other proxy servers servicing my network
(and out of my control).
This scheme has nothing to do with client IPs. It's all about the
destination. I have an application that will call web services on a
range of different servers and some of the web service calls must go
through proxy A, others must go through proxy B, and some must be
direct (i.e., no other proxy)...and the application can either handle
no proxy or one proxy. I would like to install squid on the same box
and point my application to 127.0.0.1 for its proxy server and let
squid handle the rest.
Thanks!
Yes it is possible. Fairly easy in fact.
You need to lookup the types of ACL available, cache_peer,
cache_peer_access, always_direct, and never_direct directives.
The directives combine with ACL to route requests individually to
certain sources, including direct.
http://www.squid-cache.org/Versions/v3/3.0/cfgman/
Amos
--
Please use Squid 2.7.STABLE4 or 3.0.STABLE9
