Problem: After migrating from FileMaker WebDirect to Klai Studio, old bookmarks such as /fmi/webd/portal?homeurl=... return an Express 404 before the SPA loads.
Workaround: Create a Klai page matching the legacy /fmi/webd/portal path (including support for the query string) and configure it to redirect users to /#/login. Alternatively, configure a custom error-page handler that routes unknown browser paths to /#/login while leaving API endpoints unaffected.
Thread Attachments
Original Slack Thread
User U057L133LV6: We migrated our portal from FileMaker WebDirect to Klai Studio. Our custom domain `<http://portal.nightwatchepilepsy.com|portal.nightwatchepilepsy.com>` now points to the Klai infrastructure (`<http://alias.bfoperations.com|alias.bfoperations.com>`).
Many existing users still have old WebDirect bookmarks such as:
`<https://portal.nightwatchepilepsy.com/fmi/webd/portal?homeurl=https://nightwatchepilepsy.com/>`
These currently return an Express 404 before the Klai SPA loads.
Can you configure a server-side 302 redirect for:
`/fmi/webd/*`
to:
`/#/login`
Ideally we would also like unknown browser routes to land at `/#/login` rather than returning the JSON/Express 404, provided that does not affect API endpoints.
User UBBJX2EHM: Interesting, well I will check and confirm but with out new SSR/SEO features you shoudl be able to create a page with that path ``/fmi/webd/portal?` and then add a redirect to /login
User UBBJX2EHM: You can alternatly add a custom error page handler for that too
User UBBJX2EHM: <@U057L133LV6>