head	1.6;
access;
symbols
	RELEASE_8_3_0:1.6
	RELEASE_9_0_0:1.6
	RELEASE_7_4_0:1.6
	RELEASE_8_2_0:1.6
	RELEASE_6_EOL:1.6
	RELEASE_8_1_0:1.6
	RELEASE_7_3_0:1.6
	RELEASE_8_0_0:1.6
	RELEASE_7_2_0:1.6
	RELEASE_7_1_0:1.4
	RELEASE_6_4_0:1.4
	RELEASE_5_EOL:1.4
	RELEASE_7_0_0:1.2
	RELEASE_6_3_0:1.2
	PRE_XORG_7:1.2
	RELEASE_4_EOL:1.2
	RELEASE_6_2_0:1.2
	RELEASE_6_1_0:1.1
	RELEASE_5_5_0:1.1
	RELEASE_6_0_0:1.1
	RELEASE_5_4_0:1.1
	RELEASE_4_11_0:1.1
	RELEASE_5_3_0:1.1
	RELEASE_4_10_0:1.1
	RELEASE_5_2_1:1.1
	RELEASE_5_2_0:1.1
	RELEASE_4_9_0:1.1;
locks; strict;
comment	@# @;


1.6
date	2009.03.20.07.33.13;	author lwhsu;	state Exp;
branches;
next	1.5;

1.5
date	2009.02.09.21.04.05;	author miwi;	state Exp;
branches;
next	1.4;

1.4
date	2007.12.12.17.27.49;	author koitsu;	state Exp;
branches;
next	1.3;

1.3
date	2007.12.11.20.38.58;	author koitsu;	state Exp;
branches;
next	1.2;

1.2
date	2006.05.10.22.23.14;	author pav;	state Exp;
branches;
next	1.1;

1.1
date	2003.06.25.06.50.52;	author daichi;	state Exp;
branches;
next	;


desc
@@


1.6
log
@- Update to 0.7.1

PR:		ports/132768
Submitted by:	Yi-Jheng Lin <yzlin AT cs.nctu.edu.tw> (maintainer)
@
text
@----------------------------------------------------------------
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.
-----------------------------------------------------------------

-----------------------------------------------------------------
For those versions upgraded from 0.6.x to 0.7.x. There are some
new features and changes for the configuration file:

    - Multiple path (with patterns) & variable substitution
      support for docroots
    - Double-quoted strings at section '[handlers]'
      ex. application/x-httpd-php="php:/usr/local/bin/php-cgi"

These changes may lead to internal server error if without
modifications of the configuration file from previous version.
-----------------------------------------------------------------
@


1.5
log
@- Update to 0.7.0
- Pass maintainership to submitter

PR:		131451
Submitted by:	Yi-Jheng Lin <yzlin@@cs.nctu.edu.tw>
@
text
@d47 13
@


1.4
log
@Fix for previous commit; user reported privately that Apache would print
"Cannot get media type from 'x-httpd-php'" as a warning in the ErrorLog.  Issue
caused by incorrect AddType syntax.

This commit fixes the pkg-message syntax described, as well as the example
suphp.conf to reflect the proper type (value "application/x-httpd-php", not
"x-httpd-php").

Submitted by:	<dark@@aspu.ru>
@
text
@d4 1
a4 1
    	http://www.suphp.org/
d12 1
a12 1
changes in 0.6.x that can cause your current Apache environment
d23 1
a23 1
	/usr/local/etc/suphp.conf-example
d34 1
a34 1
	suPHP_Engine on
d38 1
a38 1
In suPHP 0.6.x, you should use the following:
d40 1
a40 1
	suPHP_Engine on
a46 1

@


1.3
log
@Upgrade to suPHP 0.6.2.  This upgrade is quite major; it introduces
numerous features necessary for hosting, adds the use of a configuration
file (vs. compile-time settings) for configuration details, and is
presently supported by the software author.

Changes to httpd.conf are required for this to work, otherwise PHP
content is offered for download and not parsed.  pkg-message contains
full migration details, but here's the simple version:

suPHP 0.5.2                            suPHP 0.6.2
===========                            ===========
AddType application/x-httpd-php .php   AddType x-httpd-php .php
AddHandler x-httpd-php .php            suPHP_AddHandler x-httpd-php

Tested on RELENG_6 and RELENG_7, using Apache 2.0 and 2.2, with the
help of the PR submitter.

Testing for Apache 1.3 was not performed, thus the port requires the
use of 2.0 or later.  suPHP 0.6.2 does support Apache 1.3, but I'll
need someone running 1.3 to work with me on fixing the port to support
it, if desired.

PR:		ports/116281
Submitted by:	Vladimir Korkodinov <viper@@perm.raid.ru>
@
text
@d41 2
a42 2
        AddType x-httpd-php .php
        suPHP_AddHandler x-httpd-php
@


1.2
log
@- Fix for recent PHP changes, correct path to php-cgi binary
- Add user-overridable variable SUPHP_PATH
- Cosmetics

PR:		ports/97047
Submitted by:	Jeremy Chadwick <freebsd@@jdc.parodius.com> (maintainer)
@
text
@a1 3
You have installed mod_suphp, a module that provides a wrapper 
for PHP for Apache.

a5 1
Important hints:
d9 39
@


1.1
log
@Add suphp 0.2.2,
suPHP is a combination which provides a wrapper
for PHP.

PR:		42790
Submitted by:	Clement Laforet <sheepkiller@@cultdeadsheep.org>
@
text
@d6 2
a7 1
    	http://www.suphp.org
@

