[Galene] Re: Behind reverse proxy, not at the root

[Juliusz Chroboczek <jch@irif.fr>]

> I expected the URL to be:
>     http://127.0.0.1:8443/foo/mainpage.css
> And not:
>     http://127.0.0.1:8443/mainpage.css

I understand that's what you expected.  But that's not what the "proxyURL"
option does.

The "proxyURL" option informs Galene that URLs visible to the client are
different from the URLs visible to Galene.  It makes it possible to run
Galene behind a reverse proxy that rewrites request, for exemple by
remapping HTTPS to HTTP, by remapping an external host to localhost, or,
in your case, by remapping URLs.

Galene will not do any URL rewriting, that's the job of the reverse proxy.
Of course, I could implement URL rewriting in Galene itself, but since
reverse proxies already know how to do rewriting, I'd spending time doing
work that has already been done (probably much better and in a more
flexible manner) by reverse proxy developers.

So please configure your reverse proxy to rewrite URLs before they hit
Galene, or else explain to me why it's better to rewrite URLs in Galene
rather than in the reverse proxy.

-- Juliusz