This repository has been archived by the owner on Sep 26, 2019. It is now read-only.
-
Notifications
You must be signed in to change notification settings - Fork 49
Commit
This commit does not belong to any branch on this repository, and may belong to a fork outside of the repository.
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
- Loading branch information
Showing
3 changed files
with
46 additions
and
23 deletions.
There are no files selected for viewing
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters