Changes for page Betrieb hinter Proxy/Load-Balancer o.ä.
From version 1.3
edited by XIMA Admin
on 22.09.2021, 18:21
on 22.09.2021, 18:21
Change comment:
There is no comment for this version
Summary
-
Page properties (2 modified, 0 added, 0 removed)
Details
- Page properties
-
- Author
-
... ... @@ -1,1 +1,1 @@ 1 -XWiki. ximaadmin1 +XWiki.sas - Content
-
... ... @@ -22,8 +22,17 @@ 22 22 1. 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. 23 23 1. 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). 24 24 25 - This configuration,as wellasany settings thatmaybenecessarywhenusingself-generatedcertificates,is briefly illustratedhere:25 +For the Apache settings it is necessary to activate the corresponding modules. The following are required as minimum: 26 26 27 +* proxy 28 +* proxy_http 29 +* proxy_wstunnel 30 +* rewrite 31 + 32 +Further information about the modules of Apache you will find [[here>>https://httpd.apache.org/docs/current/mod/||rel="noopener noreferrer" target="_blank"]]. 33 + 34 +The configuration described above, as well as any settings that may be necessary when using self-generated certificates, is briefly illustrated here: 35 + 27 27 ((( 28 28 {{code language="none"}} 29 29 <VirtualHost www.example.com:80> ... ... @@ -111,4 +111,4 @@ 111 111 </Engine> 112 112 {{/code}} 113 113 114 -**Note:** If the configuration of the //X-Forwarded// header does not work, it may be necessary to configure the IPs of the trustworthy proxy servers in the //internalProxies// property. One or more IP addresses or an IP address range is expected here, which can be defined using a regular expression (e.g .: 169\.254\.\d{1,3}\.\d{1,3}). 123 +**Note:** If the configuration of the //X-Forwarded// header does not work, it may be necessary to configure the IPs of the trustworthy proxy servers in the //internalProxies// property. One or more IP addresses (e.g.: 192\.168\.0\.10|192\.168\.0\.11) or an IP address range is expected here, which can be defined using a regular expression (e.g .: 169\.254\.\d{1,3}\.\d{1,3}).