Fix for EU-Buckets #26
Open
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
|
I have the same problem, I'm going to try your fix. |
|
I just can't believe this bug. Wasted my day. |
|
nt: we changed the gem version to git://github.com/JezC/aws-s3.git |
|
Thanks, I will take a look. |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in 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 access EU-Buckets one HAS to use the VirtualHost-method to address buckets, i.e. instead of
GET /bucket/somekey
Host: s3.amazonaws.com
it has to be
GET /somekey
Host: bucket.s3.amazonaws.com
Yet the canonical string for authorization remains the same for both.
This fix is a quick&dirty soluation that works for me so far. Though it is still necessary to set the ":server" option in establish_connection!. Maybe this should be set as well (at least for :persistent => false)