diff options
| author | Max Kanat-Alexander <mkanat@bugzilla.org> | 2010-07-21 05:34:41 +0200 |
|---|---|---|
| committer | Max Kanat-Alexander <mkanat@bugzilla.org> | 2010-07-21 05:34:41 +0200 |
| commit | 10f4954b4530a67d88c66ba8e397ee81487f4752 (patch) | |
| tree | 7682e9b1974c208cb98af3e6e52284f9199a2ae1 /.htaccess | |
| parent | 0d280b9011568abf2c5f95a33fd20195b91528d9 (diff) | |
| download | bugzilla-10f4954b4530a67d88c66ba8e397ee81487f4752.tar.gz bugzilla-10f4954b4530a67d88c66ba8e397ee81487f4752.tar.xz | |
Bug 428313: Properly expire the browser's CSS and JS cache when there
are new versions of those files. This also eliminates single-file skins
and should also allow Extensions to have skins.
r=glob, a=mkanat
Diffstat (limited to '.htaccess')
| -rw-r--r-- | .htaccess | 11 |
1 files changed, 11 insertions, 0 deletions
@@ -2,3 +2,14 @@ <FilesMatch ^(.*\.pm|.*\.pl|.*localconfig.*)$> deny from all </FilesMatch> +<FilesMatch (\.js|\.css)$> + ExpiresActive On + # According to RFC 2616, "1 year in the future" means "never expire". + # We change the name of the file's URL whenever its modification date + # changes, so browsers can cache any individual JS or CSS URL forever. + # However, since all JS and CSS URLs involve a ? in them (for the changing + # name) we have to explicitly set an Expires header or browsers won't + # *ever* cache them. + ExpiresDefault "now plus 1 years" + Header append Cache-Control "public" +</FilesMatch> |