we use 2 URLs for our Confluence: one is an internal which can be reached only from the company intranet, the other is an external which can be reached from everywhere.
We use version 4.2 Confluence.
The weird thing is that when we are on a page with the internal URL and we write a comment to the page, we push the Save button and the URL changes to the external URL! The Confluence doesn't logged us out, we are logged in henceforward. So it is not a blocking problem just a weird phenomenon.
What can be the cause?
Confluence only expects to run on one url and uses the "base url" to define it. It sounds like your base url is set to the external url, so Confluence is happily using it to generate the next url to go to after many actions.
There is no way to "fix" this inside Confluence, because it's not doing anything wrong. I'm not even sure you can fix this within your network - you could start messing around with Apache and rewriting urls (I'm out of my depth on that, I just know it can be done), but I really don't know how you'd get Apache (or any other web server) to detect when it should rewrite the internal/external url.
I don't know.
My best guess is that your network admins had set up something that was doing the rewrite for Confluence 3.5. The newer version of Confluence may have changed the url formats (noticably after completing actions?) so the old filters can't pick up the rewrites. But I really am guessing. On the 3.5 install in front of me, without any networky cleverness, I'm seeing exactly the behaviour you're getting on your 4.2 install, so I don't think it's Confluence at all.
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
We're bringing product updates and pro tips on teamwork to ten cities around the world.Save your spot