Rest API: DELETE method always returns 204

[Kampfgnom]

When calling DELETE on a resource, the response code is always 204 with an empty body, independently from whether the resource exists or not, or if it has been deleted or not (headers omitted for brevity):

$ curl -i http://localhost:3000/api/TodoLists
HTTP/1.1 200 OK
[]

$ curl -i -X PUT http://localhost:3000/api/TodoLists
HTTP/1.1 200 OK
{"id":"27e2ea50-e814-11e4-8782-29c27147e8f9"}

$ curl -i http://localhost:3000/api/TodoLists
HTTP/1.1 200 OK
[{"title":null,"id":"27e2ea50-e814-11e4-8782-29c27147e8f9","systemUserId":null}]

$ curl -i -X DELETE http://localhost:3000/api/TodoLists/asd
HTTP/1.1 204 No Content

$ curl -i http://localhost:3000/api/TodoLists
HTTP/1.1 200 OK
[{"title":null,"id":"27e2ea50-e814-11e4-8782-29c27147e8f9","systemUserId":null}]

$ curl -i -X DELETE http://localhost:3000/api/TodoLists/27e2ea50-e814-11e4-8782-29c27147e8f9
HTTP/1.1 204 No Content

$ curl -i http://localhost:3000/api/TodoLists
HTTP/1.1 200 OK
[]

$ curl -i -X DELETE http://localhost:3000/api/TodoLists/27e2ea50-e814-11e4-8782-29c27147e8f9
HTTP/1.1 204 No Content

I see the same behaviour in the API-explorer and my (currently in development) Qt-Client.

Thanks for any help.

[superkhau]

@Kampfgnom I've verified your observations and 204 is always returned as you described. Escalating to bug status.

[fabien]

@raymondfeng we should really get this fixed, see also: #1543 (comment)

I would suggest a config option: deleteInfo as well as Model.settings.deleteInfo or something like that to enable it. Ideally I would like such option to work like this: loopbackio/loopback-connector-mongodb#164 (comment) - but with the global setting to be in your app config.

[raymondfeng]

Sure. @superkhau Can you take this one? It's very similar as the work you did for update.

[superkhau]

Assigned to myself so we can prioritize during sprint planning.

/cc @chandadharap

[superkhau]

• Functional test the above endpoints
• Escalate to bug status depending on the results of the functional tests
• Make functional tests pass
  • Isolate where the error is coming from
  • Add the fix