JIRA Documentation

JIRA 6.4 EAP
JIRA 6.0 Documentation
JIRA 5.2 Documentation
JIRA 5.1 Documentation
More...
 

 

Search the Knowledge Base and Documentation Spaces

You're visiting the JIRA Knowledge Base. Visit the JIRA Knowledge Base Home for an overview.

Skip to end of metadata
Go to start of metadata

The content on this page relates to platforms which are not supported for JIRA. Consequently, Atlassian cannot guarantee providing any support for it. Please be aware that this material is provided for your information only and using it is done so at your own risk.

Problem

On a JIRA instance using Apache Web Server, some links contain the actual host name and port the application is running on, rather than JIRA's configured Server Base URL. This can cause the links to be unreachable because of intervening firewalls or DNS resolution configurations as the BaseURL matches the VirtualHost alias of the presentation proxy.

For example, the base URL is

  • http://example.com/jira

but link URLs point to

  • http://tomcat01:8180/jira/

 

Cause

This is usually caused by the VirtualHost configuration section in Apache httpd does not specify the ProxyPreserveHost directive. This would instruct Apache to relay requests towards the internal server using the hostname provided by the client. This in turn will provide Tomcat with the correct DNS name for the ServletRequest.getServerName method used by JIRA to build URL links in the generated HTML response.

Solution

This JIRA documentation page configuring mod_proxy provides a working example of a configuration enabling the required ProxyPreserveHost directive.

1 Comment

  1. KY

    ProxyPerserveHost is wrongly spelled.

    It's ProxyPreserveHost. Please fix it. Thanks.