933356 - theguardian.com serves the desktop version to Firefox OS

Status: RESOLVED FIXED

(Web Compatibility :: Site Reports, defect)

Description

[Karl Dubost💡 :karlcow]

Site: http://www.theguardian.com/
theguardian.com serves the desktop version to Firefox OS

:: Steps To Reproduce

1. Access http://www.theguardian.com/ with a Firefox OS device.


:: Expected Result

Receive a mobile friendly content like it is happening for Firefox on Android.

:: Actual Result

Firefox OS device received the desktop version.

:: Additional Information

Software Version: 1.1
Device Information: ZTE roamer2
Reporter's User Agent: Mozilla/5.0 (Android; Mobile; rv:18.0) Gecko/18.0 Firefox/18.0

Comment 1

[Karl Dubost💡 :karlcow]

→ http -b GET http://www.theguardian.com/uk User-Agent:'Mozilla/5.0 (Mobile; rv:18.0) Gecko/18.0 Firefox/18.0' | grep -i mobile
    <span><a href="/preference/platform/mobile?page=http%3A%2F%2Fwww.theguardian.com%2Fuk%3Fview%3Dmobile" class="switch-to-mobile" data-link-name="Switch to mobile" rel="nofollow"Mobile</a></span>


I'll contact someone from the Guardian to see if we can get love ;)

Comment 2

[kaelig]

Hi,

A fix is in the pipeline.

The fix I am proposing is that we redirect all user agents containing "Mobile" to the mobile site (which at some point will be set to be the default website for everyone). What do you think?

Comment 3

[Karl Dubost💡 :karlcow]

kaelig,

if it's the alpha responsive version I'm currently using on Desktop. It is a very good decision.
http://www.theguardian.com/help/2013/oct/04/alpha-testing-and-evolution-of-our-mobile-site

Thanks.

Comment 4

[kaelig]

Hi again,

By redirecting all user-agents containing "Mobile" (which seems to be the hint in FFOS' user agent), we'd also redirect iPads to the mobile site (and probably other false positives that are not part of our current strategy).

How do you suggest we could redirect FFOS but not the other "Mobile" browsers we don't want to redirect yet?

If that's too complicated we'll just wait till we start redirecting iPads to the mobile responsive site.

Comment 5

[Mike Taylor [:miketaylr]]

You could also match the UA string against a regex like /mobile.+firefox/i if you're worried about false-positives. That should also cover Firefox for Android.

Comment 6

[kaelig]

Thanks Mike for the help, I should have thought about that. A fix is in the pipeline (again).

Comment 7

[kaelig]

I just deployed a fix, can you please confirm this is working?

On:

curl -s -A 'Mozilla/5.0 (Mobile; rv:18.0) Gecko/18.0 Firefox/18.0' -i http://www.theguardian.com/uk | head -n 20
HTTP/1.1 200 OK

You should get this header back:

X-GU-Platform: next-gen-router

Comment 8

[Mike Taylor [:miketaylr]]

Bingo!

$ http --print=hH http://www.theguardian.com/uk User-Agent:"$FFOS"
GET /uk HTTP/1.1
Accept: */*
Accept-Encoding: gzip, deflate, compress
Host: www.theguardian.com
User-Agent: Mozilla/5.0 (Mobile; rv:18.1) Gecko/18.1 Firefox/18.1

HTTP/1.1 200 OK
Accept-Ranges: bytes
Age: 0
Cache-Control: max-age=60,  stale-while-revalidate=60, stale-if-error=345600, private
Connection: keep-alive
Content-Encoding: gzip
Content-Length: 63302
Content-Type: text/html; charset=utf-8
Date: Wed, 13 Nov 2013 17:01:51 GMT
Expires: Wed, 13 Nov 2013 17:02:51 GMT
Server: nginx
Vary: Accept-Encoding,User-Agent
Via: 1.1 varnish
X-Cache: MISS
X-Cache-Hits: 0
X-GU-Edition: us
X-GU-Platform: next-gen-router
X-GU-Varnish: MISS
X-Served-By: cache-d46-DAL

https://cloudup.com/ckxOlO2dsxY

Awesome work, thanks!

Comment 9

[Karl Dubost💡 :karlcow]

Thanks! http://twitter.com/MozWebCompat/status/400671119914827776

Comment 10

[Anthony Ricaud (:rik)]

(In reply to Mike Taylor [:miketaylr] from comment #5)
> You could also match the UA string against a regex like /mobile.+firefox/i
> if you're worried about false-positives. That should also cover Firefox for
> Android.
Matching "mobile WITH firefox" only fixes the issue for Firefox browsers. I think matching for "mobile WITHOUT ipad" is a more universal fix.

Comment 11

[kaelig]

Thanks for the idea, I think you're right. In the next few months we'll roll out the responsive site for everyone so I guess this is not too big a deal to have false positives in the long tail in the mean time.