Andrea Aime wrote:
On Mon, Sep 22, 2014 at 1:25 PM, Ian Turton <ijturton@...403...> wrote:
from a quick check (sorry still jet lagged) I think everything up to GEOS-6647 will go in. GEOS-6651 is the only one that looks like a show stopper but I have no idea if any one is working on it.
Doh, GEOS-6651 is actually a user error, they changed the version of WMS without flipping the bbox coordinates, no wonder
it's not showing anything...
Right, and I made an elementary mistake by not checking that. Perhaps there is still something also on our side. Notice that the wrong axis order was hidden because &VERSION=1.3 sent a map. Actually almost anything in VERSION sends a map: "000", "0.00", "99.99". It needs to be something like "XYZ" before getting an error:
<ows:Exception exceptionCode="NoApplicableCode">
<ows:ExceptionText>java.util.IllegalFormatConversionException: d != java.lang.String
d != java.lang.String</ows:ExceptionText>
</ows:Exception>
</ows:ExceptionReport>
Perhaps we should send an error also for unsupported numeric WMS versions ? Excerpt from WMS 1.3.0 standard:
1) 7.3.3.1 VERSION
The mandatory VERSION parameter is defined in 6.9.1. The value “1.3.0” shall be used for GetMap requests that
comply with this International Standard.
2) An invalid GetMap request shall yield an error output in the requested Exceptions format (or a network protocol
error response in extreme cases).
-Jukka Rahkonen-