792974 - Kuma: Send Expires headers on pages

Status: RESOLVED WORKSFORME

(developer.mozilla.org Graveyard :: General, defect)

Description

[Eric Shepherd [:sheppy]]

It doesn't look like the site is sending Expires headers on any of the
content (pages, style sheets), which it probably should be.

This means that the default HTTP expiration algorithm based on
Last-Modified headers applies (expiration is 1/10 of the age as
determined by last-modified), which basically isn't a useful result.

I think the site should be sending Expires headers (e.g., 5 or 15
minutes from the present) so that any problems like this will at
least go away within a few minutes.

Comment 1

[David Walsh :davidwalsh]

Should be a quick .htaccess fix:

http://www.askapache.com/htaccess/apache-speed-expires.html

Comment 2

[David Baron :dbaron: (⌚️UTC-4, no longer working on Mozilla)]

The normal way to do this in Apache is something like:

ExpiresActive on
ExpiresDefault "access plus 5 minutes"

Comment 3

[John Karahalis [:openjck]]

Dupe of bug 783851?

Comment 4

[Jean-Yves Perrier [:teoli]]

Bug 783851 is a subset of this bug. It handles only the case of css/js files that never changes (or, as they are revved, change names when changed). For these a different value of Expires is needed (something like ExpiresDefault "access plus 1 month"). The goal of 783851 is also different, it is to lower the loading time. This one is to prevent the default algorithm to be used.

But both bugs can be solved at the same time.

Comment 5

[Jean-Yves Perrier [:teoli]]

This has been fixed when migrating to the CDN