Last modified: 2014-06-24 14:43:59 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 T69015, the corresponding Phabricator task for complete and up-to-date bug report information.
Bug 67015 - m.wikipedia.org incorrectly redirects to en.m.wikipedia.org
m.wikipedia.org incorrectly redirects to en.m.wikipedia.org
Status: NEW
Product: Wikimedia
Classification: Unclassified
Apache configuration (Other open bugs)
wmf-deployment
All All
: Normal normal (vote)
: ---
Assigned To: Nobody - You can work on this!
http://m.wikipedia.org
: mobile
Depends on:
Blocks:
  Show dependency treegraph
 
Reported: 2014-06-24 03:15 UTC by MZMcBride
Modified: 2014-06-24 14:43 UTC (History)
1 user (show)

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


Attachments

Description MZMcBride 2014-06-24 03:15:36 UTC
http://m.wikipedia.org currently redirects to http://en.m.wikipedia.org

I don't believe m.wikipedia.org previously redirected in this way. The current behavior seems broken. The markup of http://www.wikipedia.org was specifically updated to better accommodate mobile users (responsive design with @media queries) and it makes logical sense that wikipedia.org and m.wikipedia.org should point to the same page content, I think.

(It seems http://www.m.wikipedia.org works as expected.)

I guess the first step here would be to figure out whether the current behavior is intentional.
Comment 2 Yuri Astrakhan 2014-06-24 05:32:41 UTC
ZRMA extension is obsolete, the new code is in https://git.wikimedia.org/blob/mediawiki%2Fextensions%2FZeroBanner.git/6411d46a0d81abc2be87093626860d20a371b07c/includes%2FPageRenderingHooks.php#L978

In any case, it would be easy to change the desired behavior - the only case Zero team is concerned with is the m. and zero. redirect to the "default" language for the given carrier in case traffic is coming from the Zero partner network. Otherwise, any behaviour is fine with us.
Comment 3 Yuri Astrakhan 2014-06-24 05:35:47 UTC
Btw, this also means that we are not handling the www.m. case correctly - it should go through the same route as m. Might need a bug for this i think.

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


Navigation
Links