Marco, It's the WMS spec itself that requires 200 response codes. You can hack the code or even add a configuration option to return something other than 200, but you'll risk breaking your clients. Also note that checking for specific text is not going to work all the time, as the client can request an "inimage" exception text, i.e. returned as pixels in a png image.
-- thomas On Wed, Oct 19, 2016 at 9:03 AM deduikertjes <deduikert...@xs4all.nl> wrote: > Finding and modifying status codes > > I'd like to find out (and maybe modify) the HTML status codes mapserver > attaches to a WMS service exception report. > > I deploy mapserver behind Nginx with supervisord as a fastcgi provider and > process manager. Nginx does caching of responses on getmap requests. > > As I don't want Service Exception reports to be cached I've added a > directive to the Nginx config not to cache error documents containing > 'serviceException'. > This is not working properly, I think because nginx only regards a response > as an error when a non-200 status code is attached. > > So I'm trying to find the status codes mapserver attaches to a response. > If I do from command line mapserv7 > QUERY_STRING="map=my.map&SERVICE=WMS&VERSION=1.1.1&REQUEST=GetMap&....(rest > of valid wms request)" I see the headers (and the png) when te request > leads > to a response containing a map. > If I do the same with a request that generates an service exception report > I > get back error messages instead of the response I see in my browser. > > So, how to find out the headers of the response before it goes trough > supervisord an nginx? > Or does anyone know what status code the header contains? > And the million dollar question: can we stick a 500 status code header on > the response if it's not there? > > Any help greatly appreciated, MArco > > > > -- > View this message in context: > http://osgeo-org.1560.x6.nabble.com/Finding-and-modifying-status-codes-of-mapserver-responses-tp5291371.html > Sent from the Mapserver - User mailing list archive at Nabble.com. > _______________________________________________ > mapserver-users mailing list > mapserver-users@lists.osgeo.org > http://lists.osgeo.org/mailman/listinfo/mapserver-users
_______________________________________________ mapserver-users mailing list mapserver-users@lists.osgeo.org http://lists.osgeo.org/mailman/listinfo/mapserver-users
