Closed
Bug 735050
Opened 12 years ago
Closed 12 years ago
[perf] Homepage isn't cached at all (because of Cache-Control:max-age=0?)
Categories
(Mozilla Reps Graveyard :: reps.mozilla.org, task)
Mozilla Reps Graveyard
reps.mozilla.org
Tracking
(Not tracked)
RESOLVED
INVALID
People
(Reporter: stephend, Unassigned)
References
()
Details
(Keywords: perf)
Attachments
(1 file)
|
968.44 KB,
image/png
|
Details |
Screenshot, with headers
Every single time we do a GET for http://reps-dev.allizom.org, we fetch it anew, rather than using an in-browser-cached version: [14:31:58.469] GET https://reps.mozilla.org/ [HTTP/1.1 200 OK 1682ms] (At least, it sure looks that way, due to Cache-Control:max-age=0.)
|
Reporter | |
Comment 1•12 years ago
|
||
|
||
Comment 2•12 years ago
|
||
Stephen, We do not cache the dev sites due to the fact that most developers want to see the changes immediately instead of waiting for cache to expire. You will notice that the production site (reps.mozilla.org) is being cached (X-Cache-Info: cached). Regards
Status: NEW → RESOLVED
Closed: 12 years ago
Resolution: --- → INVALID
|
||
Updated•4 years ago
|
Product: Mozilla Reps → Mozilla Reps Graveyard
You need to log in
before you can comment on or make changes to this bug.
Description
•