-
-
Notifications
You must be signed in to change notification settings - Fork 275
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
ssl requests do not get passed through correctly #35
Comments
Yeah, I'm having the same problem (version 0.5.9). Using import urllib2
from httpretty import HTTPretty
url = 'https://www.cloudflare.com/ips'
HTTPretty.reset()
HTTPretty.enable()
response = urllib2.urlopen(url) (I've been getting the same thing from a couple of other domains, too, so it's not specific to CloudFlare, though that error message seems to be specific to nginx.) |
This appears to be due to HTTPretty not implementing a proper SSL wrapper. |
Has anyone come up with a workaround for this? |
I fixed this issue in my fork: https://github.com/pegler/httpretty I also added the ability to pass in a function to register_uri that accepts the data sent, so that it can respond to dynamically to what was sent instead of having to hardcode everything. It was a long time ago, and I don't really remember making those changes. |
+1 |
+1 this is fairly recent |
Hey, folks, please refrain from +1 or "thumbs up" or "me too" comments. Contrary to what it might appears to you, such comments are not productive and might even lead to the project owners disabling comments for the issue. We don't need this, really. |
@kostix sorry but this is def a way to prioritise issue priority and is quite commonly accepted. I have managed to resolve the issue as there appears to be some conflict in the lib dependencies (as expected).. deleted the vm and then recreate with unpinned dependencies should all resolve "nicely" |
Hey @rosscdh, |
Hey Yarden, Am afk atm but in brief. Reinstall brew OpenSSL and then reinstall all the Will send version numbers later On Thursday, 24 March 2016, Yarden Sachs notifications@github.com wrote:
|
Any news ? |
HTTPretty needs some TLC which I intend to work on ASAP 😬 |
As demonstrated by the shell session below, there is a bug in how ssl is handled when passing through HTTPretty. I didn't see a note in the readme about it having this limitation.
The text was updated successfully, but these errors were encountered: