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.
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).