Don't skip TRR if confirmation is still pending
Categories
(Core :: Networking: DNS, defect, P2)
Tracking
()
Tracking | Status | |
---|---|---|
firefox87 | --- | fixed |
People
(Reporter: nhnt11, Assigned: nhnt11)
References
Details
(Whiteboard: [necko-triaged])
Attachments
(1 file)
Currently TRR is completely blocked on confirmation. In mode 2 we have fallback anyway, so at least until we are sure that confirmation failed, we can do the lookup optimistically and let it fallback if something is wrong.
Additionally, we should avoid blocklisting individual hosts if confirmation state is not OK, because we don't do any logic to be sure that the failure is for an individual name.
Assignee | ||
Comment 1•4 years ago
|
||
Assignee | ||
Comment 2•4 years ago
|
||
This patch brings the total TRR_NOT_CONFIRMED failures at startup down from 10 to 1 on my local build.
Assignee | ||
Comment 3•4 years ago
|
||
Assignee | ||
Comment 4•4 years ago
•
|
||
The semantics of Enabled() are slightly different than my first interpretation. Patch updated and new try push is here:
https://treeherder.mozilla.org/#/jobs?repo=try&revision=c0a365853f5ba313918670bb7fa087d93ff534cf
https://treeherder.mozilla.org/#/jobs?repo=try&revision=83b96c0d8acc065587524844071586bcd33ec43d
Updated•4 years ago
|
Updated•4 years ago
|
Assignee | ||
Updated•4 years ago
|
Assignee | ||
Comment 5•4 years ago
|
||
Comment 7•4 years ago
|
||
bugherder |
Description
•