Confluence 2.6 has reached end of life
Check out the [latest version] of the documentation
Introduction
Running Confluence behind a web server should be done for performance reasons in high-load environments. 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 |
Features |
---|---|
mod_proxy (also known as reverse proxy) |
|
mod_jk (also known as AJP) |
|
Features common to both mod_proxy and mod_jk |
---|
|
Mod_proxy documentation
- Using Apache with mod_proxy is the main documentation for this configuration.
- If you want to set up the common configuration of JIRA and Confluence virtual hosts, you can use Apache's virtual hosts with separate application servers, then Tomcat's virtual hosts to run both applications on a single instance of Tomcat.
Mod_jk documentation
- Using Apache with mod_jk is the main documentation for this configuration.
- You can follow a similar method to the mod_proxy documentation above for setting up virtual hosts in Apache and Tomcat, if required.
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.