On Mon, Sep 17, 2012 at 4:35 PM, Konstantin Khomoutov <[email protected]> wrote: [...snip...] > I'm by no means an expert in setting up this sort of complicated stuff > in Apache, so I can't really tell if this new change in php5 packaging > introduces a regression or it's just a misconfiguration on my part. > In the latter case, it would be cool if someone could provide me with > any hints on how to configure handling of PHP scripts by FastCGI > server-wide (rather than patching each PHP-enabled vhost using that > <FilesMatch> override). Any suggestions?
The NEWS file for php5-cgi which you ought to read when upgrading reads: --cut here-- php5 (5.4.4-5) unstable; urgency=low Please be aware that the mime-support package has dropped non-standard definitions for PHP that might affect any systems using PHP 5 running as CGI or FastCGI. The following definitions were dropped: application/x-httpd-php phtml pht php application/x-httpd-php-source phps application/x-httpd-php3 php3 application/x-httpd-php3-preprocessed php3p application/x-httpd-php4 php4 application/x-httpd-php5 php5 The php5-cgi package mitigates any known issues by creating a (dummy) apache2 module php5_cgi with a configuration containing handlers for all previously defined extensions. ****Even though we believe that this configuration should keep your PHP scripts interpreted, it might be a good idea to check your apache2 site-wide configuration as well as any specific PHP configuration for websites running on your system.**** As far as we know definitions from the mime-support packages are not used in any other webserver included in Debian, but it might affect any application which relies on system MIME types to interpret PHP files. --cut here-- I am currently thinking how to accomodate all types of users (cgi and fastcgi), but I haven't come to any conclusion yet. If you have an idea, how to not break the configuration for neither CGI nor FastCGI users, feel free to share. O. -- Ondřej Surý <[email protected]> -- To UNSUBSCRIBE, email to [email protected] with a subject of "unsubscribe". Trouble? Contact [email protected]
