[mapserver-users] Parens making GetFeature crash with Mapserver 7
Alexandre Saunier
alexandre.saunier at camptocamp.com
Fri Sep 5 03:50:37 PDT 2014
Hi,
I am testing the coming Mapserver 7 and have noticed that WFS GetFeature
requests crash when using parens in a property value filter. Actually only
the opening paren seems to be a problem, not the closing one.
For instance:
<wfs:GetFeature xmlns:wfs="http://www.opengis.net/wfs" service="WFS"
version="1.1.0" xsi:schemaLocation="http://www.opengis.net/wfs
http://schemas.opengis.net/wfs/1.1.0/wfs.xsd" xmlns:xsi="
http://www.w3.org/2001/XMLSchema-instance"><wfs:Query
typeName="feature:monuments" srsName="EPSG:3857" xmlns:feature="
http://mapserver.gis.umn.edu/mapserver"><ogc:Filter xmlns:ogc="
http://www.opengis.net/ogc"><ogc:PropertyIsEqualTo
matchCase="false"><ogc:PropertyName>nom</ogc:PropertyName><ogc:Literal>*foo*
</ogc:Literal></ogc:PropertyIsEqualTo></ogc:Filter></wfs:Query></wfs:GetFeature>
works as expected, whereas
<wfs:GetFeature xmlns:wfs="http://www.opengis.net/wfs" service="WFS"
version="1.1.0" xsi:schemaLocation="http://www.opengis.net/wfs
http://schemas.opengis.net/wfs/1.1.0/wfs.xsd" xmlns:xsi="
http://www.w3.org/2001/XMLSchema-instance"><wfs:Query
typeName="feature:monuments" srsName="EPSG:3857" xmlns:feature="
http://mapserver.gis.umn.edu/mapserver"><ogc:Filter xmlns:ogc="
http://www.opengis.net/ogc"><ogc:PropertyIsEqualTo
matchCase="false"><ogc:PropertyName>nom</ogc:PropertyName><ogc:Literal>*foo
(bar)*
</ogc:Literal></ogc:PropertyIsEqualTo></ogc:Filter></wfs:Query></wfs:GetFeature>
returns
<ows:ExceptionReport xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance"
version="1.1.0" xmlns:ows="http://www.opengis.net/ows" language="en-US"
xsi:schemaLocation="http://www.opengis.net/ows
http://schemas.opengis.net/ows/1.0.0/owsExceptionReport.xsd">
<ows:Exception locator="filter" exceptionCode="InvalidParameterValue">
<ows:ExceptionText>msWFSGetFeature(): WFS server error. Wrong number of
filter elements, one filter must be specified for each feature type listed
in the TYPENAME parameter.</ows:ExceptionText>
</ows:Exception>
</ows:ExceptionReport>
Both requests work fine with Mapserver 6.0.1.
Is it a known problem with Mapserver 7? No idea if this happens with
intermediate Mapserver versions.
I have found no issue about that on Mapserver's github.
Thanks,
Alexandre
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.osgeo.org/pipermail/mapserver-users/attachments/20140905/18bc501b/attachment.htm>
More information about the MapServer-users
mailing list