[Tech Evangelism] Southwest Airlines site serves Firefox OS desktop content and does not redirect to mobile site



Tech Evangelism
4 years ago
2 years ago


(Reporter: Brogan Zumwalt [Inactive], Unassigned)


Gonk (Firefox OS)

Firefox Tracking Flags

(b2g-v2.0 affected, b2g-v2.1 affected, b2g-v2.2 affected)


(Whiteboard: [2.2-exploratory-1] [serversniff] [contactready] [country-us], URL)


(1 attachment)



4 years ago
Created attachment 8531333 [details]

When user navigates to Southwest Airlines site http://www.southwest.com they are not redirected to the mobile site https://www.mobile.southwest.com

User is served desktop content only.
Repro Steps:
1) Update a Flame device to BuildID: 20141202040207
2) Launch browser
3) Navigate to southwest.com
User is served desktop content and is not taken to mobile site.
User is redirected to mobile site.
Environmental Variables:
Device: Flame 2.2 Master (319mb)(Kitkat Base)(Full Flash)
BuildID: 20141202040207
Gaia: 725685831f5336cf007e36d9a812aad689604695
Gecko: 2c9781c3e9b5
Gonk: 48835395daa6a49b281db62c50805bd6ca24077e
Version: 37.0a1 (2.2 Master)
Firmware: V188-1
User Agent: Mozilla/5.0 (Mobile; rv:37.0) Gecko/37.0 Firefox/37.0

Repro frequency: 3/3, 100%
See attached: screenshot

Comment 1

4 years ago
Issue does occur on Flame 2.0 and Flame 2.1

Actual Results: User is served desktop content and is not taken to mobile site.

Device: Flame 2.0 (319mb)(Kitkat Base)(Full Flash)
Build ID: 20141202000201
Gaia: 8d1e868864c8a8f1e037685f0656d1da70d08c06
Gecko: c756bd8bf3c3
Gonk: 48835395daa6a49b281db62c50805bd6ca24077e
Version: 32.0 (2.0)
Firmware Version: v188-1
User Agent: Mozilla/5.0 (Mobile; rv:32.0) Gecko/32.0 Firefox/32.0

Device: Flame 2.1 (319mb)(Kitkat Base)(Full Flash)
Build ID: 20141202001201
Gaia: ccb49abe412c978a4045f0c75abff534372716c4
Gecko: 18fb67530b22
Gonk: 48835395daa6a49b281db62c50805bd6ca24077e
Version: 34.0 (2.1)
Firmware Version: v188-1
User Agent: Mozilla/5.0 (Mobile; rv:34.0) Gecko/34.0 Firefox/34.0
QA Whiteboard: [QAnalyst-Triage?]
Flags: needinfo?(dharris)
This appears to be a tech evangelism bug. Not nominating to block
QA Whiteboard: [QAnalyst-Triage?] → [QAnalyst-Triage+]
Flags: needinfo?(dharris)
This site intends to send mobile browsers to a mobile site, but doesn't know that Firefox OS devices are smartphones. Hence the browser on Firefox OS phones get desktop content instead of mobile.

The HTTP traffic analysis below shows how the sniffing works:

Firefox Android and Safari on iPhone are redirected to http://mobile.southwest.com/, Firefox OS not redirected

Selected HTTP response headers (Firefox OS, Firefox on Android, Safari on iPhone):

Response for: 'Mozilla/5.0 (Mobile; rv:29.0) Gecko/29.0 Firefox/29.0'
Response Status: 200
content-length: 395755
content-type: text/html;charset=utf-8

Response for: 'Mozilla/5.0 (Android; Mobile; rv:26.0) Gecko/26.0 Firefox/26.0'
Response Status: 302
content-length: 212
location: http://mobile.southwest.com/
content-type: text/html; charset=iso-8859-1

Response for: 'Mozilla/5.0 (iPhone; CPU iPhone OS 6_0 like Mac OS X) AppleWebKit/536.26 (KHTML, like Gecko) Version/6.0 Mobile/10A5376e Safari/8536.25'
Response Status: 302
content-length: 212
location: http://mobile.southwest.com/
content-type: text/html; charset=iso-8859-1
Whiteboard: [2.2-exploratory-1] → [2.2-exploratory-1] [serversniff] [contactready] [country-us]
SeeAlso https://github.com/webcompat/web-bugs/issues/384
There is a dependency on the Mobile version which sends a blank screen to Firefox Mobile.
With A chrome mobile UA (on Firefox Desktop), this happens:

12:55:53.471 GET http://southwest.com/ [HTTP/1.1 302 Found 446ms]
12:55:53.926 GET http://mobile.southwest.com/ [HTTP/1.0 302 Found 652ms]
12:55:54.592 GET https://mobile.southwest.com/ [HTTP/1.1 200 OK 1692ms]
12:55:56.291 GET https://mobile.southwest.com/spaandroid/konyspaandroid320.css [HTTP/1.1 200 OK 191ms]
12:55:56.292 GET https://mobile.southwest.com/spaandroid/jslib/konyframework.js [HTTP/1.1 200 OK 1066ms]
12:55:56.382 GET https://mobile.southwest.com/spaandroid/images/320/defaults.png [HTTP/1.1 200 OK 339ms]
… etc.

Though at a point it seems to be blocked by a request to 

It has a lot of tracking parameters.


Also it seems that the DOM is being written then it becomes blank again.

the main app.js script has, once it has been prettified, around 184,000 lines of code.
You need to log in before you can comment on or make changes to this bug.