Return headers on successful response #265
Merged
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.
…esful responses along with params value
Summary
We're performing multipart uploads to s3, once all parts are uploaded we need to let aws know that the file is ready to be put back together by sending back all header values for each part uploaded. Having access to headers helps us to be able to let aws know past files have been successfully uploaded.
This is a simple change that is changes androids
GlobalRequestObserverDelegate
We've been testing this simple update and have had good success with it, we believe it might be helpful for others.
| OS | Implemented |
| Android | ✅ |
Checklist
README.md