Create a Post
cancel
Showing results for 
Search instead for 
Did you mean: 
Romaryo
Contributor
Jump to solution

R81.20 "HTTP parsing error occurred" / body filter failed in response

Hello everyone!
We’ve encountered the following phenomenon: many websites don’t fully load when opened (for example, Reddit, GitHub, etc.). In the logs, we see the following events (see attached screenshots). At the same time, we notice HTTP parser errors, and despite the fact that we have the Allow Fail-Open mode enabled and the traffic is allowed, the sites still don’t work. In the browser’s debug console, we can see that connections for fetching *.js files are being reset.
Does anyone have any ideas about this?
Thanks in advance!

0 Kudos
65 Replies
PhoneBoy
Admin
Admin

Are there explicit HTTPS Inspection logs confirming that HTTPS Inspection IS happening over VPN?

0 Kudos
Romaryo
Contributor

Yes.

0 Kudos
PhoneBoy
Admin
Admin

You can, however, explicitly block QUIC at the firewall (UDP/443).
This should cause the browser to go back to HTTP/1.1 on its own.

0 Kudos
Romaryo
Contributor

Unfortunately not. We explicitly block "Quic," and it has no positive effect. Only explicitly disabling HTTP/2 in the browser has a positive effect.

 

best regards,

Roman

0 Kudos
Romaryo
Contributor

Hello everyone! Thank you very much for your support! The problem is solved. The SK116022 has become the solution!

 

best regards,

Roman

0 Kudos
_Val_
Admin
Admin

thanks for sharing

0 Kudos

Leaderboard

Epsum factorial non deposit quid pro quo hic escorol.

Upcoming Events

    CheckMates Events