ou should deny dynamically or statically.
Original Message
From: c0nw0nk
Sent: Tuesday, September 27, 2016 11:42 AM
To: nginx@nginx.org
Reply To: nginx@nginx.org
Subject: Re: 444 return code and rate limiting
It is a response by the time the 444 is served it is to late a true DDoS is
not about w
nd you can bet those clowns proving for WordPress vulnerabilities
> today will be employing the next script kiddie to come along in the future.
>
> *From: *B.R.
> *Sent: *Wednesday, September 28, 2016 9:57 AM
> *To: *nginx ML
> *Reply To: *nginx@nginx.org
> *Subject: *Re: 444 return code a
ins is if you should deny dynamically or statically.
Original Message
From: c0nw0nk
Sent: Tuesday, September 27, 2016 11:42 AM
To: nginx@nginx.org
Reply To: nginx@nginx.org
Subject: Re: 444 return code and rate limiting
It is a response by the time the 444 is served it is to late a true DD
: nginx@nginx.org
> Subject: Re: 444 return code and rate limiting
>
> It is a response by the time the 444 is served it is to late a true DDoS is
> not about what the server outputs its about what it can receive you can't
> expect incoming traffic that amounts to 600Gbps to be pr
What I would say to do is write IP's from your toolkit or what ever you are
using for reading your access.log and those that trigger and spam the 503
error within milliseconds or what ever range it is you can do an API call
and add those IP's to be blocked at a router level.
With CloudFlare you
11:42 AM
To: nginx@nginx.org
Reply To: nginx@nginx.org
Subject: Re: 444 return code and rate limiting
It is a response by the time the 444 is served it is to late a true DDoS is
not about what the server outputs its about what it can receive you can't
expect incoming traffic that amounts
It is a response by the time the 444 is served it is to late a true DDoS is
not about what the server outputs its about what it can receive you can't
expect incoming traffic that amounts to 600Gbps to be prevented by a 1Gbps
port it does not work like that Nginx is an Application preventing any
Your reply does not agree with the documentation.
https://httpstatuses.com/444
Original Message
From: B.R.
Sent: Tuesday, September 27, 2016 10:09 AM
To: nginx ML
Reply To: nginx@nginx.org
Subject: Re: 444 return code and rate limiting
Responding 444 is... a response.
It is not anything
Responding 444 is... a response.
It is not anything else than a (non-standard, thus 'unknown', just like 499
nginx chose to illustrate client-side premature disconnection) HTTP status
code as any other.
Some speedup might come from using return instead of doing further
processing, but there is
I pulled this off the rate limiting thread since I think the 444 return is a
good topic all on its own.
"But under a DoS attack I always feel those values would be better being
"444" since the server won't respond and cut's the connection rather than
waste bandwidth on a client who is opening
10 matches
Mail list logo
