cURL and SSL issues

mr_zog

I am currently having issues with script that uses cURL through an SSL connection.

I receive the following error back from the gateway when posting.

(curl_exec returned FALSE, SSL certificate problem, verify that the CA cert is OK)

I have discussed this with the hosting techs and the cert is fine. It is running on a Win2k3 box with PHP 4.3.2.
The cURL config is :libcurl/7.10.5 OpenSSL/0.9.7b.

Is there something else that would need to be configured or added for proper use of SSL with PHP on Win2k3?

Here is the code(which came from another post here - thanks):

$url = 'https://www.ccprocessing.gateway.url';
$postfields = 'var=foo';    // for more vars, use HTTP GET format (even tho we're POSTing)

// prepare cURL library to do the POST
$ch = curl_init();

curl_setopt($ch, CURLOPT_RETURNTRANSFER, 1);

curl_setopt($ch, CURLOPT_URL, $url);
curl_setopt($ch, CURLOPT_POST, 1);                        // yes, do a post
curl_setopt($ch, CURLOPT_POSTFIELDS, $postfields);        // post fields, in HTTP 'GET' format

// use output buffering instead of direct echo to screen...
// (tho I think it's unnecessary with CURLOPT_RETURNTRANSFER turned on)
ob_start();
$return = curl_exec($ch);
ob_end_clean();

if (!$return) echo "(curl_exec returned FALSE, ".curl_error($ch).")<br>";

curl_close($ch); 

echo "return is $return";

// note that you'll probably want to use parse_str() to manage $return

Thanks in advance,

zyON

I'm having exactly the same problem.

Running PHP 4.3.3 on a Windows Server 2003 with IIS and with libcurl/7.10.5 OpenSSL/0.9.7b.

I'm really lost 🙁

pilitiger

My plateform is Windows 2000 Server + IIS + PHP.
I also encountered the same problem when I upgrade from PHP 4.2.2 to 4.3.3.
Is there any solution for this problem???

Weedpacket

Never heard of this myself, but it sounded like a cURL problem, so I went to that site and noted something in the FAQ that suggested something which is given in more detail on this page which may or may not be of benefit to the three of you.

If I'm right, remember that that took me all of six minutes to track down.

spotnyk

Worked with cURL quite a bit and had this problem connecting to one of our other boxes. Turned out that the admin had not correctly installed all the CHAIN certs correctly.

Alot of times the company that issues the cert is doing it under the authority of one or sometimes two or three other companies. Therefore they issue chain certs with the primary. Some browsers seem to not notice, or care. But cURL does.

Have you tried telling cURL to ignore cert issues. From what I know, it will ignore everything about a cert except if it is expired. But you should be able to tell it to ignore the signing.

Two cents.

Spot

bbaassiri

this is how i ignore ssl checking

curl_setopt( $ch , CURLOPT_SSL_VERIFYPEER , false );
curl_setopt( $ch , CURLOPT_SSL_VERIFYHOST , false );

racy_rick

bbaassiri;10885331 wrote:
this is how i ignore ssl checking
curl_setopt( $ch , CURLOPT_SSL_VERIFYPEER , false );
curl_setopt( $ch , CURLOPT_SSL_VERIFYHOST , false );[/QUOTE]
This worked for me. I was getting this error from a server I exchange xml with:

Error: SSL certificate problem, verify that the CA cert is OK. Details:
error:14090086:SSL routines:SSL3_GET_SERVER_CERTIFICATE:certificate verify failed

sneakyimp

I had this same problem and posted about it here. If the idea of turning off all SSL validation gives you the heebie-jeebies, then there is some (pretty long-winded) advice there about how to deal with the certificate stuff in a slightly more sophisticated fasion -- meaning you can add the cert of your target page to your certificate authority file rather than just accepting any old certificate from god knows who. Keep in mind that certificates are meant to verify the identity of someone you are communicating with. If you don't bother checking their validity, it pretty much defeats the purpose of using SSL.