mirror of
https://github.com/alexbelgium/hassio-addons.git
synced 2026-09-09 11:19:10 +02:00
48ac78c59d
* fix(filebrowser_quantum): repair direct access on port 8071 1.5.1.1 published the port but direct access still did not work, in two ways measured against a running instance: 1. The root redirect was absolute, so nginx built it from $server_port and sent the browser to :8072 — the container-internal port, not the published one. `absolute_redirect off` keeps the redirect relative. 2. The page served under /filebrowser_quantum/ referenced its assets under the app's own baseURL (the ingress entry path), which that vhost did not route: GET /api/hassio_ingress/<hash>/public/static/favicon.svg returned 404 while the same file under /filebrowser_quantum/ returned 200. The page loaded and every asset on it failed. Rather than translating paths, the vhost now passes requests through unchanged and redirects only the bare root to the app's baseURL, which is what its own links already point at. Asset, API and websocket URLs then work without any response rewriting. Ingress is untouched. * docs(filebrowser_quantum): describe the legacy redirects accurately The comments, CHANGELOG and README still said only the bare root was redirected, which stopped being true when the two /filebrowser_quantum compatibility redirects were added. Raised by CodeRabbit and Codex.