Project

General

Profile

Bug #13469

Delete on expired objects should return 404 with Swift API

Added by Yuan Zhou over 8 years ago. Updated over 7 years ago.

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.

Associated revisions

Revision fee71447 (diff)
Added by Yuan Zhou over 8 years ago

rgw: fix response of delete expired objects

GET/HEAD requests to the expired-but-not-yet-deleted objects will
'404 Not Found' currently.

Swift's response to a DELETE of an expired object is 404; however,
the object does get deleted.

This patch fixes this issue by checking the expire time in Swift DELETE
op, delete the object with a 404 http code.

Fixes #13469

Signed-off-by: Yuan Zhou <>

History

#2 Updated by Abhishek Lekshmanan over 7 years ago

  • Status changed from New to Resolved

Also available in: Atom PDF