You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Copy file name to clipboardExpand all lines: localstack-core/localstack/aws/spec-patches.json
+12Lines changed: 12 additions & 0 deletions
Original file line number
Diff line number
Diff line change
@@ -540,6 +540,12 @@
540
540
"location": "header",
541
541
"locationName": "x-amz-checksum-crc32c"
542
542
},
543
+
"ChecksumCRC64NVME":{
544
+
"shape":"ChecksumCRC64NVME",
545
+
"documentation":"<p>This header can be used as a data integrity check to verify that the data received is the same data that was originally sent. This header specifies the Base64 encoded, 64-bit <code>CRC64NVME</code> checksum of the object. The <code>CRC64NVME</code> checksum is always a full object checksum. For more information, see <a href=\"https://docs.aws.amazon.com/AmazonS3/latest/userguide/checking-object-integrity.html\">Checking object integrity in the Amazon S3 User Guide</a>.</p>",
546
+
"location":"header",
547
+
"locationName":"x-amz-checksum-crc64nvme"
548
+
},
543
549
"ChecksumSHA1": {
544
550
"shape": "ChecksumSHA1",
545
551
"documentation": "<p>The base64-encoded, 160-bit SHA-1 digest of the object. This will only be present if it was uploaded with the object. With multipart uploads, this may not be a checksum value of the object. For more information about how checksums are calculated with multipart uploads, see <a href=\"https://docs.aws.amazon.com/AmazonS3/latest/userguide/checking-object-integrity.html#large-object-checksums\"> Checking object integrity</a> in the <i>Amazon S3 User Guide</i>.</p>",
@@ -552,6 +558,12 @@
552
558
"location": "header",
553
559
"locationName": "x-amz-checksum-sha256"
554
560
},
561
+
"ChecksumType":{
562
+
"shape":"ChecksumType",
563
+
"documentation":"<p>This header specifies the checksum type of the object, which determines how part-level checksums are combined to create an object-level checksum for multipart objects. You can use this header as a data integrity check to verify that the checksum type that is received is the same checksum that was specified. If the checksum type doesn’t match the checksum type that was specified for the object during the <code>CreateMultipartUpload</code> request, it’ll result in a <code>BadDigest</code> error. For more information, see Checking object integrity in the Amazon S3 User Guide. </p>",
564
+
"location":"header",
565
+
"locationName":"x-amz-checksum-type"
566
+
},
555
567
"ServerSideEncryption": {
556
568
"shape": "ServerSideEncryption",
557
569
"documentation": "<p>If you specified server-side encryption either with an Amazon Web Services KMS key or Amazon S3-managed encryption key in your PUT request, the response includes this header. It confirms the encryption algorithm that Amazon S3 used to encrypt the object.</p>",
0 commit comments