.htaccess does not support php5

Which version of Apache are you using? I only have PHP 5 installed under an Apache 2 box.
Do you happen to know if the PHP module name changes depending on Apache 1 or 2?

Looking at the PHP documentation shows the following example for configuration changes:

<IfModule mod_php5.c>
  php_value include_path ".:/usr/local/lib/php"
  php_admin_flag safe_mode on
</IfModule>
<IfModule mod_php4.c>
  php_value include_path ".:/usr/local/lib/php"
  php_admin_flag safe_mode on
</IfModule>
<IfModule mod_php3.c>
  php3_include_path ".:/usr/local/lib/php"
  php3_safe_mode on
</IfModule>

But, there's a couple of comments saying that you need for Apache2 on both FreeBSD and Windows. So, I've added another block to catch PHP5 on Apache1.

Anyone care to test the attached patch?

No patch attached.

stupid attachment discarding preview....

I believe "sapi_apache2" was ONLY used in PHP4 under Apache 2, so we can't really label that one as being PHP5. If they merged the modulename to just mod_php5.c, for both Apache 1 and 2, that'd be the most ideal (and based on their documentation, that's what it looks like). I don't have time to make a patch now, but I'd like to see one that does mod_php4.c first, then the sapi_apache2.c, and then mod_php5.c, along with documentation stating that "the first is for PHP 4 under Apache 1, the second for PHP 4 under Apache 2, and the third for PHP 5 under either version".

Awesome for your interest, openwereld. As for issue assignation, it is only used when you assign an Issue to *yourself* - to say "I will most assuredly take command of this issue and see it through to the bitter, bitter end." It is never used by one developer assigning it to another developer (who may not have a care in the world about the actual problem). So, if you'd like to make a patch for it, and follow it through religiously, have a blast! Go ahead and make one and "Assign" the issue to yourself. Note, of course, as drewish did, you certainly don't HAVE to assign the issue to yourself - doing so is more of a "no one touch this - I got it. No, really. All mine. MINE! AHAHHAHAhahAH!" sorta thing.

here's a patch based on Morbus Iff's suggestions.

Just a comment.

Drupal needs PHP to run, and all those commands set the same exact PHP settings, so why use IfModule? Why not leave the supplied .htaccess with:

  php_value magic_quotes_gpc                0
  php_value register_globals                0
  php_value session.auto_start              0

Because PHP is not *always* run as a module - it could be running as a CGI, through FastCGI, or something else entirely, in which case, those directives in the .htaccess file would cause a 500 Internal Server Error (since Apache wouldn't recognize them as part of it's loaded list of commands).

Ah, I haven't thought about that. Thanks

Made some minor style changes.

Committed to HEAD.