Comments on: MediaWiki 1.19 deployment to Wikimedia sites: Test it before it breaks

By: Roan Kattouw

Roan Kattouw — Thu, 16 Feb 2012 10:57:12 +0000

Re #3: one reason to return a 200 OK for a missing article rather than 404 Not Found is because a large number of Microsoft IIS setups out there is misconfigured and will override any 404 response with a custom error page, even if the response body contains, say, an edit form.

By: Eliz

Eliz — Tue, 14 Feb 2012 14:38:07 +0000

Just out of curiosity, from line 105 of the release notes:

Added $wgSend404Code, true by default, which can be set to false to send a
200 status code instead of 404 for nonexistent articles.

What would be a reason to want nonexistent articles to return OK status?

By: Mark A. Hershberger

Mark A. Hershberger — Mon, 13 Feb 2012 04:00:08 +0000

If a bug is rejected as already existing (in Bugzilla this is “RESOLVED DUPLICATE” with the bug number given) then check to see if it is the same bug. If it is not the same bug, you can re-open your bug report and say *why* it is the not the same bug.

It is certainly better to have a few clearer bug reports (something this process will produce) rather than many vaguely similar bug reports.

By: European Alba

European Alba — Sun, 12 Feb 2012 06:17:43 +0000

Good news for starting a new wiki-based website. I love it how your software becomes more and more robust each time.

Submitting bugs would be more helpful, when the developers would not reject them as already existing bugs. Most of the time the users can not describe the problem well enough, so that it looks similar to other bugs.

Thank you for great work !