Problem is here:
>....HIER_DIRECT/127.0.0.1 ...<
Strange enough, squid forwards the request to 127.0.0.1 ....
I am not sure, whether you need 2 ports to be specified:
http_port 3129
http_port 3128 intercept
In your setup, you need special firwall rules, to avoid a loop:
DG forwards to port 80, squid intercepts, forwards to port 80, NO INTERCEPT
THEN (hopefully)
So you should post firewall rules, as well.
Otherwise:
I always did it the other way:
client --- (transparent) squid ---DG --web
because
1) client does not need to specify proxy explicitly (in your setup, a MUST)
2) no need to cache content, later on blocked by DG
3) Not sure any more, whether DG supports parent proxy
Then my setup matched the rules in
http://wiki.squid-cache.org/ConfigExamples/Intercept/LinuxRedirect
Only the line
cache_peer 127.0.0.1 parent DG-port 0 no-query no-digest no-netdb-exchange
to be added to squid.conf
-- View this message in context: http://squid-web-proxy-cache.1019090.n4.nabble.com/How-to-make-Squid-3-3-8-a-transparent-proxy-tp4665624p4665633.html Sent from the Squid - Users mailing list archive at Nabble.com.Received on Sat Apr 19 2014 - 06:15:27 MDT
This archive was generated by hypermail 2.2.0 : Sun Apr 20 2014 - 12:00:05 MDT