681335 - Firefox mobile not passing through useragent of the actual device

Status: RESOLVED DUPLICATE of bug 625238

(Firefox for Android Graveyard :: General, defect)

Description

[Rich Gubby]

User Agent: Mozilla/5.0 (Windows NT 6.1; WOW64) AppleWebKit/535.1 (KHTML, like Gecko) Chrome/13.0.782.112 Safari/535.1

Steps to reproduce:

Browsed a site with Firefox Mobile


Actual results:

The site didn't render properly with missing http headers.


Expected results:

When using Firefox Mobile, the useragent of the original device is not being passed through as an http header when browsing to a site.

At Wapple, we use these headers extensively to profile a device exactly. We need to know everything there is to know about a device, here are a few examples:

Screen width: Without knowing what device is browsing a site, we don't know how wide to render graphics. We repurpose graphics on the fly so the user automatically gets graphics at the right width, but without knowing how wide the device is, we cannot do this.

Capabilities: We need to know what type of video a handset supports - without knowing the device, we don't reliably know, so we can't deliver the right video with any certainty.

Click to call: If a device supports tel: rather than wtai://wp/mc; we need to know - but without the useragent http header, we can't tell.

Can Firefox Mobile please pass through the original useragent of the device so that we can successfully profile devices correctly and deliver a great user experience. With the current system, we are providing a really poor experience to users.

Thanks.
Rich Gubby