Hi,
I'm not a rules demon but I noticed that on p.63 of the WFS 1.0 spec that the 'service' parameter is mandatory for all WFS requests:
https://portal.opengeospatial.org/files/?artifact_id=7176
but I got no exception when I issued the following request, instead getting the full capabilities back:
http://myserver:myport/geoserver/wfs?request=GetCapabilities&
A bug?
Duncan Clarkson
Hi Duncan,
I have raised this question before as well. I don't believe its is a bug
as GeoServer does support the version parameter, just makes it optional.
However if following strict standards compliance you could make a case
for it.
I guess our position is that if we pass ogc cite tests then we must be
compliant.
-Justin
Duncan Clarkson wrote:
Hi,
I'm not a rules demon but I noticed that on p.63 of the WFS 1.0 spec
that the 'service' parameter is mandatory for all WFS requests:https://portal.opengeospatial.org/files/?artifact_id=7176
but I got no exception when I issued the following request, instead
getting the full capabilities back:http://myserver:myport/geoserver/wfs?request=GetCapabilities&
A bug?
Duncan Clarkson
-------------------------------------------------------------------------
Using Tomcat but need to do more? Need to support web services, security?
Get stuff done quickly with pre-integrated technology to make your job easier
Download IBM WebSphere Application Server v.1.0.1 based on Apache Geronimo
http://sel.as-us.falkag.net/sel?cmd=lnk&kid=120709&bid=263057&dat=121642
_______________________________________________
Geoserver-devel mailing list
Geoserver-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/geoserver-devel!DSPAM:1004,44e5cb18280581527717022!
--
Justin Deoliveira
The Open Planning Project
jdeolive@anonymised.com
It could be argued that the tests are deficient despite the fact OGC are certifying people on this basis. We had a similar problem with an in house WFS implementation and someone said "well, it passes the OGC tests" - unfortunately it seems this doesn't mean it complies with the written standard.
I think version is only optional if the request is GetCapabilities...?
Duncan
Justin Deoliveira wrote:
Hi Duncan,
I have raised this question before as well. I don't believe its is a bug
as GeoServer does support the version parameter, just makes it optional.
However if following strict standards compliance you could make a case
for it.I guess our position is that if we pass ogc cite tests then we must be
compliant.-Justin
Duncan Clarkson wrote:
Hi,
I'm not a rules demon but I noticed that on p.63 of the WFS 1.0 spec that the 'service' parameter is mandatory for all WFS requests:
https://portal.opengeospatial.org/files/?artifact_id=7176
but I got no exception when I issued the following request, instead getting the full capabilities back:
http://myserver:myport/geoserver/wfs?request=GetCapabilities&
A bug?
Duncan Clarkson
-------------------------------------------------------------------------
Using Tomcat but need to do more? Need to support web services, security?
Get stuff done quickly with pre-integrated technology to make your job easier
Download IBM WebSphere Application Server v.1.0.1 based on Apache Geronimo
http://sel.as-us.falkag.net/sel?cmd=lnk&kid=120709&bid=263057&dat=121642
_______________________________________________
Geoserver-devel mailing list
Geoserver-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/geoserver-devel!DSPAM:1004,44e5cb18280581527717022!
My interpretation is that if we were testing clients this is something you would test. But I don't think GeoServer needs to be raising nasty exceptions if the client isn't completely implementing and we can provide a reasonable default. It doesn't say in the spec that the server is required to raise an error if a client doesn't include all mandatory params - but it does say the server must raise an error in other situations.
I actually raised this on the next CITE tests, they have a test to test a mandatory param, it may even be the version, I forget. But I advocate as I do above, that if we're doing client tests then we should test it, a server shouldn't be tested to see if it raises errors. We'll see what the others say, and indeed I'm interested in feedback from the geoserver community. Should we be raising an exception there? It's obviously easy for us to fix. And we're helping define what cite tests should be, so we have a say in this.
Chris
Justin Deoliveira wrote:
Hi Duncan,
I have raised this question before as well. I don't believe its is a bug
as GeoServer does support the version parameter, just makes it optional.
However if following strict standards compliance you could make a case
for it.I guess our position is that if we pass ogc cite tests then we must be
compliant.-Justin
Duncan Clarkson wrote:
Hi,
I'm not a rules demon but I noticed that on p.63 of the WFS 1.0 spec that the 'service' parameter is mandatory for all WFS requests:
https://portal.opengeospatial.org/files/?artifact_id=7176
but I got no exception when I issued the following request, instead getting the full capabilities back:
http://myserver:myport/geoserver/wfs?request=GetCapabilities&
A bug?
Duncan Clarkson
-------------------------------------------------------------------------
Using Tomcat but need to do more? Need to support web services, security?
Get stuff done quickly with pre-integrated technology to make your job easier
Download IBM WebSphere Application Server v.1.0.1 based on Apache Geronimo
http://sel.as-us.falkag.net/sel?cmd=lnk&kid=120709&bid=263057&dat=121642
_______________________________________________
Geoserver-devel mailing list
Geoserver-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/geoserver-devel
--
Chris Holmes
The Open Planning Project
http://topp.openplans.org