How to route redirects?

[warmthsea]

I looked through the documentation and didn't find anything related to routing redirection.

I want to solve this problem by redirecting the router to the correct address:

• Algolia search brings me to 404 half the time vueuse/vueuse#4309 (comment)

https://github.com/vueuse/vueuse/blob/39274b09660de91a1090b07134476ef417a9a1db/packages/.vitepress/theme/index.ts#L17C3-L36C5

[brc-dd]

For that particular issue, I think the PWA plugin is causing issues. Netlify treats requests as case-insensitive and will do 301 redirect automatically if needed. The asset requests don't get redirected, but still are served correctly.

Algolia doesn't support case-sensitive URLs. So the URL is always lowercased like /core/usescrolllock/#usescrolllock. When you click that link, vitepress router intercepts it and fetches /assets/core_usescrolllock_index.md.[hash].js. The vitepress router doesn't care about case-sensitivity either for getting the hash, so the hash is correct. Now, I believe in certain cases, that request returns 404 because the file is actually /assets/core_useScrollLock_index.md.[hash].js. But in a normal Netlify site, both requests will return the same chunk. Here, I think the service worker is intercepting the request and maybe it's treating the request as case-sensitive.

/cc @userquin

[userquin]

I can confirm the problem is the PWA: the problem at vueuse is about using pascal instead kebap case, I'm going to send a fix later.

[brc-dd]

There could be a partial fix at vitepress side too. Because polka (server used in vitepress preview) is also case-sensitive. So, locally it doesn't work even without PWA. (Though using npx serve dist works.) Maybe the assets should always be in lowercase? So, the router always fetches the lowercased version, and the original file is always stored in lowercase.

Alternatively, maybe we could ship another meta similar to __VP_HASH_MAP__ that does the reverse mapping, and use it inside Algolia component or maybe at the router-level.

I'm more inclined towards the second approach.

[userquin]

There is no need, we can fix it adding urlManipulation to the sw precache options (since we're using custom service worker), otherwise (generateSW) we need some hack like this: https://github.com/vite-pwa/nuxt/pull/195/files (check the notes in the enableWorkboxPayloadQueryParams option)

NOTE: the hack is similar, not the same case, here we need to deal with ignore case, the linked pr is about url params.

[userquin]

Here the PR: vueuse/vueuse#4769

[warmthsea]

👍 👍