Closed Bug 1809488 Opened 2 years ago Closed 2 years ago

The TRR mode3 error page should not add exception when the resolver is not accessible

Categories

(Firefox :: Security, task, P1)

task

Tracking

()

RESOLVED FIXED
111 Branch
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.

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.

Depends on D168077

Pushed by valentin.gosu@gmail.com: https://hg.mozilla.org/integration/autoland/rev/fed641dc5ab5 The TRR mode3 error page should not add exception when the resolver is not accessible r=acreskey,Gijs
Status: NEW → RESOLVED
Closed: 2 years ago
Resolution: --- → FIXED
Target Milestone: --- → 111 Branch
Flags: needinfo?(valentin.gosu)
Blocks: 1815209
You need to log in before you can comment on or make changes to this bug.

Attachment

General

Created:
Updated:
Size: