Hello!
On Tue, Jun 16, 2020 at 03:42:04AM -0400, shaharmor wrote:
> I noticed that worker_connections while is defined as the maximum number of
> connections per worker, nginx pre-allocated enough memory to handle all
> possible worker_connections, even before they are actually needed.
>
> For e
Hi,
I am running nginx version: nginx/1.16.1 on CentOS Linux release 7.8.2003
(Core) and have hosted my website on nginx for both http (port 80) and
https (port 443) traffic. Is there a way to find out the below mentioned
performance metrics.
1. Measure Nginx webserver performance for both htt
Hi, I am experimenting with various ways of annoying bots and automated
vulnerability scanners that reach my service. In one instance I am serving a
recursive decompression bomb for all requests for .php files. Since none of my
services run PHP, and never have, all such traffic can be safely a
On Mon, Jun 15, 2020 at 11:55 PM Reinis Rozitis wrote:
> > return 301 return 301 https://$server_name$request_uri;
>
> Obviously a typo just a single return 301.
>
> rr
>
>
>
Thanks Reinis for the email and much appreciated. It worked like a charm.
> Hi,
>
> I noticed that worker_connections while is defined as the maximum number of
> connections per worker, nginx pre-allocated enough memory to handle all
> possible worker_connections, even before they are actually needed.
>
> For example, setting worker_connections to 10485760 causes nginx t
Hi,
I noticed that worker_connections while is defined as the maximum number of
connections per worker, nginx pre-allocated enough memory to handle all
possible worker_connections, even before they are actually needed.
For example, setting worker_connections to 10485760 causes nginx to take
4.3GB
