You should not have to choose

Hi. In some situations you have to choose if you want to use the cgi-version of PHP or the apache module. I don't think this is good. You should be able to do everything no matter what kind of PHP version you use. For an example, by using the cgi-version and suEXEC it's possible to: 1) Run PHP-scripts with the owners UID. But it's not possible to: 1) Send headers like HTTP 401, because Apache will add Content-type: text/html before your HTTP-header. 2) Use PHP-scripts that uses the variable $SCRIPT_NAME. 3) Achieve the same performence as when using the mod_php version. The HTTP question can be solved by: 1) Renaming the php binary to nph-php, but then you will have to: 2) Create headers for ALL you scripts, and that's not the easiest thing in the world, the headers are not the same in every situation. I think it would be a very good idea if you could suEXEC php-scripts even if you use the module version of PHP. I know this is a webserver problem, but there must be a way to solve it anyway. Like, creating a Apache-patch that the user can choose to apply or not. I hope someone one day figures out a solution for this problem. And if the suEXEC feature existed in the module version of PHP, many ISPs would stop using the cgi-version. Then the statistics of how many users PHP has would become more reliable. This is a difficult problem to solve, I know, but I think the great developers of PHP can do it! No doubt about it. Thanks for the most useful module for Apache ever! PHP is the future! Best regards, Joel Jacobson, student, Sweden/Stockholm.