>> follow_x_forwarded_for allow localhost > acl_uses_indirect_client on > delay_pool_uses_indirect_client on > log_uses_indirect_client on ... are all Squid config lines to integrate with DG. Try removing them, or at least commenting out the first one. > no_cache deny no_cache_sites > http_access deny limituserconStudent > http_access allow manager localhost > http_access deny manager > http_access deny banned_ips > http_access allow update-micro-dom > http_access deny !Safe_ports > http_access deny CONNECT !SSL_ports > http_access allow username > http_access allow localhost « [hide part of quote] Um, only localhost services or authenticated traffic is permitted. Is that correct for your policy? < Opposite, to what I thought, it looks like a setup with DG having squid as parent. DG listens on external port, and forwards the traffic to squid on same host. So the localhost traffic (which is all filtered traffic) passes squid. When removing DG: No go any more. -- View this message in context: http://squid-web-proxy-cache.1019090.n4.nabble.com/Squid-wont-work-when-removing-DG-tp4664359p4664373.html Sent from the Squid - Users mailing list archive at Nabble.com.
