Global proxy

This configuration defines a network-independent global HTTP proxy for managed devices.

The Global proxy configuration defines an HTTP proxy that applies regardless of the connected network. It is intended for the enrollment types Managed Device → and managed device with a personal profile → (COPE), not for devices with a work profile → (BYOD).

The portal shows the following notice in the form:

A per-network proxy is defined in the Proxy settings section of the Wi-Fi → configuration.


Proxy type

The Proxy type field determines how the proxy is defined. Different fields are shown depending on the selection.

  • Direct – host, port and exclusions are specified manually. This option is preselected in a new configuration.
  • PAC script – the proxy is configured automatically via a PAC script.

Direct

  • Proxy host (required) – IPv4 address (e.g. 10.0.0.1) or URL with http:// or https:// and a domain name with a top-level domain in lowercase (e.g. http://proxy.example.com), in each case without port and path. A host name without protocol (proxy.example.com) or without top-level domain (http://proxy) is not accepted. If the input is invalid, the field is marked as erroneous and the configuration cannot be saved.
  • Proxy port (required) – port of the proxy; values from 0 to 65535 are accepted.
  • Hosts for which the proxy is bypassed – list of hosts whose connections do not go through the proxy. Host names may contain wildcards such as *.example.com.

PAC script

  • PAC script URI (required) – URI of the PAC script used to configure the proxy. The portal expects a valid URL.

Validation

When saving, Relution checks that a Proxy host is specified for proxy type Direct and a PAC script URI for proxy type PAC script. Fields of the other proxy type are not transferred to the device.

Top