fix(ui): resolve path issues when served behind hero_router #14
No reviewers
Labels
No labels
prio_critical
prio_low
type_bug
type_contact
type_issue
type_lead
type_question
type_story
type_task
No milestone
No project
No assignees
2 participants
Notifications
Due date
No due date set.
Dependencies
No dependencies set.
Reference
lhumina_code/hero_voice!14
Loading…
Add table
Add a link
Reference in a new issue
No description provided.
Delete branch "development_fix_ui_path_resolution"
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?
Summary
X-Forwarded-Prefixheader and<meta name="base-path">tag injection/rpcproxy route to the UI Axum serverRelated Issue
Closes #10
Changes
BasePathstruct, updated middleware to extractX-Forwarded-Prefix, added/rpcroute withrpc_handler, modifiedserve_staticto inject base-path meta tag intoindex.htmlBASEconstant derived from meta tag with pathname fallback, prefixed all URL references (RPC, WebSocket, audio files, transforms) withBASE./app.jsfor explicit relative resolution, added base-path reading to inline health-check script, prefixedfetch()calls with base pathTest Results
fix(ui): resolve path issues when served behind hero_routerto WIP: fix(ui): resolve path issues when served behind hero_routerb4fae2b502c376ad400cc376ad400c033824d61d1072af1f30242cb89c91WIP: fix(ui): resolve path issues when served behind hero_routerto fix(ui): resolve path issues when served behind hero_routerTested, working when I opened hero voice UI from hero router