This section provides a proxy server configuration example to use a specific domain name and path to access a Fluid Topics portal using the Apache web server.
It includes a proxy definition for:
https://proxy-portal/tohttps://institutional-portal/https://proxy-portal/pathtohttps://documentation-portal/
Every request should include the following request headers:
X-Forwarded-Proto: httpsX-Forwarded-Host: proxy-portalFT-Forwarded-Path: /path/
<VirtualHost *:443>
ServerName proxy-portal
# (1)
SSLEngine on
SSLCertificateFile "/path/to/cert.pem"
SSLCertificateKeyFile "/path/to/key.pem"
# (2)
SSLProxyEngine on
# (3)
RequestHeader set X-Forwarded-Proto "https"
RequestHeader set X-Forwarded-Host "proxy-portal"
# (4)
<Location "/">
ProxyPass "https://institutional-portal/"
ProxyPassReverse "https://institutional-portal/"
</Location>
# (5)
<Location "/path">
ProxyPass "https://documentation-portal/"
ProxyPassReverse "https://documentation-portal/"
RequestHeader set FT-Forwarded-Path "/path/"
</Location>
</VirtualHost>
- The use of SSL for the Fluid Topics web application is mandatory. It is possible to implement SSL configuration at the virtual host level, as shown in the example. It is also possible to manage SSL configuration at the load balancer level through SSL offloading.
- The
SSLProxyEnginedirective may be required to proxy a domain that is exposed with HTTPS enabled. - Apache automatically forwards client details using the
X-Forwarded-*headers. If this does not occur, it is necessary to explicitly add these headers. The proxied base domain needs the required headers to ensure correct functioning of the Fluid Topics server. - This virtual host allows requests to a proxy domain to be forwarded to a given domain.
- This virtual host configuration allows requests sent to a specific path (
https://proxy-portal/path) to be forwarded to a Fluid Topics server available athttps://documentation-portal/.
To ensure optimal performance, configure the proxy server to accept the following headers: Accept, Accept-Encoding, Cookies.
Do not force or override the Content-Type header in the proxy configuration. Forcing content types causes integration failures.