Closed Bug 1487432 Opened Last year Closed Last year

make LOAD_DISABLE_TRR avoid connection reuse of non-TRR connections

Categories

(Core :: Networking: DNS, enhancement, P1)

enhancement

Tracking

()

RESOLVED FIXED
mozilla63
Tracking Status
firefox63 --- fixed

People

(Reporter: bagder, Assigned: bagder)

References

Details

(Whiteboard: [necko-triaged][trr])

Attachments

(1 file)

To make the flag really have an effect also when there are existing connections to the the given host names, we must make sure requests that explicitly disable TRR isn't mixed with connections that allow TRR. Because if we do, the disable-TRR request can easily end up reusing an existing TRR-resolved connection.

Note that the connections don't really know if TRR will be used or not when resolving.
Blocks: 1473519
so that such requests don't inadvertently reuse connections done that
might have used TRR.

MozReview-Commit-ID: 2bO4VCGSgOO
Comment on attachment 9005252 [details]
bug 1487432 - make LOAD_DISABLE_TRR enforce a different hashkey

Valentin Gosu [:valentin] has approved the revision.
Attachment #9005252 - Flags: review+
Pushed by daniel@haxx.se:
https://hg.mozilla.org/integration/autoland/rev/6550838c8046
make LOAD_DISABLE_TRR enforce a different hashkey r=valentin
https://hg.mozilla.org/mozilla-central/rev/6550838c8046
Status: ASSIGNED → RESOLVED
Closed: Last year
Resolution: --- → FIXED
Target Milestone: --- → mozilla63
You need to log in before you can comment on or make changes to this bug.