[Geoserver-devel] Version number leniency (and maybe too much of it)

GeoServer GeoServer Developer
1

Hi,
as you probably all know when we specify no version number in a request, we get back a response
matching the highest available version:

http://localhost:8080/geoserver/topp/ows?service=WFS&request=GetFeature&typeName=topp:tasmania_cities&maxFeatures=50

However, what would you expect from this:

http://localhost:8080/geoserver/topp/ows?service=WFS&request=GetFeature&typeName=topp:tasmania_cities&maxFeatures=50&version=10.0.0

Honestly, I would have expected a service exception, but GeoServer returns a response in version 2.0 instead.
Isn’t this a bit too much leniency?

Cheers
Andrea

–

==
Our support, Your Success! Visit http://opensdi.geo-solutions.it for more information.

Ing. Andrea Aime

@geowolf
Technical Lead

GeoSolutions S.A.S.
Via Poggio alle Viti 1187
55054 Massarosa (LU)
Italy
phone: +39 0584 962313
fax: +39 0584 1660272
mob: +39 339 8844549

http://www.geo-solutions.it
http://twitter.com/geosolutions_it

2

I think for capabilities requests this is actually something the specs require, that we respond with the highest version number that is less than or equal to the specified version, and there are tests that specify the version number 99.99.99 to test that. When implementing the dispatcher we chose to extend this flexibility to the other operations. Although for non-capabilities requests I think it would be ok to throw back an error from the spec point of view to throw an exception.

I would be ok with tightening this up but wouldn’t do it on a stable branch, as it technically a contract change to all of our published services.

$0.02

···

On Tue, Oct 15, 2013 at 8:10 AM, Andrea Aime <andrea.aime@anonymised.com> wrote:

Hi,
as you probably all know when we specify no version number in a request, we get back a response
matching the highest available version:

http://localhost:8080/geoserver/topp/ows?service=WFS&request=GetFeature&typeName=topp:tasmania_cities&maxFeatures=50

However, what would you expect from this:

http://localhost:8080/geoserver/topp/ows?service=WFS&request=GetFeature&typeName=topp:tasmania_cities&maxFeatures=50&version=10.0.0

Honestly, I would have expected a service exception, but GeoServer returns a response in version 2.0 instead.
Isn’t this a bit too much leniency?

Cheers
Andrea

–

==
Our support, Your Success! Visit http://opensdi.geo-solutions.it for more information.

Ing. Andrea Aime

@geowolf
Technical Lead

GeoSolutions S.A.S.
Via Poggio alle Viti 1187
55054 Massarosa (LU)
Italy
phone: +39 0584 962313
fax: +39 0584 1660272
mob: +39 339 8844549

http://www.geo-solutions.it
http://twitter.com/geosolutions_it

October Webinars: Code for Performance
Free Intel webinars can help you accelerate application performance.
Explore tips for MPI, OpenMP, advanced profiling, and more. Get the most from
the latest Intel processors and coprocessors. See abstracts and register >
http://pubads.g.doubleclick.net/gampad/clk?id=60135031&iu=/4140/ostg.clktrk

Geoserver-devel mailing list
Geoserver-devel@anonymised.comsts.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/geoserver-devel

–

Justin Deoliveira
Vice President, Engineering | Boundless
jdeolive@anonymised.com
@j_deolive

3

Our WMS 1.3.0 GetCapabilities document, depend on GetLegendGraphics filling in the highest available version.

We have not provided a WMS 1.3.0 GetLegendGraphics mapping, although we refer to GetLegendGraphics (perhaps without version number) in the GetCapabilities document.

···

On Tue, Oct 15, 2013 at 8:10 AM, Andrea Aime <andrea.aime@anonymised.com> wrote:

Hi,
as you probably all know when we specify no version number in a request, we get back a response
matching the highest available version:

http://localhost:8080/geoserver/topp/ows?service=WFS&request=GetFeature&typeName=topp:tasmania_cities&maxFeatures=50

However, what would you expect from this:

http://localhost:8080/geoserver/topp/ows?service=WFS&request=GetFeature&typeName=topp:tasmania_cities&maxFeatures=50&version=10.0.0

Honestly, I would have expected a service exception, but GeoServer returns a response in version 2.0 instead.
Isn’t this a bit too much leniency?

Cheers
Andrea

–

==
Our support, Your Success! Visit http://opensdi.geo-solutions.it for more information.

Ing. Andrea Aime

@geowolf
Technical Lead

GeoSolutions S.A.S.
Via Poggio alle Viti 1187
55054 Massarosa (LU)
Italy
phone: +39 0584 962313
fax: +39 0584 1660272
mob: +39 339 8844549

http://www.geo-solutions.it
http://twitter.com/geosolutions_it

October Webinars: Code for Performance
Free Intel webinars can help you accelerate application performance.
Explore tips for MPI, OpenMP, advanced profiling, and more. Get the most from
the latest Intel processors and coprocessors. See abstracts and register >
http://pubads.g.doubleclick.net/gampad/clk?id=60135031&iu=/4140/ostg.clktrk

Geoserver-devel mailing list
Geoserver-devel@anonymised.comsts.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/geoserver-devel

–

Justin Deoliveira
Vice President, Engineering | Boundless
jdeolive@anonymised.com
@j_deolive