You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
{{ message }}
Repository navigation
Bug: Path matching fails when the URL contains encoded parts #1403
It seems this issue is still there, also in ASP.NET Core? #178
When matching the url, escaped elements remain escaped, as expected (url/escapedchar%2Finpathsegment/restofurl
When matching the path, escaped elements are unescaped, as notexpected (url/escapedchar/inpathsegment/restofurl
This gives unconsistent behaviour when matching the url
Expected behavior:
Both path en url should not be unescaped before matching
Other related info
I found this issue, but it is not clear that this behaviour is still expected? #178
Activity
Bafyn commentedon Aug 20, 2026
@StefH is this still relevant? Would it be expected not to unescape special-meaning chars?