Last modified: 2011-03-11 02:48:19 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 T17910, the corresponding Phabricator task for complete and up-to-date bug report information.
Bug 15910 - Reduce smaxage on WMF wikis
Reduce smaxage on WMF wikis
Status: RESOLVED FIXED
Product: Wikimedia
Classification: Unclassified
Site requests (Other open bugs)
unspecified
All All
: Normal minor (vote)
: ---
Assigned To: Nobody - You can work on this!
: shell
Depends on:
Blocks:
  Show dependency treegraph
 
Reported: 2008-10-09 06:11 UTC by MZMcBride
Modified: 2011-03-11 02:48 UTC (History)
3 users (show)

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


Attachments

Description MZMcBride 2008-10-09 06:11:22 UTC
The current smaxage for Wikimedia wikis is 2678400 seconds (31 days). It should be reduced to 604800 seconds (7 days).

Thirty-one days is a very long time and makes implementing new site-wide CSS and JS much more tedious.
Comment 1 Brion Vibber 2008-10-09 20:41:02 UTC
A more permanent fix should be actually doing purges of the standard raw URLs for standard-pattern CSS/JS pages on edit...

The corollary there is having a sane max-age for client-side caching, though. Hrm...
Comment 2 Roan Kattouw 2010-11-30 15:08:03 UTC
This will be superseded by the Resource Loader once it's deployed.
Comment 3 MZMcBride 2010-11-30 16:11:23 UTC
(In reply to comment #2)
> This will be superseded by the Resource Loader once it's deployed.

How so?
Comment 4 Roan Kattouw 2010-12-01 14:42:53 UTC
(In reply to comment #3)
> (In reply to comment #2)
> > This will be superseded by the Resource Loader once it's deployed.
> 
> How so?
ResourceLoader uses timestamp parameters to work around caching when a resource changes; for resources where we can't generate timestamp parameters without having those timestamps themselves be cached (e.g. because they'd be embedded in HTML that's cached in Squid, like $wgStyleVersion currently), we set short (s-)maxages instead.
Comment 5 p858snake 2011-03-11 02:48:19 UTC
(In reply to comment #2)
> This will be superseded by the Resource Loader once it's deployed.
FIXED per this

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


Navigation
Links