I guess I've found a minor - but yet annoying - bug in Confluence. The use case is the following:
What happens is that the copied page refer to the absolute url of the original image. You can see in your browser debugger requests to http://oldhostname/confluence...
For me, the bug is that Confluence does not recognize its own resources when copying a page, and refer to them with an absolute url. That leads to inconsistencies when for example, you migrate your content from an instance to another, or put a backup of production data in your integration environment. Request are still made to the production host.
Keep using the old DNS alias, pointing to the new physical host, helps only if the copied pages have no access restrictions. It there is, then the image fails to load (you take a redirect), since you need to authenticate under http://oldhostname to access it.
A request like "UPDATE BODYCONTENT SET BODY = REPLACE(BODY, ', ' WHERE BODY LIKE '%http://oldhostname%'" + a reindex seems to fix the issue, but hum... nobody knows if it does not corrupt the content (ie. do we really want to change the old host in every occurences?) and I don't feel comfortable running it...
Is it already known, or should I open a bug report somewhere ?
Two vulnerabilities have been published for Confluence Server and Data Center recently: March 20, 2019 CVE-2019-3395 / CVE-2019-3396 April 17, 2019 CVE-2019-3398 The goal of this article is...
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