62 Ошибка! Используйте вкладку "Главная" для применения Heading 1 к тексту, который должен здесь отображаться. asecurity_rules - Web Application protection. Config file: rules.conf. Default: 0
(disabled). asecurity_jitp - Just in Time Patches for Vulnerable Applications. Config file: jitp.conf.
Default: 0 (disabled). asecurity_useragents - Bad UserAgents blocking. Config file: useragents.conf. Default:
0 (disabled). asecurity_blacklist - Comment spam blacklist. Config file: blacklist.conf. Default: 0
(disabled). asecurity_blacklist2 - Compromised/Hacker boxes blacklist. Config file: blacklist2.conf.
Default: 0 (disabled). asecurity_apache2-rules - Additional Apache 2.x rules. Effective for apache 2.2 only.
Config file: apache2-rules.conf. Default: 0 (disabled). asecurity_rootkits - Known rootkits/worms. Config file: rootkits.conf. Default: 0
(disabled). asecurity_exclude - Rule Exclusions. Config file: exclude.conf. Default: 0 (disabled). asecurity_recons - “Google Hacks” signatures. Config file: recons.conf. Default: 0
(disabled).
PHP Modes
For each available Apache version you can choose from libphp (default), cgi, or fastcgi:
libphp - PHP runs as an Apache module. The advantage is that PHP is always in memory use which results in a higher speed capability and lower server load.
cgi - PHP runs as a CGI script in a separate process which starts with each request and completes its work upon the script execution. This provides a simpler and more secure PHP work, but draws excessive memory usage and higher memory load.
fastcgi - PHP also runs as a CGI script, but under a single process which does not stop when the script is executed. This allows to minimize server load while running
PHP in CGI mode.
To configure advanced PHP mode settings in admin CP, go to
E.Manager->Servers-
>P.Servers and click on the Settings icon for a physical server. You will see the following interface:
Ошибка! Используйте вкладку "Главная" для применения Heading 1 к тексту, который должен здесь отображаться. 63
This form allows you to choose which PHP 4 and PHP 5 libphp/cgi/fastcgi modes will be available for end users whose domains are hosted on this physical server, and to set the default mode for each PHP version.
The fastcgi and cgi modes can be enabled for all PHP versions, but the libphp mode, only for one of them. Modes checked as Enabled will be available for end users to choose from in the Advanced PHP configuration interface in Web Options. When users switch PHP version in the “simplified” PHP configuration interface, they switch between the default modes of PHP versions (the Default column in the form - choose one default mode per PHP version). After that, users will be able to choose from the selected modes for each domain.
If you have enabled fastcgi mode using mod_fastcgi, you can configure its VirtualHost options in the form below:
64 Ошибка! Используйте вкладку "Главная" для применения Heading 1 к тексту, который должен здесь отображаться.
fcgi_idle-timeout - the number of seconds of FastCGI application inactivity allowed before the request is aborted and the event is logged (at the error LogLevel). The inactivity timer applies only as long as a connection is pending with the FastCGI application. If a request is queued to an application, but the application doesn ‟t respond (by writing and flushing) within this period, the request will be aborted. If communication is complete with the application but incomplete with the client (the response is buffered), the timeout does not apply.
fcgi_killInterval - determines how often the dynamic application instance killing policy is implemented within the process manager. Smaller numbers result in a more aggressive policy, larger numbers - in a less aggressive policy.
fcgi_minProcesses - minimum total number of dynamic FastCGI application instances allowed to run at any time without being killed by the process manager (due to lack of demand).
fcgi_maxClassProcesses - maximum number of dynamic FastCGI application instances allowed to run for any FastCGI application. It must be less or equal to maxProcesses (this condition is not programmatically enforced).
fcgi_maxProcesses - maximum total number of dynamic FastCGI application instances allowed to run at any time. It must be greater or equal to maxClassProcesses (this condition is not programmatically enforced).
fcgi_restart - causes the process manager to restart dynamic applications upon failure (similar to static applications).
fcgi_multiThreshold - an integer between 0 and 100 determining whether any instance of a FastCGI application should be terminated. If more than one instance of the application is currently running, this attribute is used to decide whether one of them should be terminated. If only one instance remains, -singleThreshold is used instead.
fcgi_singleThreshold - An integer between 0 and 100 determining whether the last instance of a FastCGI application can be terminated. If the process manager computed that the load factor for the application is lower than the specified threshold, the last instance is terminated. In order to make your executables run in the “idle” mode for a long time, specify a value closer to 1. However, if memory or
CPU time is of primary concern, a value closer to 100 is more appropriate. Setting it to 0 prevents the last instance of an application from being terminated; this is the default value, changing it is not recommended (especially if -appConnTimeout is set).
fcgi_updateInterval - determines how often statistical analysis is performed for dynamic FastCGI applications.