We are changing our data collection to accept JSON documents that are case sensitive. It has been possible to send incorrect case and it was handled in our processing. JSON specifies that field names are case sensitive.
Here’s the definition of what we mean:
For field names, case is retained, and comparisons are case sensitive.
For field values, case is retained, and there is no change in the current behavior.
Making this change provides the following benefits:
Our implementation matches JSON case sensitivity expectations (JavaScript and JSON are case sensitive languages).
Our implementation matches the case sensitivity rules of many of the programming languages we support (C#, Java, C++, JavaScript, etc.).
Our implementation matches related technologies, like performance counter names in Windows, which are also case sensitive.
After this change, if applications POST data with incorrect casing of field names, the data will be rejected with a status code 400.
The .NET Services SDK implements the correct casing and we’re reviewing the current versions of the other Microsoft SDKs.
We are changing our data collection to accept JSON documents that are case sensitive. It has been possible to send incorrect case and it was handled in our processing. JSON specifies that field names are case sensitive.
Here’s the definition of what we mean:
Making this change provides the following benefits:
After this change, if applications POST data with incorrect casing of field names, the data will be rejected with a status code 400.
The .NET Services SDK implements the correct casing and we’re reviewing the current versions of the other Microsoft SDKs.