Too many redirect for Confluence behind IBM reverse proxy HTTPS - base url keep appending junction

Andrew_Zhao

Too many redirect and URL keep appending with Junction name

https://www.sample.com/confluence/confluence/confluence/...

Confluence is behind IBM reverse proxy with HTTPS

Base URL: https://www.sample.com/confluence

Reverse Proxy Junction Name: /confluence

Junction Type: TCP at port 8090 on Confluence backend server

Tomcat server.xml

<Connector port="8090" connectionTimeout="20000" redirectPort="8443"
maxThreads="48" minSpareThreads="10"
enableLookups="false" acceptCount="10" debug="0" URIEncoding="UTF-8"
protocol="org.apache.coyote.http11.Http11NioProtocol"
scheme="https" secure="true" proxyName="www.sample.com" proxyPort="443"/>

Fiddler log

1. /confluence

2. /login.action?os_destination=/confluence/

3. /confluence/dologin.action

4. /confluence/confluence/

5. /confluence/confluence/confluence

Message Noted: Looks like we lost your session.

Followup - after changing junction type to transparent and set context path to /confluence, the URL no longer appending. However browser page still keeps redirecting and refreshing.

<Context path="/confluence" docBase="../confluence" 

Daniel Eads

Hi Andrew,

Ok - looks like you've discovered from the reverse proxy guide (this one's Apache but the Confluence-side changes will still be the same) that the context path needs to be set in server.xml. Excellent. Just want to confirm you've restarted Confluence after adding that in.

Next up, the base URL in Confluence needs to be updated. This will be pretty straightfoward - it's going to be https://sample.com/confluence and can be set from the General Configuration page:

1. Choose the cog icon , then choose General Configuration under Confluence Administration
2. Choose General Configuration in the left-hand panel
3. Choose Edit
4. Enter the new URL in the Server Base URL text box
5. Choose Save

(this procedure and more info about the context path here)

I'd recommend doing a hard refresh the first time you load Confluence up after this to make sure your browser is getting "freshly" generated URLs from the Confluence server.

At this point if you're still seeing issues, it's probably not on the application side. I'm not familiar with websphere configurations but am happy to take a look at your configuration if you can paste the relevant bits if there's still trouble.

Cheers,
Daniel