The new router in rc.1 breaks when a url parameter contains a forward slash

[fctucker]

Steps to reproduce and a minimal demo of the problem
Putting a slash in the url parameter causes the router and /or the page to break.

e.g. The following urls would not work when loading an angular2 app that uses @angular/router
localhost/home?some_param=someval/withaslash
or with matrix parameters
localhost/home;some_param=someval/withaslash

If the forward slash is escaped as %2f then it works fine. I remember this was an issue with the old router (now @angular/router-deprecated) but it was eventually fixed.

I have a workaround in place to escape the slashes, but it is hacky. It'd be nice if the new router could handle forward slashes in url or matrix parameters

Thanks!

[mhevery]

Thank you for submitting the issue. All issues require a plunker which demonstrates the problem and how to reproduce it. Please re-open the issue or create a new issue once you have a reproducible use case.

We are sorry that we are so aggressive on closing the issues. We are overwhelmed with the number of issues we get, and so we only have time to look at the ones which are easy for us to reproduce.

[vsavkin]

Fixed #9581

[Delagen]

@vsavkin not work. Error: Cannot match any routes:

[digeomel]

I'm having this issue with Angular Router 7.2.14.
In fact, even though the parameter is escaped (%2F), I get a 400 error.
Is this a regression?

[angular-automatic-lock-bot]

This issue has been automatically locked due to inactivity.
Please file a new issue if you are encountering a similar or related problem.

Read more about our automatic conversation locking policy.

_{This action has been performed automatically by a bot.}