While the service provider should certainly fix their non-compliant capabilities doc, it is probably not the last time that someone will blindly switch http for https, with the increased prominence of projects like "HTTPS Everywhere", "Let's Encrypt" and so on in mind. It seems safe to me to catch the exception and then s/^https:/http:/ before re-throwing.
Even if you decide not to allow non-compliant namespaces it would be nice if GeoServer could report a meaningful error rather than a NullPointerException. :) Cheers, Kristian On Thu, Dec 07, Nuno Oliveira wrote: > It should be *http://www.w3.org/1999/xlink* and not > *https://www.w3.org/1999/xlink*. > > So I see two options: > > * make the remote server be compliant with WMS 1.1.1 > * make GeoServer capable of accepting this non compliant capabilities > document > > Regards, > > Nuno Oliveira ------------------------------------------------------------------------------ Check out the vibrant tech community on one of the world's most engaging tech sites, Slashdot.org! http://sdm.link/slashdot _______________________________________________ Geoserver-users mailing list Please make sure you read the following two resources before posting to this list: - Earning your support instead of buying it, but Ian Turton: http://www.ianturton.com/talks/foss4g.html#/ - The GeoServer user list posting guidelines: http://geoserver.org/comm/userlist-guidelines.html [email protected] https://lists.sourceforge.net/lists/listinfo/geoserver-users
