Re: [squid-users] Access denied on transparent after upgrade 3.1.x to 3.3

Hi
I do intercept traffic using iptables, problem is same config works
for squid 3.1.2, I did remove all access rules and ended up with the
config below but I still get an access denied error.

always_direct allow all
ssl_bump allow all
sslproxy_cert_error allow all

http_port 0.0.0.0:80 transparent
http_port 0.0.0.0:8080 transparent
http_port 0.0.0.0:3128
#http_port 127.0.0.1:3080 intercept
#https_port 0.0.0.0:443 transparent intercept
cert=/etc/squid/proxy.example.com.cert
key=/etc/squid/proxy.example.com.key
#https_port 0.0.0.0:443 transparent ssl-bump
cert=/etc/squid/proxy.example.com.cert
key=/etc/squid/proxy.example.com.key

http_access allow all

coredump_dir /usr/local/squid/var/cache/squid

# Add any of your own refresh_pattern entries above these.
refresh_pattern ^ftp: 1440 20% 10080
refresh_pattern ^gopher: 1440 0% 1440
refresh_pattern -i (/cgi-bin/|\?) 0 0% 0
refresh_pattern . 0 20% 4320
#debug_options ALL,3

Regards

On Wed, Dec 19, 2012 at 9:45 PM, Eliezer Croitoru <eliezer_at_ngtech.co.il> wrote:
> egards,
> Eliezer
Received on Thu Dec 20 2012 - 09:05:47 MST