Hi Jakub,
I can't replicate this myself making requests for GetCapabilities
documents. What was the version "number" you were using? Or was it for a
different request type?
On an old 2.7 instance, the following bring back an exception document
of type NoApplicableCode containing the following:
<ows:ExceptionText>java.util.IllegalFormatConversionException: d !=
java.lang.String
d != java.lang.String</ows:ExceptionText>
version:
a
a.1
the following work (returning a 1.1.1 getcap):
a.a.1
1.a.a
a.a.a
So for me at least it only gives the exception if it's not three characters.
I did notice one extremely trivial bug during this though. If the
version negotiation is triggered, the resultant xml file is always
called getcapabilies_1.3.0.xml, even if the contents are 1.1.1.
I think we can skip a JIRA on that one. :-)
Cheers,
Jonathan
On 23/11/2016 08:21, Jakub Balhar wrote:
Hello,
I ran into an issue with the WMS service in GeoServer. If I try to
send the incorrect version such as something else than valid numbers,
the returned Exception contains the details of the Java exception.
Is it possible to change that behaviour to returning something like
Incorrect version number?
Example URL:
geoserver/ows?service=WMS&version=%27&request=GetCapabilities
--
Best regards,
Jakub Balhar
------------------------------------------------------------------------------
_______________________________________________
Geoserver-users mailing list
[email protected]
https://lists.sourceforge.net/lists/listinfo/geoserver-users
------------------------------------------------------------------------------
_______________________________________________
Geoserver-users mailing list
[email protected]
https://lists.sourceforge.net/lists/listinfo/geoserver-users
