The TRR mode3 error page should not add exception when the resolver is not accessible
Categories
(Firefox :: Security, task, P1)
Tracking
()
Tracking | Status | |
---|---|---|
firefox111 | --- | fixed |
People
(Reporter: valentin, Assigned: valentin)
References
(Blocks 3 open bugs)
Details
(Whiteboard: [necko-triaged])
Attachments
(2 files)
If the TRR resolver is not accessible, and we add an exception, it might not help usually.
Additionally, if the page you are loading contains any resources hosted on other domains, it will break in different ways.
Assignee | ||
Comment 1•2 years ago
|
||
If the error is caused by the TRR server not being accessible (maybe the
network is down) then adding an exception is unlikely to make the load.
Most likely the subsequent page load will also lead to an error page.
However, after connectivity is restored, the exception would remain.
Currently the ability to remove exceptions is lacking a UI.
In the future we might want to replace the exception button with a button
that would exclude the current tab from TRR instead - that way the
exception is not permanent when the failure is caused by a connection
failure to the TRR server.
Assignee | ||
Comment 2•2 years ago
|
||
Depends on D168077
Comment 5•2 years ago
|
||
Backed out for causing for causing bc failures in browser/base/content/test/about/browser_aboutNetError_trr.js
Backout link: https://hg.mozilla.org/integration/autoland/rev/61ccf9e87d019eb3efa2f9c396e88bb355cf9c3b
Comment 7•2 years ago
|
||
bugherder |
https://hg.mozilla.org/mozilla-central/rev/fed641dc5ab5
https://hg.mozilla.org/mozilla-central/rev/72fbdf21d978
Assignee | ||
Updated•2 years ago
|
Description
•