Bablu Raul created HDDS-17835:
---------------------------------

             Summary: S3 DeleteObjects deletes the object when Content-MD5 is 
wrong
                 Key: HDDS-17835
                 URL: https://issues.apache.org/jira/browse/HDDS-17835
             Project: Apache Ozone
          Issue Type: Bug
          Components: S3
            Reporter: Bablu Raul


{{POST /?delete}} accepts a Content-MD5 that does not match the delete XML and 
still deletes the key.

AWS requires Content-MD5 on DeleteObjects. A mismatch must be HTTP 400 
{{{}BadDigest{}}}, and the object must stay. Ozone returns HTTP 200, lists the 
key under {{{}Deleted{}}}, and the next HeadObject is 404.

Content-MD5 is already checked on PutObject and UploadPart. A wrong value there 
is {{BadDigest}} and the object is not stored. {{BucketEndpoint.multiDelete}} 
never reads the header.

 



--
This message was sent by Atlassian Jira
(v10.3.26#10030026)

---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]

Reply via email to