swetashre
commented
4 years ago @pulllow - Thank you for your post. This is the way signature version v2 works with header . For version s3v2 the signature does not factor in the header so it will work even if you don't send it. This is why v2 signature are deprecated and being phased out in favor of V4. SigV4 guarantees the header is present and is a particular value as part of the signature but V2 does not. So you will get error in the second part of code if you specify different header value or omit the header which explains the behavior you are seeing.
pulllow
github-actions[bot]
mtvx
If you create a client without specifying the signature version in the config it will not honor the range set in the get _object.
boto3 1.13.2 python 3.8
Steps to reproduce
create client without signature version
s3 = boto3.client('s3') url = s3.generate_presigned_url( 'get_object', Params={ 'Key':
different_range_headers = {'range': 'bytes=21-39'}
does not acknowledge range in signature and will retrieve bytes
resp = requests.get(url, headers=different_range_headers)
create client with signature version
s3 = boto3.client('s3', config=Config(signature_version='s3v4')) url = s3.generate_presigned_url( 'get_object', Params={ 'Key':
different_range_headers = {'range': 'bytes=21-39'}
this will fail 403 as expected
resp = requests.get(url, headers=different_range_headers)