Don W. Voorhies

Recently, I’ve put in a support-ticket with my webhost provider, simply.com; the reason for this support-ticket was that I couldn’t understand why this website was gettting transferred via the HTTP 1.1-protocol, when they (i.e.: simply.com) have annonced already back in late-2018 that their servers have been updated to serve via the HTTP/2!

Well, apart from a thread with simply.com’s support that (unfortunately!) gradually went totally sideways, I’ve found out during the past weekend that it was the Bitdefender protection-suite that I have installed on my
laptop, which IS the culprit preventing the HTTP/2-protocol transfers from simply.com’s servers to – in this case – my laptop!

A fact which Bitdefender have been aware of for at at least a couple of years, by the looks of this:
https://community.bitdefender.com/en/discussion/81392/browser-http-1-1-instead-of-http-2-online-global-protection

The quick-fix solution to this issue is to swich off the “Encrypted Web Scan” option, found under Bitdefender’s menu item: “Protection“, then under: “Online Threat Protection -> Settings“.
If Bitdefender’s “Encrypted Web Scan” is necessary, while every “Thomas”, “Richard” and “Harold” are using https, I can’t say; but apparenly (or rather, as I see it) it isn’t a priorty at Bitdefender to remedy this irritating deficiency.

But at least here’s a fix for all of you Bitdefender-users out there!

My whatever apologies to the support-team at simply.com, but guys: try and be a little more forthcoming next time, instead of circle-jerking me around – T.I.A.!

Thanks for reading this…!