Re: [Geoserver-users] bad request

2017-04-13 Thread Stephen Crawford
, April 13, 2017 9:35 AM *To:* Stephen Crawford *Cc:* geoserver-users@lists.sourceforge.net *Subject:* Re: [Geoserver-users] bad request Hi, I'd look into what's around GeoServer, by itself GeoServer reports errors with a 200 and the details in a XML encoded ServiceException, this 400 doe

Re: [Geoserver-users] bad request

2017-04-13 Thread Chris Snider
Subject: Re: [Geoserver-users] bad request Hi, I'd look into what's around GeoServer, by itself GeoServer reports errors with a 200 and the details in a XML encoded ServiceException, this 400 does not seem like it would be coming from it (at least not directly) Cheers Andrea On Thu, Apr 1

Re: [Geoserver-users] bad request

2017-04-13 Thread Andrea Aime
Hi, I'd look into what's around GeoServer, by itself GeoServer reports errors with a 200 and the details in a XML encoded ServiceException, this 400 does not seem like it would be coming from it (at least not directly) Cheers Andrea On Thu, Apr 13, 2017 at 5:19 PM, Stephen Crawford wrote: > Hi

[Geoserver-users] bad request

2017-04-13 Thread Stephen Crawford
Hi All, I have an app that has been running for 8 or so years using a WFS request with a filter. Last week the request stopped working and returns a 400 BAD REQUEST. If I change the filter to then it works. We we running geoserver 2.5.5. The issue prompted us to finally upgrade to 2.11