WMTS client code automatically uppercases key names in KVP requests which breaks non standard servers
Description
Per this email on user list it seems cascading MapBox and other services that need a non standard key value (api-key) can't be bothered to handle upper case values.
To make life easier for them we should only uppercase Well Known Key values in the WMTS client.
Per this email on user list it seems cascading MapBox and other services that need a non standard key value (api-key) can't be bothered to handle upper case values.
To make life easier for them we should only uppercase Well Known Key values in the WMTS client.