Closed Bug 771170 Opened 12 years ago Closed 12 years ago

[bedrock] Add Expires headers on static components

Categories

(www.mozilla.org :: General, defect, P1)

defect

Tracking

(Not tracked)

VERIFIED FIXED

People

(Reporter: icaaq, Assigned: pmac)

References

Details

(Keywords: perf)

User Agent: Mozilla/5.0 (Macintosh; Intel Mac OS X 10.7; rv:16.0) Gecko/16.0 Firefox/16.0 Build ID: 20120705030540 Steps to reproduce: 1. Press Cmd+N to open a new browser window, then type http://www.mozilla.org/en-US/ in the address bar and press Enter 2. Use firebug and yslow or visit https://developers.google.com/speed/pagespeed/insights#url=http_3A_2F_2Fwww.mozilla.org_2Fen-US_2F&mobile=false&rule=LeverageBrowserCaching to look at the expire dates on static components Actual results: The expire date is not set on static components Expected results: the expire date on static components should be set to a far future date (at least 1 week into the future like the pagespeed page above suggests)
Keywords: perf
Status: UNCONFIRMED → NEW
Ever confirmed: true
Component: www.mozilla.org → General
Product: Websites → www.mozilla.org
Priority: -- → P1
Depends on: 742890
Assignee: nobody → pmac
This is in prod. Link from c0 shows only 4 short expires, two are for GA, and 2 are supposed to be short for tabzilla.
Status: NEW → RESOLVED
Closed: 12 years ago
Resolution: --- → FIXED
I'm seeing expires headers for static content on production now. This bug is fixed
Status: RESOLVED → VERIFIED
You need to log in before you can comment on or make changes to this bug.