You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
When creating a feature, the server may compute automatically some fields (UUIDs, timestamps, etc.) that the client may wish. Currently it needs to follow the Location header returned by the 201 response. It could be worth to have a way of getting the updated feature representation, returned as the body of the response, to save a client-server round-trip. If we don't want to impose such behaviour as required, that could be done through some "Return-Created-Feature: true" request header, optionally honored by the server.
Meeting 2024-06-03: Having the possibility to get the representation in the response sounds like a useful option. The default behavior should be to not require content in the response.
When creating a feature, the server may compute automatically some fields (UUIDs, timestamps, etc.) that the client may wish. Currently it needs to follow the Location header returned by the 201 response. It could be worth to have a way of getting the updated feature representation, returned as the body of the response, to save a client-server round-trip. If we don't want to impose such behaviour as required, that could be done through some "Return-Created-Feature: true" request header, optionally honored by the server.
(triggered by qgis/QGIS#57486)
The text was updated successfully, but these errors were encountered: