-
-
Notifications
You must be signed in to change notification settings - Fork 9.3k
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
Boto/Route53 + GAE Compatibility Issue #1911
Comments
We will not support GAE as we have frequently discussed on the issue tracker (most recently on https://github.com/kennethreitz/requests/issues/1905). Please search the bug tracker before opening requests in the future. Cheers! |
Ah, my bad. Thanks. |
Almighty requests developer, Now that the underlying |
It is not a supported platform. =) We will announce if and when we make that decision, but maintaining support for it is tricky and unhelpful. |
The issue described here applies to both Boto and gtaylor/python-route53.
Basically, when running Boto or Route53 on GAE, the way in which Requests extends httplib doesn't work with Google's httplib, which uses urlfetch instead of self.sock/self.connect. (Assuming I understood everything correctly in my quick debugging.) This causes the connection, despite being created as an HTTPS connection, to be established as HTTP, which Amazon refuses.
The text was updated successfully, but these errors were encountered: