On 17/09/11 19:39, Babu Chaliyath wrote:
On Thu, Sep 15, 2011 at 5:44 PM, Amos Jeffries wrote:
On 15/09/11 06:45, MargaretGillon wrote:
Hi Amos,
Even if I do not use the IP address the .services.chromalloy.local is
being blocked.
Adding the IP to this line
acl localServices dstdomain .services.chromalloy.local 192.168.3.42
did not fix anything. Both addresses are blocked.
Wow. Strange. Try setting debug_options to "ALL,1 28,4 85,2" and see what
ACLs are denying it.
Amos
--
Sorry if I am jumping the gun, isn't it the IP of squid proxy server
to be used instead of 192.168.3.42?
Sorry if that question was wrong
Babs
Normally this type of thing is done with reverse-proxy mode, where it is
the IP of the Squid server. Since that is where the browsers and agents
are connecting to.
In this particular case MargaretGillon has the agent operating in
forward-proxy traffic which can pass the raw-IP of the remote server to
Squid for forward-proxy connection to be established. The logs displayed
in earlier emails indicate that these uncommon circumstance is happening.
Amos
--
Please be using
Current Stable Squid 2.7.STABLE9 or 3.1.15
Beta testers wanted for 3.2.0.11
