Per comments from web api team, IIS will escape back slash and this is not configurable.
A temp solution with end to end test case is added with #415, refer to it for detail on how to enable , but back slash and slash is not recommended used in the key as Web API suggests, as there may become a security hole.
Also for permanent solution, it is tracked with #421 , key value will be as query options and refer to URL via key alias.
I close this issue now, any questions or comments, let us know.
With a path such as this: /service/Users('Some%5Cuser') a 404 is always returned. What is the best way to fix this or override the issue within Restier?
Build a service on a EF context with a table with string key
Ensure a record with key 'Some\user'
browse to /service/Users('Some%5Cuser')
Expect a return value.
This is due to a "by design" behavior of Web API OData. An explanation and a workaround is provided in this sample:
However, I'm unclear how to implement this in Restier.
The text was updated successfully, but these errors were encountered: