Closed Bug 528141 Opened 15 years ago Closed 15 years ago

Our far future expires headers are bunk

Categories

(addons.mozilla.org Graveyard :: Public Pages, defect, P2)

Product:
addons.mozilla.org Graveyard
Component:
Public Pages
Type:
defect

Tracking

(Not tracked)

Status:
VERIFIED WORKSFORME

People

(Reporter: clouserw, Assigned: clouserw)

References

Details

Turns out our fancy build system that appends revision numbers to our CSS files and stuff isn't really working because we aren't actually sending expires headers right now.  wtf.

We need to check the rule in webroot/.htaccess and figure out why it's not working.
Blocks: 482737
Assignee: nobody → clouserw
Priority: -- → P2
Uhh

https://addons.mozilla.org/js/amo2009/amo2009.min.js?56011
https://addons.mozilla.org/en-US/firefox/images/t/7564/

both give me expires headers +10 years.  I'm pretty sure someone else was sitting next to me and witnessed not having headers, but.  yeah.
Status: NEW → RESOLVED
Closed: 15 years ago
Resolution: --- → WORKSFORME
I saw it!

And yet, it wfm now as well. I wonder what was up at the time?
Status: RESOLVED → VERIFIED
I blame puppet!
Product: addons.mozilla.org → addons.mozilla.org Graveyard
You need to log in before you can comment on or make changes to this bug.