Thanks for the help sriram, It looks like this was not a WURFL problem by rather a MVC/ WebAPI problem. The useragent was being URL Decoded twice thereby removing the + in the middle of the user agent string. This then caused WURFL to not be able to detect the device. The reason that we thought it w...

Hi, We are running version 1.4.4 of the WURFL API downloaded to our .Net project using Nuget. and the latest definition file (August 11, 2013) and yet the following user agent is not being detected: Mozilla/5.0 (BB10; Touch) AppleWebKit/537.10+ (KHTML, like Gecko) Version/10.1.0.1720 Mobile Safari/5...

Hi again, We have spotted that WURFL is not returning information for the Midori browser (http://www.midori-browser.org). Here are a list of user agents that fail to return BrandName, ModelName, MarketingName, etc. Midori/0.2 (X11; Linux; U; it-it) WebKit/531.2+ Midori/0.3 (Windows; Windows; U; fr-f...

Hi Osiris, Thank you for your post and heads-up about the is_bot capability. We are currently working on optimizing the bot detection logic in the WURFL API and we'll also make sure the capability values are fixed. Thanks and cheers! Not a problem sriram. If you could, please let us know when you r...

Hi, We have recently been looking at the bot traffic hitting our sites and have noticed that there are a few bots sneaking passed our WUFRL detection. We are using the latest version of the definition file June 2, 2013 and v1.4.4.0 of the .Net API. Here are the UserAgents that are not being correctl...