Please note: This article is provided as-is. Due to the varying nature of client environments, Hannon Hill Product Support does not provide assistance for configuring Apache. Consequently, Hannon Hill Product Support can not guarantee providing any support in configuring Apache.
If assistance with configuration is required, please raise a question on the community forums.
This page describes one possible way to use Apache HTTP Server 2.4 to proxy requests for Cascade CMS running in a standard Tomcat container.
Note: This page documents a configuration of Apache, rather than of Cascade CMS itself. Hannon Hill will support Cascade CMS with this configuration, but we cannot guarantee to help you debug problems with Apache. Please be aware that this material is provided for your information only, and that you use it at your own risk.
Apache 2.4 modules used
Apache 2.4 can be used to proxy requests to the Cascade CMS Tomcat container. The benefit being additional control over request handling and simplified SSL handling.
Here is a sample configuration that forces connections over SSL using
mod_proxy, handles SSL using
mod_ssl, proxies requests to the Tomcat container using
mod_proxy_ajp and adds compression using
Given the apove Apache 2.4 configuration, the following Connectors are assumed within the Tomcat container's
server.xml configuration file is located within the installation directory at
Cascade CMS utilizes Websockets for almost-real-time notifications and partial UI refreshing, as opposed to repeatedly polling with AJAX requests. As such, the
mod_proxy_wstunnel module and additional configuration are required in order to allow Apache to handle these websocket requests. Note the following section within the above configuration:
# Websocket configuration ProxyPass /websocket ws://localhost:8080/websocket ProxyPassReverse /websocket ws://localhost:8080/websocket
The key is the port within this directive needs to match the non-SSL port defined within the Tomcat container. Don't worry about this not being SSL here, normal web requests are forced over SSL and Cascade CMS will automatically change the websocket request over to
wss://, which is the secure protocol for websockets.