WMS GetCapabilities should return v1.3.0 by default

[dmorissette]

Reported by James Passmore:

I have just noticed that if you omit the optional version parameter in a GetCapabilities request, MapServer 5.6 returns a 1.1.1 GetCapabilities response whereas it should return a 1.3.0 GetCapabilities response.

See OGC 06-042 (available via ​http://www.opengeospatial.org/standards/wms)

Section 6.2.4 Version number negotiation:

...

All service metadata shall include a protocol version number and shall comply with the XML DTD or Schema defined for that version. In response to a GetCapabilities request (for which the VERSION parameter is optional) that does not specify a version number, the server shall respond with the highest version it supports. In response to a GetCapabilities request containing a version number that the server implements, the server shall send that version. If the server does not support the requested version, the server shall respond with output that conforms to a version it does support, as determined by the following rules: ...

[dmorissette]

Simple patch to return WMS 1.3.0 GetCapabilitites by default

[dmorissette]

Assefa, can I apply this patch (see attachment). Is there any reason why we should not return WMS 1.3.0 GetCapabilities by default?

[assefa]

No technical reason. I did hesitate at implementation time to do this change because most clients support only 1.1.1 and not 1.3.0

[tomkralidis]

We should be returning 1.3.0 as the latest supported version. Having said this, this will have to be revisited when we tackle #2531.

[dmorissette]

Thanks for the quick feedback. Fix committed in r9445. Will be in 5.6.0-beta4.

[tomkralidis]

Added test in r9446 for good measure.