Landing page /hero_cockpit/web/ uses root-relative links — break when served behind a path-prefix gateway #7
Loading…
Add table
Add a link
Reference in a new issue
No description provided.
Delete branch "%!s()"
Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?
The cockpit landing page at
/hero_cockpit/web/renders:These are root-relative paths. When the cockpit is served behind a path-prefix gateway (TFGrid Web Gateway, hero_router, reverse proxies in general), the gateway adds the prefix
/hero_cockpit/web/to all served pages. Root-relative links bypass that prefix and 404.Live repro at s158 admin VM:
https://hcockpit.gent01.qa.grid.tf/hero_cockpit/web/shows the landing page; clicking the/serviceslink goes tohttps://hcockpit.gent01.qa.grid.tf/serviceswhich is 404. The real services dashboard lives athttps://hcockpit.gent01.qa.grid.tf/hero_cockpit/web/services(HTTP 200, 188 KB).This makes the landing page actively misleading for any tester. Strangers click the link, get 404, conclude Hero OS doesn't work.
Fix: use path-relative links (
servicesinstead of/services) OR include the prefix dynamically (read X-Forwarded-Prefix per thehero_webreverse-proxy skill convention).This is the primary blocker for a stranger self-serving from a public URL hand-off.
Closed by hero_cockpit
bac28da— landing page is now an Askama template extendingbase.htmlwithbase_path|safe-prefixed links. Direct-push squash todevelopmentdid not auto-close (Forgejo only auto-closes on PR merge events). Verified clean on a fresh build.