All HowTo's Cyber-Security Web Servers

Confluence Configuration when using an Apache SSL Reverse Proxy

This article demonstrates how to configure the Confluence “server.xml” file when using Confluence behind an Apache Reverse Proxy on “HTTPS://”. Confluence runs on Tomcat which uses the “server.xml” for its basic settings. The following is a working example of the “server.xml” file when Confluence is running behind a secure (SSL/HTTPS) Apache Reverse Proxy.

This example assumes the hostname of this server is “”. Change it accordingly. For the Apache configurations, read this.


<Server port="8000" shutdown="SHUTDOWN" debug="0">
 <Service name="Tomcat-Standalone">
 <Connector port="8090" connectionTimeout="20000" redirectPort="8443"
 maxThreads="48" minSpareThreads="10"
 enableLookups="false" acceptCount="10" debug="0" URIEncoding="UTF-8"
 proxyName="" proxyPort="443" scheme="https"
 protocol="org.apache.coyote.http11.Http11NioProtocol" />

<Engine name="Standalone" defaultHost="localhost" debug="0">

<Host name="localhost" debug="0" appBase="webapps" unpackWARs="true" autoDeploy="false" startStopThreads="4">
 <Context path="" docBase="../confluence" debug="0" reloadable="false" useHttpOnly="true">
 <!-- Logger is deprecated in Tomcat 5.5. Logging configuration for Confluence is specified in confluence/WEB-INF/classes/ -->
 <Manager pathname="" />
 <Valve className="org.apache.catalina.valves.StuckThreadDetectionValve" threshold="60" />

<Context path="${confluence.context.path}/synchrony-proxy" docBase="../synchrony-proxy" debug="0" reloadable="false" useHttpOnly="true">
 <Valve className="org.apache.catalina.valves.StuckThreadDetectionValve" threshold="60" />



Leave a Reply

Your email address will not be published. Required fields are marked *