blob: 97b31b5a10fb5b65109802c85ddf6a400a14045e (
plain) (
blame)
1
2
3
4
5
6
7
8
9
10
11
12
13
14
15
16
17
18
19
20
21
22
23
24
25
26
27
28
29
30
31
32
33
34
35
36
37
38
39
40
41
42
43
44
45
46
|
----------------------------------------------------------------
For help on using this module, please see the suPHP homepage:
http://www.suphp.org/
Using suPHP can break some PHP-scripts, because of Apache's CGI
interface.
-----------------------------------------------------------------
-----------------------------------------------------------------
For those migrating from suPHP 0.5.x, be aware there are many
changes since 0.6.x that can cause your current Apache environment
to stop working or behave oddly. Here are two migration tips:
suPHP now uses a configuration file for runtime configuration.
The file is located at:
/usr/local/etc/suphp.conf
...but *has not* been created for you. A sample configuration
file has been installed here:
/usr/local/etc/suphp.conf-example
This means that many of the make.conf(5) knobs for the
www/suphp port are no longer used, and are modifiable in
real-time; thus, things like WITHOUT_CHECKPATH and SUPHP_PATH
are no longer needed. Instead, edit the config file.
Equally as important, suPHP no longer uses a static MIME type
for determining what content get handled by suPHP. In 0.5.x,
you used the following Apache directives:
suPHP_Engine on
AddType application/x-httpd-php .php
AddHandler x-httpd-php .php
Since suPHP 0.6.x, you should use the following:
suPHP_Engine on
AddType application/x-httpd-php .php
suPHP_AddHandler application/x-httpd-php
Otherwise, Apache will begin serving PHP files as downloadable
content, rather than parse them with the PHP interpreter.
-----------------------------------------------------------------
|
