On 11/23/2012 10:00 AM, Leslie Jensen wrote:
I'm not really sure that I understand the meaning or effect of the
above. We do not have browsers configured with proxy. When I set this up
a few years back the whole idea was that the users should not have to
make any configuration of the browser.
Maybe that's why we got the error with 3.2?
So if I understand correctly this is what I should do
http_port 127.0.0.1:8080 intercept
http_port 172.18.0.1:8080 intercept
http_port 127.0.0.1:8080
http_port 172.18.0.1:8080
The above settings cannot exist!
this is since you are using one port paired with IP for intercept.
squid must have one http_port XXX what ever if you will use it or not.
if you have one port used for either intercept or regular forward proxy
you can't use for another whatever use you want so:
http_port 172.18.0.1:8080 intercept
http_port 127.0.0.1:8080
should be what need.
Also I dont know why you should have a 127.0.0.1:8080 with intercept on
the same line.
I have never seen a use for that in real world unless you are
intercepting the local outgoing connections which I doubt is good.
But it's your needs.
Regards,
Eliezer
--
Eliezer Croitoru
https://www1.ngtech.co.il
sip:ngtech@xxxxxxxxxxxx
IT consulting for Nonprofit organizations
eliezer <at> ngtech.co.il
