Actions
Bug #13469
closedDelete on expired objects should return 404 with Swift API
Status:
Resolved
Priority:
Normal
Assignee:
-
Target version:
-
% Done:
0%
Source:
other
Tags:
Backport:
Regression:
No
Severity:
3 - minor
Reviewed:
Affected Versions:
ceph-qa-suite:
Pull request ID:
Crash signature (v1):
Crash signature (v2):
Description
Swift's response to a DELETE of an expired object is 404; however,the object does get deleted.
RGW's response to a DELETE of an expired objects is 204, and the object gets deleted.
GET/HEAD requests to the expired-but-not-yet-deleted objects will '404 Not Found' currently. This is the same as Swift.
We should check the expire time in Swift DELETE op, delete the object with a 404 http code returning.
Updated by Abhishek Lekshmanan almost 8 years ago
- Status changed from New to Resolved
Actions