| > Surely they would just not use HTTP/3 if they can't do it through the configured proxy. That's what I thought, at first. But, back when Chrome introduced QUIC, this was a known phenomenon in proxy-restricted but not-UDP restricted setups. I doubt I'd be able to find a bug report for it, given Google's nature, but there's a few reports[1][2][3] by proxy vendors asking for QUIC to be disabled or traffic will go through, even when Chrome is configured to use a proxy. And here's[4] a user report with the same observation, with Chrome connecting directly to its mothership without going through the configured proxy. The user reports successful blocking upon disabling QUIC 1: https://www.currentware.com/support/disable-quic/ 2: https://support.umbrella.com/hc/en-us/articles/360051232032-... 3: https://support.forcepoint.com/customerhub/s/article/0000154... 4: https://superuser.com/questions/1688524/why-google-com-doesn... > You are spreading FUD. I assure you, I had no such intention. I was just reporting from memory, of years ago, back when I was in college and had to deal with a proxy-restricted network, and QUIC was being rolled out. > My Chrome 115.0.5790.170 doesn't seem to use HTTP 3 at all. Maybe your Chrome has HTTP/3 blocked for some reason. Or, more likely, Chrome supports a different draft of the HTTP/3 spec than the server you're testing against. It has a history of doing that too. |
In this thread we were talking about the user willingly configuring a proxy in the browser or OS.