Hello,
A self contained solution would be to double proxy, first through nginx stream
server and then locally back to nginx http server (with proxy_pass via unix
socket, or to localhost on a different port).
You can implement your own custom rate limiting logic in the stream server with
NJS (j
Hello!
On Sun, Nov 19, 2023 at 12:41:11PM +0300, Mark wrote:
> Hello Mr. Maxim, thank you very much for your reply.
>
> Things are much clearer now, thanks!
>
> One, last question;
>
> I have implemented nginx as a reverse proxy with TLS termination in my
> FreeBSD host machine, and another ng
> sudden surge of requests, existing connections can get enough share of CPU
> to be served properly, while excessive connections are rejected
While you can't limit the connections (before the TLS handshake) there is a
module to limit the requests per client/ip
https://nginx.org/en/docs/http/n
Hello Mr. Maxim, thank you very much for your reply.
Things are much clearer now, thanks!
One, last question;
I have implemented nginx as a reverse proxy with TLS termination in my
FreeBSD host machine, and another nginx instance running in my jail, in;
10.10.10.2.
So, the host machine does the
