Hi there,
I've seen that HTTPS traffic is now handled by the proxy in transparent mode also if I don't scan https traffic. I no more need an extra firewall rule for https traffic.
HTTPS SNI inspection was introduced into 9.165. Under "HTTPS (SSL) traffic:", there's "Do not scan", "URL filtering only" (new), and "Decrypt and scan". The new option is for SNI inspection where newer clients will indicate their desired target server as a part of the TLS negotiation.
The following is with the "Web Filtering" "Operation Mode" in "Transparent Mode". When I have it set to "Do not scan", HTTPS traffic isn't noted at all by the web filter and can be blocked by a simple drop rule. When set to "URL filtering only", the HTTPS drop rule no longer drops the traffic and it is instead filtered by the transparent proxy. While in "Transparent Mode", an HTTP drop rule also has no affect as it's controlled by the transparent proxy.
When in "Standard Mode", I see that "Do not scan" is no longer an option and it forces it to "URL filtering only" and a simple HTTP drop rule blocks transparent access.
hi genec,
you missunderstood me. "Do not scan" is configured. A simple drop rule no more works. All https traffic is handled by the proxy. This is a new behavior.
In the log/pictures, I see critical details that are likely relevant. I was only tweaking the defaullt profile and not a system-specific profile. Does your default profile include "URL filtering only"? This is begining to sound like it's a bug as it should either be noting a different profile/policy OR doing absolutely nothing.
A possible workaround is to configure the default as "Transparent Mode", "Do not scan" then apply "URL Filtering" on another profile that includes the other systems.
I have to discuss that internally. It's possible that we will go with a work around for the next time. I would like to wait for the official version because we use it in a productive environment.
It would be really good to know the publishing date.