On 21.8.2007, at 14:36, Michael Stucki wrote: > Here are two different setups. Which one is better, and why? > > === cut FCGIWrapper === > > AddHandler fcgid-script .php > > <Directory /var/www/> > FCGIWrapper /usr/local/bin/php .php > Options +ExecCGI > </Directory> > > === cut FCGIWrapper === > > === cut Action === > > AddHandler php-fcgi .php > Action php-fcgi /fcgi-bin/php5-cgi > AddType application/x-httpd-php .php > Alias /fcgi-bin/ /usr/bin/ > > <Location /fcgi-bin/> > SetHandler fcgid-script > Options +ExecCGI > </Location> > > === cut Action ===
Hi Michael, from my experience, both setups offer the same functionality in the end. I prefer using handlers to FCGIWrapper too, as it's much more flexible (as you noticed), you can have PHP4 and PHP5 compiled with FastCGI and switch on a per-directory context using AddHandler in .htaccess, rather then fiddling with Apache directives on httpd.conf level config (if .htaccess control is what you need/want). Furthermore your Apache config doesn't break if the PHP executable goes missing (unlike FCGIWrapper), which is important if you use wrapper scripts and suexec instead of calling the binary directly (e.g. for virtual hosting environment), and risk users getting rid of the wrapper scripts by accident. Regards, Filip Hajny ------------------------------------------------------------------------- This SF.net email is sponsored by: Splunk Inc. Still grepping through log files to find problems? Stop. Now Search log events and configuration files using AJAX and a browser. Download your FREE copy of Splunk now >> http://get.splunk.com/ _______________________________________________ Mod-fcgid-users mailing list Mod-fcgid-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/mod-fcgid-users
