Last modified: 2010-05-15 15:33:17 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 1872 - MediaWiki pages won't refresh in Firefox unless browser cache is cleared
MediaWiki pages won't refresh in Firefox unless browser cache is cleared
Status: RESOLVED DUPLICATE of bug 1763
Product: MediaWiki
Classification: Unclassified
Parser (Other open bugs)
PC Windows XP
: Normal normal with 1 vote (vote)
: ---
Assigned To: Nobody - You can work on this!
Depends on:
  Show dependency treegraph
Reported: 2005-04-11 15:13 UTC by Erin Jo Adair
Modified: 2010-05-15 15:33 UTC (History)
0 users

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


Description Erin Jo Adair 2005-04-11 15:13:14 UTC
Everytime a MediaWiki page is refreshed using a Firefox browser, the page will
not appear (just a blank screen)until the cache is cleared every single time. 
Is there a way to stop this from happening so users do not have to clear the
cache each time and then login again?
Comment 1 Michael Keppler 2005-04-11 20:12:30 UTC
I have no such problem with Firefox on any MediaWiki installation. Please give
an URL and state your OS, OS version and Firefox version. Did you try creating a
new profile in Firefox without any extension to see if the problem remains? Are
there any proxies or firewalls on your side which could cause the problem?
Comment 2 Brion Vibber 2005-04-12 06:58:04 UTC
Michael, the reporter *did* provide a URL. Quick examination shows it to be running on IIS 
6.0, having the same problems as bug 1763.

I'm marking this bug as a duplicate of 1763. Erin, there's a partial workaround mentioned 
in the comments on that bug though the underlying cause is not yet known.

*** This bug has been marked as a duplicate of 1763 ***

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