Closed
Bug 993919
Opened 11 years ago
Closed 11 years ago
[tarako] Add querystrings of content hashes to appcache manifest
Categories
(Marketplace Graveyard :: Consumer Pages, defect, P2)
Tracking
(Not tracked)
RESOLVED
FIXED
2014-04-15
People
(Reporter: cvan, Assigned: cvan)
References
Details
(Keywords: perf, Whiteboard: [qa-])
Because we're setting far-future `Cache-Control` `max-age`s on the resources defined in the appcache manifest, we need to add querystring parameters to properly cachebust the resources listed in the appcache manifest. The cachebusting-querystring parameter should be a hash of the resource's contents, so we don't accidentally invalidate a resource when it actually hasn't changed.
Assignee | ||
Comment 1•11 years ago
|
||
https://github.com/mozilla/darjeeling/commit/d2ec568
Wooooooo! This is awesome!
Status: NEW → RESOLVED
Closed: 11 years ago
Resolution: --- → FIXED
Assignee | ||
Updated•11 years ago
|
Whiteboard: [qa-]
Assignee | ||
Comment 2•11 years ago
|
||
Reverted: https://github.com/mozilla/darjeeling/commit/b23d925
We don't need this anymore. As long as we never set `Cache-Control`/`Expires` headers and always stick to `ETag`s, we don't need to do cachebusting. And there's no perf hit incurred anyway.
You need to log in
before you can comment on or make changes to this bug.
Description
•