How can I block QUIC without.......

Hi JohnMMM ,

Thank you for reaching out to the community, by enabling - Block QUIC protocol - Blocks QUIC protocol by dropping outbound UDP packets to ports 80 and 443 for traffic that matches the rule's criteria. It's selected by default when you select a web policy or turn on scanning for HTTP and decrypted HTTPS. Chrome uses the protocol by default to establish sessions with Google services. QUIC traffic can't be scanned and bypasses web filtering. Please refer the useful KBAs below:
> https://5t9h.short.gy/9jlfbt
> Add a firewall rule
> Control traffic requiring web proxy filtering.
> To get better reporting refer HTTPS decrypt and scan FAQ.
> Behavior of HTTPS websites when HTTPS scanning is turned off.

Hi JohnMMM ,

Thank you for reaching out to the community, by enabling - Block QUIC protocol - Blocks QUIC protocol by dropping outbound UDP packets to ports 80 and 443 for traffic that matches the rule's criteria. It's selected by default when you select a web policy or turn on scanning for HTTP and decrypted HTTPS. Chrome uses the protocol by default to establish sessions with Google services. QUIC traffic can't be scanned and bypasses web filtering. Please refer the useful KBAs below:
> https://5t9h.short.gy/9jlfbt
> Add a firewall rule
> Control traffic requiring web proxy filtering.
> To get better reporting refer HTTPS decrypt and scan FAQ.
> Behavior of HTTPS websites when HTTPS scanning is turned off.

As an extension of Viveks explanation...

yes, if the firewall “sees something again” it can also check and log the traffic.

The web filter and weblogging are working again.

Just an update, at this stage he is not using Sophos products and was answered in other post.

Ian