We read every piece of feedback, and take your input very seriously.
To see all available qualifiers, see our documentation.
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
I am getting a warning I have never seen before when creating an audience in SDK version 2.3.1, Python version 2.7.9:
InsecurePlatformWarning: A true SSLContext object is not available. This prevents urllib3 from configuring SSL appropriately and may cause certain SSL connections to fail. For more information, see https://urllib3.readthedocs.org/en/latest/security.html#insecureplatformwarning.
After reading through the link, it appears that this is related to an incompatibility with urllib3 and Python 2.7.
Is there actually a security hole here or is this just an overly-cautious warning?
The text was updated successfully, but these errors were encountered:
Are you sure you got this on Python 2.7.9? It should be fixed on that version.
In any case, it's probably not a security issue for connecting to the Graph API, because graph.facebook.com doesn't use either TLS compression or SNI. See urllib3/urllib3#557 (comment) and https://www.ssllabs.com/ssltest/analyze.html?d=graph.facebook.com
Sorry, something went wrong.
You can fix this issue with the following pip command: pip install requests[security]
pip install requests[security]
More info: http://stackoverflow.com/questions/29134512/insecureplatformwarning-a-true-sslcontext-object-is-not-available-this-prevent
No branches or pull requests
I am getting a warning I have never seen before when creating an audience in SDK version 2.3.1, Python version 2.7.9:
After reading through the link, it appears that this is related to an incompatibility with urllib3 and Python 2.7.
Is there actually a security hole here or is this just an overly-cautious warning?
The text was updated successfully, but these errors were encountered: