Bug report #13182

QGIS WFS Server returns empty answer

Added by dr - over 4 years ago. Updated 9 months ago.

Status:Closed
Priority:Normal
Assignee:René-Luc ReLuc
Category:QGIS Server
Affected QGIS version:master Regression?:No
Operating System:Windows Easy fix?:No
Pull Request or Patch supplied:No Resolution:end of life
Crashes QGIS or corrupts data:No Copied to github as #:21244

Description

GetCapabilities works fine but GetFeature returns empty response:

<wfs:FeatureCollection xmlns:wfs="http://www.opengis.net/wfs" xmlns:ogc="http://www.opengis.net/ogc" xmlns:gml="http://www.opengis.net/gml" xmlns:ows="http://www.opengis.net/ows" xmlns:xlink="http://www.w3.org/1999/xlink" xmlns:qgs="http://www.qgis.org/gml" xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance" xsi:schemaLocation="http://www.opengis.net/wfs http://schemas.opengis.net/wfs/1.0.0/wfs.xsd http://www.qgis.org/gml http://localhost:81/qgis_mapserv.fcgi.exe?map=C:%5CDocuments and Settings%5CAdministrator%5Cqgisserver%5Cqgis-mapnik.qgs&amp;SRSNAME=EPSG:4326&amp;SERVICE=WFS&amp;VERSION=1.0.0&amp;REQUEST=DescribeFeatureType&amp;TYPENAME=boundary&amp;OUTPUTFORMAT=XMLSCHEMA">

History

#1 Updated by Jukka Rahkonen over 4 years ago

You should add so much details and sample data for the layer "boundary" that others can reproduce your issue. With this information it is impossible to do anything.

#3 Updated by Jukka Rahkonen almost 4 years ago

It may not help, but I would have a try with correct request by removing &format, &width, and &height which do not belong to WFS. Unknown parameters should be quietly skipped but sometimes they make problems. Have you checked from the GetCapabilities that outputformat=GeoJSON appears there and that it is written exactly that way?

#4 Updated by asgerpetersen - almost 4 years ago

I think this issue may be related to #13991

The response may look empty because the server sets a wrong content-length header in the http response.

#5 Updated by asgerpetersen - almost 4 years ago

Is this issue still relevant? If it is a duplicate of #13991 it probably should be closed.

#6 Updated by René-Luc ReLuc almost 4 years ago

  • Assignee set to René-Luc ReLuc

#7 Updated by Henrik Uggla over 3 years ago

This bug is still present in 2.8.8.

#8 Updated by Henrik Uggla over 3 years ago

Bug present since 2.8.2

#9 Updated by Giovanni Manghi over 2 years ago

  • Regression? set to No
  • Easy fix? set to No

#10 Updated by Giovanni Manghi 9 months ago

  • Resolution set to end of life
  • Status changed from Open to Closed

Also available in: Atom PDF