HTTP DELETE throws 404 #39
Description
What?
Requesting a DELETE on a not existent resource throws 404.
How?
What should be achieved with such a call is that the resource is gone after the call is completed. If it was not there before, the desired target state is already reached prior to the method call. In the sense of fault tolerance and better applicability of the API, it could also return 200. This saves the client side from having to handle the 404 in these cases.