Think I am having this problem. Has anyone been able to make this work recently?

I am not allowed to purchase plugins for a big "On-Prem" instance of Confluence.  Why would Atlassian recommend (or allow) a 3rd party plugin (especially at an additional cost) be the fix to their bug???  

Here is my scenario:

1) I am on an "On-Prem" instance of Confluence. The URL is something like:

    (Note this on machine 1)

    https://machine1.big.researchdomain.net/display/myproject/

2) I have a page on this Confluence instance called "InformationPage" so the full URL is:

    (Note this on machine 1)

    https://machine1.big.researchdomain.net/display/myproject/InformationPage

3) Also on the network is separate web server hosting a separate webpage (under another co-teams control):

    (Note this on machine 2)

    https://machine2.big.researchdomain.net/different-page-I-want-to-display-in-confluence.html

4) On this "different-page-I-want-to-display-in-confluence.html" page, there are some referenced URL's:

    (Note they are all also hosted on machine 2 - the same separate web server under another co-teams control)

    https://machine2.big.researchdomain.net/infopageA.html

    https://machine2.big.researchdomain.net/infopageB.html

    https://machine2.big.researchdomain.net/infopageC.html

5) I was able to get the "HTML Macro" and the "HTML Include Macro" working

6) I was able to get this URL of the other server (machine 2 - https://machine2.big.researchdomain.net ) added to the allowlist of trusted URLs in Confluence (again on machine 1).

7) When I add a "HTML Macro" OR "HTML Include Macro" to my Confluence page it works! (but wait for it)

    (again my Confluence page on machine 1)

    https://machine1.big.researchdomain.net/display/myproject/InformationPage

    (the page from machine 2... that is now being displayed on my Confluence page on machine 1)

    https://machine2.big.researchdomain.net/different-page-I-want-to-display-in-confluence.html

    (now all the URL's on that page are being rewritten)
    (Note they are all pointing to machine 1 and not machine 2 like they are supposed to... see #4 above)

    https://machine1.big.researchdomain.net/infopageA.html

    https://machine1.big.researchdomain.net/infopageB.html

    https://machine1.big.researchdomain.net/infopageC.html

Lastly, this is a single very simple example of a much bigger problem for me. My actual problems are more complicated (but same principle). Other problems include:

• pages that call other dynamic javascripts and web service URLs to build pages that when displayed via Confluence do not work due to rewriting.
• pages that display, but the data that feeds the page is via another service call (so no data ever arrives).
• pages that display, but the formatting (CSS, etc.) that is needed is never called therefore the page is not readable (as it never formatted).

HELP!!!!

Seconding... now that Portfolio is actually usable, I can't post a link to it in Confluence, I guess because it's a relative link.  Yes, I've had the admin turn on the macro and white list the site.

Wow... get your apps to talk to each other.

>  mean does Atlassian reject ANY feature request, that already provided by ANY 3rd party software complient with Atlassian product?

Historically (and I mean many years ago) the theory was no, Atlassian would not stomp over an existing app with a duplicate of the functionality, and if they wanted it badly enough (flash workflow editor, Valiantys SLA), then they'd buy the app.  Of late, it seems like there has been a sea change, where even a pre-existing non-trivial solution such as Enterprise Mail Queue for Jira that's been around for 5years providing Email Digesting functionality in Jira as a solution to JRA-1369 suddenly becomes the target of a new feature Email Digesting coming soon in Jira8.  Nobody contact us!  Apparently, after we reached out,, the person leading that feature saw no conflict between EMQ Email Digester and Jira Email Digesting.  I can't tell if this is a deliberate change in policy or an exceptionally poorly handled fit-gap analysis by Atlassian staff.

CHTMLIR was written to solve my own problems, integrating local net web server CGI output, it was great!   Commercially, sure, its not a killer app, its a point solution, don't be grumpy, be happy someone bothered to solve a problem, support them even!  Maybe if you have a related problem such a smaller company will be agile enough to actually do something to help you.

Is an issue resolution a result of official Atlassian policy?

I mean does Atlassian reject ANY feature request, that already provided by ANY 3rd party software complient with Atlassian product?

If it is not I think it would be nice enough to motivate your rejection.