Installation - Operation behind Proxy, Load-Balancer or similar

Page / - last modified by MKO on 29.05.2020, 18:11

Operation behind Proxy, Load-Balancer or similar

last modified by MKO

on 29.05.2020, 18:11

Table of Contents

Example configuration Apache

Usage of X-Forwarded headers for unencrypted communication

Configuration examples

If the application server (e.g. Apache Tomcat) on which Xima® Formcycle is installed is running behind another server, e.g. a reverse proxy, a load balancer or similar, it should be checked that the information of a request is passed on to it unchanged. In concrete terms this means that both the Host header and the protocol used must be passed on unchanged by the intermediate servers. In most standard configurations, however, this is not the case because the requests are received by the intermediate server and sent to the application server as a new request.

Manipulation of the host and the protocol by a reverse proxy.

The problematic scenario (see figure) is the following:

The user calls the URL https://www.example.com/formcycle.

The request is received and evaluated by the intermediate server.

The intermediate server makes a new request to the designated server. However, since an internal request is made here, the call URL is changed to http://192.168.0.1/formcycle. This URL now arrives at the application server and no longer contains the required information about which URL was actually called by the user.

Since Xima® Formcycle interprets the original request URL of the user, especially when logging into a form, and this URL may not be determined correctly, it is necessary to configure intermediate servers accordingly. Make sure that both the HTTP header Host and the protocol used (HTTP or HTTPS) are forwarded unchanged. Also, the correct forwarding of WebSocket connections must be provided. Alternatively to the concret protocols, the intermediate server can also use X-Forwarded headers to indicate which protocol the request used originally.

Example configuration Apache

For the correct configuration of an Apache server, which acts as a reverse proxy, three points are relevant and have to be stored e.g. in the configuration of the VirtualHosts:

The instruction ProxyPreserveHost On to get the originally called Host header

The separation of the individual protocols and its usage when forwarding to the application server. This means that for HTTP and HTTPS a separate VirtualHost with appropriate configuration must be used.

Configuration of the conditional RewriteRule for the forwarding of WebSocket connections via WS and WSS. By default, FORMCYCLE uses the corresponding ports of the servlet container (WS port = HTTP port, WSS port = HTTPS port).

This configuration, as well as any settings that may be necessary when using self-generated certificates, is briefly illustrated here:

<VirtualHost www.example.com:80>
...
# Enables retention of the originally called host up to the application server.
ProxyPreserveHost On
...
# Forwarding via HTTP
ProxyPass / http://192.168.0.1/
ProxyPassReverse / http://192.168.0.1/
...
# Forwarding of websocket-connections via WS
RewriteEngine on
RewriteCond %{HTTP:Upgrade} websocket [NC]
RewriteCond %{HTTP:Connection} upgrade [NC]
RewriteRule ^/?(.*) "ws://192.168.0.1:80/$1" [P,L]
</VirtualHost>
<IfModule mod_ssl.c>
<VirtualHost www.example.com:443>
...
SSLEngine on
SSLProxyEngine On
...
# Enables retention of the originally called host up to the application server.
ProxyPreserveHost On
# Deactivates the certificate check of the application server if necessary.
# Necessary if the certificates are self-created.
SSLProxyVerify none
SSLProxyCheckPeerCN off
SSLProxyCheckPeerName off
SSLProxyCheckPeerExpire off
...
# Forwarding via HTTPS
ProxyPass / https://192.168.0.1/
ProxyPassReverse / https://192.168.0.1/
...
# Forwarding of websocket-connections via WSS
RewriteEngine on
RewriteCond %{HTTP:Upgrade} websocket [NC]
RewriteCond %{HTTP:Connection} upgrade [NC]
RewriteRule ^/?(.*) "wss://192.168.0.1:443/$1" [P,L]
</VirtualHost>
</IfModule>

Usage of X-Forwarded headers for unencrypted communication

If the intermediate server supports sending X-Forwarded headers and the servlet container which hosts Xima® Formcycle can evaluate these headers, the communication between the intermediate server and Xima® Formcycle can also be done via another protocol. Both the intermediate server and the servlet container must be configured to use these headers. For more information on configuration, refer to the documentation of the respective product.

Configuration examples

With Apache, for example, the following configuration inside the responsible VirtualHosts can be used to include the appropriate headers:

//HTTP
RequestHeader set X-Forwarded-Port "80"
RequestHeader set X-Forwarded-Proto "http"
//HTTPS
RequestHeader set X-Forwarded-Port "443"
RequestHeader set X-Forwarded-Proto "https"

With nginx, for example, the following configuration can be used to send the corresponding headers in the section responsible for the reverse proxy:

proxy_pass http://127.0.0.1:8080/formcycle/;
proxy_set_header Host $http_host;
proxy_set_header x-real-ip $remote_addr;
proxy_set_header x-forwarded-proto $scheme;

For Apache Tomcat servers, the following valve entry must be added to the server.xml within the catalina engine to evaluate the sent X-Forwarded headers:

<Engine......
<Valve className="org.apache.catalina.valves.RemoteIpValve"
remoteIpHeader="x-forwarded-for"
protocolHeader="x-forwarded-proto"
protocolHeaderHttpsValue="https" />
</Engine>