Reverse Proxy and folder

[ben-64]

Hello,

I would like to run shaarli behind a reverse proxy (I am using the Shaarli docker image). My reverse proxy configuration is the following:

server {
        listen 443 ssl;
...
        location /folder/ {
                proxy_set_header  X-Real-IP         $remote_addr;
                proxy_set_header  X-Forwarded-For   $proxy_add_x_forwarded_for;
                proxy_set_header  X-Forwarded-Proto $scheme;
                proxy_set_header  X-Forwarded-Host  $host;

                # pass requests to the proxied host
                proxy_pass http://shaarli/;
                proxy_set_header Host  $host;
                proxy_connect_timeout  30s;
                proxy_read_timeout     120s;
        }

So a very basic configuration I would say.
Due to the fact that shaarli is requested on /, it generates URL without the folder part for web browser. Therefore they are requesting files without this folder, and of course it fails.

According to that issue, it is a normal behaviour. It would be very easy to bypass this limitation with this pull request. I am using it since multiple weeks and it works perfectly.

What is the correct configuration to use at nginx level or shaarli level to run behind a reverse proxy ?

Thank you in advance,

[ArthurHoaro]

Hi, thank you for your detailed report.

I booted up a quick EC2 instance and was able to reproduce your issue. I tried to play with nginx config and proxy headers but @virtualtam was right in the issue you linked and there is no easy way to pass the proxy location into the container's request path without changing the configuration inside our Docker image.

I will take some time to have a more in-depth look at your previous PR and find a solution to handle this at the project's configuration level without introducing breaking changes to other configurations.

[miltosc]

Hello, wish for that feature too. Hope you will manage make it work...