This behavior is intended for regular params like :param because the / is a delimiter of params, but it should probably not happen for star params (:param(.*))

Note to myself in edit comment

Hey, thanks for the reply. Hopefully one day I can contribute a bug fix PR myself. For now, is there any workaround that you can suggest while I wait for the official fix?

Hi, is there any update to this?
Perhaps point me to the correct place where this bug occurs so I can attempt to tackle the issue?

Here's a workaround that we/I've come up with - it's not perfect as it's applied to the whole path, so we enable it only for routes with meta.patchCleanPath === true but it works well enough for us for now (although we obviously would like to see an upstream fix, so we can get rid of this):

import { RouteLocation, RouteLocationNormalizedLoaded, RouteLocationRaw, Router } from 'vue-router'

export const patchRouter = (router: Router) => {
  const cleanPath = (route) =>
    [
      ['%2F', '/'],
      ['//', '/']
    ].reduce((path, rule) => path.replaceAll(rule[0], rule[1]), route || '')

  const bindResolve = router.resolve.bind(router)
  router.resolve = (
    raw: RouteLocationRaw,
    currentLocation?: RouteLocationNormalizedLoaded
  ): RouteLocation & {
    href: string
  } => {
    const resolved = bindResolve(raw, currentLocation)
    if (resolved.meta?.patchCleanPath !== true) {
      return resolved
    }

    return {
      ...resolved,
      href: cleanPath(resolved.href),
      path: cleanPath(resolved.path),
      fullPath: cleanPath(resolved.fullPath)
    }
  }

  const routerMethodFactory = (method) => (to) => {
    const resolved = router.resolve(to)
    if (resolved.meta?.patchCleanPath !== true) {
      return method(to)
    }

    return method({
      path: cleanPath(resolved.fullPath),
      query: resolved.query
    })
  }

  router.push = routerMethodFactory(router.push.bind(router))
  router.replace = routerMethodFactory(router.replace.bind(router))

  return router
}

Hey, thanks for your patch. Will try it out. It is very appreciated.

If you find any edge cases that don't work, I'm happy to hear.

Your patch works. Good enough for us to ship the site for now. Thank you so much @dschmidt.

@posva Is there any plans to fix this behavior? I think that bef97d6 is what caused the regression, since I used to be able to do things like redirecting to error pages without mangling the URL.

Same issue, it seems it doesn't happen when you use something like :category(.*)* but the problem is the catch all is greedy and causes issue because then the following /:category(.*?)*/(page/:page(\d+))? will never have page matched, it will go into category (which I think is also a behavior that should be changed or allow a second modifier token in the parser (like :category(.*?)*?to indicate non greediness)