Running Confluence behind Apache
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.
Introduction
For improved performance in high-load environments, you should run Confluence behind a web server. In general, web server caching and thread management is far superior to that provided by your application server's HTTP interface.
To run Confluence behind the Apache httpd web server, there are two main configuration options: mod_jk or mod_proxy.
Connection type | Unique features | Common features to both mod_proxy and mod_jk |
|---|---|---|
mod_proxy (also known as reverse proxy) |
|
|
mod_jk (also known as AJP) |
|
Configuration Guides
Please choose one configuration. Trying to configure for both mod_proxy and mod_jk will only lead to confusion and tears.
Mod_jk2 not supported
The misleadingly-named mod_jk2 is an older method of connecting to Tomcat from Apache. Since mod_jk2 is no longer supported by the Apache Foundation, we do not support this configuration, and are not updating our mod_jk2 documentation. Mod_jk2 also has unresolved problems with Unicode URLs; you need to use either mod_proxy or mod_jk for international characters to work correctly in Confluence.
Caching static content via mod_disk_cache
To improve performance of a large Confluence site, we recommend that you move the caching of static content from the JVM into Apache. This will prevent the JVM from having a number of long running threads serving up static content. See Configuring Apache to Cache Static Content via mod_disk_cache.