ID: 20356 User updated by: [EMAIL PROTECTED] Reported By: [EMAIL PROTECTED] Status: Open -Bug Type: Apache2 related +Bug Type: *Web Server problem Operating System: linux 2.4.19 PHP Version: 4CVS-2002-11-11 New Comment:
Same for PHP i would say, but that doesn't help now. But the CGI has to send the header itself, so i think it is logical that apache can't be the source of the problem. My perl scripts work fine with SSL, python and ruby are also doing the right output, only php doesn't, so why should i believe that it's an apache2 problem? Or are you just pushing the blame on someone else? Furthermore i've got the same problems with apache1, as others too. Previous Comments: ------------------------------------------------------------------------ [2002-11-11 10:47:23] [EMAIL PROTECTED] That doesn't change the fact that A CGI can architecturally not cause what you are seeing and if it does then the server is buggy. And yes, Apache2 is a very buggy server at this point and should not be used in production. ------------------------------------------------------------------------ [2002-11-11 10:42:47] [EMAIL PROTECTED] Hm, but then the problem would also accour with other languages... but it doesn't. ------------------------------------------------------------------------ [2002-11-11 10:19:24] [EMAIL PROTECTED] This looks like an Apache2 bug to me. When running PHP as a CGI it is the web server that is responsible for sending back the 200 OK and making sure nothing gets sent back before it. PHP as a CGI has been tested for years with dozens of other web servers. ------------------------------------------------------------------------ [2002-11-11 06:51:39] [EMAIL PROTECTED] recategorize ------------------------------------------------------------------------ [2002-11-11 06:40:40] [EMAIL PROTECTED] It's just like http://bugs.php.net/bug.php?id=14751 Except now i'm confirming that with Apache2 in SSL-mode. It has to be a PHP problem, because a HTTP-Header looks like this: ---------- 0 HTTP/1.1 200 OK Date: Mon, 11 Nov 2002 11:31:32 GMT Server: Apache/2.0.43 (Unix) mod_ssl/2.0.43 OpenSSL/0.9.6g ---------- Yes, THERE IS a "0\n\n" before the real header... and that happens ONLY with PHP, all other CGI-Scripts work fine. PHP is configured like this in htt.conf: ---------- ScriptAlias /php4-cgi-bin-dir "/pool/system/php4/bin" Action application/x-httpd-php /php4-cgi-bin-dir/php AddHandler application/x-httpd-php .php ---------- ------------------------------------------------------------------------ -- Edit this bug report at http://bugs.php.net/?id=20356&edit=1
