rack-attack
rack-attack copied to clipboard
rack
Rack middleware for blocking & throttling
Provides a handy helper to help generate the response headers either based off throttle data e.g. `env['rack.attack.match_data']` or even `env['rack.attack.throttle_data'][throttle_name]`. I don't know if this is worth being included in...
Hi! I am working on the monitoring solution for rack attack [here](https://github.com/dsalahutdinov/yabeda-rack-attack). It listens to events and [increments specific counters](https://github.com/dsalahutdinov/yabeda-rack-attack/blob/master/lib/yabeda/rack/attack/notifier.rb#L31-L33) for any rule type (throttle, blacklist, whitelist, and track). For...
Hi! Big PR. But not to worry. It's not that complicated. Aims to fix #480 and addresses #380. The Initial goal was to try to fix the throttle limit reaching...
Upon upgrading to 6.2.1 (from 6.1.0), we end up with Rack::Attack twice in our middleware stack. Actual behavior: ``` $ rails middleware ... use Rack::Head use Rack::ConditionalGet use Authenticator::PartOne use...
I've blacklisted a specific IP, setup the `rack-attack.rb` file in my initializers, and updated my `application.rb` file. And I still am getting the following mess at around 30x a second....
I have a rake task that simulates a request to my server. I use this as part of a deploy script as a sanity check to ensure the code I'm...
Previously, if a request triggered a ban, there was no instrumentation for knowing the ban occurred. This instruments bans under the `ban.rack_attack` notification.
I want to use rack-attack to block pentesters based on 4xx requests. It's not possible with the current gem API. So here is a POC how it might look like:...
I have been (unknowingly) running into [the issue described in this comment](https://github.com/rack/rack-attack/issues/480#issuecomment-627501609). The problem is that I am trying to implement (and test the correctness of) a layered set of...
This PR removes the `rescuing` blocks from Dalli/RedisProxy classes and instead catches errors at the top level. It is a simpler version of #639
