Firefox user-agent with "toolbar" attribute wrong detected

I have this HTTP request, I expected this, but WURFL is returning that. Please provide enough data to reproduce the problem.
mimmi
Posts: 11
Joined: Sun Jul 24, 2011 6:12 am

Firefox user-agent with "toolbar" attribute wrong detected

Postby mimmi » Sun Jul 24, 2011 6:39 am

I found a lot of user agents in my logs who looks like Firefox, but are detected as a Novarra Proxy (id: stupid_novarra_proxy_sub73). See below for some examples..

I am using the PHP API 1.3.1.
It looks to me that the word "toolbar" causes this.
Should this be the correct behavior?

Mozilla/5.0 (Windows; U; Windows NT 5.1; de; rv:1.9.2.18) Gecko/20110614 Firefox/3.6.18 (.NET CLR 3.5.30729) SearchToolbar/1.2
Mozilla/5.0 (Windows; U; Windows NT 5.1; de; rv:1.9.2.18) Gecko/20110614 AlexaToolbar/alxf-2.01 AskTbSPC2/3.12.2.16749 Firefox/3.6.18 GTB7.1 ( .NET CLR 3.5.30729)
Mozilla/5.0 (Windows; U; Windows NT 6.0; en-US; rv:1.9.1.3 Alexa Toolbar) Gecko/20090824 Firefox/3.5.3
with kind regards
Thomas Müller

I'm using the PHP API 1.3.1 with wurfl.xml from 2011-07-13

nick_bss
Posts: 1
Joined: Tue Mar 03, 2015 12:00 pm

Re: Firefox user-agent with "toolbar" attribute wrong detect

Postby nick_bss » Tue Mar 03, 2015 12:01 pm

Did anyone come across a solution to this? I have run across the same problem.

For instance this Mozilla/5.0 (Windows NT 6.3; WOW64; rv:35.0) Gecko/20100101 Firefox/35.0 AlexaToolbar/alxf-2.21 UA will not be detected as desktop firefox, but as an LG Saber UN200.

sriram
Posts: 161
Joined: Wed Jan 04, 2012 10:01 am

Re: Firefox user-agent with "toolbar" attribute wrong detect

Postby sriram » Tue Mar 03, 2015 12:50 pm

Hi Nick,
For instance this Mozilla/5.0 (Windows NT 6.3; WOW64; rv:35.0) Gecko/20100101 Firefox/35.0 AlexaToolbar/alxf-2.21 UA will not be detected as desktop firefox, but as an LG Saber UN200.
I'm unable to replicate the issue you're having with the UA from your post. It correctly shows up as Firefox 35 on our end.

Could you please provide us with the following details so we can look into this:
1. Type and language of the WURFL API used
2. Version of the WURFL API used
3. Date of the WURFL.xml file used (if applicable)

Thanks,
Sriram Sridharan


Who is online

Users browsing this forum: No registered users and 2 guests