Uses CURLOPT_ERRORBUFFER as a more informative source of error messages for network errors when encountered. if error buffer is not available falls back to old way, which is also the recommended curl method via the example in the error buffer documentation.
example error message before:
"curlCode: 7, Couldn't connect to server"
after
"Failed to connect to localhost port 443 after 1 ms: Couldn't connect to server"
Check all that applies:
[x] Did a review by yourself.
[x] Added proper tests to cover this PR. (If tests are not applicable, explain.)
[x] Checked if this PR is a breaking (APIs have been changed) change.
[x] Checked if this PR will not introduce cross-platform inconsistent behavior.
[x] Checked if this PR would require a ReadMe/Wiki update.
Check which platforms you have built SDK on to verify the correctness of this PR.
[x] Linux
[x] Windows
[ ] Android
[x] MacOS
[ ] IOS
[ ] Other Platforms
By submitting this pull request, I confirm that you can use, modify, copy, and redistribute this contribution, under the terms of your choice.
Issue #, if available: TBD
Description of changes:
Uses CURLOPT_ERRORBUFFER as a more informative source of error messages for network errors when encountered. if error buffer is not available falls back to old way, which is also the recommended curl method via the example in the error buffer documentation.
example error message before:
"curlCode: 7, Couldn't connect to server"after
"Failed to connect to localhost port 443 after 1 ms: Couldn't connect to server"Check all that applies:
Check which platforms you have built SDK on to verify the correctness of this PR.
By submitting this pull request, I confirm that you can use, modify, copy, and redistribute this contribution, under the terms of your choice.