2 connectors with 2 different context paths?

[Dylan Perks]

We have a Confluence server running just fine, however, we need another connector with a different context path, but I have no idea how to do this?

Current connector

Path: /confluence

Port: 8090

Additional connector requirements

Path: /

Port: <any>

Any help would be appreciated.

[Dylan Perks]

I contacted Atlassian support and they reckon I can get what I want with mod_proxy and mod_rewrite

[Edwin Kyalangalilwa]

Hi Dylan,

This is done in server.xml

<install-dir>/conf/server.xml

There you can see an example of the different context paths for Confluence and Synchrony

<Context path="" docBase="../confluence" debug="0" reloadable="false" useHttpOnly="true"> 
      <Manager pathname=""/> 
      <Valve className="org.apache.catalina.valves.StuckThreadDetectionValve" threshold="60"/> </Context>

 <Context path="${confluence.context.path}/synchrony-proxy" docBase="../synchrony-proxy" debug="0" reloadable="false" useHttpOnly="true"> 
      <Valve className="org.apache.catalina.valves.StuckThreadDetectionValve" threshold="60"/> 
</Context>

[Dylan Perks]

I tried this, as well as tried creating an additional host.

<Context path="/confluence" docBase="../confluence" debug="0" reloadable="false" useHttpOnly="true"> <!-- Logger is deprecated in Tomcat 5.5. Logging configuration for Confluence is specified in confluence/WEB-INF/classes/log4j.properties --> <Manager pathname="" /> <Valve className="org.apache.catalina.valves.StuckThreadDetectionValve" threshold="60" /> </Context>
 <Context path="" docBase="../confluence" debug="0" reloadable="false" useHttpOnly="true"> <!-- Logger is deprecated in Tomcat 5.5. Logging configuration for Confluence is specified in confluence/WEB-INF/classes/log4j.properties --> <Manager pathname="" /> <Valve className="org.apache.catalina.valves.StuckThreadDetectionValve" threshold="60" /> </Context>
 <Context path="${confluence.context.path}/synchrony-proxy" docBase="../synchrony-proxy" debug="0" reloadable="false" useHttpOnly="true"> <Valve className="org.apache.catalina.valves.StuckThreadDetectionValve" threshold="60" /> </Context>

 This causes Tomcat to spit out 404 errors, regardless of what URL.

Duplicating the host, but with a different path, caused Tomcat to hang and become unstable.

[Edwin Kyalangalilwa]

What exactly are you trying to accomplish?

[Dylan Perks]

We need to access confluence from two paths:

https://hub.ultz.co.uk/confluence and https://docs.ultz.co.uk/

The latter is mainly for Scroll Viewport

[Dylan Perks]

Right now, we have the server.xml setup for https://hub.ultz.co.uk/confluence

[Edwin Kyalangalilwa]

This can be done by adding two xml files under

<install>/conf/Standalone/localhost

confluence.xml

<?xml version='1.0' encoding='utf-8'?>

<Context path="/confluence" docBase="../confluence" debug="0" reloadable="false" useHttpOnly="true">

    <Valve className="org.apache.catalina.valves.StuckThreadDetectionValve" threshold="60" />

</Context>

 ROOT.xml

<?xml version='1.0' encoding='utf-8'?>

<Context path="/" docBase="../confluence" debug="0" reloadable="false" useHttpOnly="true">

    <Valve className="org.apache.catalina.valves.StuckThreadDetectionValve" threshold="60" />

</Context>

I wouldn't recommend this because of issues that might occur.

So to understand correctly, users will access the default Confluence in /confluence and a Scroll Viewport version on / ?  

[Dylan Perks]

So to understand correctly, users will access the default Confluence in /confluence and a Scroll Viewport version on / ?  

Yep! Obviously different hostnames.

[Nic Brough -Adaptavist-]

Even with Scroll viewport, you are going to have some problems with this - Confluence only has one base url, which is what goes out on emails and what the system will take the users back to, no matter where they started browsing.