September 27, 2016 03:28PM
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 can have CloudFlare block those IP's before they reach your server like so https://api.cloudflare.com/#user-level-firewall-access-rule-properties

If you use OVH you can write the IP's that trigger 503's to OVH's Firewall https://api.ovh.com/console/#/ip/{ip}/firewall#POST

This should be of interest too https://twitter.com/olesovhcom/status/779297257199964160

But anything the firewall does not get your server now has a way to communicate with your router / firewall to prevent this requests even hitting the machine any more.

http://www.networkflare.com/
Subject Author Posted

444 return code and rate limiting

gariac September 27, 2016 12:46PM

Re: 444 return code and rate limiting

B.R. September 27, 2016 01:10PM

Re: 444 return code and rate limiting

gariac September 27, 2016 01:16PM

Re: 444 return code and rate limiting

c0nw0nk September 27, 2016 02:42PM

Re: 444 return code and rate limiting

gariac September 27, 2016 03:14PM

Re: 444 return code and rate limiting

c0nw0nk September 27, 2016 03:28PM

Re: 444 return code and rate limiting

B.R. September 28, 2016 12:58PM

Re: 444 return code and rate limiting

gariac September 28, 2016 01:32PM

Re: 444 return code and rate limiting

Richard Stanway September 28, 2016 02:00PM

Re: 444 return code and rate limiting

gariac September 28, 2016 04:00PM



Sorry, only registered users may post in this forum.

Click here to login

Online Users

Guests: 130
Record Number of Users: 8 on April 13, 2023
Record Number of Guests: 500 on July 15, 2024
Powered by nginx      Powered by FreeBSD      PHP Powered      Powered by MariaDB      ipv6 ready