Bug #15307 Updated: Segmentation fault if cURL tries to get a page and the server returns nothing.

ID: 15307 Updated by: eles.zoltan@creditreform.hu Reported By: jacob@siamesecode.com Status: Open Bug Type: cURL related Operating System: Linux 2.4.x PHP Version: 4.1.1 New Comment: I've experienced the same problem. Additionally info: it works fine with PHP 4.0.6. Previous Comments: ------------------------------------------------------------------------ [2002-01-30 22:22:29] jacob@siamesecode.com Oops - that's wrong; the OpenSSL option is installed in libcurl, but this particular segfault happened using plain old http. ------------------------------------------------------------------------ [2002-01-30 22:17:12] jacob@siamesecode.com One more thing - I'm using https protocol for the transfer. ------------------------------------------------------------------------ [2002-01-30 22:14:25] jacob@siamesecode.com I found this behavior while building a client-server system that uses cURL to get data from the server; when my server-side script didn't return anything at all, it caused the client side Apache process to actually die with a signal 11. I have the latest libcurl and the latest PHP, and I've just tried updating Apache to see if that affects the behavior (it doesn't, but it seemed like a good excuse to get my development system up to date). The only option I'm using for cURL is CURLOPT_RETURNTRANSFER. I'm not sure if this means anything, but if I run cURL from the command line, it doesn't segfault when visiting the same totally empty URL. Thanks for PHP! It's good, fast, AND cheap ------------------------------------------------------------------------ -- Edit this bug report at http://bugs.php.net/?id=15307&edit=1