mirror of
https://github.com/wiremock/WireMock.Net.git
synced 2026-01-11 22:30:41 +01:00
Request Path and query parameter keys are case-sensitive #164
Reference in New Issue
Block a user
Delete Branch "%!s()"
Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?
Originally created by @simardst on GitHub (Mar 6, 2019).
In many cases, the casing of the request path and the querystring keys (not the values) is not important. It would be very usefull to:
This could be a global settings or configurable for each request (whatever is the simplest way to implement it).
@StefH commented on GitHub (Mar 6, 2019):
For path , you should be able to use:
@simardst commented on GitHub (Mar 6, 2019):
Thank you, but achieving the same for the querystring keys is far more complex. I achieved to create an extension for the path, but didn't find any way to do the same with the querystring keys.
@StefH commented on GitHub (Mar 6, 2019):
Cookies and Headers do support this logic.
But I think indeed that querystring does not support this.
I will take a look at the code to ser if I can add logic.
@StefH commented on GitHub (Mar 7, 2019):
I've updated the code and new NuGet is available on MyGet (https://github.com/WireMock-Net/WireMock.Net/wiki/MyGet-preview-versions)
WireMock.Net.1.0.8-ci-11023
Use it like:
Will match:
http://localhost/param?key=testand
http://localhost/param?kEY=test@StefH commented on GitHub (Mar 8, 2019):
@simardst does this work for you?
@simardst commented on GitHub (Mar 8, 2019):
This seems to resolve our issues, and I will test it using your preview version by the end of the day.
Thank you very much.
@StefH commented on GitHub (Mar 8, 2019):
You're welcome.
If you have tested and all is working as expected, I'll merge this code to master and create a new official nuget.
@simardst commented on GitHub (Mar 8, 2019):
I, ve done few tests. This works perfectly!
I will update as soon as it is available.
@StefH commented on GitHub (Mar 9, 2019):
So all is tested and I can merge and create a new official NuGet?
@simardst commented on GitHub (Mar 11, 2019):
As far as I'm concerned, yes you can proceed.
@StefH commented on GitHub (Mar 12, 2019):
A new NuGet will be released soon.