Version info:

qutebrowser v3.5.1
Git commit: a45d57fee-dirty on main (2025-06-06 12:53:10 +0200)
Backend: QtWebEngine 6.9.1
  based on Chromium 130.0.6723.192
  with security patches up to 136.0.7103.114 (plus any distribution patches)
  (source: api)
Qt: 6.9.1

Does the bug happen if you start with --temp-basedir?: yes

Description

Somewhat similar to #8568, Reddit.com:

and https://user-agent-client-hints.glitch.me/:

("SSL Certificate Required"‽)

I opened a ticket with Reddit and set "number of users affected" to 1000+ (only fair I'd say). Let's see what they have to say.

Interestingly, "copy as curl" in the devtools works just fine, and with --qt-flag disable-http2 both pages suddenly start working again. So maybe there is some difference in the HTTP/2 implementation between QtWebEngine and Chromium that breaks this?!

Incredibly frustrating how often this kind of thing is happening recently. My best bet is that the big corporate "security solution" providers wanted to have their own equivalent of https://anubis.techaro.lol/ to block AI scrapers, and in turn ended up with overzealous blocking of qutebrowser as collateral damage. Sigh.