Hi,
I've just spotted a user trying to use 1.3.0 version in wms requests
and... geoserver does not complain at all.
This can be confusing imho, since in 1.3.0 the axis of bbox are
supposed to be lat/lon (as far as I remember the spec, just glanced
over it once).
Soo... shall we be more strict and throw an exception? That's what
we are supposed to do anyways. Afaik we're not even complaining
when a get capabilities with 1.3.0 version is issued, for example:
http://artois.openplans.org:8080/geoserver/wms?service=WMS&request=GetCapabilities&version=1.3.0
returns a capabilities document all right.
This is the opposite of what's happening with wfs. Note that being
strict has downsides as well, for example qgis cannot connect to
GeoServer because they are asking for version 1.1.1... I tried
to make them fix it, but they won't listen (mapserver accepts
version 1.1.1).
Anyways, I think I like the wfs behaviour better, if anyone is making
wms 1.3 requests fully following the wms 1.3 spec, he's up to a surprise and the issues he'll find are not easy to diagnose.
Opinions?
Cheers
Andrea
definitely throw an exception.
About qgis asking for version 1.1.1, isn't that just the one we're working
with? at least getcapabilities returns 1.1.1, guess I'm not quite getting
your concern
Gabriel
On Thursday 10 January 2008 10:47:04 am Andrea Aime wrote:
Hi,
I've just spotted a user trying to use 1.3.0 version in wms requests
and... geoserver does not complain at all.
This can be confusing imho, since in 1.3.0 the axis of bbox are
supposed to be lat/lon (as far as I remember the spec, just glanced
over it once).
Soo... shall we be more strict and throw an exception? That's what
we are supposed to do anyways. Afaik we're not even complaining
when a get capabilities with 1.3.0 version is issued, for example:
http://artois.openplans.org:8080/geoserver/wms?service=WMS&request=GetCapab
ilities&version=1.3.0 returns a capabilities document all right.
This is the opposite of what's happening with wfs. Note that being
strict has downsides as well, for example qgis cannot connect to
GeoServer because they are asking for version 1.1.1... I tried
to make them fix it, but they won't listen (mapserver accepts
version 1.1.1).
Anyways, I think I like the wfs behaviour better, if anyone is making
wms 1.3 requests fully following the wms 1.3 spec, he's up to a surprise
and the issues he'll find are not easy to diagnose.
Opinions?
Cheers
Andrea
-------------------------------------------------------------------------
Check out the new SourceForge.net Marketplace.
It's the best place to buy or sell services for
just about anything Open Source.
http://ad.doubleclick.net/clk;164216239;13503038;w?http://sf.net/marketplac
e _______________________________________________
Geoserver-devel mailing list
Geoserver-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/geoserver-devel
!DSPAM:4045,4785eb9a291021439371379!
Sorry, disregard the last message, in my understanding of the spec, its ok to
return a capabilities document for the higher version known to the server:
<quote>
Version number negotiation occurs as follows:
1) If the server implements the requested version number, the server shall
send that
version.
2a) If a version unknown to the server is requested, the server shall send the
highest
version less than the requested version.
2b) If the client request is for a version lower than any of those known to
the server, then
the server shall send the lowest version it knows.
3a) If the client does not understand the new version number sent by the
server, it may
either cease communicating with the server or send a new request with a new
version
number that the client does understand but which is less than that sent by the
server (if
the server had responded with a lower version).
3b) If the server had responded with a higher version (because the request was
for a
version lower than any known to the server), and the client does not
understand the
proposed higher version, then the client may send a new request with a version
number
higher than that sent by the server.
</quote>
On Thursday 10 January 2008 11:01:26 am Gabriel Roldán wrote:
definitely throw an exception.
About qgis asking for version 1.1.1, isn't that just the one we're working
with? at least getcapabilities returns 1.1.1, guess I'm not quite getting
your concern
Gabriel
On Thursday 10 January 2008 10:47:04 am Andrea Aime wrote:
> Hi,
> I've just spotted a user trying to use 1.3.0 version in wms requests
> and... geoserver does not complain at all.
> This can be confusing imho, since in 1.3.0 the axis of bbox are
> supposed to be lat/lon (as far as I remember the spec, just glanced
> over it once).
>
> Soo... shall we be more strict and throw an exception? That's what
> we are supposed to do anyways. Afaik we're not even complaining
> when a get capabilities with 1.3.0 version is issued, for example:
> http://artois.openplans.org:8080/geoserver/wms?service=WMS&request=GetCap
>ab ilities&version=1.3.0 returns a capabilities document all right.
>
> This is the opposite of what's happening with wfs. Note that being
> strict has downsides as well, for example qgis cannot connect to
> GeoServer because they are asking for version 1.1.1... I tried
> to make them fix it, but they won't listen (mapserver accepts
> version 1.1.1).
> Anyways, I think I like the wfs behaviour better, if anyone is making
> wms 1.3 requests fully following the wms 1.3 spec, he's up to a surprise
> and the issues he'll find are not easy to diagnose.
>
> Opinions?
> Cheers
> Andrea
>
> -------------------------------------------------------------------------
> Check out the new SourceForge.net Marketplace.
> It's the best place to buy or sell services for
> just about anything Open Source.
> http://ad.doubleclick.net/clk;164216239;13503038;w?http://sf.net/marketpl
>ac e _______________________________________________
> Geoserver-devel mailing list
> Geoserver-devel@lists.sourceforge.net
> https://lists.sourceforge.net/lists/listinfo/geoserver-devel
-------------------------------------------------------------------------
Check out the new SourceForge.net Marketplace.
It's the best place to buy or sell services for
just about anything Open Source.
http://ad.doubleclick.net/clk;164216239;13503038;w?http://sf.net/marketplac
e _______________________________________________
Geoserver-devel mailing list
Geoserver-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/geoserver-devel
!DSPAM:4045,4785ed05294631628642973!
Gabriel Roldán ha scritto:
definitely throw an exception.
About qgis asking for version 1.1.1, isn't that just the one we're working with? at least getcapabilities returns 1.1.1, guess I'm not quite getting your concern
I was talking about wfs, in particular, the qgis wfs client was asking explicitly for version 1.1.1 when issuing the wfs GetCapabilities request, last time I checked.
Afaik the only wms and wcs have a 1.1.1 spec.
Cheers
Andrea
Ahh... sorry, so I replied too fast before getting to the end of the message.
My bad.
Gabriel
On Thursday 10 January 2008 11:07:41 am Andrea Aime wrote:
Gabriel Roldán ha scritto:
> definitely throw an exception.
> About qgis asking for version 1.1.1, isn't that just the one we're
> working with? at least getcapabilities returns 1.1.1, guess I'm not quite
> getting your concern
I was talking about wfs, in particular, the qgis wfs client was asking
explicitly for version 1.1.1 when issuing the wfs GetCapabilities
request, last time I checked.
Afaik the only wms and wcs have a 1.1.1 spec.
Cheers
Andrea
!DSPAM:4045,4785ee72296278362916074!
Gabriel Roldán ha scritto:
Ahh... sorry, so I replied too fast before getting to the end of the message. My bad.
Gabriel
On Thursday 10 January 2008 11:07:41 am Andrea Aime wrote:
Gabriel Roldán ha scritto:
definitely throw an exception.
About qgis asking for version 1.1.1, isn't that just the one we're
working with? at least getcapabilities returns 1.1.1, guess I'm not quite
getting your concern
I was talking about wfs, in particular, the qgis wfs client was asking
explicitly for version 1.1.1 when issuing the wfs GetCapabilities
request, last time I checked.
My confusion too... I did not remember properly... qgis 0.9
does manage to do wfs capabilities request, it bombs after that in two ways thought:
* it does not use the namespace, so every request hitting a layer
on a non default namespace is bound to fail (geoserver will report
"layer not found")
* if the request works, qgis will read the describeFeatureType output
and state the layer is not valid... at least that's what's happening
on my localhost (which is using trunk)... if I connect it to
geo.openplans.org it actually works? Oh well, I have no time to investigate this now...
Cheers
Andrea