Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Use region specific endpoint when updating s3 hostname #170

Merged
merged 2 commits into from
Nov 2, 2013

Conversation

jamesls
Copy link
Member

@jamesls jamesls commented Nov 1, 2013

This fixes an issue when using govcloud regions, as s3.amazonaws.com won't
map to the govcloud region.

All botocore/awscli unit/integ tests pass

This fixes an issue when using govcloud regions,
as `s3.amazonaws.com` won't map to the govcloud region.

All botocore/awscli unit/integ tests pass
@jamesls
Copy link
Member Author

jamesls commented Nov 1, 2013

I'm not sure about this anymore.

Maybe we should just fix a list of regions for which we don't rewrite the hostname. Otherwise you'll get the permanent redirect if you use the wrong region.

@garnaat
Copy link
Member

garnaat commented Nov 1, 2013

Yeah, I've been looking at this fix and it makes it impossible to use the DNS resolution to redirect you to the right region rather than knowing the endpoint explicitly.

I think we need to think of s3.amazonaws.com as being the universal endpoint for for all standard regions. But for special regions like govcloud we need to know that they don't use the universal endpoint. Or maybe we think of it as the special region having it's own, unique universal endpoint.

Fixes an issue when using the govcloud region for s3.
@jamesls
Copy link
Member Author

jamesls commented Nov 2, 2013

Ok, PR updated, please review again.

@garnaat
Copy link
Member

garnaat commented Nov 2, 2013

LGTM

@jamesls jamesls merged commit be4ed78 into boto:develop Nov 2, 2013
@jamesls jamesls deleted the fix-s3-host branch June 23, 2014 18:15
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

2 participants