Hello. In admin > System > Server Config > FastCGI i can choose wich of this i will use: FastCGI config syntax: "Old Apache 2.0" or "New Apache 2.2" Wich of them will be best too use? I have looked at the manual i bought but it dosnt excist there. Thanks!
Yeah it does:- • PHP Options : Specify which PHP modes should be available for the client when he creates/modifies a web site. The following four modes are available: Fast-CGI, CGI, Mod-PHP, SuPHP. • Fast-CGI: Advantages: • Scripts will be executed with user privileges of the web site; • More than one PHP version can be run as FastCGI; • Might be better in speed compared to CGI and suPHP. Disadvantages: • php.ini values cannot be changed via PHP scripts, vhost files, .htaccess files. But it is possible to use the Custom php.ini settings field on the Options tab of a web site in ISPConfig to specify custom php.ini settings (see chapter 4.6.1.1). • CGI: Advantages: • Scripts will be executed with user privileges of the web site; • More than one PHP version can be run as CGI. Disadvantages: • CGI might use a little more memory (RAM) - therefore, it's not recommended to run PHP as CGI on slow virtual servers; • php.ini values cannot be changed via PHP scripts, vhost files, .htaccess files. But it is possible to use the Custom php.ini settings field on the Options tab of a web site in ISPConfig to specify custom php.ini settings (see chapter 4.6.1.1). • Mod-PHP: Advantages: • Speed; • Needs less memory (RAM) than CGI; • php.ini values can be changed via PHP scripts, vhost files, .htaccess files. Disadvantages: • Scripts are being executed with Apache privileges, which might lead to somesecurity related problems; • Only one version of PHP can be installed as Apache module; • You cannot use the Custom php.ini settings field on the Options tab of a web site in ISPConfig to specify custom php.ini settings (see chapter 4.6.1.1). • SuPHP: Advantages: • Scripts will be executed with user privileges of the web site; • Each vhost can have its own php.ini file; • Needs less memory (RAM) than CGI; • More than one PHP version can be run as suPHP. Disadvantages: • php.ini values cannot be changed via PHP scripts, vhost files, .htaccess files. But it is possible to use the Custom php.ini settings field on the Options tab of a web site in ISPConfig to specify custom php.ini settings (see chapter 4.6.1.1); • SuPHP might be a little slower than mod_php. • Recommendations: • High-Traffic Web Sites: Fast-CGI + suExec • Low-Traffic Web Sites: CGI + suExec or SuPHP
Take a look at http://httpd.apache.org/mod_fcgid/mod/mod_fcgid.html#upgrade : "All directives have been renamed in order to use a common prefix "Fcgid". Underscores in directive names have been eliminated in favor of CamelCase. The old directive names will still work but are deprecated."
Is it other things thats are better if using "new 2.2"? If I write with new or old style dosn't care me so much.. I just want everything to work
This is not about being better, the functionality is the same. You just have to use the config style that matches the apache version installed on your server.
