Bug #11483

Have mirrors.json use proper server-side caching control

Added by intrigeri 2016-05-24 20:48:52 . Updated 2016-06-01 10:40:12 .

Status:
Resolved
Priority:
Normal
Assignee:
Category:
Infrastructure
Target version:
Tails_2.4
Start date:
2016-05-24
Due date:
% Done:

100%

Feature Branch:
Type of work:
Website
Blueprint:

Starter:
Affected tool:
Deliverable for:
269

Description

Subtasks

Related issues

Blocked by Tails - Feature #8642: Enable the mirror pool dispatcher on all website pages that need it Resolved 2015-01-09 2016-04-15

History

#1 Updated by intrigeri 2016-05-26 13:21:53

  • blocked by Feature #8642: Enable the mirror pool dispatcher on all website pages that need it added

#2 Updated by intrigeri 2016-05-26 13:23:09

  • Status changed from Confirmed to In Progress
  • % Done changed from 0 to 50
  • Type of work changed from Communicate to Website

Done in commit:31787dc65754eadb5bf49f3d09491a8c05304d02, but I won’t be able to easily test until Feature #8642 is live.

#3 Updated by intrigeri 2016-05-31 13:11:59

  • Target version changed from Tails_2.4 to Tails_2.5

I have no clue when Feature #8642 will be reviewed’n’merged, so I can’t keep this on my 2.4 plate.

#4 Updated by intrigeri 2016-06-01 10:40:12

  • Status changed from In Progress to Resolved
  • Assignee deleted (intrigeri)
  • Target version changed from Tails_2.5 to Tails_2.4
  • % Done changed from 50 to 100

Now that the dispatcher is live, I’ve verified that mirrors.json is indeed cached.