Azure API Management Versioning: making Query Parameter scheme case insensitive

Question

Hello,

Apologies if this was asked before, my search yielded no results.

Our team is introducing versions to our APIs. If we introduce API versioning with the Query Parameter scheme, how do we make the version case insensitive?

Example:

In the example above, querying with the query string parameter 'preview' (lower case) instead of 'Preview' would result in 404 not found status code.

We tried transformation policies as described in Azure docs but that didn't help.

Any other ideas or is this just the way versioning was designed? Any help or pointing in the right direction would be greatly appreciated.

Answer 1

@RedasK AFAIK it is not possible and it matches with the exact query string (with case sensitive) but I will get the confirmation from my team and will update my answer.

Update:
As URL is case sensitive so it would not be possible. The policy will not help as APIM is the first one to handle the request and it returns the 404 as the URL is case sensitive.
There is already discussion in stack but not specifically related to APIM but discussion on related to URL case sensitive.