On Fri, May 3, 2013 at 4:32 PM, Michael Moore <[email protected]> wrote:
> On our Geoserver 2.2 installation even requests that I think should fail
> return "HTTP/1.1 200 OK".
>
> The XML that is returned is correct, but the HTTP response codes are
> always 200. Is this expected behavior, or do I have something
> mis-configured?
>
Expected behavior, you always get 200 no matter of the result.
OGC is in the process changing its mind and having the OGC services return
a mix of 40x and 50x depending on the error,
but only on specs that are based on OWS 2.0
As of now that pretty much means WCS 2.0 only, all other specs are still
based on OWS 1.1
So, when they do WMS 1.4 and WFS 2.1 they will start returning full HTTP
codes, but before that, it's 200
Cheers
Andrea
--
==
GeoServer training in Milan, 6th & 7th June 2013! Visit
http://geoserver.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
-------------------------------------------------------
------------------------------------------------------------------------------
Get 100% visibility into Java/.NET code with AppDynamics Lite
It's a free troubleshooting tool designed for production
Get down to code-level detail for bottlenecks, with <2% overhead.
Download for free and get started troubleshooting in minutes.
http://p.sf.net/sfu/appdyn_d2d_ap2
_______________________________________________
Geoserver-users mailing list
[email protected]
https://lists.sourceforge.net/lists/listinfo/geoserver-users
