Frontend doesn't use PathBase

[stefanloerwald]

Describe the bug

I have a reverse proxy (nginx) in front of baget that forwards requests to http://host/baget to the docker container. The docker container is configured with -e PathBase=/baget. In VS, download works fine, but the browser UI at http://host/baget fails to load correctly:

Static resources are not loaded correctly, but that can be fixed by forwarding requests with the referer http://host/baget to the docker container. However, links in the UI (e.g. Packages) at the top link to http://host, i.e. without the correct path. The API call that tries to fetch the list of packages also goes to http://host instead of http://host/baget.

To Reproduce

Steps to reproduce the behavior:

1. Set up reverse proxy, e.g. with nginx

server {
        listen 80;
        location /nuget/ {
            proxy_pass http://host.docker.internal:8080/; # assuming baget is reachable on this URI
        }
}

2. Browse http://localhost/nuget/ in a browser

[cispiroglu]

I have the same issue with traefik.

[LaplancheMaxime]

I have the same problem

[LaplancheMaxime]

hi @loic-sharma, BaGet scheduled to accept a basepath?

[xujintao]

Same problem. However, swagger works for href/src attribute of static file is relative, e.g. href="./swagger-ui.css". At the same time, pgadmin also works by setting extra http header, e.g. X-Script-Name.