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

[Francis Bolduc <fbolduc@gmail.com>]

If you recall my original email, I did not ask for URL rewriting.

What I would like to do is to host Galene in a directory, so that it
would look like this from the client side:
    GET https://myhost.com/foo/index.html
    GET https://myhost.com/foo/mainpage.css
    GET https://myhost.com/foo/galene.css
    GET https://myhost.com/foo/mainpage.js
    GET https://myhost.com/foo/common.css

As you suggested, I did configure my reverse proxy so that Galene gets
modified HTTP GET requests with the "/foo/" directory removed. I
thought that was weird, as the other applications I use on the same
host such as filebrowser.org and forge-vtt.com do not require such
fiddling with the HTTP requests. But I gave it a try anyway.

And that did not work because Galene seems to return the same content
without any modification to any path no matter what I configure in the
proxyURL field.

I don't know of any reverse proxy that can inspect the backend HTML
outputted by Galene, rewrite the paths to add the "/foo/" directory,
and then send the modified HTML to the client from the frontend. And I
doubt this is even possible considering Javascript is involved.

Or am I missing something?

Regards,
Francis