[php-maint] Bug#594571: libapache2-mod-suphp: conflicts with libapache2-mod-php5

Julian Gilbey jdg at debian.org
Fri Aug 27 09:37:08 UTC 2010

Package: libapache2-mod-php5
Version: 0.7.1-1
Severity: important

When I have both mod-php5 and mod-suphp enabled, with the default
.load files in /etc/apache2/mods-enabled, opening a php document uses
mod-php5 rather than mod-suphp.

I think that the source of the problem is that apache sees *two*
"AddType" commands for .php* files in its configuration, and so it
uses the first one it sees, which is presumably mod-php5.

The effect of this is that the commands are run as the webserver user
rather than using suphp.  In the case that suphp is configured to
allow user directories to be used, this means that php files in
/home/*/public_html get served as raw files (i.e., as source) rather
than as processed php.

The only sensible solutions are probably:
(1) make libapache2-mod-suphp conflict with libapache2-mod-php5
(2) have the .conf file read something like:
           AddType application/x-httpd-suphp .suphp
    instead, and a readme which explains that either files should be
    suffixed with .suphp, or libapache2-mod-php5 should be uninstalled
    and the .conf file can then be modified back to the way it was.


More information about the pkg-php-maint mailing list