Network / Proxy Settings

These specific settings are rarely relevant. CCM19 is designed to generally work without any problems using the provider's standard settings.

Force HTTPS-Connection

Use this option if the application is located behind a load-balancer or a similar environment where, for example, SSL-offloading takes place. If certain headers are not passed through, an HTTPS-connection may not be automatically detected, which could result in front-end-resources being incorrectly requested over an unsecured connection.

If you encounter issues with SSL-functions, this is your first point of contact.

Base URL

The URL for CCM19 is usually determined automatically. In cases where the URL cannot be reliably determined, this URL is used as a fallback to generate links. This setting only needs to be changed if the name truly cannot be resolved.

Maximum Session-Inactivity Time

This setting allows you to specify the maximum wait time after which inactive backend-users are automatically logged out. Set to 0 for unlimited. The session-lifetime may still be limited by other factors beyond CCM19’s control.

Additional Settings

Proxy Settings

Use this option only if connections from this server must be routed through a company-owned proxy. Use server:port or http://server:port for HTTP-proxies, https://server:port for HTTPS-, socks4://server:port for SOCKS 4- and socks5://server:port for SOCKS 5-proxies.

Trusted Reverse-Proxies

The IP-addresses or -subnets specified here are trusted, for example, regarding which hostname should be used and what IP-address the original client has. In the default configuration, reverse-proxies on the same server (127.0.0.0/8 and ::1/128) are trusted.

Call Counters-Exceptions

Here you can exclude IP-addresses and User-Agent-strings from the call count. This can be used to prevent search engines-bots, and local users from increasing the call count and thereby contributing to rate-limitations.

In the cloud-version, this feature is set globally for all users by the administrator. In the case of the CCM19 Cloud, the settings are managed directly by the CCM19 team.