Forums

Articles
Create
cancel
Showing results for 
Search instead for 
Did you mean: 

Need clarification of Websockets and MOD_PROXY with Apache and SSL

ktaufner
I'm New Here
I'm New Here
Those new to the Atlassian Community have posted less than three times. Give them a warm welcome!
June 18, 2018

The configuration on the "Using Apache with MOD_PROXY" page is confusing...
Using_Apache_With_Mod_Proxy

RewriteEngine On
RewriteCond %{REQUEST_URI} !^/synchrony
RewriteRule ^/(.*) http://<domain>:8090/$1 [P]

It's in the section referring to when you're NOT using a context path of "confluence". Aka, when confluence IS the primary role of the server. In our case, our Confluence server is the host.

If I'm reading this right, you're putting in a RE-WRITE rule, to re-write the request URI if it does NOT include "/synchrony" on the end of the request, to go after the "http" (not SSL) pages, and then on top of that, append the "domain:port" to the request.

This makes _zero_ sense with Apache as a reverse proxy, terminating SSL.

You'd end up taking a URI such as:

https://confluence.atlassian.com/somepath

and turning it into

"http://confluence.atlassian.com:8090/somepath",

which the reverse proxy wouldn't be able to understand.

The rest of the config presented looks fine. Perhaps it's a vestige that came from a previous release? Or am I reading something wrong here?

Need clarification please.

0 answers

Suggest an answer

Log in or Sign up to answer
TAGS
AUG Leaders

Atlassian Community Events