We're not the first to see the problem with https failing in a child process. There's a thread about it on the libcurl list. The lead developer of libcurl doesn't quite seem to know what's causing it. He speculates that perhaps it is an issue with OpenSSL. It doesn't seem to play nicely with fork(). His suggestion is to call curl_global_cleanup before the fork and curl_global_init after the fork. That's not really an option for us. I'd like to come up with another way of implementing background downloads if I can, perhaps by running curl_easy_perform in a separate thread? But that will be so ugly.
PS. As a point of comparison, I'm running OpenSSL 1.0.1I -- Chris _______________________________________________ Edbrowse-dev mailing list [email protected] http://lists.the-brannons.com/mailman/listinfo/edbrowse-dev
