Application Control - HTTP parsing error occurred

[sx8n20394]

I may have posted about this previously on a thread but wanted to see if anyone else is having this show up in their logs for all QUIC traffic. Checkpoint is supposed to be able to parse QUIC but we get nothing but parsing errors. The default action is to block the connection but we are getting complaints that some services get disrupted such as Teams, Outlook, etc

Application Control - HTTP parsing error occurred

[Chris_Atkinson]

Concerning QUIC - HTTP/3 inspection specifically?

With chromium preventing custom CAs for QUIC as of recently I suspect it can no longer be done reliably since Edge / Chrome are the most prevalent browsers in enterprises.

Refer also: https://support.checkpoint.com/results/sk/sk111754 

[SaxMan]

Hi,
I'm just checking if you had any resolution to this?

I have the same error message popping up on an IoT device (Rainbird Sprinkler).
(Device is in IoT Vlan)

On a 1800 with version: R82.00.10 (998002203), I have created two exception rules in Threat Prevention for the device, namely destinations rbcloud and AWS to be ignored for HTTP in the Anti-Virus blade.
In the logs, I can see the IoT device connecting to the destinations (I'm using the public IP addresses for rbcloud and AWS' Load Balancers...not their domain names).
However, on the user's Android Rainbird app, the error message is that the device/controller has not "checked in with the cloud"

The weird part is that I moved the IoT device to a different WiFi SSID connected to a 1500 SMB with R81...and bingo!... it works!

PS. 
Both SMB gateways are locally managed.

Please let me know if you've found a "workaround" or resolution.
Thanks.