DELETE routes return HTTP 204 even if the item doesn't exist
Bug #1596935 reported by
Domhnall Walsh
This bug affects 2 people
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
OpenStack Backup/Restore and DR (Freezer) |
Fix Released
|
Medium
|
Vishakha Agarwal |
Bug Description
If we try to DELETE a non-existent item (action, session, backup, job or client), then the API returns a HTTP 204 (No Content) whether the item exists or not. If it does not exist, the API *should* return a HTTP 404 (Not Found) instead.
Changed in freezer: | |
assignee: | nobody → Domhnall Walsh (domhnall-walsh) |
Changed in freezer: | |
importance: | Undecided → Medium |
Changed in freezer: | |
assignee: | Domhnall Walsh (domhnall-walsh) → Vishakha Agarwal (vishakha.agarwal) |
To post a comment you must log in.
I suppose not. HTTP methods( get/delete/ put) have idempotence feature.
When you retrive a non-existent object, a 404 error code should be returned, but if you delete a non-existent object, a 204 code should be fine.