Confirmed users
1,567
edits
Compatibility/Tools: Difference between revisions
Jump to navigation
Jump to search
→Client Side User Agent Detection: explaining client side ua
(→Things to think about when testing: Documenting UA override management script) |
(→Client Side User Agent Detection: explaining client side ua) |
||
| Line 84: | Line 84: | ||
== Client Side User Agent Detection == | == Client Side User Agent Detection == | ||
=== Prepare === | |||
First of all it is a good idea to install the Firefox Add-On [http://chrispederick.com/work/user-agent-switcher/ User Agent Switcher] (see the [https://miketaylr.com/posts/2014/01/useragent-switcher-xml.html blogpost by Mike Taylor]). It will help to impersonate the User Agent of other browsers at both the HTTP and JavaScript levels. | |||
For example, on Firefox Desktop once impersonated as Firefox for Android, you would get on the Web console. | |||
=== Search === | |||
Some Web developers have no control on the server configurations. To be able to redirect to a Web site with tailored content for Mobile they will rely on '''user agent detection''' on '''the client side'''. There are different techniques for discovering if the scripts on the site are doing User Agent detection. You may want to look for | |||
navigator.userAgent | |||
or simply | |||
userAgent | |||
Another way of finding if there is user agent detection is by looking for: | |||
navigator.platform | |||
== Redirection based on Geolocation == | == Redirection based on Geolocation == | ||