#20356 [Opn->Bgs]: PHP delivers sourcecode

ID: 20356 User updated by: janus@linux-de.org Reported By: janus@linux-de.org -Status: Open +Status: Bogus Bug Type: *Web Server problem Operating System: linux 2.4.19 PHP Version: 4CVS-2002-11-11 New Comment: I've to excuse. Recently i got the same problem with one of my ruby-scripts, i'm sorry for the rebukes. Best regards, simon Previous Comments: ------------------------------------------------------------------------ [2002-11-13 08:02:06] janus@linux-de.org I've posted it to the apache-mailinglist... i need a solution, so i've to ask around :) If i've new informations, i'll post'em here. ------------------------------------------------------------------------ [2002-11-11 12:20:42] janus@linux-de.org Which one? PHP or another one? Ther error occours even if i let the script print "hello world". It's really boring... i only want to run php in a safe way... and because the perchild-mpm for apache2 isn't working yet, i have to use suexec, so every script runs with the right permission, that's the only reason why i'm using the cgi-version of php. If there's another safe way, i'll take a look at it. ------------------------------------------------------------------------ [2002-11-11 11:13:45] rasmus@php.net Your CGI script does not send the HTTP/1.1 200 OK response, the web server does. No matter what the CGI script returns, the server cannot legally send anything before that header. If it does then the server is broken by definition. There is just no arguing that point. But what exactly does your cgi script generate when you run it from the command line? ------------------------------------------------------------------------ [2002-11-11 11:10:07] janus@linux-de.org 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. ------------------------------------------------------------------------ [2002-11-11 10:47:23] rasmus@php.net 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. ------------------------------------------------------------------------ The remainder of the comments for this report are too long. To view the rest of the comments, please view the bug report online at http://bugs.php.net/20356 -- Edit this bug report at http://bugs.php.net/?id=20356&edit=1