Uploaded image for project: 'Confluence Data Center'
  1. Confluence Data Center
  2. CONFSERVER-33020

PDF Export Retrieves Images From JIRA Macros via the Display URL and not the Application URL

      Steps to Reproduce

      1. Create an Application Link between Confluence and JIRA
      2. 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)
      3. Create a page and add a JIRA issue into the page
      4. 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

            [CONFSERVER-33020] PDF Export Retrieves Images From JIRA Macros via the Display URL and not the Application URL

            Atlassian Update - 11 April 2025

            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

            George Varghese added a comment - Atlassian Update - 11 April 2025 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

            Ciao Fabio

            Thanks for your suggestion; we already added as a workaround the display-server-name in the /etc/hosts, which lets us at least produce the pdfs – without the icons ...

            I will discuss this with our reverse proxy specialists ...

            BR Alexander

            L2 System Infrastructure added a comment - Ciao Fabio Thanks for your suggestion; we already added as a workaround the display-server-name in the /etc/hosts, which lets us at least produce the pdfs – without the icons ... I will discuss this with our reverse proxy specialists ... BR Alexander

            Hi Alexander,

            wainting for the fix, as workaround, I setup a rule on the server side so that each call to the disply URL will be redirected to the Application URL.

            Hope this helps,
            Fabio

            Fabio Racobaldo [Catworkx] added a comment - Hi Alexander, wainting for the fix, as workaround, I setup a rule on the server side so that each call to the disply URL will be redirected to the Application URL. Hope this helps, Fabio

            Hi ... is there any progress going on?

            We still have this problem here.

            BR Alexander

            L2 System Infrastructure added a comment - Hi ... is there any progress going on? We still have this problem here. BR Alexander

            We see this effect also on our testsystem which is on 5.7.

            This is issue is quite important for us

            Thanks for your effort.
            BR Alexander

            Alexander (Sascha) Pelzer added a comment - - edited We see this effect also on our testsystem which is on 5.7. This is issue is quite important for us Thanks for your effort. BR Alexander

            Affects also 5.6.6.

            Alexander (Sascha) Pelzer added a comment - Affects also 5.6.6.

            Any news?

            Is it a minor issue? Many our customers are affected by this issue. They CAN'T export pages, linked to JIRA issue, in PDF Format.
            It could be fixed just changing one line code. Isn't it?

            Thanks in advance,
            Fabio

            Fabio Racobaldo [Catworkx] added a comment - Is it a minor issue? Many our customers are affected by this issue. They CAN'T export pages, linked to JIRA issue, in PDF Format. It could be fixed just changing one line code. Isn't it? Thanks in advance, Fabio

              Unassigned Unassigned
              fsim Foo Sim (Inactive)
              Affected customers:
              15 This affects my team
              Watchers:
              21 Start watching this issue

                Created:
                Updated:
                Resolved: