fix(router): accept trailing slash on iframe service paths #80

Merged

zaelgohary merged 1 commit from development_fix_router_trailing_slash into development

2026-04-30 11:32:05 +00:00

zaelgohary commented

2026-04-30 10:37:22 +00:00

Member

Summary

Iframe-served services were 404ing on cold loads because hero_router redirected /<svc>/<webname>/ to /<svc>/<webname> (no trailing slash). Browsers then resolved <script src="./app.js"> against the slashless URL — landing on /<svc>/app.js instead of /<svc>/<webname>/app.js — and got 404.

Closes #79

Changes

Drop the trailing-slash 301 redirect fallback (added in b4d1aa3).
Register /:service_name/:webname/ as an alias of /:service_name/:webname.

Test Results

cargo check + cargo fmt + cargo test all pass. Smoke: /hero_voice/ui/ now returns 200, /hero_voice/ui/app.js loads.

## Summary Iframe-served services were 404ing on cold loads because hero_router redirected `/<svc>/<webname>/` to `/<svc>/<webname>` (no trailing slash). Browsers then resolved `<script src="./app.js">` against the slashless URL — landing on `/<svc>/app.js` instead of `/<svc>/<webname>/app.js` — and got 404. ## Related Issue Closes #79 ## Changes - Drop the trailing-slash 301 redirect fallback (added in b4d1aa3). - Register `/:service_name/:webname/` as an alias of `/:service_name/:webname`. ## Test Results cargo check + cargo fmt + cargo test all pass. Smoke: /hero_voice/ui/ now returns 200, /hero_voice/ui/app.js loads.