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

From: Date: Thu, 31 Jan 2002 03:17:12 +0000
Subject: Bug #15307 Updated: Segmentation fault if cURL tries to get a page and the server returns nothing.
References: 1  Groups: php.dev 
Request: Send a blank email to php-dev+get-78643@lists.php.net to get a copy of this message
ID: 15307 Comment by: jacob@siamesecode.com Reported By: jacob@siamesecode.com Status: Open Bug Type: cURL related Operating System: Linux 2.4.x PHP Version: 4.1.1 New Comment: One more thing - I'm using https protocol for the transfer. Previous Comments: ------------------------------------------------------------------------ [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

« previous php.dev (#78643) next »