Could browser.dns.resolve support to resolve HTTPS records?
Categories
(WebExtensions :: General, enhancement)
Tracking
(Not tracked)
People
(Reporter: fantasyfate, Unassigned)
Details
(Whiteboard: [necko-triaged])
Steps to reproduce:
Browsing any website with uBlock Origin installed and DoH enabled
Actual results:
Currently, if browser.dns.resolve is used, Firefox only resolves A and AAAA records for it (https://searchfox.org/mozilla-central/source/toolkit/components/extensions/parent/ext-dns.js#74 and https://searchfox.org/mozilla-central/source/netwerk/dns/nsIDNSService.idl#34-42), then resolves A, AAAA, and HTTPS records. In the first step, A and AAAA records are cached by DNS resolver, so resolving DNS HTTPS records is possibly slower than A and AAAA records, and HTTPS upgrade or HTTP/3 upgrade brought by HTTPS records could be more likely to fail to work.
Expected results:
The browser.dns.resolve supports to resolve HTTPS records.
|
||
Comment 1•3 years ago
|
||
The Bugbug bot thinks this bug should belong to the 'Core::Networking: DNS' component, and is moving the bug to that component. Please correct in case you think the bot is wrong.
|
Reporter | |
Comment 2•3 years ago
|
||
Furthermore, is it possible to make website and browser.dns.resolve share the DNS cache in the browser? If so, superfluous DNS requests could be eliminated.
|
||
Comment 3•3 years ago
|
||
To support this, most of work needs to be done in toolkit/components/extensions/parent/ext-dns.js, so change the component to WebExtensions.
Description
•