Last modified: 2011-07-13 21:52:37 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 11769 - make maxlag message spit out html
make maxlag message spit out html
Product: MediaWiki
Classification: Unclassified
General/Unknown (Other open bugs)
All All
: Low minor (vote)
: ---
Assigned To: Nobody - You can work on this!
Depends on:
  Show dependency treegraph
Reported: 2007-10-26 23:16 UTC by Carl Fürstenberg
Modified: 2011-07-13 21:52 UTC (History)
3 users (show)

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


Description Carl Fürstenberg 2007-10-26 23:16:06 UTC
could be nice, especially for clients expecting xml parseable data to be retrievable when connection MW, to not get a headake when recieving a 503, as they usually parse the data before thinking about the 503.
Comment 1 Niklas Laxström 2009-02-28 19:01:02 UTC
What is maxlag and what it has to do with 503 (HTTP error code?)
Comment 2 Brad Jorsch 2009-02-28 19:55:35 UTC
[[mw:Manual:Maxlag parameter]]

IMO, the client should be checking the HTTP status code before looking at the content.
Comment 3 Niklas Laxström 2009-02-28 20:01:44 UTC
I don't see what it would achieve to make it xml/html then. The clients would just work wrong in an another way.
Comment 4 Dan Collins 2011-07-13 21:52:37 UTC
The bug appears to be that clients will ignore the error that explicitly tells them that the request was not handled, and will attempt to parse the response anyway, and get confused. The solution is to pay attention to the HTTP error when one is provided. Making this message as simple as possible is in the best interests of the devs, and while there obviously isn't a performance reason not to wrap the output in the necessary HTML fluff, there isn't a good reason to do that either. It's not like returning HTML would give the ignorant client everything it asked for, it would just be a little bit bigger. For these reasons, closing this invalid.

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