The User Agent string identifies the types of devices requesting online content.
The server that the request is sent to will then determine the type of content to display, the layout, identify any re-directions for that device type, as well as use the information for analysing web-traffic.
You can find the setting for User Agent control under Settings > Page & Content > User Agent (Kiosk Browser) or Settings > Browser > Page & Content > User Agent (Kiosk Launcher).
Default User Agent
By default, the WebView on which Kiosk Browser is based provides the user agent string, which is determined by various device properties.
Desktop User Agent
You can set the User Agent to desktop which will force the page to load in desktop mode.
Custom User Agent
To set a Custom User Agent, firstly you would need to select the option for this under Settings > Page & Content > User Agent. (Kiosk Browser) or Settings > Browser > Page & Content > User Agent (Kiosk Launcher)
Once you have enabled the Custom User Agent, you will need to enter the string for the User Agent that you wish to use, under Settings > Page & Content > Custom User Agent (Kiosk Browser) or Settings > Browser > Page & Content > Custom User Agent (Kiosk Launcher)
Custom User Agent String
As an example below, you can see the device User Agent has been set to that of a Windows 10 based PC using Edge Browser, the string for this would be:
Mozilla/5.0 (Windows NT 10.0; Win64; x64) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/42.0.2311.135 Safari/537.36 Edge/12.246
Some example User Agent strings can be found here. This list is external and is by no means exhaustive, as there are millions of possible User Agents.
As with other Kiosk Browser/Launcher settings, the User Agent can also be defined under Profiles or Configurations in both remote management products.
There is some further external material regarding User Agents available to read here.
Updated on: 03 / 03 / 2021