Leandro Costa created an issue |
Strange behavior when invalid xsi:schemaLocation is sent in a WFS-T request |
Issue Type: |
Bug |
---|---|
Affects Versions: |
2.4.5 |
Assignee: |
|
Components: |
WFS |
Created: |
19/Mar/14 8:58 AM |
Environment: |
GeoServer 2.4.5, Ubuntu 10.04, java version “1.7.0_51” (Oracle) |
Priority: |
Major |
Reporter: |
When an invalid xsi:schemaLocation is passed to GeoServer in a WFS-T request it doesn’t return anything (I got a timeout in 120s). After that GeoServer stops responding to DescribeFeatureType requests too. To reproduce, just create a layer, enable WFS in the workspace and send a POST request with an invalid value in xsi:schemaLocation, like xsi:schemaLocation=“foo http://www.opengis.net/wfs http://schemas.opengis.net/wfs/1.1.0/wfs.xsd” I’m using the following raw body: <wfs:Transaction |
This message was sent by Atlassian JIRA (v6.1.6#6162-sha1:7af547c) |