Hm, this does not seem to fix the issue for me.

Btw, what is the easiest/best way to check this ? I manually copy/pasted your changes in my vendor folder now.

Now that it's merged, you can require~4.1@dev I think. Copy/pasting in vendor works also.
About your issue, without a reproducer, I'm can't to anything I'm afraid.
I think you have a route earlier in the list that takes precedence. Is it legit or not? I can't tell without having it :)

I don't know if is the same issue, but I have a problem with the route /{id}/

The route matches but the id parameter value is appended with the '/'.

For example /1/ . The id value should be "1" but i get "1/"

This problem began with version 4.1.8 and with this patch the problem remains.

any reproducer?

I've created a demo app to reproduce the issue. If you try to access /user/ or /admin/, you'll get the error while those routes are ok according to debug:router.

https://github.com/jimmycleuren/routing-issue

@jimmycleuren thanks understood, I'm on it (#29380 fixes it but is still not finished)