How to make Odata request binding case insensitive

[brijeshb]

How do i make odata bind request json in a case insensitive manner? I really appreciated this feature in web api and now as i try toward better odata compatibility this feels like an unnecessary hindrance on my clients. (I'm currently using the latest release on .net core. If there does exist documentation about this, please direct me to it.)

[xuzhg]

@brijeshb Web API OData supports the basic Uri case insensitive. Would you please take a look this tutorial at http://odata.github.io/WebApi/#06-01-custom-url-parsing and let us know if there's anything missing for your scenario.

[brijeshb]

I mean making the actual request body binding case insensitive.
So i am aware that one can configure the builder to support either PascalCase or camelCase using builder.EnableLowerCamelCase(); and this affects both requests and responses.

But is there a way to make it case insensitive for the request binding?

So i want the model binding to treat all request bodies below as the same

{ EntityName: "" } { entityName: : ""} { entityname: "" }

[jimmy3912msncom]

I have a similar issue. I'm using Microsoft.AspNetCore.App 2.1.5 with Microsoft.AspNetCore.OData 7.0.1 and Microsoft.AspNetCore.OData.Versioning 3.0.0-beta1.

When making a POST request passing in a request body for the following model:

public class Model { public string FriendlyName { get; set; } }

if I pass { "friendlyName": "dog" } it works fine but if I pass { "FriendlyName": "dog" } then it doesn't get recognized in my ODataController method and gives me null. And to be clear, I have no issue with case sensitivity with the URL route. This issue is strictly with the request body binding.

Is there a way to make the body binding to the model case-insensitive? We have other ASP.NET Core applications not using OData and they handle case-insensitivity without issues which makes it simpler for our clients to adopt as most of them will likely send a request by doing default JSON.NET binding which to a C# POCO that will result in the case I mentioned above that doesn't work.

[brannmar]

Not sure this belongs here but i will give it a shot.

Do you guys have an update to this question? I am experiencing a similar issue where the methods cannot resolve updated properties in a Delta change. The model itself have the property with an uppercase letter in the beginning but with a JsonPropertyAttribute with a lowercase letter.

This will resolve:
{ "Title":"(PATCHED) Title" }

But not: (lowercase property name)
{ "title":"(PATCHED) Title" }

[Mankala]

Hi, I have a requirement where $filter should work where as any other case of filter i.e. $Filter $filTer $filteR should throw an error. How to achieve it?

[GreenEyedAndy]

Any progress here?
We have the same problem. All is working well GET, POST, DELETE but PATCH isn't working because of the different case sensitive handling.