We are using a border firewall too. This firewall includes an option to
auto update "list of bad IP" from a proprietary database.
Also you can use a public bad IP list, for example:
https://feodotracker.abuse.ch/blocklist/ or
https://github.com/mlsecproject/combine/wiki/Threat-Intelligence-Feeds-G
On 6/16/2021 9:05 PM, Will Fatherley wrote:
Hi All,
I have been using A2 for a few years now, but I've not really needed
to implement any deny/black-listing because I simply have no
meaningful security/traffic constraints. In moving forward with
development on top of A2 which does have securi
Hi All,
I have been using A2 for a few years now, but I've not really needed to
implement any deny/black-listing because I simply have no meaningful
security/traffic constraints. In moving forward with development on top of
A2 which does have security implications, I'm hoping it might be possible
Any thoughts on this before I post a bug report?
On Tue, Jun 15, 2021 at 9:07 PM Nick Folino wrote:
> So I changed the config to eliminate the order question:
>
>
> Header add Set-Cookie "RZROUTEID=.%{BALANCER_WORKER_ROUTE}e; path=/"
> env=BALANCER_ROUTE_CHANGED
> BalancerMember http://
