Tim Burke e22960fd71 s3api: Fix ETag when copying a MU part from another MU ... Previously, we'd preserve the sysmeta that we wrote down with the original multipart-upload to track its S3-style etag on the new part, causing it to have an ETag like `<MD5>-<N>`. Later, when the client tried to complete the new multipart-upload, it would send that etag back to the server, which would reject the request because the ETag didn't look like a normal MD5. Now, have s3api include blank values in the copy request to overwrite the source sysmeta, and treat a blank etag override the same as a missing one. Change-Id: Id33a7ab9d0b8f33fede73eae540d6137708e1218 Closes-Bug: #1829959		2019-05-22 13:36:41 -07:00
..
__init__.py	Start transition to boto3 in s3api tests.	2019-05-21 22:10:20 +00:00
s3_test_client.py	Start transition to boto3 in s3api tests.	2019-05-21 22:10:20 +00:00
test_acl.py	Add another user for s3api func tests	2018-09-14 13:33:51 +00:00
test_bucket.py	Start transition to boto3 in s3api tests.	2019-05-21 22:10:20 +00:00
test_multi_delete.py	s3api: Allow concurrent multi-deletes	2018-12-06 23:20:52 +00:00
test_multi_upload.py	s3api: Fix ETag when copying a MU part from another MU	2019-05-22 13:36:41 -07:00
test_object.py	Merge "Properly handle custom metadata upon an object COPY operation"	2018-10-17 07:07:11 +00:00
test_presigned.py	Import swift3 into swift repo as s3api middleware	2018-04-27 15:53:57 +09:00
test_service.py	Import swift3 into swift repo as s3api middleware	2018-04-27 15:53:57 +09:00
utils.py	Import swift3 into swift repo as s3api middleware	2018-04-27 15:53:57 +09:00