This repository was archived by the owner on Dec 14, 2018. It is now read-only.
This repository was archived by the owner on Dec 14, 2018. It is now read-only.
Content negotiation does a case-sensitive matching of media type's parameter values #1429
Closed
Description
For a formatter having a supported media type like application/json;ver=v1, a request having accept header application/json;ver=v1 matches it but a media type like application/json;ver=V1 does not match (note the case of the parameter ver's value)...In Web API, this both these worked, i.e it considered both the name and values as case INsensitive..
From Http spec its not clear if parameter values are supposed to be case sensitive, so I am not sure which is the right behavior..