-
Bug
-
Resolution: Low Engagement
-
Low
-
None
-
5.3.4, 5.4.2, 5.4.3, 5.6.6
-
21
-
Severity 3 - Minor
-
0
-
Steps to Reproduce
- Create an Application Link between Confluence and JIRA
- Set the Display URL to a non-existent address, or to a proxy address that is reachable from the client's browser, but not accessible from the Confluence Server itself (the whole point of having an Application URL / Display URL separation)
- Create a page and add a JIRA issue into the page
- Export the page to PDF
You will notice Errors such as these:
2014-03-22 17:57:51,167 WARN [http-8542-1] [confluence.extra.flyingpdf.ConfluenceExportUserAgent] getImageResource Could not retrieve image resource http://192.168.2.3:8614/jira614/images/icons/statuses/open.png during Confluence export -- url: /c542/spaces/flyingpdf/pdfpageexport.action | page: 1933317 | userName: admin | referer: http://localhost:8542/c542/display/GIE/sa+dasd+as+d+assad | action: pdfpageexport
It seems that the getImageResource will attempt to obtain /images/icons/statuses/open.png via the Display URL, and not the Application URL. The Confluence Server is unable to reach the Display URL, hence, the error
Workaround
Set the Display URL to a URL that the Confluence Server is able to reach
- relates to
-
CONFSERVER-29142 Application Navigator uses Application URL instead of Display URL from Application Link
-
- Closed
-
- was cloned as
-
CONFCLOUD-54693 PDF Export Retrieves Images From JIRA Macros via the Display URL and not the Application URL
-
- Closed
-
Hi,
At Atlassian, our goal is to ensure we’re providing the best experience for our customers. With our new Data Center strategy, Atlassian's focus is on security, compliance, and performance and is a key driver in prioritizing bugs. Closing the bugs that do not fall into those categories will allow us to focus on the ones in the most current versions of our products.
This bug is being closed due to a lack of engagement in the last four years, including no new watchers, votes, or comments; this inactivity suggests a low impact.
Please note the comments on this thread are not being monitored.
You can read more about our bug fix policy here and how we prioritize bugs.
To learn more about our recent investments in Confluence Data Center, please check our public roadmap and dashboards containing recently resolved issues, current work, and future plans.
Kind regards,
Confluence Data Center