Feature #15755
Test the download mirror before using it on the download page
0%
Description
For example, the client JS could check that the trace (https://mirrors.edge.kernel.org/tails/project/trace) can be retrieved without error before replacing the mirror URL on the page.
I think it should be a simple matter of programming™. Possible issues:
- This code is also run from Tails Upgrader so care will need to be taken not to break that (e.g. the Upgrader will need to ensure the JS code uses Tor to check the mirror).
- Semantics will change a bit but the current design does not seem totally adverse to that.
Subtasks
History
#1 Updated by sajolida 2019-06-19 09:59:15
- Assignee deleted (
None) - Target version set to Tails_3.15
This is the ticket about the code. The parent describes an abstract problem that could be solved in different ways.
#2 Updated by CyrilBrulebois 2019-07-10 10:34:07
- Target version changed from Tails_3.15 to Tails_3.16
#3 Updated by CyrilBrulebois 2019-09-05 00:05:36
- Target version changed from Tails_3.16 to Tails_3.17
#4 Updated by intrigeri 2019-09-12 14:25:19
- Target version changed from Tails_3.17 to Tails_4.0
#5 Updated by Anonymous 2019-10-21 11:39:32
- Target version deleted (
Tails_4.0)
I had already started working on this, but as it is volunteer work, it has seen no follow up lately. I’m currently unsure if I will do that soon or not, so I’m dropping the target version.
#6 Updated by Anonymous 2019-10-21 11:55:49
- Assignee deleted (
)
Actually, I’ll also drop myself as assignee unless there is a budget to work on this.
#7 Updated by sajolida 2019-11-04 19:45:48
- Affected tool set to Verification Extension
The mirror team has been a bit less responsive lately and solving this would drastically lower the pressure on them.
I’ll find someone to work on this on the Verification Extension budget.
It’s only vaguely related but it’s JS on the same page and should be little work (~2 h).