Charles Farquhar 5b8c15d680 Ignore md5sum header during multi-part upload init
Some S3 client libs send an Etag/Content-Md5 header during multi-part object
initialization.  The S3 API reference does not mention how the MD5 checksum
header is treated at this stage, and the API itself appears to ignore the
headers.

Prior to this commit, swift3 passed the headers on, which were later compared
to the md5sum of the request's body, which is always empty.  This results in the
upload failing when the client-supplied checksum (generally the checksum for the
entire object) does not match the checksum for a null object.

After this commit, the Etag and Content-Md5 headers are ignored during the
multi-part initialization phase.  This mimics the behavior of AWS' S3 API.

Closes-Bug: 1697741
Change-Id: I2cb5376994bf270890bd9b06ec2bf521350c826d
2017-07-28 18:04:37 +00:00
..
2016-06-01 19:03:37 -07:00
2014-12-08 22:11:24 -08:00
2014-12-16 05:40:57 -08:00
2017-01-05 00:10:32 +00:00
2016-09-15 17:39:56 -07:00