s3api: Stop requiring Content-MD5 for multi-deletes

Code Issues Proposed changes

...at least, provided the client sent a X-Amz-Content-SHA256 header.
Apparently Content-MD5 is no longer strictly required by AWS? Or maybe
it never was, provided the client sent a SHA256 of the content.
This also allows us to test with newer boto3, botocore, s3transfer.
Related-Bug: #2098529
Co-Authored-By: Clay Gerrard <clay.gerrard@gmail.com>
Change-Id: Ifbcde9820bee72d80cab0fe3e67ea0f5817df949

This commit is contained in:

Tim Burke

2025年01月24日 14:08:39 -08:00

parent 364a47b176

commit a5db202c55

3 changed files with 91 additions and 4 deletions

Show all changes Ignore whitespace when comparing lines Ignore changes in amount of whitespace Ignore changes in whitespace at EOL

Download Patch File Download Diff File Expand all files Collapse all files

6
py3-constraints.txt

View File

@@ -17,10 +17,10 @@ autopage===0.5.2

bandit===1.7.10;python_version>='3.8'

bandit===1.7.5;python_version=='3.7'

bandit===1.7.1;python_version=='3.6'

boto3===1.35.71;python_version>='3.8'

boto3===1.36.6;python_version>='3.8'

boto3===1.33.13;python_version=='3.7'

boto3===1.23.10;python_version=='3.6'

botocore===1.35.71;python_version>='3.8'

botocore===1.36.6;python_version>='3.8'

botocore===1.33.13;python_version=='3.7'

botocore===1.26.10;python_version=='3.6'

certifi===2024年8月30日

@@ -188,7 +188,7 @@ rfc3986===2.0.0;python_version>='3.7'

rfc3986===1.5.0;python_version=='3.6'

rich===13.9.3;python_version>='3.8'

rich===13.8.1;python_version=='3.7'

s3transfer===0.10.4;python_version>='3.8'

s3transfer===0.11.2;python_version>='3.8'

s3transfer===0.8.2;python_version=='3.7'

s3transfer===0.5.2;python_version=='3.6'

setuptools===75.3.0;python_version>='3.12'

s3api: Stop requiring Content-MD5 for multi-deletes

6 py3-constraints.txt Unescape Escape View File

6
py3-constraints.txt

View File