Consume (and discard) body in Initiate Multipart Upload request #2048
Conversation
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
# for free
to join this conversation on GitHub.
Already have an account?
# to comment
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.
… (to satisfy AWS CRT-based S3 client)
Description
A PutObject request to upload a stream of unknown size results in a timeout when using the AWS CRT-based S3 client. It seems that this client is a bit picky with HTTP protocol, other clients work fine. The TransferManager behaves similarly.
PutObject with a stream of unknown size initiates a multipart upload. This POST request does not require any input in the body. If we do not consume the (empty) body, the S3 client will hang and timeout after 10 seconds.
Streams of known size did not result in a timeout.
Related Issue
Tasks