-
Notifications
You must be signed in to change notification settings - Fork 1.5k
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Router should use raw HTTP path for route matching #284
Comments
I just came here to open this same issue. It seems that |
EDIT: @weiwei-lin @DiegoZoracKy Btw, it doesn't make sence that named parameters should match |
Unfortunately, that only works if we only have encoded character in the last path component.
You are right. But my point was that
The whole point of doing URL escaping is because we don't want to treat the encoded characters as special characters. Using decoded path to perform routing defeats the whole purpose of URL escaping. |
I just updated #209 if it's helpful to you. I had to use a forked version with this change on a project due to the nature of the urls we had to deal with. |
Also here looking for this. Any chance this might be added? |
At the moment,
"/param1a%2fparam1b/tail"
matches route"head/:param1/:param2/tail"
instead of":param1/tail"
. There's no way we can have a'/'
in a URL param.The text was updated successfully, but these errors were encountered: