540217 - Browser cache for JS, CSS, and images on AMO

Status: RESOLVED FIXED

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

Description

[Justin Scott [:fligtar]]

According to Tamper Data, Firefox requests every single background image, CSS stylesheet, and JS file on every page load and never caches it because of SSL.

According to this post (http://blogs.gnome.org/jamesh/2008/05/01/firefox-ssl/) if we set Cache-control to public, it will become cacheable. Cache-control on these items is currently "no-cache".

We should investigate this 1.5 years ago.

Comment 1

[Justin Scott [:fligtar]]

Note that my "no-cache" mention was as a logged-in user. When logged out, we don't seem to send a cache-control header at all.

Also, dolske pointed me to bug 531801 which would cache SSL content even without this header, but that's a while off, so we should still look into using it now.

Comment 2

[Wil Clouser [:clouserw]]

I can't reproduce this when logged out.  After loading the page once, if I visit the page again I only see a couple of requests.  It looks for js_constants a lot, but the majority of stuff isn't requested again.

Comment 3

[Jeff Balogh (:jbalogh)]

If I cmd+R refresh while looking at Firebug's net tab, I see a lot of 304 not modified responses for background images and such.  If I navigate to the page normally, everything comes from cache without the extra requests.  Were you refreshing fligtar?

Comment 4

[Justin Scott [:fligtar]]

This bug still seems to exist: navigating around the site with Tamper Data, images and CSS have no cache-control headers.

Comment 5

[Wil Clouser [:clouserw]]

This is all coming off the CDN now and it's sending cache-control headers.