Zach Albrecht wrote:
I'm looking for a way for squid to transparently let https bypass or let it flow through properly. I'm using Clarkconnect which is using 2.7 with the latest stable version. I noticed 3.0 has a possibility of letting https flow through but its not yet ported into squid?
I'm not sure I understand what you mean by the above.
Version 2.7 and version 3.0 are two different package releases of Squid.
There is no (or absolute minimal) porting of things 3.0->2.7.
All the porting in Squid happens the other way around as some people
only send patches for 2.x and we are forced to spend time re-writing
them to work with the current 3.x development release.
Any help is greatly appreciated. I just want our users to have access to all websites, there is no need for content filtering.
Best option:
Configure your interception rules to not intercept HTTPS port 443.
Alternative:
use WPAD and PAC to configure browsers transparently. All current
Squid releases handle HTTPS CONNECT method nicely.
Amos
--
Please be using
Current Stable Squid 2.7.STABLE6 or 3.0.STABLE16
Current Beta Squid 3.1.0.9
