Page MenuHomePhabricator

On mobile, wikivoyage.org redirects to www.m.wikivoyage.org which does not exist
Closed, ResolvedPublic

Description

from #...-tech:
<NicolasRaoul> Hello all! On Android, wikivoyage.org redirects to www.m.wikivoyage.org which does not exist


Version: unspecified
Severity: critical

Details

Reference
bz48318

Event Timeline

bzimport raised the priority of this task from to High.Nov 22 2014, 1:25 AM
bzimport set Reference to bz48318.
bzimport added a subscriber: Unknown Object (MLST).

Copying from bug 48394 :

Originally reported (as far as I know ) at
http://en.wikivoyage.org/wiki/Wikivoyage:Travellers%27_pub#Android:_wikivoyage.org_redirects_to_www.m.wikivoyage.org_which_does_not_exist

Essentially google still finds www.wikivoyage.org urls for some of it's
searches (I assume because of old link juice) especially if you're looking for
wikivoyage specific urls with a "wikivoyage X" type search. The easiest search
to use to recreate the issue is "wikivoyage austria" (I've tried a couple other
searches and don't always have the issue this one is pretty consistent).

This is fine for the desktop site because www.wikivoyage.org/wiki/Austraia
redirects to en.wikivoyage.org/wiki/Austria (or possibly other languages
depending on where you come from). However on mobile this redirects to
www.m.wikivoyage.org/wiki/Austraia which does not exist and so finishes at a
dead end page.

  • Bug 48394 has been marked as a duplicate of this bug. ***

adjusting title, this isn't just an android bug (I confirmed on my iphone), it appears to be any recognized mobile device.

Removing shell. It's an ops task as shell users can't merge apache config.

I'm also not sure apache is the correct place for this to be

Any progress on this?
It is probably hurting Wikivoyage's Google reputation, in addition from preventing readers from using the website.

Another bump on this to see if we have an update. Last I checked we still weren't totally sure 'who' is responsible though it seems like once we find that group it is 'likely' to be a relatively easy fix. <said with the knowledge that he may be wrong on that> However it is not something we should leave sitting around for months if we can avoid it.

i just tested again on my phone, and wikivoyage.org gets me to www.wikivoyage.org (Motorola Droid 4)

@daniel: Yes but try www.wikivoyage.org/wiki/Paris for instance.

After 2 months the bug is still present.
www.m.wikivoyage.org has still not been redirected (is it that hard?), so googlers searching "wikivoyage austria" still get "Server not found" :-(

(In reply to comment #9)

@daniel: Yes but try www.wikivoyage.org/wiki/Paris for instance.

Confirming that problem, though one might argue that it's a different problem as your example is a www address. See the summary of this bug report.

After 2 months the bug is still present.

I can offer a large number of reports that are still present after years. :)
Providing patches can speed up the process of fixing.

(In reply to comment #10)

(In reply to comment #9)

@daniel: Yes but try www.wikivoyage.org/wiki/Paris for instance.

Confirming that problem, though one might argue that it's a different problem
as your example is a www address. See the summary of this bug report.

While the portal page (www.wikivoyage.org and wikivoyage.org which redirects to same) work you don't need the www to get the bug. wikivoyage.org/wiki/Paris has the same issue. It's possible that the bug title should be clearer but given the examples (in my text that you copied over above about austria for example) I think this is clearly still the same bug :).

After 2 months the bug is still present.

I can offer a large number of reports that are still present after years. :)
Providing patches can speed up the process of fixing.

That assumes someone else has found the actual place this happens to write a patch for it etc. I'd really rather not use that we sometimes ignore bad bugs for much longer as an excuse :).

We should bring this up in a meeting with Ops and Mobile team together to figure out where the change actually needs to be made.

(In reply to comment #12)

We should bring this up in a meeting with Ops and Mobile team together to
figure out where the change actually needs to be made.

Honestly I'm not really sure how that will help .. it seems like a waste of time. I can't foresee anything here that could be on the mobile side, it seems fairly straightforwardly on the ops side.

Just another ping... it is worrying that a "critical" bug is being left open for so long.

https://www.wikipedia.org/wiki/Test fails in the same way. It is probably also true for other projects, but I didn't verify.

How to test:
wget -O /dev/null --debug --user-agent='Mozilla/5.0 (Linux; Android 4.0.4; Galaxy Nexus Build/IMM76B) AppleWebKit/535.19 (KHTML, like Gecko) Chrome/18.0.1025.133 Mobile Safari/535.19' https://www.wikipedia.org/wiki/Test

The failure comes to be because the redirecting of www.../wiki/ to en... is done in apache which only gets consulted after the mobile redirect.

from operations/apache-config.git file www.wikipedia.conf
RewriteRule ^/wiki$ http://en.wikipedia.org/ [R=301,L]

similar rule in the same file for wikivoage
RewriteRule ^(.*)$ http://en.wikivoyage.org$1 [R=301,L]

It is probably best solved by tweaking the pattern of which URLs are eligible for mobile redirects.

That pattern might be in operations/puppet.git file templates/squid/redirector.conf.erb but my mind is much too tired now to wield such heavy machinery.

Change 89879 had a related patch set uploaded by JanZerebecki:
Omit URLs like http://www.wikivoyage.org/wiki/Test from the redirect to mobile as www.m... does not exist.

https://gerrit.wikimedia.org/r/89879

Change 89879 had a related patch set uploaded by Faidon Liambotis:
Varnish: don't mobile redirect www.$project.org

https://gerrit.wikimedia.org/r/89879

Change 89879 merged by Faidon Liambotis:
Varnish: don't mobile redirect www.$project.org

https://gerrit.wikimedia.org/r/89879