search

Alex313031 / thorium

Chromium fork named after radioactive element No. 90. Windows and MacOS/Raspi/Android/Special builds are in different repositories, links are towards the top of the README.md.
https://thorium.rocks/
BSD 3-Clause "New" or "Revised" License
5.04k stars 153 forks source link

Http3 not working #827

Closed bhunter234 closed 1 month ago

bhunter234 commented 2 months ago

System Details

Problem Even after enabling http3 through chrome://flags/#enable-quic all request are going from http2 protocol. Tested on chrome http3 is working fine there and have alt-svc: h3=":443"; ma=86400 header in all responses if server support http3.

Chrome: image

Thorium

image

Visit https://cloudflare-quic.com/ to test http3

gz83 commented 2 months ago

FYI

https://github.com/Alex313031/thorium/issues/824#issuecomment-2358467879

bhunter234 commented 2 months ago

Dns resolution have nothing to do with the protocols its a bug in thorium tested http3 on brave ,edge and chrome working fine on all those try to open website I mentioned on my previous comment.

gz83 commented 2 months ago

Have you tried the solution I provided? In addition, I found that you and the user in https://github.com/Alex313031/thorium/issues/824 are using similar websites and software, and seem to be trying to bypass network restrictions. You also need to check their settings.

gz83 commented 2 months ago

It may also be due to version differences, which may result in different levels of support for QUIC.

joshbali commented 2 months ago

Dns resolution have nothing to do with the protocols its a bug in thorium tested http3 on brave ,edge and chrome working fine on all those try to open website I mentioned on my previous comment.

Have you tried the solution I provided? In addition, I found that you and the user in #824 are using similar websites and software, and seem to be trying to bypass network restrictions. You also need to check their settings.

@bhunter234 I can confirm that the solution given in #824 works (both on Debian 12 and Windows 11 using Th24 Beta 2 build M126.0.6478.251). As I run Unbound as my DNS resolver with forced secure DNS forwarding on my local network, I don't need any custom secure DNS configuration in my browser. Enabling the "Disable Thorium Custom DNS Config" flag made HTTP3 work on the Cloudflare test page. Enabling or disabling the "Experimental QUIC protocol" flag makes no difference.