Join GitHub today
GitHub is home to over 50 million developers working together to host and review code, manage projects, and build software together.Sign up
Some fixes for `curl_global_sslset()` when built with a single SSL backend #3346
While working on #3345, I realized that there were a couple of issues with the
This PR fixes both issues.
It is allowed to call that function with id set to -1, specifying the backend by the name instead. We should imitate what is done further down in that function to allow for that. Signed-off-by: Johannes Schindelin <email@example.com>
When compiled with a single SSL backend, Curl_ssl is never set to Curl_ssl_multi, but to that single backend from the beginning. When the caller tries to set the SSL backend to a different backend than the one that was compiled in, in this scenario we should not say that it is too late to set the SSL backend, but that it is an unknown backend to begin with. Signed-off-by: Johannes Schindelin <firstname.lastname@example.org>