Nick Craig-Wood e5a1bcb1ce s3: fix InvalidRequest copying to a locked bucket from a source with no MD5SUM ... Before this change, we would upload files as single part uploads even if the source MD5SUM was not available. AWS won't let you upload a file to a locket bucket without some sort of hash protection of the upload which we don't have with no MD5SUM. So we switch to multipart upload when the source does not have an MD5SUM. This means that if --s3-disable-checksum is set or we are copying from a source with no MD5SUMs we will copy with multipart uploads. This patch changes all uploads, not just those to locked buckets because having no MD5SUM protection on uploads is undesirable. Fixes #6846		2023-03-17 11:34:20 +00:00
..
gen_setfrom.go	s3: refactor to use generated code instead of reflection to copy structs	2022-08-05 16:45:23 +01:00
s3_internal_test.go	all: fix spelling across the project	2022-08-30 11:16:26 +02:00
s3_test.go	s3: fix SetModTime on GLACIER/ARCHIVE objects and implement set/get tier	2019-09-14 09:18:55 +01:00
s3.go	s3: fix InvalidRequest copying to a locked bucket from a source with no MD5SUM	2023-03-17 11:34:20 +00:00
setfrom.go	s3: refactor to use generated code instead of reflection to copy structs	2022-08-05 16:45:23 +01:00
v2sign.go	s3: fix copy multipart with v2 auth failing with 'SignatureDoesNotMatch'	2021-01-27 14:43:02 +00:00