Details
-
Bug
-
Resolution: Unresolved
-
Low
-
None
-
5.6, 5.7, 5.8, 5.9.7, 6.7.1
-
15
-
Severity 3 - Minor
-
3
-
Description
Steps to Reproduce
- Setup JIRA behind a reverse proxy, with an alternative access port
- Assume that http://localhost:8080/jira is the unproxied URL
- Assume that http://localhost/jira is the proxied address
- The base URL is set to the unproxied URL until after the application link is created
- Setup Confluence
- Create an application link to localhost:8080/jira
- Change JIRA's base URL to the proxied address
- In the application link configuration, change JIRA's display URL to the proxied address
- Communication will go from Confluence to JIRA over the unproxied port, but user facing links will use the display URL for hyperlinks.
- Insert a Two Dimensional Macro Chart Macro in Confluence
Expected Results
The links in the chart link to the proxied address
Actual Results
The links in the chart use the application URL instead. If that port is not accessible to users, this may result in links failing, or if the DNS does not resolve.
Workaround
Recreate the application link so it does not bypass the reverse proxy. This may require SSL certificates from each application to be added to the other application's trust store. This KB article explains how import the SSL certificates for each application involved in the application link.
Attachments
Issue Links
- is related to
-
CONFSERVER-38860 JIRA Report Change Log uses Application URL instead of Display URL
- Gathering Impact
-
CONFSERVER-43324 JIRA Chart Macro Two Dimensional Link Broken
- Gathering Impact
- relates to
-
CONFSERVER-38930 Some JIRA gadgets Do not Respect the Display URL
- Gathering Impact
- was cloned as
-
JRASERVER-68835 Jira should provide an API for querying data about its gadgets
- Gathering Interest