Last modified: 2014-03-10 18:07:58 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 T64245, the corresponding Phabricator task for complete and up-to-date bug report information.
Bug 62245 - "DoCoMo/2.0" feature-phone browsers get 502 errors from ja.wikipedia.org
"DoCoMo/2.0" feature-phone browsers get 502 errors from ja.wikipedia.org
Status: RESOLVED FIXED
Product: MobileFrontend
Classification: Unclassified
stable (Other open bugs)
unspecified
All All
: Unprioritized normal
: ---
Assigned To: Nobody - You can work on this!
: ops
Depends on:
Blocks:
  Show dependency treegraph
 
Reported: 2014-03-05 03:47 UTC by Yusuke Matsubara
Modified: 2014-03-10 18:07 UTC (History)
7 users (show)

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


Attachments

Description Yusuke Matsubara 2014-03-05 03:47:44 UTC
Some users of DoComo's feature phones from Japan has reported that they cannot access any Wikipedia pages with their device.  The problem has been reported repeatedly since early November 2013.

It seems that they are not redirected to ja.m.wikipedia.org from ja.wikipedia.org.  They say that it works when they go to http://ja.m.wikipedia.org/wiki/* directly.

Some of the affected devices (according to the reports):
* NTT Docomo SH-03A (User-agent: "DoCoMo/2.0 SH03A")
* NTT Docomo SH-01C (User-agent: "DoCoMo/2.0 SH01C")
* NTT Docomo F-01C  (User-agent: "DoCoMo/2.0 F01C")

Reports:
* https://ja.wikipedia.org/wiki/WP:BUG#.E3.83.95.E3.82.A3.E3.83.BC.E3.83.81.E3.83.A3.E3.83.BC.E3.83.95.E3.82.A9.E3.83.B3.E3.81.8B.E3.82.89.E3.81.AE.E9.96.B2.E8.A6.A7.E3.81.8C.E5.87.BA.E6.9D.A5.E3.81.AA.E3.81.84
* http://d.hatena.ne.jp/a_happy_ending/20131230/1388389603 (with screenshot)
* http://detail.chiebukuro.yahoo.co.jp/qa/question_detail/q13118343363 (with screenshot)
Comment 1 Max Semenik 2014-03-05 11:26:08 UTC
Did some investigation on this:
* The error is emitted not by WMF sites but by some intermediate DoCoMo proxy, we don't output 502 errors in Japanese.
* It happens only upon redirecting from desktop site to mobile.
* Early November coincides nicely with our switch of desktop sites from Squid to Varnish - this could have slightly altered responses.
* I couldn't reproduce this bug in their simulator: https://www.nttdocomo.co.jp/english/service/developer/make/content/browser/html/tool2/download/
Comment 2 Yusuke Matsubara 2014-03-06 10:19:48 UTC
I'm not sure if this is relevant, but some (who experience the same problem) suggest emitting the "Content-Length" header in the response to deal with this 502 error: http://umakoya.com/blog/log/eid179.html

According to the specifications given by Docomo, their browsers (and proxies, too?) require the "Content-Length" header: https://www.nttdocomo.co.jp/english/service/developer/make/content/browser/xhtml/notice/basis/
Comment 3 Bingle 2014-03-07 17:50:46 UTC
Prioritization and scheduling of this bug is tracked on Mingle card https://wikimedia.mingle.thoughtworks.com/projects/mobile/cards/1750
Comment 4 Gerrit Notification Bot 2014-03-07 21:14:59 UTC
Change 117471 had a related patch set uploaded by MaxSem:
Always output Content-Length on mobile redirect

https://gerrit.wikimedia.org/r/117471
Comment 5 Gerrit Notification Bot 2014-03-10 17:28:13 UTC
Change 117471 merged by Faidon Liambotis:
Always output Content-Length on mobile redirect

https://gerrit.wikimedia.org/r/117471
Comment 6 Jon 2014-03-10 18:07:58 UTC
Let's see if this patch fixes the problem. Please reopen if it doesn't!

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


Navigation
Links