Serious Discussion QUIC protocol and ECH BrowserLeaks Test

[simmerskool]

I don't know about that. You need to create network.http.http3.enable entry in about:config manually, then set it to true.

If it was enabled by default, user wouldn't have to do a thing.

... but I agree with @Sampei.Nihira -- when I looked in firefox about:config it was there and it was true, ie enable(d).

 

[Sampei.Nihira]

QUIC has been default on Firefox since 2021 So, not sure what was wrong with your Firefox

Actually, this is not correct. HTTP/1.1 and HTTP/2 can also be TLS 1.3.
You just have to right-click on the title bar and tick Protocol. If the protocol is HTTP/3 then it's QUIC. Same in Chromium browsers.
View attachment 292922

Oh, okay. In that case, I understand. Inspecting QUIC traffic is not as straightforward yet. One example would be that Chromium still don't give an option to inspect QUIC traffic using self-signing certificate (Firefox allows). ECH is also adopted by basically nobody for similar reason. Even if a testing site says, you are using ECH, it is almost 100% useless since it has to enabled server side and almost nobody has enabled it yet.
I have said this before in a different thread that pirated websites like torrent, pirated streams has the highest adoption of QUIC & ECH rate thanks to Cloudflare (which is used by our MT also). Like 9/10 of them or maybe 10/10 (that I sometimes visit) use both.

Perhaps, but as I wrote elsewhere some time ago, the protocol column confuses you even more than Chromium-based browsers.
The test is sufficient with Firefox.
If you analyze various websites that use QUIC with development tools and compare them with Chrome... you'll go crazy.

 

[SeriousHoax]

Perhaps, but as I wrote elsewhere some time ago, the protocol column confuses you even more than Chromium-based browsers.
The test is sufficient with Firefox.
If you analyze various websites that use QUIC with development tools and compare them with Chrome... you'll go crazy.

Yeah, there are a lot in the development tools. The protocol column gives simply an easy overview of whether the site is loaded in H2 or H3. browserleak website for example loads in H2 but in the QUIC testing page it sends a separate quic.browserleaks.com request for testing quic and ech.

 

[SpiderWeb]

It works in Safari but only if I disable iCloud Private Relay which causes HTTP3 to break because not all relays support it yet.