Handle 307 redirect for file-like object, don't use isinstance check #236
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.
This fixes aws/aws-cli#544 and aws/aws-cli#654
The issue here is that the CLI uses a file like object
that implements .read() and .seek(), but doesn't actually
inherit from the file/_IOBase.
This means that we weren't rewinding the stream in the case of 307 redirects
when using multipart uploads in the CLI.