https://test.wikipedia.org/wiki/Bug%3F?action=history doesn't show the history page, unlike https://test.wikipedia.org/w/index.php?title=Bug%3F&action=history. From what I know about URL structure and MediaWiki, they should act the same. Do we have broken routing / rewrite rules or something?
Description
Status | Subtype | Assigned | Task | ||
---|---|---|---|---|---|
Resolved | He7d3r | T123060 Error: module already implemented: user.options on ptwiki | |||
Resolved | Krinkle | T123062 mw.util.getUrl should produce working URLs for titles ending in "?" | |||
Resolved | None | T123276 URL parameters do not work with pages that have "?" in their names | |||
Resolved | None | T132629 Data passed to HHVM ($_SERVER variables) is a mixed bag of already-decoded and non-decoded nonsense | |||
Resolved | Danny_B | T139271 wgRedirectedFrom not populated/exposed if redirect accessed via index.php?title=Redirect_page |
Event Timeline
how does this "work for you" ?
the screenshot does not look to me like a history page. what am i missing?
peace.
Well the description is a little convoluted, but what I'm seeing is that the title of his test page is literally Bug%3F, where %3F is the ascii hex for ?. For a normal article name /wiki/Foo?action=history actually works*, but the presence of %3F at the end of the title breaks ?action=history. A better set of example URLs (to me anyways) is:
https://test.wikipedia.org/wiki/Bug%3F?x=y&action=history - works
https://test.wikipedia.org/wiki/Bug%3F?action=history - borked, shows article content instead of history
* - (although it's debatable whether it should - shouldn't we have one canonical action=history URL, and isn't it usually the ?title= form? but that's a side issue)
I noticed another related bug while testing this, based on this example
If you change the question mark to an ampersand, you'll get the correct page, but the page title is incorrect: https://test.wikipedia.org/wiki/Bug%3F&action=history will show the title Bug?&action=history.
I can't reproduce this problem any more. I assume this was fixed by migrating to PHP 7 (T176370).