S3UploadFailedError due to boto3 integrity checks on non AWS providers

[fritterhoff]

Hi!

we are using a NetApp as S3 provider instead of AWS. Due to the transient dependency to boto3 and their change in version 1.36 (boto/boto3#4392) the uploads fail with error(s) similar to this one:

Failed to upload /data/media_store/local_content/xx/xx/xxxxxxxxxx to matrix/local_content/xx/xx/xxxxxxxxxx: An error occurred (InvalidArgument) when calling the PutObject operation: x-amz-content-sha256 must be UNSIGNED-PAYLOAD, STREAMING-AWS4-HMAC-SHA256-PAYLOAD or a valid sha256 value.

From my understanding/point of view we need an additional option to make this integrity checks optional again.

[davefatkin]

I had to handle this too as I am using Digital Ocean Spaces. They had an open issue on their end due to the change in boto3 that they have since resolved (Spaces is now compatible with current version of boto3). Since then, I've switched back to using the main repo. davefatkin#1

[fritterhoff]

Mhm. That would require to get an Update of our NetApps ... prop that will take some time.