Maybe add a /etc/hosts parser
Categories
(Core :: Networking: DNS, enhancement, P2)
Tracking
()
Tracking | Status | |
---|---|---|
firefox83 | --- | fixed |
People
(Reporter: valentin, Assigned: valentin)
References
(Blocks 1 open bug)
Details
(Whiteboard: [necko-triaged][trr])
Attachments
(1 file)
We've been avoiding this for a while, mostly because the system resolver already checks this file. But lately we've encountered some issues that seem to require us parsing the file.
Comment 1•4 years ago
|
||
We should make sure we can handle very large hosts files. We can test the parser on file generated by AdAway. The generated hosts file on my phone has 48000 lines.
Assignee | ||
Comment 2•4 years ago
|
||
Thanks for the info, Michal.
I've been thinking that we probably don't want to enable it on Android at the moment, considering TRR isn't enabled there.
However, Android is a great testcase for parsing a big file with limited hardware resources, so I'll make sure to test it before we ship it.
Assignee | ||
Updated•4 years ago
|
Assignee | ||
Comment 3•4 years ago
|
||
Updated•4 years ago
|
Updated•4 years ago
|
Updated•4 years ago
|
Comment 5•4 years ago
|
||
bugherder |
Comment 7•3 years ago
|
||
I know this issue is resolved, but I want to mention that Firefox fails to parse a large hosts file (mine has 42000 entries a.t.m).
Happens in a fresh profile as well.
FWIW, Chromium-dev 95.0.4624.0 with DoH enabled (same provider, Quad9) does parse the large file.
A hosts file with only 1 entry is parsed, however it takes some time to display the error message.
Linux Mint 19.3; Firefox 91.0.2
Modified preferences:
network.trr.blocklist_cleanup_done ---> true
network.trr.custom_uri --- > https://dns.quad9.net/dns-query
network.trr.mode --- > 2
network.trr.request_timeout_ms --- > 4000
network.trr.uri --- > https://dns.quad9.net/dns-query
Description
•