Last modified: 2006-12-26 05:45:20 UTC

Wikimedia Bugzilla is closed!

Wikimedia has migrated from Bugzilla to Phabricator. Bug reports should be created and updated in Wikimedia Phabricator instead. Please create an account in Phabricator and add your Bugzilla email address to it.
Wikimedia Bugzilla is read-only. If you try to edit or create any bug report in Bugzilla you will be shown an intentional error message.
In order to access the Phabricator task corresponding to a Bugzilla report, just remove "static-" from its URL.
You could still run searches in Bugzilla or access your list of votes but bug reports will obviously not be up-to-date in Bugzilla.
Bug 6037 - Generated style sheets have wrong cache control settings for logged-in users
Generated style sheets have wrong cache control settings for logged-in users
Product: MediaWiki
Classification: Unclassified
Parser (Other open bugs)
All All
: Normal normal (vote)
: ---
Assigned To: Nobody - You can work on this!
: 2127 (view as bug list)
Depends on:
  Show dependency treegraph
Reported: 2006-05-21 13:53 UTC by Duncan Harris
Modified: 2006-12-26 05:45 UTC (History)
1 user (show)

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


Description Duncan Harris 2006-05-21 13:53:29 UTC
Nasty looking funny? question marks have started to appear? next to redlinks. 
This disrupts the flow of? text because you don't? want random question? marks
throughout a sentence.  What was wrong? with the old way??  Isn't there
something ''bro?ken'' that needs fixing?
Comment 1 dean 2006-05-21 13:55:39 UTC
From your bug report (full of qurstion marks), it looks like something screwey 
with your computer or browser, not the websites.
Comment 2 Rob Church 2006-05-21 14:39:31 UTC
1. Check you haven't enabled the alternate broken link display in your preferences
2. Hard-refresh your browser and/or clear your cache
3. If the problem persists, please reopen this bug report and send a screenshot
Comment 3 Duncan Harris 2006-05-21 14:44:44 UTC
No, it came on momentarily and then went off again.  I think it was someone
messing with the settings for some unfathomable reason.  The questoin marks in
the report were supposed to be illustrative.
Comment 4 Rob Church 2006-05-21 14:46:33 UTC
Sounds like some corrupt CSS was loaded, which is frequent enough to be
irritating, but isn't a problem we can fix per se.
Comment 5 Duncan Harris 2006-05-21 19:43:29 UTC
They're back.  Redlinks have turned black, lost their underlining and have
acquired question marks at the end of them.
Comment 6 Rob Church 2006-05-21 20:33:27 UTC
(In reply to comment #5)
> They're back.  Redlinks have turned black, lost their underlining and have
> acquired question marks at the end of them.

You checked the user preference again?
Comment 7 Brion Vibber 2006-05-21 20:38:29 UTC
Please provide your username and the URL to the wiki on which 
you see this effect.
Comment 8 Duncan Harris 2006-05-21 20:43:02 UTC
My username is Duncharris.  I'm running default Monobook on Firefox (I'll try
upgrading  Firefox and see if it has an effect).

No-one's given me a monobook.js present (if that's possible).
Comment 9 Duncan Harris 2006-05-21 20:47:33 UTC
I've resaved my preferences and it's working okay now.  Something straneg was
happening becaus I didn't touch my prefs.
Comment 10 Brion Vibber 2006-05-21 20:53:56 UTC
Generated JS is sending incorrect cache control headers, 
which could cause people to sometimes see the wrong style 

Cache-Control: s-maxage=2678400, max-age=2678400
Vary: Accept-Encoding

It should probably look more like:

Cache-Control: s-maxage=0, max-age=2678400
Vary: Accept-Encoding, Cookie
Comment 11 Rob Church 2006-12-24 08:20:26 UTC
Brion fixed this some time ago, and the fix seems to have worked; we haven't had
reports of the behaviour since.
Comment 12 Rob Church 2006-12-26 05:45:20 UTC
*** Bug 2127 has been marked as a duplicate of this bug. ***

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