s3api: Validate additional checksums on upload
See https://docs.aws.amazon.com/AmazonS3/latest/userguide/checking-object-integrity.html for some background. This covers both "normal" objects and part-uploads for MPUs. Note that because we don't write down any client-provided checksums during initiate-MPU calls, we can't do any verification during complete-MPU calls. crc64nvme checksums are not yet supported; clients attempting to use them will get back 501s. Adds crt as a boto3 extra to test-requirements. The extra lib provides crc32c and crc64nvme checksum support in boto3. Co-Authored-By: Ashwin Nair <ashnair@nvidia.com> Co-Authored-By: Alistair Coles <alistairncoles@gmail.com> Signed-off-by: Tim Burke <tim.burke@gmail.com> Signed-off-by: Alistair Coles <alistairncoles@gmail.com> Change-Id: Id39fd71bc59875a5b88d1d012542136acf880019
This commit is contained in:
committed by
Alistair Coles
parent
364cc6556f
commit
be56c1e258
@@ -2,6 +2,11 @@ start =
|
||||
element CompleteMultipartUpload {
|
||||
element Part {
|
||||
element PartNumber { xsd:int } &
|
||||
element ETag { xsd:string }
|
||||
element ETag { xsd:string } &
|
||||
element ChecksumCRC32 { xsd:string }? &
|
||||
element ChecksumCRC32C { xsd:string }? &
|
||||
element ChecksumCRC64NVME { xsd:string }? &
|
||||
element ChecksumSHA1 { xsd:string }? &
|
||||
element ChecksumSHA256 { xsd:string }?
|
||||
}+
|
||||
}
|
||||
|
||||
Reference in New Issue
Block a user