DNS over HTTPS retry too aggressive on failure
Categories
(Core :: Networking: DNS, defect, P1)
Tracking
()
People
(Reporter: junk07+mozilla, Unassigned)
Details
(Whiteboard: [necko-triaged])
Attachments
(1 file)
|
521 bytes,
text/plain
|
Details |
User Agent: Mozilla/5.0 (X11; Ubuntu; Linux x86_64; rv:76.0) Gecko/20100101 Firefox/76.0
Steps to reproduce:
This morning, a Windows PC running Firefox 77.0.1 effectively launched a DOS attack against my proxy. Direct HTTP(S) requests are explicitly rejected (not merely dropped) by my firewall.
Actual results:
Firefox desperately tried all day (250 times per second!) to use DNS over HTTPS (even though it was disabled in the GUI -- that's a separate issue), trying both cloudflare and nextdns addresses. After millions of attempts, my proxy logs ran out of disk space...
Expected results:
Even if DNS over HTTPS is enabled by the user, Firefox should be a bit less aggressive about trying to use it, esp. since it gave the user no idea that it was happening.
Comment 1•6 years ago
|
||
Bugbug thinks this bug should belong to this component, but please revert this change in case of error.
Comment 2•6 years ago
|
||
There was a bug in 77.0. it should have been fixed in 77.0.1. Can you confirm that the user was running 77.0.1?
Updated•6 years ago
|
| Reporter | ||
Comment 3•6 years ago
|
||
I didn't think to check the version until after restarting FireFox. I'm not as familiar w/ behavior on Windows (most of my work's on Linux) but if it's possible that the upgrade was already in place and it quietly switched on exit/re-launch, that might explain it. I just looked at the program directory, and a ton of files (including the .exe) have a modification timestamp of...right about the time last night that I would've restarted FireFox. To me that suggests that the upgrade to 77.0.1 took place then, I reported the wrong version, and this ticket can be closed! If you agree, please go ahead and close it. And thank you!
Comment 4•6 years ago
|
||
Thank you very much for reporting the bug. It is very appreciated that you reported this bug.
I will closed the bug.
Description
•