Red Hat Bugzilla – Bug 962855
deleting operation history returns 204 when invalid id is specified
Last modified: 2015-11-01 19:43:11 EST
Description of problem:
Version-Release number of selected component (if applicable):
Steps to Reproduce:
1. do DELETE /operation/history/foo
Actual results: server returns 204
Expected results: server should return 404 or 406
I think the current behavior is correct in the REST sense as
operations are supposed to be idempotent - you should be able to run them multiple times with the same result (POST is the exception).
The reasoning is that REST is not reduced to REST over http, but could be applied over other transports that are less safe and which may drop packets.
Of course if the parameter is not an integer, an error should be thrown (I think RestEasy may automatically do that anyway).
Delete operations are by default idempotent and should return a 204 code no matter if the entity existed or not.
I will introduce a 'validate' parameter, that checks for existence and which can then return a 404 code
Bulk closing of old issues now that HRQ 4.9 is in front of the door.
If you think the issue has not been solved, then please open a new bug and mention this one in the description.