Type
New feature
Description
Right now, upload operations in R2 (PutObject, CopyObject, UploadPart with multipart uploads) support the HTTP standard “Content-MD5” header to ensure transfer integrity. However, this is limiting compatibility with some libraries who leverage the “x-amz-checksum-algorithm” to indicate which algorithm is used. For example, boto3 uses this header as part of its Transfer API, which manages retries and multipart uploads automatically.
Benefit
Even if the only value supported for R2 was MD5, this would allow users to leverage boto3’s Transfer API, or any other library that relies in this header. This would make R2 more accessible and easier to use.