This is a discussion on CURL: Result on console and in PHP are different within the PHP Language forums, part of the PHP Programming Forums category; On Wed, 31 Oct 2007 12:31:29 +0100, Paul van Brouwershaven <p.vanbrouwershaven@gmail.com> wrote: > ...
|
|||||||
| FAQ | Members List | Calendar | Search | Today's Posts | Mark Forums Read |
|
|||
|
On Wed, 31 Oct 2007 12:31:29 +0100, Paul van Brouwershaven
<p.vanbrouwershaven@gmail.com> wrote: > As saw the space problem just before you post, but this still doesn't > solve the problem that there is no value in the ssl_verify_result > result. > > If the SSL Certificate is wrong or right it always returns 0! > > I can check the result of the curl_exec to see if the certificate is > valid, but this doen't tell me what the problem is. Well, I get a clear: "SSL certificate problem, verify that the CA cert is OK. Details: error:14090086:SSL routines:SSL3_GET_SERVER_CERTIFICATE:certificate verify failed" ...with curl_error(), as I don't have the certificate. set verify peer to false would result in either this curl_error() output: SSL: certificate subject name 'www.verisign.com' does not match target host name 'verisign.com' [ssl_verify_result] => 0] Or no error with the right hostname: [ssl_verify_result] => 19] -- Rik Wasmus |
|
|||
|
On Oct 31, 1:04 pm, "Rik Wasmus" <luiheidsgoe...@hotmail.com> wrote:
> Well, I get a clear: > "SSL certificate problem, verify that the CA cert is OK. Details: > error:14090086:SSL routines:SSL3_GET_SERVER_CERTIFICATE:certificate verify > failed" > > ..with curl_error(), as I don't have the certificate. Ok found the problem, the curl_close($ch) was before the curl_error($ch) > set verify peer to false would result in either this curl_error() output: > SSL: certificate subject name 'www.verisign.com'does not match target > host name 'verisign.com' > [ssl_verify_result] => 0] > Or no error with the right hostname: > [ssl_verify_result] => 19] ssl_verify_result does not change in my results |
|
|||
|
Paul van Brouwershaven <p.vanbrouwershaven@gmail.com> wrote in
news:1193847270.228502.306510@22g2000hsm.googlegro ups.com: > On Oct 31, 1:04 pm, "Rik Wasmus" <luiheidsgoe...@hotmail.com> wrote: >> Well, I get a clear: >> "SSL certificate problem, verify that the CA cert is OK. Details: >> error:14090086:SSL routines:SSL3_GET_SERVER_CERTIFICATE:certificate >> verify failed" >> >> ..with curl_error(), as I don't have the certificate. > Ok found the problem, the curl_close($ch) was before the > curl_error($ch) > >> set verify peer to false would result in either this curl_error() >> output: SSL: certificate subject name 'www.verisign.com'does not >> match target host name 'verisign.com' >> [ssl_verify_result] => 0] > >> Or no error with the right hostname: >> [ssl_verify_result] => 19] > > ssl_verify_result does not change in my results are you still using "verisign.com" and not "www.verisign.com" ? |
|
|||
|
-------------------------------------------------------------------------------------------------- Panda IS 2008 has detected that this email could be spoofe Take maximum precautions, as spoofed emails could be the sign of a fraud attempt -------------------------------------------------------------------------------------------------- Paul van Brouwershaven wrote: > On Oct 31, 1:04 pm, "Rik Wasmus" <luiheidsgoe...@hotmail.com> wrote: >> Well, I get a clear: >> "SSL certificate problem, verify that the CA cert is OK. Details: >> error:14090086:SSL routines:SSL3_GET_SERVER_CERTIFICATE:certificate verify >> failed" >> >> ..with curl_error(), as I don't have the certificate. > Ok found the problem, the curl_close($ch) was before the > curl_error($ch) > >> set verify peer to false would result in either this curl_error() output: >> SSL: certificate subject name 'www.verisign.com'does not match target >> host name 'verisign.com' >> [ssl_verify_result] => 0] > >> Or no error with the right hostname: >> [ssl_verify_result] => 19] > > ssl_verify_result does not change in my results > > No, it won't. The request failed, so there is no info to get. -- ================== Remove the "x" from my email address Jerry Stuckle JDS Computer Training Corp. jstucklex@attglobal.net ================== -------------------------------------------------------------------------------------------------- Panda IS 2008 has detected that this email could be spoofe Take maximum precautions, as spoofed emails could be the sign of a fraud attempt -------------------------------------------------------------------------------------------------- |
|
|||
|
-------------------------------------------------------------------------------------------------- Panda IS 2008 has detected that this email could be spoofe Take maximum precautions, as spoofed emails could be the sign of a fraud attempt -------------------------------------------------------------------------------------------------- Jerry Stuckle wrote: > Paul van Brouwershaven wrote: >> On Oct 31, 1:04 pm, "Rik Wasmus" <luiheidsgoe...@hotmail.com> wrote: >>> Well, I get a clear: >>> "SSL certificate problem, verify that the CA cert is OK. Details: >>> error:14090086:SSL routines:SSL3_GET_SERVER_CERTIFICATE:certificate >>> verify >>> failed" >>> >>> ..with curl_error(), as I don't have the certificate. >> Ok found the problem, the curl_close($ch) was before the >> curl_error($ch) >> >>> set verify peer to false would result in either this curl_error() >>> output: >>> SSL: certificate subject name 'www.verisign.com'does not match target >>> host name 'verisign.com' >>> [ssl_verify_result] => 0] >> >>> Or no error with the right hostname: >>> [ssl_verify_result] => 19] >> >> ssl_verify_result does not change in my results >> >> > > No, it won't. The request failed, so there is no info to get. > Sorry - forgot to trim the anti-virus. Wish I could get it to stop doing that in newsgroups. -- ================== Remove the "x" from my email address Jerry Stuckle JDS Computer Training Corp. jstucklex@attglobal.net ================== -------------------------------------------------------------------------------------------------- Panda IS 2008 has detected that this email could be spoofe Take maximum precautions, as spoofed emails could be the sign of a fraud attempt -------------------------------------------------------------------------------------------------- |
|
|||
|
stuckle, why are you top posting? have you given up so quickly on your
position? "Jerry Stuckle" <jstucklex@attglobal.net> wrote in message news:apKdndHjGeZwKLXanZ2dnUVZ_hninZ2d@comcast.com. .. > > --------------------------------------------------------------------------------------------------- > Panda IS 2008 has detected that this email could be spoofed > > Take maximum precautions, as spoofed emails could be the sign of a fraud > attempt. > --------------------------------------------------------------------------------------------------- > Paul van Brouwershaven wrote: >> On Oct 31, 1:04 pm, "Rik Wasmus" <luiheidsgoe...@hotmail.com> wrote: >>> Well, I get a clear: >>> "SSL certificate problem, verify that the CA cert is OK. Details: >>> error:14090086:SSL routines:SSL3_GET_SERVER_CERTIFICATE:certificate >>> verify >>> failed" >>> >>> ..with curl_error(), as I don't have the certificate. >> Ok found the problem, the curl_close($ch) was before the >> curl_error($ch) >> >>> set verify peer to false would result in either this curl_error() >>> output: >>> SSL: certificate subject name 'www.verisign.com'does not match target >>> host name 'verisign.com' >>> [ssl_verify_result] => 0] >> >>> Or no error with the right hostname: >>> [ssl_verify_result] => 19] >> >> ssl_verify_result does not change in my results >> >> > > No, it won't. The request failed, so there is no info to get. > > -- > ================== > Remove the "x" from my email address > Jerry Stuckle > JDS Computer Training Corp. > jstucklex@attglobal.net > ================== > > --------------------------------------------------------------------------------------------------- > Panda IS 2008 has detected that this email could be spoofed > > Take maximum precautions, as spoofed emails could be the sign of a fraud > attempt. > --------------------------------------------------------------------------------------------------- > |
|
|||
|
Yes, there must be a failed status in the [ssl_verify_result]. Or a
success status in the [ssl_verify_result] but this value is always zore. A faild status should more logical because it can fail because of more then one reason. |