browser caching of added content is too long
Bug #2054347 reported by
Galen Charlton
This bug affects 2 people
| Affects | Status | Importance | Assigned to | Milestone | |
|---|---|---|---|---|---|
| Evergreen |
New
|
Undecided
|
Unassigned | ||
Bug Description
The default max-age of one year set by the patch for bug 1681095 can make updates of cover images slower than it should be, as ultimately there's no way around having to do a forced reload to be sure you're getting the most recent image. (Even after you clear the AC cache - see bug 1939162).
Short of calculating a per-cover-image version number, a shorter expiration is in order. 5 minutes would be too short; a couple hours might be OK; but a year is far too long.
| tags: | added: caching |
| summary: |
- caching of added content is too long + browser caching of added content is too long |
To post a comment you must log in.
