The objective of this task is to verify that MSP360 uses the UploadPartCopy API to copy objects greater than 5 GB in size while maintaining the original multipart upload structure and not using arbitrary byte ranges or other methods. We can't support the latter, so this is to find out if we can conform to S3's internal limitation without reconfiguring all clients while using Storj's S3-compatible API.
Acceptance Criteria
Successfully analyze and dump the requests issued by MSP360 when copying objects greater than 5 GB.
Verify that MSP360 uses the UploadPartCopy API and maintains the original multipart upload structure.
Ensure MSP360 doesn't use arbitrary byte ranges or other methods to copy the object.
Document the findings and any necessary recommendations or adjustments based on the analysis.
Goal
The objective of this task is to verify that MSP360 uses the UploadPartCopy API to copy objects greater than 5 GB in size while maintaining the original multipart upload structure and not using arbitrary byte ranges or other methods. We can't support the latter, so this is to find out if we can conform to S3's internal limitation without reconfiguring all clients while using Storj's S3-compatible API.
Acceptance Criteria
Links