Open
Bug 1834715
Opened 1 years ago
Updated 1 year ago
Make sure DoH supports HTTP/3
Categories
(Core :: Networking: DNS, defect, P2)
Core
Networking: DNS
Tracking
()
NEW
People
(Reporter: valentin, Unassigned)
References
(Blocks 1 open bug)
Details
(Whiteboard: [necko-triaged])
There shouldn't be anything preventing the TRRServiceChannel from using HTTP/3, but current telemetry shows it's never being used.
Although there's a HTTPS record for mozilla.cloudflare-dns.com, we never end up using that, as we need DoH to resolve the HTTPS record.
The alternative is the Alt-Svc header, but it seems the cloudflare DoH servers don't send that back in the response.
I did try using https://dns.google/dns-query which does return an Alt-Svc header, but for some reason the DoH connection isn't using it.
Ultimately, we have two issues here:
- Make sure the TRRServiceChannel can use the alt-svc. We can probably add unit test for that.
- Make sure we can resolve HTTPS records using native DNS. This seems like a rather extensive project.
You need to log in
before you can comment on or make changes to this bug.
Description
•