Closed Bug 843151 Opened 11 years ago Closed 6 years ago

citibank.com doesn't recognize B2G UA as mobile

Categories

(Web Compatibility :: Site Reports, defect, P5)

Product:
Web Compatibility
Component:
Site Reports
Platform:
ARM
Gonk (Firefox OS)
Type:
defect

Tracking

(Not tracked)

Status:
RESOLVED WONTFIX

People

(Reporter: lmandel, Assigned: karlcow)

References

(
URL
)

Details

(Whiteboard: [uaoverride] [country-all] [sitewait] [serversniff])

Attachments

(1 file)

Screenshot from Flame smartphone
70.40 KB, image/png
Details 
citibank.com serves a desktop site to B2G. Bug 823364 added an UA override for this domain. The override should be removed once the domain serves mobile content to B2G. This bug tracks the evangelism for the site to recognize the B2G UA and the removal of the override at that time.
Blocks: citibank.com
URL: citibank.com
Whiteboard: [uaoverride]
On desktop computer, when typing http://citibank.com/, we are redirected to https://online.citibank.com/US/Welcome.c

On ZTE device with UA override we receive a working mobile content. same URI https://online.citibank.com/US/Welcome.c

On ZTE device with UA override we receive a desktop content. same URI https://online.citibank.com/US/Welcome.c


# Firefox for Android

HEAD / HTTP/1.1
Accept: */*
Accept-Encoding: gzip, deflate, compress
Host: citibank.com
User-Agent: Mozilla/5.0 (Android; Mobile; rv:18.0) Gecko/18.0 Firefox/18.0



HTTP/1.1 301 Moved Permanently
Connection: close
Content-length: 0
Date: Thu, 01 Aug 2013 16:13:14 GMT
Location: https://online.citibank.com/US/Welcome.c
Server: ""

The HEAD is not working

HEAD /US/Welcome.c HTTP/1.1
Accept: */*
Accept-Encoding: gzip, deflate, compress
Host: online.citibank.com
User-Agent: Mozilla/5.0 (Android; Mobile; rv:18.0) Gecko/18.0 Firefox/18.0



HTTP/1.1 501 Not Implemented
Connection: keep-alive
Content-Encoding: gzip
Content-Length: 20
Content-Type: text/html
Date: Thu, 01 Aug 2013 16:14:09 GMT
Vary: accept-encoding


Switching to a GET

GET /US/Welcome.c HTTP/1.1
Accept: */*
Accept-Encoding: gzip, deflate, compress
Host: online.citibank.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-cache, must-revalidate, proxy-revalidate, no-store
Connection: keep-alive
Content-Encoding: gzip
Content-Language: en-US
Content-Length: 6226
Content-Type: text/html; charset=ISO-8859-1
Date: Thu, 01 Aug 2013 16:14:57 GMT
Expires: Thu, 01 Jan 1970 00:00:00 GMT
Jid: M30801121457197708095978
P3P: policyref="http://online.citibank.com/w3c/p3p.xml",CP="CAO DSP CUR ADM DEV OUR NOR STP UNIo NAV STA PREi  TAI"
Pragma: no-cache
Set-Cookie: JSESSIONID=0000MGFW6CKYE3-ANXfPLfB5tLS:prap17-usgcb3; Path=/; Secure
Vary: accept-encoding
X-frame-options: SAMEORIGIN
X-ua-compatible: IE=edge
X-ua-compatible: IE=edge

<!doctype html>

Working! Let's see if we can find something to test for the future in regression testing. Yes we have differences in between Firefox OS and Firefox for Android.

# Firefox for Android
→ http -v GET https://online.citibank.com/US/Welcome.c User-Agent:'Mozilla/5.0 (Android; Mobile; rv:18.0) Gecko/18.0 Firefox/18.0'  | grep -i device

	var deviceType = "1";
<meta name="viewport" content="width=device-width; user-scalable=0;" />
myForm.ioBlackBox.value = deviceprint_blackbox();
function deviceprint_blackbox()
<input type="hidden" name="devicePrint" value=""/>
<!-- running  rule explicitly to reset the Device detection for the next page scenario -->

# Firefox OS
→ http -v GET https://online.citibank.com/US/Welcome.c User-Agent:'Mozilla/5.0 (Mobile; rv:18.0) Gecko/18.0 Firefox/18.0'  | grep -i device

	var deviceType = "0";


Also
var mobile = false; Firefox OS
var mobile = true;  Firefox for Android
Whiteboard: [uaoverride] → [uaoverride] [country-all] [sitewait] [serversniff]
Assignee: nobody → kdubost
Asking again. Had no answer the first time.
http://twitter.com/MozWebCompat/status/374908521961512960

Sent also question through the site feedback widget at the bottom
http://www.citigroup.com/citi/about/countrypresence/
Sent an email to the suggested email customer.help@citi.com.
http://twitter.com/AskCiti/status/374912533968478208
Status: NEW → ASSIGNED
sent a reminder
Tried again to the direct contact I have there.
So interesting the mailbox of the contact failed because… it is full. No wonder why there are no answers.
Got a human contact through an ex-developer of Citibank. Very helpful. Thanks a lot.
ok. Nice contacts going on.
Site vendor is MadMobile (http://www.madmobile.com/clients). Which I found through another bug, have asked to pass my contact info so I can share other bugs with them.
See Also: → 960446
Unfortunately MadMobile only supports webkit browsers on mobile, also they do not manage the desktop version of the site.
See Also: → 1011524
See Also: → 1099163
Contacted again today for a reminder.
Priority: -- → P5
Closing as we are not working on Firefox OS anymore.
Status: ASSIGNED → RESOLVED
Closed: 6 years ago
Resolution: --- → WONTFIX
Product: Tech Evangelism → Web Compatibility
Component: Mobile → Site Reports
You need to log in before you can comment on or make changes to this bug.

Attachment

General

Creator:
Created:
Updated:
Size: