-
Notifications
You must be signed in to change notification settings - Fork 501
New issue
Have a question about this project? # for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “#”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? # to your account
verify => false does not work with fsockopen #310
Comments
soulseekah
added a commit
to soulseekah/Requests
that referenced
this issue
Feb 11, 2018
See WordPress#310 fsockopen will fail
soulseekah
added a commit
to soulseekah/Requests
that referenced
this issue
Feb 11, 2018
As per the documentation setting verify to false suppresses all SSL checks. Fixes WordPress#310
soulseekah
added a commit
to soulseekah/Requests
that referenced
this issue
Feb 11, 2018
The `request_multi` method does not take into account the verify option, unlike `request`. Moved the verify logic into `setup_handler` which does all the `curl_setopt` calls anyway and is called from both the multiple and single request options. With tests. Contigent on WordPress#310 for fsockopen verify fix. Fixes WordPress#294
soulseekah
added a commit
to soulseekah/Requests
that referenced
this issue
Sep 26, 2019
See WordPress#310 fsockopen will fail
# for free
to join this conversation on GitHub.
Already have an account?
# to comment
The
Requests_Transport_fsockopen
still throws an exception regardless of theverify
option on invalid SSL. Test case incoming.The text was updated successfully, but these errors were encountered: