Closed
Bug 901569
Opened 11 years ago
Closed 11 years ago
ajw.asahi.com doesn't send mobile content to firefox os
Categories
(Web Compatibility :: Site Reports, defect)
Tracking
(Not tracked)
VERIFIED
FIXED
People
(Reporter: karlcow, Assigned: karlcow)
References
()
Details
(Whiteboard: [serversniff] [country-jp] [sitewait])
Steps: 1. Open Firefox OS browser 2. Type http://ajw.asahi.com/ in Firefox OS browser What do you see? We receive the desktop content of http://ajw.asahi.com/ What do you expect? Have the mobile content of http://ajw.asahi.com/. When typing the Web site address on Safari/iPodTouch, we get the mobile content. On Firefox for Android, we receive the mobile content as well. What is the version of the browser? Mozilla/5.0 (Mobile; rv:18.0) Gecko/18.0 Firefox/18.0 and Accept-Language is en-US,en;q=0.5 as displayed by http://echo.opera.com/
Assignee | ||
Comment 1•11 years ago
|
||
Understanding what is happening. # Trying with HTTP HEAD With Firefox OS User Agent string HEAD / HTTP/1.1 Accept: */* Accept-Encoding: gzip, deflate, compress Host: ajw.asahi.com User-Agent: Mozilla/5.0 (Mobile; rv:18.0) Gecko/18.0 Firefox/18.0 HTTP/1.1 200 OK Cache-Control: no-store, no-cache, must-revalidate, post-check=0, pre-check=0 Connection: keep-alive Content-Encoding: gzip Content-Type: text/html; charset=UTF-8 Content-length: 20 Date: Mon, 05 Aug 2013 17:06:16 GMT Expires: Thu, 19 Nov 1981 08:52:00 GMT Pragma: no-cache Server: Apache Set-Cookie: AJWSESSID=93d62f0730d7b5b04a31281e9cec6fff6298b42c; path=/; HttpOnly Set-Cookie: AJWSESSID=3dd9f4772abe8ee40365cc854da33e7201d3317d; path=/; HttpOnly Vary: Accept-Encoding X-Content-Type-Options: nosniff And with Firefox for Android User Agent String HEAD / HTTP/1.1 Accept: */* Accept-Encoding: gzip, deflate, compress Host: ajw.asahi.com User-Agent: Mozilla/5.0 (Android; Mobile; rv:18.0) Gecko/18.0 Firefox/18.0 HTTP/1.1 200 OK Cache-Control: no-store, no-cache, must-revalidate, post-check=0, pre-check=0 Connection: keep-alive Content-Encoding: gzip Content-Type: text/html; charset=UTF-8 Content-length: 20 Date: Mon, 05 Aug 2013 17:07:34 GMT Expires: Thu, 19 Nov 1981 08:52:00 GMT Pragma: no-cache Server: Apache Set-Cookie: AJWSESSID=26e2e6d1f8a993a0dc96a42ba5d627f98775b8d4; path=/; HttpOnly Set-Cookie: AJWSESSID=38dc7a0aa6523a4091670baa6be8ca6e4aee80d7; path=/; HttpOnly Vary: Accept-Encoding X-Content-Type-Options: nosniff Both Content-Length are minimal, we can't rely on the head. Let's see with HTTP GET. With an HTTP GET we can detect a difference in size which is consistent after a few requests. Firefox OS Content-Length: 9897 Firefox Android Content-Length: 6924 So let's continue with the body. → http GET http://ajw.asahi.com/ User-Agent:'Mozilla/5.0 (Mobile; rv:18.0) Gecko/18.0 Firefox/18.0' | grep -i mobile <a href="http://www.asahi.com/english/awsmobile/" target="_blank">Asahi Weekly Select</a> → http GET http://ajw.asahi.com/ User-Agent:'Mozilla/5.0 (Android; Mobile; rv:18.0) Gecko/18.0 Firefox/18.0' | grep -i mobile <meta name="apple-mobile-web-app-capable" content="yes"> <meta name="apple-mobile-web-app-status-bar-style" content="black" /> <link rel="stylesheet" href="/media_mobile/css/style.css" type="text/css" media="screen" /> <link rel="shortcut icon" href="/media_mobile/img/favicon.ico" /> <script src="/media_mobile/js/ajw/unmd/menu.js"></script> <script src="/media_mobile/js/ajw/unmd/bar.js"></script> <script src="/media_mobile/js/ajw/unmd/frc.js"></script> <script src="/media_mobile/js/wja/swipe.min.js" type="text/javascript" charset="UTF-8"></script> <script src="/media_mobile/js/ajw/unmd/slide_top.js" type="text/javascript" charset="UTF-8"></script> <div id="banner_smithsonian_pulverer"><a href="http://asia.si.edu/exhibitions/current/pulverer.asp" target="_blank"><img src="/media_mobile/img/common/PAM6858-Pulverer-320-x-50.gif" width="320" height="50"></a></div> <div id="banner_smithsonian_sp"><a href="/appendix/pr_smithsonian_sp/" target="_blank"><img src="/media_mobile/img/common/banner_smithsonian_sp.jpg" width="320" height="50"></a></div> So we can conclude that there is server-side sniffing on this site. I'm adding in whiteboard the following flag: [serversidesniff] Also the site is operated in Japan (English language). [country-jp]
Whiteboard: [serversidesniff] [country-jp]
Assignee | ||
Comment 2•11 years ago
|
||
Finding the contact person on the Asahi Web site. They have a twitter account but it seems to be only a robot publishing information and not people interacting. https://twitter.com/ajwasahi On their FAQ http://ajw.asahi.com/information/faq/ Q: Who should I contact if I have questions or complaints? A: For additional questions or comments, please visit our Customer Support page. Let's try https://se01.asahi.com/english/ajw_inquiry.html Using the template letters https://wiki.mozilla.org/Compatibility/StdLetters
Assignee | ||
Comment 3•11 years ago
|
||
Mail sent through the webform
> Message sent
>
> Your inquiry has been accepted. It may take a while before you receive a reply. We appreciate your patience and understanding.
Adding [sitewait] whiteboard flag.
Assignee: nobody → kdubost
Whiteboard: [serversidesniff] [country-jp] → [serversidesniff] [country-jp] [sitewait]
Updated•11 years ago
|
Whiteboard: [serversidesniff] [country-jp] [sitewait] → [serversniff] [country-jp] [sitewait]
Assignee | ||
Comment 4•11 years ago
|
||
They replied. > Dear Mr. Dubost, > Please forgive the delay in response. As our IT technical team is > out of house, and the in-house IT person is Japanese, I will need > to interpret your request as best I can. We understand from the bug > report that the new Firefox OS that you are testing is not reading > AJW.asahi.com's mobile-optimized site. We talked to the IT group > and they replied that it is possible to include the Firefox OS > browser in the code so that it is recognized as a mobile browser. > Is this all we need to do? > Could you let us know exactly what coding is required to recognize it? > Also, what is the timeframe for release of the Firefox OS browser, > i.e., by when do we need to ensure it is included in our website code? > Thank you for contacting us, we certainly want to be readable in the new OS. > C********* > AJW Customer Support > The Asahi Shimbun, Tokyo > http://ajw.asahi.com/ Which I replied to: > C****, > > Thanks a lot for the quick answer. See my answers. > Sorry for the clumsy Japanese. > > customer-support@asahi.com [2013-08-09T04:39]: > > the new Firefox OS that you are testing is not reading > > AJW.asahi.com's mobile-optimized site. > > はい。 > > > We talked to the IT group and they replied that it is possible > > to include the Firefox OS browser in the code so that it is recognized > > as a mobile browser. Is this all we need to do? > > はい。 > > > Could you let us know exactly what coding is required to recognize it? > > > Firefox OSのユーザーエージェントが 'Mozilla/5.0 (Mobile; rv:18.0) Gecko/18.0 Firefox/18.0'をです。 > 正規をご使用でない場合は'mobi' AND NOT 'tablet'のパターンを使用することをおすすめします。 > > > > Also, what is the timeframe for release of the Firefox OS browser, i.e., > > by when do we need to ensure it is included in our website code? > > スペインとポーランドのマーケットが最初で。 [1][2] > それからコロンビアとベネズエラがつづきました。[3] > 他の国々もそれ以降にリリースされる予定です。 > > [1]: https://blog.mozilla.org/blog/2013/07/01/mozilla-and-partners-prepare-to-launch-first-firefox-os-smartphones/ > [2]: https://blog.mozilla.org/blog/2013/07/11/deutsche-telekom-announces-european-launch-of-firefox-os-devices/ > [3]: https://blog.mozilla.org/blog/2013/08/01/telefonica-announces-launches-of-first-firefox-os-devices-in-latin-america/ > > > Thank you for contacting us, we certainly want to be readable in the new OS. > > ありがとうございました! >
Assignee | ||
Updated•11 years ago
|
Status: NEW → ASSIGNED
Assignee | ||
Comment 5•11 years ago
|
||
Sent a reminder
Assignee | ||
Comment 6•11 years ago
|
||
This is solved!
Status: ASSIGNED → RESOLVED
Closed: 11 years ago
Resolution: --- → FIXED
Assignee | ||
Comment 9•9 years ago
|
||
Altaf, the bug was already closed and verified. No need to do it again. There are other bugs which are opened.
Flags: needinfo?(ameycoolguy)
Updated•5 years ago
|
Product: Tech Evangelism → Web Compatibility
Updated•12 days ago
|
Component: Mobile → Site Reports
You need to log in
before you can comment on or make changes to this bug.
Description
•