DeleteObject should almost always return 204 #227

Closed
opened 2022-02-06 08:41:58 +00:00 by trinity-1686a · 0 comments

AWS happily returns 204 when deleting non-existing object, whereas we return 404.
We also send back x-amz-version-id, AWS doesn't for bucket with versionning disabled.
This might be different when versionning is enabled (untested), but we don't support versionning, so it's not a concern yet.

AWS happily returns 204 when deleting non-existing object, whereas we return 404. We also send back `x-amz-version-id`, AWS doesn't for bucket with versionning disabled. This might be different when versionning is enabled (untested), but we don't support versionning, so it's not a concern yet.
trinity-1686a added the
S3 Compatibility
label 2022-02-06 08:42:56 +00:00
KokaKiwi self-assigned this 2022-02-21 15:02:27 +00:00
KokaKiwi removed their assignment 2022-03-07 15:14:23 +00:00
lx added this to the v0.8 milestone 2022-09-14 11:14:00 +00:00
lx closed this issue 2022-09-14 15:16:40 +00:00
Sign in to join this conversation.
No Milestone
No Assignees
1 Participants
Notifications
Due Date
The due date is invalid or out of range. Please use the format 'yyyy-mm-dd'.

No due date set.

Dependencies

No dependencies set.

Reference: Deuxfleurs/garage#227
No description provided.