Re: [squid-users] handling different two way ssl-request via a proxy system

Thanks Amos. I will submit this as a new feature request on http://bugs.squid-cache.org / Abdelouahed > Op 15 apr. 2015, om 11:22 heeft Amos Jeffries het > volgende geschreven: > > On 15/04/2015 7:12 a.m., Abdelouahed Haitoute wrote: >> Hello Amos, >> >> Thank

Re: [squid-users] handling different two way ssl-request via a proxy system

On 15/04/2015 7:12 a.m., Abdelouahed Haitoute wrote: > Hello Amos, > > Thank you for your reply. > >> Problem A) >> requirements #1 and #2 above are mutually exclusive. >> >> Obeying #1 involves sending traffic from Squid to the parent proxy for >> action. >> >> Obeying #2 involves opening direct

Re: [squid-users] handling different two way ssl-request via a proxy system

Hello Amos, Thank you for your reply. > Problem A) > requirements #1 and #2 above are mutually exclusive. > > Obeying #1 involves sending traffic from Squid to the parent proxy for > action. > > Obeying #2 involves opening direct TLS connections from Squid to the > origin servers. Is it possib

Re: [squid-users] handling different two way ssl-request via a proxy system

On 14/04/2015 11:57 p.m., Abdelouahed Haitoute wrote: > > There are two thing I haven’t realized in the development > environment, because I don’t know how: > 1. Making the Squid 3.1.10 to use a proxy system, because that’s our > policy to communicate to the outside world. In apache we use the >

[squid-users] handling different two way ssl-request via a proxy system

Hello, Currently we’ve got the following situation in our production environment: Clients —HTTP—> Apache —HTTPS TWO-WAY SSL VIA EXTERNAL PROXY —> HTTPS SERVERS Just to be clear, the following services are used during this flow: http client (firefox, chrome, curl, wget, etc.) —> Apache (which se