The user agent for a browser identifies the browser to web server applications, allowing the applications to make choices about the pages and content that they serve. For example:
•For iOS, the user agent string for Web@Work on an iPad running iOS 7.0.4 is:
Mozilla/5.0 (iPad; CPU OS 7_0_4 like Mac OS X) AppleWebKit/537.51.1 (KHTML, like Gecko) Mobile/11B554a MobileIron/1.3.0 Version/7.0.4 Safari/537.51.1
•For Android, the user agent string for Web@Work on a Nexus 10 tablet running Android 4.2.2 is:
Mozilla/5.0 (Linux; Android 4.2.2; Nexus 10 Build/JDQ39) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/28.0.1500.94 Safari/537.36
Make sure your web server applications handle Web@Work requests just as they would handle native browser requests on the
The default product name (or user agent) for Web@Work contains “MobileIron/<version-number>”. The presence of the word “Mobile” confuses some web servers, causing them to return only the mobile version of a web page, even on devices with large screens.
Use the browser_product_name key to change the product name to “MISecureBrowser” to obviate this behavior.
For devices with screens that are 6.5” or smaller, Web@Work automatically uses “Mobile” in the product name.
Use this key-value pair to ensure larger-screen devices will receive appropriate content from web apps or sites that use the term “Mobile” from the user agent to determine content rendering. Small screened devices will continue to render correctly.
To configure the Web@Work product name, follow these steps to set the key-value pair described below.
|1.||Sign in to the Core Admin Portal.|
|2.||Go to Policies & Configs > Configurations.|
|3.||Select the Web@Work setting that applies to the devices of interest.|
|5.||Under Custom Configurations, click Add.|
|6.||Add the following keys and values:|
|8.||Apply this Web@Work configuration to labels that identify the devices that should receive this configuration.|