Hey,

The Integrating JIRA with Apache using SSL documentation shows how to set up JIRA to run on https://localhost:8443/jira, whereas the default configuration is to run JIRA on http://localhost/ (the difference being the jira subdirectory). There's some conflicting documentation on this, as below:

Step 1 has the following:

ProxyPass           /jira       https://localhost:8443/jira
ProxyPassReverse    /jira       https://localhost:8443/jira

And in the alternative configuration:

ProxyPass              /jira       http://localhost:8080/jira
ProxyPassReverse       /jira       http://localhost:8080/jira

Whereas Configuring Apache Reverse Proxy Using the AJP Protocol has the following:

ProxyPass        / ajp://JIRA_HOST_NAME:AJP_CONNECTOR_PORT/
ProxyPassReverse / ajp://JIRA_HOST_NAME:AJP_CONNECTOR_PORT/

Integrating JIRA with Apache has both:

ProxyPass           /jira       http://localhost:8080/jira
ProxyPassReverse    /jira       http://localhost:8080/jira

and:

ProxyPass / http://localhost:8080/
ProxyPassReverse / http://localhost:8080/

The problem seems to be some varied differences between 3 pieces of documentation.

/jira will work if the following is set in server.xml, as per the example below. The problem is that the default server.xml has the path set to "".

<Context path="/jira" docBase="${catalina.home}/atlassian-jira" reloadable="false">

This is the default:

<Context path="" docBase="${catalina.home}/atlassian-jira" reloadable="false">

If the path value is not set to "/jira" and ProxyPass[Reverse] is directed to "/jira" it will cause errors. It also means the client needs to access their JIRA instance differently, as above.

I realise this is unsupported, however is there any chance the docs could be changed to either be / instead of /jira, (like the second example in Integrating JIRA with Apache docs) or include the server.xml changes as above?