Slash in route params values Cannot match any routes on refresh with HashLocationStrategy

[robwormald]

From @Delagen on June 16, 2016 8:9

simple url http://site.com/#/route;back=/a/b/c

Error: Cannot match any routes: 'route;back=true/a/b/c'

Copied from original issue: angular/vladivostok#59

[robwormald]

From @Delagen on June 16, 2016 8:10

Referece #8603 #8461

[robwormald]

From @zoechi on June 16, 2016 8:17

What's the purpose of this issue if there are 2 similar already? What router version are you using?
If your previous comment was meant to point out duplicates you could close the issue yourself.

[robwormald]

From @Delagen on June 16, 2016 8:25

3.0.0-alpha.6
Third iteration of router but still not usable in some cases, and solution not provided

[robwormald]

From @zoechi on June 16, 2016 8:53

Sorry, I missed that this is not the https://github.com/angular/angular repo

[vsavkin]

I tried to reproduce the issue using the latest release of the router, and it looks like the issue has been fixed. If you can still repro the issue, please provide a plunker.

[Delagen]

@vsavkin @robwormald Does not fixed

http://plnkr.co/edit/dR0oN3vXaIi0zKQkyibd

Click [crisis center] link and reload FRAME via browser context menu

platform-browser.umd.js:2311 Error: Uncaught (in promise): Error: Cannot match any routes: 'crisis-center;a=true/a/a/a/a'

[vsavkin]

@Delagen

If you are pasting the following into the browser location bar crisis-center;a=true/a/a, then the router will create the following segments:

• crisis-center;a=true
• a
• a

And, as a result, it won't be able to match any routes.

However, if you navigate to that url using the router API: router.navigate('crisis-center', {a: 'true/a/a/a/'});, then the router will escape the slashes.

This is a correct behavior. The router escapes the segments and the parameters when updating the URL bar, and unescapes them when parsing the URL. If you are constructing the URL yourself, it is your responsibility to escape it.

The escaping works properly in the latest build of the router (e.g., see this plunkr to see how it is set up http://plnkr.co/edit/0scjLRAd2voWTJ4giBhO?p=preview). It does not work properly in beta2.

[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.}