Using Apache with mod_proxy
There are some common situations where you might use the configuration:
- You have an existing Apache-based website, and want to add Confluence to the mix (for example, ).
- You have two or more Java applications, each running in their own application server on different ports, for example, and . By setting up Apache with mod_proxy, you can have both available on the regular HTTP port (80) – for example, at and . This allows each application to be restarted, managed and debugged separately.
Note: This page documents a configuration of Apache, rather than of Confluence itself. Atlassian will support Confluence 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.
Set the context path
Set your Confluence application path (the part after hostname and port). To do this in Tomcat (bundled with Confluence), edit
conf/server.xml, locate the "Context" definition:
and change it to:
Then restart Confluence, and ensure you can access it at
Set the URL for redirection
Set the URL for redirection. In the same
conf/server.xml file, locate this code segment:
And append the last line:
If this isn't working for you and you're using SSL, try adding a scheme attribute to your Connector tag: scheme="https".
Now we have two options:
- If you want a URL like , follow the simple configuration.
- If you want a URL like complex configuration. , go to the
Now enable mod_proxy in Apache, and proxy requests to the application server by adding the example below to your Apache httpd.conf (note: the files may be different on your system; See Integrating JIRA with Apache for the process for Ubuntu/Debian layout):
It is recommended that you specify the absolute path to the
Complex configuration involves using the mod_proxy_html filter to modify the proxied content en-route. This is required if the Confluence path differs between Apache and the application server. For example:
Externally accessible (Apache) URL
Application server URL
Notice that the application path in the URL is different in each. On Apache, the path is /, and on the application server the path is /confluence.
The ProxyHTMLURLMap configuration can become more complex if you have multiple applications running under this configuration. The mapping should also be placed in a Location block if the web server URL is a subdirectory and not on a virtual host. The Apache Week tutorial has more information how to do this.
Final Configuration Steps
Restart your Apache server
This is needed to pick up on the new configuration. This can be done by running the following on your command line/terminal/shell:
Disable HTTP Compression
Having compression run on both the proxy and Tomcat can cause problems integrating with other Atlassian applications, such as JIRA. Please disable HTTP compression as per our Compressing an HTTP Response within Confluence docs.
Set the Confluence Base URL
- The mod_proxy_html site has documentation and examples on the use of this module in the complex configuration.
- Apache Week has a tutorial that deals with a complex situation involving two applications and ProxyHTMLURLMap.
- Using Apache with virtual hosts and mod_proxy shows how to configure the special case where you want JIRA and Confluence running on separate application servers on virtual host subdomains.
If Tomcat is your application server, you have two options:
- use mod_jk to send the requests to Tomcat
- use Tomcat's virtual hosts to make your Confluence application directory the same on the app server and the web server, removing the need for the URL mapping.
If your application server has an AJP connector, you can:
- use mod_jk to send the requests to your application server.
Was this helpful?
Thanks for your feedback!