-
Notifications
You must be signed in to change notification settings - Fork 1.8k
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
HTTP/3 support for frontend and DNS-over-HTTPS (DNS-over-HTTP/3, DoH3) #3955
Comments
AFAIK, the Go standard library currently doesn't support HTTP/3, and probably won't until it graduates the draft standard phase. Once it does, the Go standard library will probably get an implementation shortly. |
DNS-over-HTTP3 support has been recently added to Here's what we should do now:
Eventually, we'll enable it globally so there's no need to expose it to the UI. |
Updates #3955. Squashed commit of the following: commit acfd5cc Merge: caeac6e 61bd217 Author: Ainar Garipov <A.Garipov@AdGuard.COM> Date: Mon Oct 3 18:00:37 2022 +0300 Merge branch 'master' into 3955-doh3 commit caeac6e Author: Ainar Garipov <A.Garipov@AdGuard.COM> Date: Mon Oct 3 17:54:16 2022 +0300 all: fix server closing; imp docs commit 8739614 Author: Ainar Garipov <A.Garipov@AdGuard.COM> Date: Mon Oct 3 17:33:39 2022 +0300 all: add doh3 support
Added in |
I have enabled both the config file parameters
but I am unable to use the following 2 providers in my upstream. My upstream section looks like this
Can you please advise where I am going wrong? |
Should be Also, you don't need to enable these two config parameters if you use
|
Updates AdguardTeam#3955. Squashed commit of the following: commit acfd5cc Merge: caeac6e 61bd217 Author: Ainar Garipov <A.Garipov@AdGuard.COM> Date: Mon Oct 3 18:00:37 2022 +0300 Merge branch 'master' into 3955-doh3 commit caeac6e Author: Ainar Garipov <A.Garipov@AdGuard.COM> Date: Mon Oct 3 17:54:16 2022 +0300 all: fix server closing; imp docs commit 8739614 Author: Ainar Garipov <A.Garipov@AdGuard.COM> Date: Mon Oct 3 17:33:39 2022 +0300 all: add doh3 support
Hello,
as far as we all know HTTP/3 it's close... Please add HTTP/3 support for three AGH entities:
As I understand it, now the server is forcing down the connection protocol to HTTP/2☹️ Some providers already provide DoH3 support. For example, NextDNS has an DoH3 endpoint so you can try to test it too:
https://doh3.dns.nextdns.io/subscription_id/clients_id
https://help.nextdns.io/t/y4hfw14/cant-use-doh3
Thank you.
Best regards!🎁
The text was updated successfully, but these errors were encountered: