Re: [squid-users] Difference between Squid 3.1 & 3.4 regarding HTTPS CONNECT handling

2015-07-11 Thread Amos Jeffries
On 10/07/2015 8:30 a.m., Andrew Wood wrote: > OK heres the difference > > http_port 192.168.10.254:3128 intercept > http_port 192.168.10.254:3129 You should have port 3128 for the non-interept traffic. > > I had to setup squid on a second port not in intercept mode and set the > WPAD file to se

Re: [squid-users] Difference between Squid 3.1 & 3.4 regarding HTTPS CONNECT handling

2015-07-09 Thread Andrew Wood
OK heres the difference http_port 192.168.10.254:3128 intercept http_port 192.168.10.254:3129 I had to setup squid on a second port not in intercept mode and set the WPAD file to send HTTPS requests there. Why will the intercept port accept HTTPS CONNECT requests in 3.1 but not 3.4? Regard

[squid-users] Difference between Squid 3.1 & 3.4 regarding HTTPS CONNECT handling

2015-07-09 Thread Andrew Wood
Ive had Squid 3.1 running on a Debian 7 server for a couple of years working in intercept mode for HTTP traffic and using WPAD to force HTTPS to be CONNECT tunneled through Squid and it works fine. Im now trying to set up a similar system for someone else using Squid 3.4 which is the version i