Last modified: 2010-05-15 15:32:58 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 T2397, the corresponding Phabricator task for complete and up-to-date bug report information.
First Last Prev Next    This bug is not in your last search results.
Bug 397 - Special:Recentchanges returns incorrect 304 on PostgreSQL
Special:Recentchanges returns incorrect 304 on PostgreSQL
Status: CLOSED FIXED
Product: MediaWiki
Classification: Unclassified
Special pages (Other open bugs)
1.4.x
All All
: Normal normal (vote)
: ---
Assigned To: Nobody - You can work on this!
:
Depends on:
Blocks: postgres
  Show dependency tree / graph
 
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: ---

Attachments
Add an attachment (proposed patch, testcase, etc.)

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.
First Last Prev Next    This bug is not in your last search results.

Navigation
Links