You might wish to set up locations like that:
location /outer-path {
limit_req ...
}
location /outer-path/inner-path {
...
}
---
*B. R.*
On Tue, Jan 19, 2016 at 11:01 PM, Fry-kun
wrote:
> I have a location with limit_req and would like to set up an inner path
> without the limit but wi
Hi Robert
> Robert Paprocki [2016-01-20 00:14]:
>
> ModSecurity isn't a sub-process, it's compiled into the nginx binary and
> runs as part of the worker process(es). Nginx doesn't have a concept of
> spawning children in the manner you're referencing, so there's nothing to
> be monitored wrt. re
ModSecurity isn't a sub-process, it's compiled into the nginx binary and
runs as part of the worker process(es). Nginx doesn't have a concept of
spawning children in the manner you're referencing, so there's nothing to
be monitored wrt. resource consumption. Any resource monitoring would be
done by
Hi Felipe
> Felipe Zimmerle [2016-01-11 17:12]:
>
> On Sun, Jan 10, 2016 at 11:05 AM Lukas wrote:
>
> > I found that recommendation. Since I also read that it would not be
> > fully compatible with OWASP/CRS I have not given it a try.
> >
> > What is the situation regrading OWASP/CRS?
> >
>
> C
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
On Tue, Jan 19, 2016 at 11:21:46AM +0200, Nikolaos Milas wrote:
Hi there,
> location ~ /newlocation/(.*)\.php$ {
>
> alias /var/websites/externaldir$1.php;
>
> fastcgi_cache off;
>
> try_files $uri =404;
> include /etc/nginx/fastcgi_params;
> This config
=)
That module passed all our tests, both in dev and staging environments. We
were deploying in batches and got it on the first one. We also rolled back
before any incidents.
Not perfect but pretty safe, I think.
Maybe we need to be more 'creative' with our testing.
On Tue, Jan 19, 2016 at 6:47
Hello,
I have been adding (to my nginx config) directories outside of the
default "root" tree like:
location ~ /newlocation(.*) {
alias /var/websites/externaldir$1;
}
This works OK.
however, I find that the above config does not process php files. I
tried adding (before the
Testingin production?
Well you are not the only one... far from that.
There are other means to create 'realistic' traffic on benches, provided
you are thinking those tests well, though.
---
*B. R.*
On Mon, Jan 18, 2016 at 7:33 PM, Marcelo MD wrote:
> Hi,
>
> Just getting back to you. Sorry abou
