Has anyone ever tried using an apache-based reverse proxy to support simple multi-homing using apache rewrite rules?

Apache HTTPD can pretty easily rewrite URLs so the whole point about it is about how many references are being embedded within request bodies and if/how to effectively rewrite those parts.

This is definitely a feature we can benefit from Atlassian implementing. We currently allow users to connect via DNS alias's to Confluence web GUI using any of the following URL methods: Server Hostname, Base URL, IP Address, DNS alias, as example.

Not properly supporting multi-homing is impacting my ability to integrate Confluence and JIRA.

I am running the recommended configuration with Confluence and JIRA behind Apache. Apache terminates SSL connectivity and proxies to non-SSL ports hosted by JIRA and Confluence in their Tomcat servers. These non-SSL Tomcat ports require special configuration of protocol and proxy URL in server.xml.

The base URL in JIRA and Confluence is set to the SSL URL terminated by Apache since that is what users use to access the applications. This works as expected.

I have been unsuccessful at getting Confluence and JIRA application links to work via the SSL proxy. I don't know if this is a problem with my configuration of server certificates within Tomcat or if it is a problem with the way Confluence and JIRA expect to communicate.

Therefore, I configured non-proxied, non-SSL connectors within both JIRA and Confluence that they can use for "backend" application links. This seems to work for everything except displaying JIRA gadgets within Confluence. The JIRA Issue Link macro works as expected, but the gadgets don't.

When I change the base URL in Confluence to match the non-SSL, non-proxied connector and access Confluence using that URL, the JIRA gadgets work as expected. This leads me to believe it is a multi-homing issue.

See https://support.atlassian.com/browse/CSP-112385 for more detailed information.

Hi,

we really need this functionality. We need have HTTP based access for internal network on simple hostname like "http://confluence" due to simplicity for end-users (all our servers using simple hostnames to access them). and we also need to have confluence accessible through public WAN without VPN, etc... on HTTPS like "https://confluence.company.com". Why we need it, is because we have active directory domain name like "office.comapny.com" so this domain name is also suffix in all DNS requests. But using something like "https://confluence.office.company.com" to access from internet is possible but it is stupid and long. Our CEO will ask my if I'm jerk if I think that he will write and remember this hostname to access confluence from different locations (like hotels, cafes, ...).

Applications which use "server base url" configuration are today out of the box. I think confluence should completely delete parameter "base url" from general settings and use URL which is sent in REQUEST_URL parameter from client to web server.

Thanks