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.
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.