-
Bug
-
Resolution: Unresolved
-
Low
-
None
-
7.2.6
-
7.02
-
4
-
Severity 2 - Major
-
0
-
Steps to Reproduce:
- Integrate JIRA with Apache following the guide:
- An example of server.xml
<Connector acceptCount="100" connectionTimeout="20000" disableUploadTimeout="true" enableLookups="false" maxHttpHeaderSize="8192" maxThreads="150" minSpareThreads="25" port="8766" protocol="HTTP/1.1" proxyName="testing.com" proxyPort="80" redirectPort="8443" useBodyEncodingForURI="true"/>
<Engine defaultHost="localhost" name="Catalina"> <Host appBase="webapps" autoDeploy="true" name="localhost" unpackWARs="true"> <Context docBase="${catalina.home}/atlassian-jira" path="/jira" reloadable="false" useHttpOnly="true">
- With the configuration on Apache Proxy side:
<VirtualHost *:80> ServerName testing.com <Proxy *> Order deny,allow Allow from all </Proxy> ProxyRequests Off ProxyPreserveHost On ProxyPass /jira http://localhost:8766/jira ProxyPassReverse /jira http://localhost:8766/jira </VirtualHost>
- Start JIRA and restart Apache.
- Access JIRA through http://localhost:8766/jira
Expected Result:
As mentioned in the documentation:
If the context path is other than empty or root , e.g. /jira , visiting JIRA via the proxy connector (e.g. http://jiraserver:8080/jira) should redirect you to the configured proxy (e.g. https://jira.atlassian.com/jira).
Accessing through the context path will redirect it to the FQDN.
Actual Result:
It will show as mentioned in the documentation where:
If the context path is empty or root , visiting JIRA via the proxy connector (e.g. http://jiraserver:8080/) should take you to JIRA with a warning:
- is related to
-
JRASERVER-60167 Connector redirect to proxy FQDN doesn't work in JIRA 7.1+
- Closed