Bug #78891 [Com]: Bug with CURL completely stopped working

From: Date: Sat, 30 Nov 2019 17:06:48 +0000
Subject: Bug #78891 [Com]: Bug with CURL completely stopped working
References: 1  Groups: php.bugs 
Request: Send a blank email to php-bugs+get-223969@lists.php.net to get a copy of this message
Edit report at https://bugs.php.net/bug.php?id=78891&edit=1

 ID:                 78891
 Comment by:         gilperon at gmail dot com
 Reported by:        gilperon at gmail dot com
 Summary:            Bug with CURL completely stopped working
 Status:             Feedback
 Type:               Bug
 Package:            Unknown/Other Function
 Operating System:   all
 PHP Version:        7.2.25
 Block user comment: N
 Private report:     N

 New Comment:

nikic@php.net thanks for your attention. I can easily reproduce this bug installing LAMP on a CENTOS
7 new server on Linode. Just fire a cloud server, install lamp with PHP using 7.2.25 and the bug
happens.

Using file_get_contents the bug does not happen. Only with CURL. Also, the CURL code that I provided
you, does not return any error, just an empty string when the requested domain contains HTTPS
protocol. 

There is no error reported at error_log of Apache!

Regarding the version of the libcurl I executed the code "var_dump( curl_version() );" and
I got this:



array(9) {
  ["version_number"]=>
  int(466176)
  ["age"]=>
  int(3)
  ["features"]=>
  int(558781)
  ["ssl_version_number"]=>
  int(0)
  ["version"]=>
  string(6) "7.29.0"
  ["host"]=>
  string(23) "x86_64-redhat-linux-gnu"
  ["ssl_version"]=>
  string(8) "NSS/3.36"
  ["libz_version"]=>
  string(5) "1.2.7"
  ["protocols"]=>
  array(20) {
    [0]=>
    string(4) "dict"
    [1]=>
    string(4) "file"
    [2]=>
    string(3) "ftp"
    [3]=>
    string(4) "ftps"
    [4]=>
    string(6) "gopher"
    [5]=>
    string(4) "http"
    [6]=>
    string(5) "https"
    [7]=>
    string(4) "imap"
    [8]=>
    string(5) "imaps"
    [9]=>
    string(4) "ldap"
    [10]=>
    string(5) "ldaps"
    [11]=>
    string(4) "pop3"
    [12]=>
    string(5) "pop3s"
    [13]=>
    string(4) "rtsp"
    [14]=>
    string(3) "scp"
    [15]=>
    string(4) "sftp"
    [16]=>
    string(4) "smtp"
    [17]=>
    string(5) "smtps"
    [18]=>
    string(6) "telnet"
    [19]=>
    string(4) "tftp"
  }
}


Previous Comments:
------------------------------------------------------------------------
[2019-11-30 13:09:13] nikic@php.net

This issue is almost certainly not on the PHP side, but either due to a libcurl update (maybe you
pulled one in together with a PHP update?) or a misconfiguration of the certificate store (most
likely).

The fact that this happens with just curl, that there have been no recent code changes (in PHP) in
this area, and the issue is not reproducible by other people (I just tried your code, works just
fine) is a pretty strong indication of that.

To say more here, at the very least it would be important to know a) what error curl reports and b)
what libcurl version you're using and whether it was updated recently.

------------------------------------------------------------------------
[2019-11-30 12:30:55] cmb@php.net

Sorry!

------------------------------------------------------------------------
[2019-11-30 12:13:24] gilperon at gmail dot com

cmb@php.net -> clearly you didnt read this bug report! It's different from ANY of the other
bugs I reported!

Now, the CURL simply does not work. It does not matter if you will open a database connection
previsouly or if you create a previous connection with SSL. No!

This BUG HAPPENS SIMPLY USING CURL ONCE!

------------------------------------------------------------------------
[2019-11-30 07:47:16] cmb@php.net

Please stop reporting the same issue over and over again.  Thanks.

------------------------------------------------------------------------
[2019-11-30 01:45:03] gilperon at gmail dot com

Description:
------------
The test script does not work anymore using Curl with any destination that is HTTPS. If you try any
destination with HTTP it will work just fine. On .24 version this bug ONLY would happen when you
first connected to a database and after that tried to use CURL. But now, this bug affects using only
CURL and doesnt need to connect to database to trigger it anymore. This bug just got a lot more
serious.



Test script:
---------------
<?php

$curl = curl_init();

$opts = array();

$opts[CURLOPT_URL] = "https://www.sitepor500.com.br";

curl_setopt_array($curl,$opts);

echo curl_exec($curl);

?>

Expected result:
----------------
I should see the content of the requested url

Actual result:
--------------
Nothing is shown.


------------------------------------------------------------------------



--
Edit this bug report at https://bugs.php.net/bug.php?id=78891&edit=1


Thread (16 messages)

« previous php.bugs (#223969) next »