Nick Craig-Wood 0d10640aaa s3: add --s3-copy-cutoff for size to switch to multipart copy ... Before this change we used the same (relatively low limits) for server side copy as we did for multipart uploads. It doesn't make sense to use the same limits since no data is being downloaded or uploaded for a server side copy. This change introduces a new parameter --s3-copy-cutoff to control when the switch from single to multipart server size copy happens and defaults it to the maximum 5GB. This makes server side copies much more efficient. It also fixes the erroneous error when trying to set the modification time of a file bigger than 5GB. See #3778		2019-12-03 10:37:55 +00: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: add --s3-copy-cutoff for size to switch to multipart copy	2019-12-03 10:37:55 +00:00
v2sign.go	s3: fix v2 signer on files with spaces - fixes #2438	2018-10-14 00:10:29 +01:00