Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Http3 not working #827

Open
bhunter234 opened this issue Sep 19, 2024 · 5 comments
Open

Http3 not working #827

bhunter234 opened this issue Sep 19, 2024 · 5 comments

Comments

@bhunter234
Copy link

bhunter234 commented Sep 19, 2024

System Details

  • OS: Windows 11
  • Thorium Version: latest

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
Copy link
Collaborator

gz83 commented Sep 19, 2024

FYI

#824 (comment)

@bhunter234
Copy link
Author

bhunter234 commented Sep 19, 2024

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
Copy link
Collaborator

gz83 commented Sep 19, 2024

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.

@gz83
Copy link
Collaborator

gz83 commented Sep 19, 2024

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

@joshbali
Copy link

joshbali commented Sep 20, 2024

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.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

3 participants