Last modified: 2014-11-18 18:07:24 UTC

Wikimedia Bugzilla is closed!

Wikimedia migrated from Bugzilla to Phabricator. Bug reports are handled in Wikimedia Phabricator.
This static website is read-only and for historical purposes. It is not possible to log in and except for displaying bug reports and their history, links might be broken. See T19821, the corresponding Phabricator task for complete and up-to-date bug report information.
Bug 17821 - Synchronize css/js caching
Synchronize css/js caching
Status: RESOLVED WORKSFORME
Product: MediaWiki
Classification: Unclassified
General/Unknown (Other open bugs)
unspecified
All All
: Low enhancement with 1 vote (vote)
: ---
Assigned To: Nobody - You can work on this!
:
Depends on:
Blocks:
  Show dependency treegraph
 
Reported: 2009-03-06 22:48 UTC by Tisza Gergő
Modified: 2014-11-18 18:07 UTC (History)
2 users (show)

See Also:
Web browser: ---
Mobile Platform: ---
Assignee Huggle Beta Tester: ---


Attachments

Description Tisza Gergő 2009-03-06 22:48:00 UTC
Due to caching, changes to the site-wide css/js MediaWiki pages can take up to one month to effect readers. The delay changes between readers, and also between files, which can be very frustrating when multiple interacting scripts or stylesheets need to be changed: weird backwards compatibility code needs to be added to ensure that all possible combinations of old and new files work correctly. It would make life easier, if all the css/js files updated at the same time for any single user, maybe by using a cookie to set max age values in the HTTP header or to trigger a javascript-based reload.
Comment 1 Andre Klapper 2014-08-27 11:51:19 UTC
Related: 
* bug 34779: add timestamp near cache key (JS/CSS minify)
* bug 26338: Wikimedia JS/CSS files get an extra max-age cache-control param
Comment 2 Krinkle 2014-08-27 13:45:39 UTC
(In reply to Andre Klapper from comment #1)
> Related: 
> * bug 34779: add timestamp near cache key (JS/CSS minify)
> * bug 26338: Wikimedia JS/CSS files get an extra max-age cache-control param

The individual words seem related, but neither bug is related to this issue.

This bug is no longer relevant. We haven't loaded Common.js this way since 2010 when ResourceLoader was introduced.

Note You need to log in before you can comment on or make changes to this bug.


Navigation
Links