Last modified: 2010-05-15 15:32:58 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 397 - Special:Recentchanges returns incorrect 304 on PostgreSQL
Special:Recentchanges returns incorrect 304 on PostgreSQL
Product: MediaWiki
Classification: Unclassified
Special pages (Other open bugs)
All All
: Normal normal (vote)
: ---
Assigned To: Nobody - You can work on this!
Depends on:
Blocks: postgres
  Show dependency treegraph
Reported: 2004-09-06 09:44 UTC by Brion Vibber
Modified: 2010-05-15 15:32 UTC (History)
1 user (show)

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


Description Brion Vibber 2004-09-06 09:44:55 UTC
Probably an issue with timestamp formats. When recentchanges has been modified by editing or protection etc, the next visit to 
the page should send new content due to the latest entry in the table being newer than the clients If-Modified-Since header. 
This is failing when set for PostgreSQL; the wiki continues to send a 304 response.

The Date header sent with the (forced) 200 responses look ok.
Comment 1 Domas Mituzas 2004-09-06 10:12:33 UTC
does it work right now? wfTimestamp() magic applied. 
Comment 2 Brion Vibber 2004-09-06 10:27:02 UTC
Yes, working great now!

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