1451890 - TRR: set wait-for-portal false by default?

Status: RESOLVED FIXED

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

Description

[Daniel Stenberg [:bagder]]

When doing a session restore with a bunch of tabs, including a bunch of pinned ones, Firefox will do a number of name resolves before the captive portal check has "green-lighted" the current connection.

Right now, the default pref says that TRR isn't to be used until captive portal is okay which in trr-first and trr-race modes will cause a number of native resolves at startup. (trr-only mode never waits for captive portal)

I propose that we change the default so that TRR doesn't wait for captive portal so that we can get more early TRR resolves (primarily) in trr-first mode.

And also, a captive portal is detected and then later again cleared, we flush the TRRblacklist at the time of the CP clear event so that the failed TRR resolves that occurred while in CP don't stick around unnecessarily long.

Comment 1

[Sylvestre Ledru [:Sylvestre]]

Moving to p3 because no activity for at least 24 weeks.

Comment 2

[Valentin Gosu [:valentin] (he/him)]

Attachment: Bug 1451890 - TRR: set wait-for-portal false r=mayhemer

Comment 3

[Pulsebot]

Pushed by [e-mail]:
https://hg.mozilla.org/integration/autoland/rev/a75b9d4e8408
TRR: set wait-for-portal false r=mayhemer

Comment 4

[Bogdan Tara[:bogdan_tara | bogdant]]

https://hg.mozilla.org/mozilla-central/rev/a75b9d4e8408