Closed
Bug 1613423
Opened 4 years ago
Closed 4 years ago
AsyncResolveWithTrrServer should not check for blacklisted hosts
Categories
(Core :: Networking: DNS, defect, P1)
Core
Networking: DNS
Tracking
()
RESOLVED
FIXED
mozilla74
| Tracking | Status | |
|---|---|---|
| firefox74 | --- | fixed |
People
(Reporter: dragana, Assigned: dragana)
Details
(Whiteboard: [necko-triaged])
Attachments
(1 file, 1 obsolete file)
AsyncResolveWithTrrServer does not really need to check gTrrService->IsTRRBlackliste because it has a specific use.
Checking IsTRRBlackliste cause us to perform TRRServer confirmation. First we do not want to do that and it also cause some AsyncResolveWithTrrServer to fail until the confirmation is done.
|
Assignee | |
Comment 1•4 years ago
|
||
|
|
Assignee | |
Comment 2•4 years ago
|
||
|
||
Updated•4 years ago
|
Attachment #9124523 -
Attachment is obsolete: true
Pushed by ddamjanovic@mozilla.com: https://hg.mozilla.org/integration/autoland/rev/ae0b66604393 Make sure AsyncResoleWithTrrServer does not depend on confirmationNS of the default server. r=valentin
|
||
Comment 4•4 years ago
|
||
| bugherder | ||
Status: ASSIGNED → RESOLVED
Closed: 4 years ago
status-firefox74:
--- → fixed
Resolution: --- → FIXED
Target Milestone: --- → mozilla74
You need to log in
before you can comment on or make changes to this bug.
Description
•