This repository has been archived by the owner on Jan 17, 2023. It is now read-only.
S3 Authorization #14
Merged
S3 Authorization #14
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
|
Not at all! I let this one get away from me. Thanks so much for the changes. I've merged them in and tagged a new release (0.2.0). Bonus: Real documentation instead of stubs now! |
This was referenced May 1, 2013
Sign up for free
to subscribe to this conversation on GitHub.
Already have an account?
Sign in.
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.
What about using those accessKey and secret fields? This adjustment assigns the requests following the Amazon definitions and now we can download and upload private data from S3.
IMPORTANT: I couldn't make it work through https.
Feel free to make suggestions!