I have some feedback from those in the know at OGC... OWS is not a RESTful interface, so its not really bound by these considerations. A RESTful version of OWS is something that is under consderation - with active debate about it. In a way, these findings seem to settle the argument about whether OWS can be considered RESTful :-) (and the answer is of course no!)
good luck with the workarounds - its really working around I.E's behaviour, which is frustrating on many levels. Rob On Sat, Dec 11, 2010 at 10:00 AM, Rob Atkinson <robatkinson...@gmail.com> wrote: > moral support, at the very least :-) > > I'll forward it on to the OGC as well - and see if I can get a > response. There is an emerging discussion on HTTP protocol and > browser-friendliness... > > > Rob > > On Sat, Dec 11, 2010 at 6:18 AM, Andrea Aime > <andrea.a...@geo-solutions.it> wrote: >> Hi, >> tried implement the OWS 2.0 policy of returning proper HTTP status >> codes when a service exception is returned. >> >> The patch attached to http://jira.codehaus.org/browse/GEOS-4255 >> has the basics of it: >> - a new class to represent the ows error code and its correspondent >> status code >> - changed service exception >> - changed the wps module to use the new code class as an example >> - made the service exception handlers set the status code >> (start the JVM with -DOWS10_HTTP_ERROR_CODES=true to have >> the codes set on WMS/WFS) >> >> Now, what's wrong with it? Well, it basically makes debugging from >> a browser impossible. >> When a 500 or a 400 is set as the status code without also setting >> the content type to html the browser just says that the web page is >> not there, and does not offer to download the service exception >> at all! >> This basically means you have to use a non browser client, >> such as "curl", to actually get the error message. Which is ridicolous. >> >> In order to get anything to display HTTPServletResponse.sendError(code, >> message) >> can be used, but at that point the container sets the content type to >> html and builds a little web page around the message, disallowing >> to use any other content type or... content. >> >> I hope there is some workaround, otherwise this seemingly good >> idea is going to turn into a tragedy (and one we won't be able >> to avoid since OWS 2.0 will be the base for future specs...) >> >> Suggestions, fixes to my eventually broken understanding, >> moral support... all greatly appreciated... >> >> Cheers >> Andrea >> >> -- >> ----------------------------------------------------- >> Ing. Andrea Aime >> Senior Software Engineer >> >> GeoSolutions S.A.S. >> Via Poggio alle Viti 1187 >> 55054 Massarosa (LU) >> Italy >> >> phone: +39 0584962313 >> fax: +39 0584962313 >> >> http://www.geo-solutions.it >> http://geo-solutions.blogspot.com/ >> http://www.linkedin.com/in/andreaaime >> http://twitter.com/geowolf >> >> ----------------------------------------------------- >> >> ------------------------------------------------------------------------------ >> Oracle to DB2 Conversion Guide: Learn learn about native support for PL/SQL, >> new data types, scalar functions, improved concurrency, built-in packages, >> OCI, SQL*Plus, data movement tools, best practices and more. >> http://p.sf.net/sfu/oracle-sfdev2dev >> _______________________________________________ >> Geoserver-devel mailing list >> Geoserver-devel@lists.sourceforge.net >> https://lists.sourceforge.net/lists/listinfo/geoserver-devel >> > ------------------------------------------------------------------------------ Oracle to DB2 Conversion Guide: Learn learn about native support for PL/SQL, new data types, scalar functions, improved concurrency, built-in packages, OCI, SQL*Plus, data movement tools, best practices and more. http://p.sf.net/sfu/oracle-sfdev2dev _______________________________________________ Geoserver-devel mailing list Geoserver-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/geoserver-devel
