recategorize

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.

Hm, but then the problem would also accour with other languages... but it doesn't.

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.

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.

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?

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.

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.

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

So now i've setup a 'test-suite'...
HTTP-Version: http://xmail.linux-de.org/test/
HTTPS-Version: https://mail.linux-de.org/test/

There are php.html, perl.html and ruby.html... all cgi-scripts printing
the ENV-Vars in a frameset.
PHP will fail nearly every time in one frame at minimum, the others
(perl and ruby) work nearly every time correct (it's absolutely
acceptable).

So now tell me, is it an PHP-Problem or Apache2? (I myself think again
it's php).

As explained on the apache-users list, this cannot be a PHP bug.