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

Open
opened 2025-12-29 08:33:09 +01:00 by adam · 0 comments
Owner

Originally created by @root79662 on GitHub (Dec 22, 2025).

Originally assigned to: @StefH on GitHub.

Describe the bug

It seems this issue is still there, also in ASP.NET Core?
https://github.com/wiremock/WireMock.Net/issues/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

I found this issue, but it is not clear that this behaviour is still expected?
https://github.com/wiremock/WireMock.Net/issues/178

Originally created by @root79662 on GitHub (Dec 22, 2025). Originally assigned to: @StefH on GitHub. ### Describe the bug It seems this issue is still there, also in ASP.NET Core? https://github.com/wiremock/WireMock.Net/issues/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? https://github.com/wiremock/WireMock.Net/issues/178
adam added the bug label 2025-12-29 08:33:09 +01:00
Sign in to join this conversation.
1 Participants
Notifications
Due Date
No due date set.
Dependencies

No dependencies set.

Reference: starred/WireMock.Net#736