On Sat, Mar 07, 2009 at 05:30:16PM +0100, Emmanuel Lacour wrote: > On Mon, Mar 02, 2009 at 08:19:50AM +0100, Sylvain Beucler wrote: > > Package: libapache2-mod-suphp > > Version: 0.6.2-3 > > Severity: normal > > > > The default configuration changed from: > > AddHandler x-httpd-php .php .php3 .php4 .php5 .phtml > > to: > > AddType application/x-httpd-php .php .php3 .php4 .php5 .phtml > > > > In my sites configuration files I had lines like: > > AddHandler x-httpd-php .php .php3 .php4 .phtml > > so the upgrade essentially disabled PHP and distributed the PHP source code > > instead (since "application/" was prepended). > > > > This warrants a piece in NEWS.Debian.gz (and this would also make it clear > > that previous documentation in that file is now obsolete). > > > > Humm yes, you're right a notice in NEWS.Debian.gz would really help > upgrades, unfortunatly it's too late for lenny :( > > I'm going to upload a fix anyway.
It's also worth nothing that new configuration gives mod-php5 priority over suPHP, while on the contrary mod-php5 was inhibited before. Not sure that the priority is the same on all platforms (both modules attempt to handle application/x-httpd-php) but that's what I get on two i386 boxes. There's a priority conflict between mod-php5 and mod-suphp while there wasn't one in the previous configuration. -- Sylvain -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
