#1025: r.in.wms doesn't process WMS server responses (errors)
-------------------------+--------------------------------------------------
Reporter: marisn | Owner: grass-dev@lists.osgeo.org
Type: defect | Status: new
Priority: normal | Milestone: 7.0.0
Component: Raster | Version: svn-develbranch6
Keywords: | Platform: Unspecified
Cpu: Unspecified |
-------------------------+--------------------------------------------------
Current r.in.wms implementation is simply downloading data and not
performing any kind of response parsing. If some WMS parameters are wrong,
r.in.wms still will download and process error messages as if they where
normal server responses. There's no use for few thousands of XML files
with content i.e. "Output format not supported", also any processing of
such "GeoTIFFs" will fail.
Replying to [comment:1 hamish]:
> Also server response can come in many many forms so it is hard to check
for with confidence.
It's not that hard to force error messages to be returned as XML, as it is
by default [1]. Current approach shomehow fails to detect XML error
messages with .tiff name. Also it's not wise to get thousands of equal
error messages.
1. WMS 1.3.0 spec:
{{{
7.3.3.11
EXCEPTIONS
The optional EXCEPTIONS parameter is defined in 6.9.4. The default value
is
“XML” if this parameter is absent from the request.
}}}
it's still relevant to the shell script version; re-targeting milestone. I
would not be surprised if the python version in trunk suffers from the
same problem though, as it is to do with funny arbitrary/out-of-spec
output from the server, which needs to be tested & approved as real image
data by whichever grass module which makes the request.