Last modified: 2014-05-10 01:18:39 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 T42912, the corresponding Phabricator task for complete and up-to-date bug report information.
Bug 40912 - Bad new behavior of redirects to special pages
Bad new behavior of redirects to special pages
Status: RESOLVED FIXED
Product: MediaWiki
Classification: Unclassified
Redirects (Other open bugs)
unspecified
All All
: Low normal (vote)
: ---
Assigned To: Nobody - You can work on this!
:
Depends on:
Blocks:
  Show dependency treegraph
 
Reported: 2012-10-10 06:38 UTC by Liangent
Modified: 2014-05-10 01:18 UTC (History)
2 users (show)

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


Attachments

Description Liangent 2012-10-10 06:38:18 UTC
In past, redirect to special pages does not do real redirect but display a link to that special page in the format of &redirect=no. Now redirect to special pages do HTTP redirect to that special page, causing edit of that redirect impossible without manual URL construction.
Comment 1 Liangent 2012-10-10 06:41:04 UTC
TODO for myself: update Gerrit change #25631 when this bug is fixed.
Comment 2 Daniel Kinzler 2012-10-10 08:42:59 UTC
Are you sure this is related to the ContentHandler? I can't think of anything I did there that would cause this behavior. I might have unintentionally changed it somehow, but... well, do you have any idea what exactly causes this change in behavior?
Comment 3 Daniel Kinzler 2012-10-10 08:56:53 UTC
Had a quick look. In WikiPage::getRedirectURL, it sais:

 // Gotta handle redirects to special pages differently:
 // Fill the HTTP response "Location" header and ignore
 // the rest of the page we're on.

This causes an HTTP redirect.

This was added by commit 829dd6ef9d some time in January. I don't see how it is related to the ContentHandler, so I'll change the component.
Comment 4 John Mark Vandenberg 2014-05-10 01:18:39 UTC
I cant reproduce this any longer.

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


Navigation
Links