| 1 | suphp (0.7.1-1) unstable; urgency=low |
| 2 | |
| 3 | To allow mod_suphp to work at the same time as mod_php, handler name was |
| 4 | renamed from application/x-httpd-php to application/x-httpd-suphp in both |
| 5 | suphp and apache configuration files. |
| 6 | You must check that any other suphp statements in your apache configuration |
| 7 | files uses the same syntax. |
| 8 | |
| 9 | -- Emmanuel Lacour <elacour@home-dn.net> Mon, 03 Aug 2009 15:31:37 +0200 |
| 10 | |
| 11 | suphp (0.6.2-2) unstable; urgency=low |
| 12 | |
| 13 | To match the same behaviour as mod_php, AddHandler was replaced by AddType |
| 14 | and x-httpd-php by application/x-httpd-php in both suphp configuration files. |
| 15 | You must check that any other suphp statements in your apache configuration |
| 16 | files uses the same syntax. |
| 17 | |
| 18 | -- Emmanuel Lacour <elacour@home-dn.net> Sun, 14 Oct 2007 19:42:30 +0200 |
| 19 | |
| 20 | suphp (0.6.0-1) unstable; urgency=low |
| 21 | |
| 22 | This new release introduce a runtime configuration file |
| 23 | (/etc/suphp/suphp.conf) and a new configuration option for apache/apache2. |
| 24 | You must now add the following line in your apache/apache2 configuration to |
| 25 | make suphp active for php scripts: |
| 26 | |
| 27 | suPHP_AddHandler x-httpd-php |
| 28 | |
| 29 | -- Emmanuel Lacour <elacour@home-dn.net> Sun, 2 Oct 2005 11:09:21 +0200 |
| 30 | |