Update AWS S3 Multipart documentation wrt CORS settings #1539
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.
Blame it on me, but because the documentation only talked about the additional
ExposeHeader
tag for theETag
header, I honestly believed that the<AllowedMethod>PUT</AllowedMethod>
was a mistake and that the allowed method must bePOST
, as with the "normal" S3 upload. I'm thus proposing to change the documentation to make it crystal clear.