I think I found what causes #136. It turns out that QGIS sends a POSTGetFeature request when publishing edits on a layer that's been loaded through the plugin. See this mitmproxy screenshot below (request is at the top).
This is of course very weird. Comparing it to the request that QGIS' "native" WFS sends I noticed that the latter capitalizes the query parameters whereas the former doesn't.
After capitalizing the parameters in uri.py QGIS sends a correct POST request and the transaction succeeds, see below.
I tested this on four machines (2 x Win, 2 x OS X) and different QGIS verions and it worked on all of them.
dakcarto
commented
8 years ago
I think I found what causes #136. It turns out that QGIS sends a
POSTGetFeaturerequest when publishing edits on a layer that's been loaded through the plugin. See this mitmproxy screenshot below (request is at the top).This is of course very weird. Comparing it to the request that QGIS' "native" WFS sends I noticed that the latter capitalizes the query parameters whereas the former doesn't.
After capitalizing the parameters in
uri.pyQGIS sends a correctPOSTrequest and the transaction succeeds, see below.I tested this on four machines (2 x Win, 2 x OS X) and different QGIS verions and it worked on all of them.