SuPHP on XMission - Revision history

Jab at 21:47, 14 January 2020

2020-01-14T21:47:28Z

← Older revision		Revision as of 15:47, 14 January 2020
Line 1:		Line 1:
			{{archived}}

	With the transition to Apache 2 servers, a new solution was needed to allow users to execute PHP scripts, while maintaining security. suPHP is a tool for executing PHP scripts with the permissions of their owners.		With the transition to Apache 2 servers, a new solution was needed to allow users to execute PHP scripts, while maintaining security. suPHP is a tool for executing PHP scripts with the permissions of their owners.

Cyeates at 18:34, 8 May 2009

2009-05-08T18:34:35Z

← Older revision		Revision as of 12:34, 8 May 2009
Line 1:		Line 1:
	~~{{archived}}~~
	With the transition to Apache 2 servers, a new solution was needed to allow users to execute PHP scripts, while maintaining security. suPHP is a tool for executing PHP scripts with the permissions of their owners.		With the transition to Apache 2 servers, a new solution was needed to allow users to execute PHP scripts, while maintaining security. suPHP is a tool for executing PHP scripts with the permissions of their owners.

Line 21:		Line 20:


	~~{{footer}}~~
	[[Category:Hosting Archives\|SuPHP on XMission]]		[[Category:Hosting Archives\|SuPHP on XMission]]

Mfrazier at 21:47, 18 March 2008

2008-03-18T21:47:01Z

← Older revision		Revision as of 15:47, 18 March 2008
Line 1:		Line 1:
			{{archived}}
	With the transition to Apache 2 servers, a new solution was needed to allow users to execute PHP scripts, while maintaining security. suPHP is a tool for executing PHP scripts with the permissions of their owners.		With the transition to Apache 2 servers, a new solution was needed to allow users to execute PHP scripts, while maintaining security. suPHP is a tool for executing PHP scripts with the permissions of their owners.

Line 18:		Line 19:
	The corresponding php.ini format is:		The corresponding php.ini format is:
	<pre>include_path = "/home/users/u/username/cgi-bin"</pre>		<pre>include_path = "/home/users/u/username/cgi-bin"</pre>


			{{footer}}
			[[Category:Hosting Archives\|SuPHP on XMission]]

Deadguy: new page

2007-07-29T00:58:38Z

new page

New page

With the transition to Apache 2 servers, a new solution was needed to allow users to execute PHP scripts, while maintaining security. suPHP is a tool for executing PHP scripts with the permissions of their owners.

Some users will have php configuration values in their .htaccess files. Some configuration lines won't work with suPHP - at least, not within the .htaccess file. In particular, "php_value" and "php_flag" values are the two that are problematic.

First, you must move all lines beginning with "php_value" and "php_flag" from your .htaccess file into a file called php.ini (in your public_html directory). Then, you must add a line to your .htaccess file like the one below (with "u" being the first letter of your username, and of course "username" being your actual username).
<pre>suPHP_ConfigPath /home/users/u/username/public_html</pre>

You will need to remove php_value and php_flag from ALL .htaccess files you may have. However, you only need to add the suPHP_ConfigPath line in the .htaccess file in your public_html directory only.

Secondly, you must make sure that the lines you put in php.ini are in the correct format:
<pre>setting_name = setting_value</pre>
Let's say you have the following line in your .htaccess file:
<pre>php_value register_globals 0</pre>
the corresponding php.ini format is as follows:
<pre>register_globals = Off</pre>
Notice how the value 0 becomes Off (without quotes) and 1 becomes On. If your php_value has quotes like the following, for example:
<pre>php_value include_path "/home/users/u/username/cgi-bin"</pre>
The corresponding php.ini format is:
<pre>include_path = "/home/users/u/username/cgi-bin"</pre>