You cannot iframe a ?????.atlassian.net site and have it work with modern browsers because of the X-Frame-Options HTTP header. It is set to only allow iframeing from the same origin. Most newer browsers will respect this HTTP header. It will work only OLD browsers though ... but then the site won't work.
Most people would reach for an iframe here, but that has the problem that it's going to pull in everything - header, footer and all the rest of the structure, and when people are asking for this, they usually mean that they only want the page. It also creates problems in that the server holding the iframe and the user reading the page have to have full and complete access to Confluence in order to render everything correctly, and things like proxies, rewrites and firewalls almost always get in the way.
The other way to do it is by having something on the other site that can understand Confluence data and re-render the pieces you need. This is complex - any system can fetch a Confluence page, via html or over REST, but it has to be coded to understand it. The html is hard to strip back to just the content that's come out. REST gives you the raw page, but then you need to understand how the macros and dynamic content are generated. Either way, it's not easy to do, and I'm not aware of anything that does it off-the-shelf.
This community is celebrating its one-year anniversary and Atlassian co-founder Mike Cannon-Brookes has all the feels.Read more
To anyone who doubts that Atlassians are a little too obsessed with collaboration, and tools related thereto, let me describe a recent discussion we had (which took place on our internal Confluence, ...
Connect with like-minded Atlassian users at free events near you!Find a group
Connect with like-minded Atlassian users at free events near you!
Unfortunately there are no AUG chapters near you at the moment.Start an AUG
You're one step closer to meeting fellow Atlassian users at your local meet up. Learn more about AUGs