Facebook
Twitter
DieterWerner
Regular Pleskian
I use the
ngx_http_limit_req_module
and I would like to ask you for the best settings.
Thanks in advance.
ngx_http_limit_req_module
and I would like to ask you for the best settings.
Thanks in advance.
-
Introducing WebPros Cloud - a fully managed infrastructure platform purpose-built to simplify the deployment of WebPros products ! WebPros Cloud enables you to easily deliver WebPros solutions — without the complexity of managing the infrastructure.
Join the pilot program today! -
The Horde component is removed from Plesk Installer. We recommend switching to another webmail software supported in Plesk.
-
The BIND DNS server has already been deprecated and removed from Plesk for Windows.
If a Plesk for Windows server is still using BIND, the upgrade to Plesk Obsidian 18.0.70 will be unavailable until the administrator switches the DNS server to Microsoft DNS. We strongly recommend transitioning to Microsoft DNS within the next 6 weeks, before the Plesk 18.0.70 release.
Resolved ngx_http_limit_req_module
- Thread starter DieterWerner
- Start date
DieterWerner
Regular Pleskian
I wonder if nobody uses or knows it
@DieterWerner
With respect to
it is probably safe to say that the above can be true - for a peculiar reason though.
Nginx, as shipped with Plesk, should not contain the ngx_http_limit_req_module - you can verify this with the command : nginx -V
However, as far as I know, you can simply declare the limit_req_zone directive, without resulting in errors at config check (via the command : nginx -t ).
I do not (yet) know whether it can be recommended to use the limit_req_zone directive, I still have to find time to get some decent checks designed and executed.
It could work though, so that is the good news - but you can imagine by now that the output of Nginx -V obfuscates the potential usage of the limit_req_zone directive.
Anyway, you should note that - in general - it is a better idea to keep bad traffic from entering the proxy level (Nginx) or the webserver level (Apache) : also use a firewall!
Kind regards.........
With respect to
it is probably safe to say that the above can be true - for a peculiar reason though.
Nginx, as shipped with Plesk, should not contain the ngx_http_limit_req_module - you can verify this with the command : nginx -V
However, as far as I know, you can simply declare the limit_req_zone directive, without resulting in errors at config check (via the command : nginx -t ).
I do not (yet) know whether it can be recommended to use the limit_req_zone directive, I still have to find time to get some decent checks designed and executed.
It could work though, so that is the good news - but you can imagine by now that the output of Nginx -V obfuscates the potential usage of the limit_req_zone directive.
Anyway, you should note that - in general - it is a better idea to keep bad traffic from entering the proxy level (Nginx) or the webserver level (Apache) : also use a firewall!
Kind regards.........
DieterWerner
Regular Pleskian
Sorry, but
ngx_ http_limit_req_module
is a part of the nginx core.
ngx_ http_limit_req_module
is a part of the nginx core.
......... and so are a lot of other modules, which are not compiled into the Nginx version shipped with Plesk.
Not to mention the fact that Nginx core is actually intended for commercial subscriptions, with the community variant being some form of testing playground.
In essence, the whole concept of Nginx is a bit different from what one might expect - I will not bother you with the details.
Kind regards......
DieterWerner
Regular Pleskian
So you recommend not to use nginx?
@DieterWerner
This question
should not be the result of what I was posting : it is highly recommend to use Nginx as a proxy in front of Apache.
In essence, it is just an additional layer that allows you to (amongst others)
- reduce the workload of the memory hungry Apache web server,
- increase security to a high degree
and so on.
The golden rule is more or less : whatever does not have to "reach" Apache, should be taken care of by a proxy like Nginx.
I hope that helps a bit.
Kind regards.......
This question
should not be the result of what I was posting : it is highly recommend to use Nginx as a proxy in front of Apache.
In essence, it is just an additional layer that allows you to (amongst others)
- reduce the workload of the memory hungry Apache web server,
- increase security to a high degree
and so on.
The golden rule is more or less : whatever does not have to "reach" Apache, should be taken care of by a proxy like Nginx.
I hope that helps a bit.
Kind regards.......
DieterWerner
Regular Pleskian
I really lik your rhetoric ;-)
Best regards!
Best regards!
Similar threads
