Sure, except there are a few dozen identical config lines in these locations... If "limit_req off" was an option, that would be the only difference. B.R. Wrote: ------------------------------------------------------- > You might wish to set up locations like that: > > location /outer-path { > limit_req ... > } > > location /outer-path/inner-path {by Fry-kun - Nginx Mailing List - English
I have a location with limit_req and would like to set up an inner path without the limit but with other settings same, e.g. location / { limit_req ...; proxy_pass ...; location /private/ { limit_req off; } } How come "limit_req off" is not an available option? Any other easy way of achieving this? Thanksby Fry-kun - Nginx Mailing List - English
Thanks Maxim, that explains it Would be nice if documentation mentioned this fact, or nginx would spit out some errors about the conflicting config ;)by Fry-kun - Nginx Mailing List - English
So it looks like the ssl config is valid per-port only. If I set up a server on a different port with different ssl config, it works. Is this a bug or is it by design?by Fry-kun - Nginx Mailing List - English
Also noticed that http-level config causes www.foo.com to show errors on https://www.200please.com/by Fry-kun - Nginx Mailing List - English
Hi all, I have a strange problem with nginx: I tried to harden the TLS stack by setting default to recommended values from https://wiki.mozilla.org/Security/Server_Side_TLS but one server has to keep backward compatibility -- so I set it up as http { ssl_protocols TLSv1.1 TLSv1.2; ssl_ciphers ... ssl_prefer_server_ciphers on; server { listen 443 spdy; server_name .foo.com bby Fry-kun - Nginx Mailing List - English
I am; that was a copy/paste error. The original config is around 3000 lines, it was easier to type & copy/paste than cleaning up unnecessary lines. ~Konstantin B.R. Wrote: ------------------------------------------------------- > Quick quesiton; I see you are using proxy_intercept_errors. Should not > you > be using fastcgi_intercept_errors > <http://nginx.org/en/by Fry-kun - Nginx Mailing List - English
I'm trying to configure my sites to failover to fastcgi_cache when backends are unavailable -- but at the same time I want to return nginx errors (hiding backend errors) Here's a simplified version of my current config: fastcgi_cache_path /dev/shm/nginx_fastcgi_cache levels=1:2 inactive=3d keys_zone=mycache:100m max_size=5000m; fastcgi_cache_use_stale error http_500 http_503 timeout updby Fry-kun - Nginx Mailing List - English