Connection settings

To access the device remotely, you need to specify the port and protocol (HTTP / HTTPS). This can be achieved by setting up an accessible port in the cellular router or terminal device through port forwarding.

For security purposes, it is recommended to enable remote access through an encrypted HTTPS port in the router or terminal device (e.g. HTTPS port 443).

The lock symbol in the graphic indicates whether the connection is using an unencrypted (insecure) HTTP or an encrypted (secure) HTTPS connection.

Controls the cookies that the mdex Gateway sends to the device.
Usually the setting "Max. performance (Passthrough)", which forwards all browser cookies.

In case of problems caused by header limits, "Max. compatibility (No web.direct cookies)" or "No cookies" are selected. However, the latter can lead to problems if the device needs its own cookies.

The standard is "Supported", which allows the device to exchange data between the browser and the end device via web sockets.

With "Supported (with X-Header)", an additional X-Forwarded-For-Header is transmitted to the end device if there are problems with web sockets, so that the device can work with the address of the mdex Gateway.

If no websocket support is required, this option can also be disabled with "Not supported".

Inline Logout: Allows you to embed a web.direct logout button in HTML pages to log out directly to the device. Disabled by default, as it can cause display problems. Alternatively, you can attach /webdirect/logout to the URL.

Security header: Adds optional security headers between mdex gateway and device that can increase security but limit compatibility.

Advanced connection settings