-
Notifications
You must be signed in to change notification settings - Fork 37
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
WMS parameter values should not be case sensitive #7
Comments
I am sorely tempted to close this as "complies with the standard" and suggest you file a bug report with either GeoServer or the OGC. :) But in the name of pragmatism I will reluctantly make the service and request parameter values case-insensitive. Note that this is not a general precedent. Other parameter values will be considered on case-by-case basis as requested but will most likely remain case-sensitive. |
(Or as my mother would put it: If Geoserver jumped off a cliff, would you?) :) |
Fixed in commit 8e33b20 |
hehe, thanks @SpacemanPaul I think this makes it better, even if it does break the rules. |
Description
Parameters values in this WMS implementation are case sensitive, and I don't think they should be.
The standard says:
So the implementation is technically correct...
But GeoServer, for example, is NOT case sensitive for most things, including parameter values, where it doesn't have to be.
What I Did
Try to get capabilities at ?service=wms&request=getcapabilities
Note that it only works with ?service=WMS&request=GetCapabilities.
The text was updated successfully, but these errors were encountered: