Amos Jeffries skrev 2012-11-23 03:14:
+ 3.2 intercept port receiving forward-proxy requests will reject them
due to NAT failure/lies.
+ 3.2 Host header validation *will* reject if forward traffic is
validated as being intercepted.
** you need at minimum to add a http_port line without "intercept" on it
for the Squid icons and configured browsers to fetch from.
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
Thanks
/Leslie
