hey,
using the latest wurfl.xml & API.
we have a set of UAs that are identified as "Desktop" (using the form_factor capability)
for example, take a look on the list below. all of them were identified as "desktop".
from a quick search those are http clients implemented in different languages, that can, theoretically be implemented both on mobile, tv, or desktop. for example, okhttp is a android & java http client.
okhttp/3.9.0
okhttp/3.5.0
okhttp/2.7.1
Apache-HttpAsyncClient/4.1.3 (Java/1.8.0_20)
scalaj-http/1.0
Go-http-client/2.0
is it intentionally ? personally, we prefer to set form_factor rather than giving incorrect values.
non accurate form_factor matching
Re: non accurate form_factor matching
Hi,
As mentioned in our other thread, we will likely modify the behavior with all the provided user agents to work similarily to the Go-http-client/2.0 user agent as we would consider all these as spiders/content-fetchers. They will be identified as robots for the form_factor virtual capability in the next API release.
Thanks,
Aaron
As mentioned in our other thread, we will likely modify the behavior with all the provided user agents to work similarily to the Go-http-client/2.0 user agent as we would consider all these as spiders/content-fetchers. They will be identified as robots for the form_factor virtual capability in the next API release.
Thanks,
Aaron
Who is online
Users browsing this forum: No registered users and 2 guests