How to work with relative links in a site in a subpath (base)

[joesonw]

I have siteUrl set to something like http://example.com/abc, it'll always redirect to http://example.com/abc/, and it gives inconsistent link behaviours. Say if I have a href link to http://example.com/abc/123, it will actually go to http://example.com/abc/abc/123 in dev environment, and no such problem in built files.

So is there a way to remove trailing slashes? I tried to set every route to strict in enhanceApp, but it did not help.

[ElMassimo]

Hi Joe!

Didn't notice it the first time, but if your siteUrl is http://example.com/abc, so base will be /abc/.

If you use the href provided in usePage it should handle the base automatically for you.

Managing relative URLs in a site that is hosted in a sub-path is tricky, but now we can discard other causes, such as trailing slash.

---

Please check the prettyUrls setting, though it's enabled by default.

[ElMassimo]

Try running vite-plugin-inspect to see if the page file is modified in an unexpected way.

Feel free to provide a repo, or the page file that defines those routes.

[joesonw]

Try running vite-plugin-inspect to see if the page file is modified in an unexpected way.

Feel free to provide a repo, or the page file that defines those routes.

There were no changes. And by inspecting the elements, they urls are still http://example.com/abc/123, but once I click it, it goes to http://example.com/abc/abc/123

[ElMassimo]

Didn't notice it the first time, but if your siteUrl is http://example.com/abc, so base will be /abc/.

If you use the href provided in usePage it should handle the base automatically for you.

Managing relative URLs in a site that is hosted in a sub-path is tricky, but now we can discard other causes, such as trailing slash.

[joesonw]

Didn't notice it the first time, but if your siteUrl is http://example.com/abc, so base will be /abc/.

If you use the href provided in usePage it should handle the base automatically for you.

Managing relative URLs in a site that is hosted in a sub-path is tricky, but now we can discard other causes, such as trailing slash.

Yeah, I did get the href part through some other way. But like I said, a link of http://example.com/abc/123 will actually go to http://example.com/abc/abc/123. But if you open it in a new tab, then no problem. There is definitely something going on with the router, I just don't know what.

[ElMassimo]

In development vue-router is configured to use provided base.

It could be that this script, meant to provide client-side navigation during development is not taking the base into account?