|
I deployed GeoServer 2.2.4 for testing on a development server and noticed that the OWS service endpoint URLs are case sensitive for the 'request' parameter, at least for GetCapabilities requests.
URL: https://geoserverurl/geoserver/wms?request=getcapabilties
Error messages in GeoServer logs are similar to this:
013-02-05 20:37:49,425 ERROR [geoserver.ows] -
org.geoserver.platform.ServiceException: No such operation wms null getcapabilties
at org.geoserver.ows.Dispatcher.dispatch(Dispatcher.java:592)
at org.geoserver.ows.Dispatcher.handleRequestInternal(Dispatcher.java:263)
at org.springframework.web.servlet.mvc.AbstractController.handleRequest(AbstractController.java:153)
...
And the error message response:
<ServiceExceptionReport version="1.3.0" xsi:schemaLocation="http://www.opengis.net/ogc https://geoserverurl/geoserver/schemas/wms/1.3.0/exceptions_1_3_0.xsd"><ServiceException code="OperationNotSupported" locator="getcapabilties">
No such operation wms null getcapabilties
</ServiceException></ServiceExceptionReport>
Adding additional parameters results such as:
https://geoserverurl/geoserver/wms?request=getcapabilties&service=WMS&version=1.3.0
2013-02-05 20:41:23,494 ERROR [geoserver.ows] -
org.geoserver.platform.ServiceException: No such operation WMS 1.3.0 getcapabilties
at org.geoserver.ows.Dispatcher.dispatch(Dispatcher.java:592)
at org.geoserver.ows.Dispatcher.handleRequestInternal(Dispatcher.java:263)
at org.springframework.web.servlet.mvc.AbstractController.handleRequest(AbstractController.java:153)
<ServiceExceptionReport version="1.3.0" xsi:schemaLocation="http://www.opengis.net/ogc https://geoserverurl/geoserver/schemas/wms/1.3.0/exceptions_1_3_0.xsd"><ServiceException code="OperationNotSupported" locator="getcapabilties">
No such operation WMS 1.3.0 getcapabilties
</ServiceException></ServiceExceptionReport>
Using a URL with capitalization is successful, for ex: https://geoserverurl/geoserver/wms?request=GetCapabilties
Have not noticed this behavior in the previous GeoServer edition we've been using, 2.2.1.
Anyone else notice this? Or is this a new expected behavior?
|
