This repository has been archived by the owner on Feb 12, 2024. It is now read-only.
Read Object POST Parameters from Form Fields #204
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
According to AWS S3 documentation, in a POST object request, parameters are passed through the multipart form instead of as HTTP headers (see http://docs.aws.amazon.com/AmazonS3/latest/API/RESTObjectPOST.html). This change makes Fake S3 parse and use parameters from the multipart form in the case of a object POST request.
This change is needed to properly handle a presigned object POST request. At the moment, FakeS3 would create an object under the wrong content type
multipart/form-data
because that's what the 'Content-Type' header said in the HTTP POST request; yet, the correct content type is passed along as one of the multipart form field of the request.