-
Notifications
You must be signed in to change notification settings - Fork 27
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
OGC service params should be case insensitive #366
Comments
@ansell suggested:
|
Fix for this is on docvalues branch. |
@adam-collins ive reverted the commits for case-insensitivity as they broke WMS |
@adam-collins @djtfmartin this issue is affecting us (see here), and I'd like to take a crack at fixing it. If I put together a PR, would it be possible for you to review, (and if you're happy with it) merge and release? |
Thanks @KeyboardSounds ! Yes that would be great. |
Tested on |
Re-opening until deployed to prod (done column) |
Closing historic issue. If this is still a problem, please reopen. |
Currently some OGC services (e.g. WMS tiles) require the OGC params to be provided in upper case. The problem is that recent versions of Leaflet send the various dynamic params in lower case by default and the tiles fail to load. There is an option in Leaflet to send params in upper case (
uppercase: true
) but this sends all params in upper case and then the ALA-defined params are ignored. E.g.LAT
andLON
are ignored, as they are required to sent in lowercase!The OGC spec says params should not be case sensitive:
http://cite.opengeospatial.org/OGCTestData/wms/1.1.1/spec/wms1.1.1.html#basic_elements.param_rules.order_and_case
The text was updated successfully, but these errors were encountered: