Hi there,
I am excited to announce the new formal release, 1.13.6.1, of the
OpenResty web platform based on NGINX and LuaJIT:
https://openresty.org/en/download.html
Both the (portable) source code distribution, the Win32 binary
distribution, and the pre-built binary Linux packages for all th
hello,
how about logs? does naxisi provide any variables that can be monitored?
so far it seems that your rules in ‘strict|relaxed’ are not triggering, the
‘default’
one will always hit (as expected), as it’s first location ‘/‘ from where you
route to other 2 locations.
also, try to log in deb
Thanks for linking, but nginx-module-vts seems over-kill and I'm concerned
about performance. Essentially we are building a product that charges by
egress bandwidth and looking for a way to track it at the NGINX level. I was
digging a bit further and it seems like using
https://www.nginx.com/blog/l
Hi,
I have updated the config to use 'map' instead of the if-statements. That's
indeed a better way.
The problem however remains:
- Naxsi mainrules are in the http-block
- Config similar to:
map $geoip_country_code $ruleSetCC {
default "strict";
CC1 "relaxed";
CC2 "re
I write a c source file, and test in my machine. At the beginning, the fd
is writable when the fd is open but the process doesn't receive the SIGIO.
so i'm confused a lot of paper or books say that the process will receive
SIGIO when the fd is writable or readable. but in fact it doesn't. so any
id
Hello!
On Fri, Nov 10, 2017 at 05:08:55PM +0800, Vis Lee wrote:
> Hi,
>
>
> The nginx is http proxy. when I use upgrade websocket and send heartbeat
> per 5s(client_body_timeout 6s;) the directives "worker_shutdown_timeout" is
> invalid, the "worker process is shutting down" produced by nginx -
At first glance config looks correct, so probably it’s something with naxi
rulesets.
Btw, why don’t you use maps?
map $geoip_coutnry_code $strictness {
default “strict";
CC_1“not-so-strict";
CC_2“not-so-strict";
# .. more country codes;
}
# strict and not-so-strict locations
ma
> Is there a way to measure and store the amount of egress bandwidth in GB a
> given server{} block uses in a certain amount of days? Needs to be somewhat
> performant. Using NGINX Unit or Lua are both possible, just no idea how to
> implement it.
Take a look at https://github.com/vozlt/nginx-modu
Is there a way to measure and store the amount of egress bandwidth in GB a
given server{} block uses in a certain amount of days? Needs to be somewhat
performant. Using NGINX Unit or Lua are both possible, just no idea how to
implement it.
Posted at Nginx Forum:
https://forum.nginx.org/read.php?2
