Closed Bug 1490088 Opened 7 years ago Closed 7 years ago

elmo webapp should send cache-friendly http headers for static

Categories

(Webtools Graveyard :: Elmo, enhancement)

Product:
Webtools Graveyard
Component:
Elmo
Type:
enhancement
Priority:
Not set
Severity:
normal

Tracking

(Not tracked)

Status:
RESOLVED FIXED

People

(Reporter: Pike, Assigned: Pike)

References

Details

As I was working on bug 1484189, I noticed that l10n.m.o sends http headers that force reload each and every request. At least for /static/*, we should send http headers to never expire, with l10nstats/progress.* being exempt to cache for 4 hours.
Commit pushed to develop at https://github.com/mozilla/elmo https://github.com/mozilla/elmo/commit/13a783ceff79ad833f3d720f3b46e4a7227ff9a3 bug 1490088, use whitenoise for static files I've run around trying to find good ways to set Cache-Control headers, and ended up looking at whitenoise again. That does it, and whatever rubbed me backwards last time, I can't find that no more. Maybe 4.0 fixed that.
> regarding the header, if the application doesn't set Cache-Control our standard nginx config adds `"private, no-cache, no-store, must-revalidate"` Ended up adding whitenoise to elmo, looks like the easiest path to get Cache-Control headers on our static files.
Assignee: nobody → l10n
This is now in prod.
Status: NEW → RESOLVED
Closed: 7 years ago
Resolution: --- → FIXED
Product: Webtools → Webtools Graveyard
You need to log in before you can comment on or make changes to this bug.