Re: [Geoserver-users] Is Geoserver 2.2 supposed to always return HTTP 200 for WFS requests?

[Michael M. <stu...@gm...>]

On Fri, May 3, 2013 at 9:55 AM, Andrea Aime <and...@ge...>wrote:

> On Fri, May 3, 2013 at 4:32 PM, Michael Moore <stu...@gm...>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
>

Thanks for the quick reply. It'll be nice when we can use the 40x and 50x
codes, but as long as things are working as intended, I guess that's good
enough for now.

--
Michael Moore