Last modified: 2011-04-14 15:12:12 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 6166 - Action=raw returns stale results
Action=raw returns stale results
Status: NEW
Product: MediaWiki
Classification: Unclassified
Page editing (Other open bugs)
Other All
: Low normal (vote)
: ---
Assigned To: Nobody - You can work on this!
: testme
Depends on:
  Show dependency treegraph
Reported: 2006-06-01 18:41 UTC by omniplex
Modified: 2011-04-14 15:12 UTC (History)
1 user (show)

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


Description omniplex 2006-06-01 18:41:39 UTC
Trying to fix a leading zero bug on [[WP:BRION]] or rather
[[Wikipedia:Bugs, Repairs, and Internal Operational News]]
I used "action=raw", because the date formula is confusing
if shown in a small edit box.

After adding a leading zero for previous months below 10
there was another issue, but "action=raw" returned the old
version. A simple "action=purge" didn't help, and the wild
guess "action=raw&action=purge" also didn't work.

From my POV "action=raw" is the poor man's external editor
emulation, this oddity might also affect the real external
editor behaviour. If that's not the case please copy the
the external editor solution to the "action=raw" code.
Comment 1 omniplex 2006-06-20 12:17:34 UTC
Using action=render also doesn't change this behaviour.
Comment 2 Rob Church 2006-07-12 11:47:36 UTC
The results appear to be being cached; a Squid max age is set, as well as a
client-side max age. The former cache would be cleared on edit.

It's *possible* something's being overlooked in RawPage...
Comment 3 DC2 2006-08-17 22:13:02 UTC
Did the request was sent by javascript (XMLHttpRequest) ? If 
it is, i know the point, it's not famous but known. Many 
browsers have a cache and did not re-send the request. (With 
IE, you may have special results like having a succes event 
without any header received). The solution is to add a 
the number could be anything (random, timestamp...) and make 
the browser act as for a new request. 
Comment 4 DC2 2006-08-17 22:16:02 UTC
(... I'm thinking : if not a javascript request it may be 
the same... Sure it was not the browser' cache ? should try 
the add in the url )
Comment 5 Aaron Schulz 2009-07-27 17:37:27 UTC
Does this still occur?
Comment 6 Max Semenik 2009-12-18 11:13:49 UTC
I encounterd it last year, removing the ancient Squid hack "&dontcountme=s" from request URL helped. Not sure if it is still there.

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