Bug Type
UI bug
Expected output, actual output, steps to recreate
Expected: all links should follow the same convention- relative or not, with a view to supporting deployment to subfolder (i.e., support reverse proxy, avoid "subfolder problem")
Actual: it seems the vast majority of links are already relative. All tools I tested in a deployment to {Host}/net-tools/ worked fine, stylesheets and JS appear to be working as well. However, links to the full /settings page and the logotype link at top left both result in sending the user back to the root of the domain {Host}/
Steps to recreate:
Prerequisite: Docker, reverse proxy (as in nginx, Caddy, etc.- in my case it's Caddy)
- Install networking-toolbox by documentation instructions for Docker
- Reverse proxy to networking-toolbox container from e.g. Caddy, something like:
handle_path /subdir/* { ... in the server block, with standard reverse_proxy $container_name:3000 { ... sending header_up X-Forwarded-Prefix /subdir
- Visit {Host}/subdir/ and click logotype link, click settings icon and view the full settings page
- End up with 404 at {Host}/settings and no effective means of returning to the main page of tools due to logotype linking to "/".
Hopefully this bug report is OK. It's my first time on Github. Maybe it would be better filed as feature request...
Thanks for the awesome work devs!
Additional Info
No response
Checklist
Bug Type
UI bug
Expected output, actual output, steps to recreate
Expected: all links should follow the same convention- relative or not, with a view to supporting deployment to subfolder (i.e., support reverse proxy, avoid "subfolder problem")
Actual: it seems the vast majority of links are already relative. All tools I tested in a deployment to {Host}/net-tools/ worked fine, stylesheets and JS appear to be working as well. However, links to the full /settings page and the logotype link at top left both result in sending the user back to the root of the domain {Host}/
Steps to recreate:
Prerequisite: Docker, reverse proxy (as in nginx, Caddy, etc.- in my case it's Caddy)
handle_path /subdir/* { ...in the server block, with standardreverse_proxy $container_name:3000 { ...sendingheader_up X-Forwarded-Prefix /subdirHopefully this bug report is OK. It's my first time on Github. Maybe it would be better filed as feature request...
Thanks for the awesome work devs!
Additional Info
No response
Checklist