Skip to content

Bug: Path matching fails when the URL contains encoded parts #1403

Open

Description

@root79662

Describe the bug

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

  1. self-assigned this
    on Dec 22, 2025
  2. Bafyn commented on Aug 20, 2026

    @Bafyn
    Contributor

    @StefH is this still relevant? Would it be expected not to unescape special-meaning chars?

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Metadata

Metadata

Assignees

Labels

bugSomething isn't working

Type

No type

Projects

No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions