Page 1 of 1
suPHP
Posted: Wed Aug 05, 2009 1:26 am
by matthijs
With a lot of hosts I have troubles with the permissions setup. Often way too loose permissions (even 777) are needed to run php scripts, etc. Now in one case the webhost offered me to switch a site to use suPHP. That way, if I understood correctly, the php scripts always run as their own owner and there should be less trouble with permissions.
Do you know if this has any other (wanted/unwanted) consequences?
Re: suPHP
Posted: Fri Aug 07, 2009 12:54 pm
by kaisellgren
Are there drawbacks to this scenario? I doubt. Have you tried running some scripts?
Re: suPHP
Posted: Fri Aug 07, 2009 1:06 pm
by Weirdan
matthijs wrote:Do you know if this has any other (wanted/unwanted) consequences?
As you're not running PHP as apache module you will not have access to apache api. By default apache will not pass basic http auth credentials to your script.
Re: suPHP
Posted: Fri Aug 07, 2009 3:35 pm
by matthijs
kaisellgren wrote:Are there drawbacks to this scenario? I doubt. Have you tried running some scripts?
No not yet as I haven't told the webhost to switch the account.
Weirdan wrote:As you're not running PHP as apache module you will not have access to apache api. By default apache will not pass basic http auth credentials to your script.
So what would be the meaning of that? When do you need apache to pass credentials to a script?
Re: suPHP
Posted: Fri Aug 07, 2009 5:50 pm
by Weirdan
matthijs wrote:So what would be the meaning of that?
Two separate issues, usually not apparent to those who switch to CGI/FastCGI from mod_php.
matthijs wrote: When do you need apache to pass credentials to a script?
Well, that's obvious - when you need to perform authentication yourself instead of relying on apache to do that.
Re: suPHP
Posted: Sat Aug 08, 2009 12:50 am
by matthijs
Weirdan wrote:matthijs wrote:So what would be the meaning of that?
Two separate issues, usually not apparent to those who switch to CGI/FastCGI from mod_php.
ok, and what are those issues then?
Weirdan wrote:matthijs wrote: When do you need apache to pass credentials to a script?
Well, that's obvious - when you need to perform authentication yourself instead of relying on apache to do that.
Obvious to you maybe, but not for me. When do you rely on apache for http credentials? When you use .htaccess and .htpasswd for authentication?
Re: suPHP
Posted: Sat Aug 08, 2009 1:18 am
by kaisellgren
If your script works fine across other HTTPDs, there should be no problem. Try Cherokee, nginx and IIS.
Re: suPHP
Posted: Sat Aug 08, 2009 1:52 am
by matthijs
kaisellgren wrote:If your script works fine across other HTTPDs, there should be no problem. Try Cherokee, nginx and IIS.
great, that shows how much I still have to learn. of those 4 terms I am familiar with 1

Re: suPHP
Posted: Sat Aug 08, 2009 9:17 am
by Weirdan
matthijs wrote:Weirdan wrote:
Two separate issues, usually not apparent to those who switch to CGI/FastCGI from mod_php.
ok, and what are those issues then?
Weirdan wrote:
- As you're not running PHP as apache module you will not have access to apache api.
- By default apache will not pass basic http auth credentials to your script.