nginx Connections

I want to limit the connections used by nginx using CLI. I know that we can set worker connections to different values in nginx conf file. But no of worker connections will include not only the connections to the host. It also includes proxy connections too. If I want to give user flexibility to

Re: Nginx 1.12.1 Memory Consumption

Hello! On Wed, Mar 14, 2018 at 05:05:42PM +, Matthew Smith wrote: > I have encountered what I consider to be an interesting behavior. We have > Nginx 1.12.1 configured to do SSL termination as well as reverse proxy. > Whenever there is a traffic spike (300 req/s > 1000 req/s, 3k active > conn

redirect to a .php file with try_files if required .php file not found

Hello, I would like to redirect to /virtual_new.php with try_files if required .php file not found, is it the right way to do so: location ~ \.php$ { if ($args ~ "netcat_files/") { expires 7d; add_header Cache-Control "public"; } fastcgi_split_

Nginx 1.12.1 Memory Consumption

Hello, I have encountered what I consider to be an interesting behavior. We have Nginx 1.12.1 configured to do SSL termination as well as reverse proxy. Whenever there is a traffic spike (300 req/s > 1000 req/s, 3k active connections > 20k active connections), there is a corresponding spike in Ngi

Re: $upstream_cache_status output definitions

Excellent, thank you so much! I had a feeling it was there and I was just missing it. ___ Michael Friscia Office of Communications Yale School of Medicine (203) 737-7932 - office (203) 931-5381 - mobile http://web.yale.edu On 3/14/

Re: $upstream_cache_status output definitions

On Wed, Mar 14, 2018 at 04:07:22PM +, Friscia, Michael wrote: Hi there, > $upstream_cache_status > keeps the status of accessing a response cache (0.8.3). The status can be > either “MISS”, “BYPASS”, “EXPIRED”, “STALE”, “UPDATING”, “REVALIDATED”, or > “HIT”. It may not be as easily findabl

$upstream_cache_status output definitions

I read this in the documentation $upstream_cache_status keeps the status of accessing a response cache (0.8.3). The status can be either “MISS”, “BYPASS”, “EXPIRED”, “STALE”, “UPDATING”, “REVALIDATED”, or “HIT”. But I’m sort of at a loss as to what the meanings are, specifically what is Hit an

Re: Using the mirror module

On Wed, Mar 14, 2018 at 08:55:39AM -0300, Kenny Meyer wrote: > How do you define a resolver? Use the "resolver" directive: http://nginx.org/en/docs/http/ngx_http_core_module.html#resolver This only makes sense if your nginx resolves domain names in runtime. In your configuration "staging.example

Re: Using the mirror module

Suggestion: Define two more locations - one that proxies www.example.com and another that proxies staging.example.com. If both locations work then your problem is probably mirroring. If one doesn’t work then the issue is your configuration and not mirroring. Either way you have reduced the size

Re: Using the mirror module

How do you define a resolver? > On 13 Mar, 2018, at 19:36, Roman Arutyunyan wrote: > > On Tue, Mar 13, 2018 at 06:58:25PM -0300, Kenny Meyer wrote: >> Hi Roman, >> >>> Are there any errors in error.log? >> No errors… >> >>> And what happens if you switch www.example.com and staging.example.com