Deki behind SSL loadbalancer/ reverse proxy

[ivan.zderadicka]

We try to deploy Deki behind load balancer/ rev.proxy which will terminate SSL encryption. So client will use https, but deki server will get http request.
Load balancer will add X-Forwarded-Proto: HTTPS header to request, which is kind of standard for these cases.
But we hit one issue there - the wiki links navigation tree contains absolute URLs which are reconstructed on by deki server, however these are absolute links are to http: protocol, not https, because server is not aware of https protocol and not ready to understand X-Forwarded-Proto header.
We have been looking into it and found that only working solution was to patch code PHP and Javascript on several places, because construction of absolute URL is done in several places.

I'm just wondering if somebody has experiences with such deployment scenario and if there is some more elegant solution (but ssl has to be terminated on loadbalancer).

[ivan.zderadicka]

Solution is easy, required just bit more search around.
Adding this line
SetEnvIf X-Forwarded-Proto "https" HTTPS=on
to Apache virtual host configuration solve the problem. Deki now renders all absolute links with https protocol.

[SteveB]

Thanks for posting the solution. Running the application behind a reverse-proxy is well supported since that's how we've deployed on our cloud infrastructure.