rack-attack
rack-attack copied to clipboard
Rack middleware for blocking & throttling
Currently, to test `rack-attack`'s behavior we need to use something like: ```ruby context "number of requests is lower than the limit" do it "does not change the request status" do...
Using `Rack::Attack.clear_configuration` breaks subsequent tests. ## Expected Behavior Second consecutive request is throttled when Rack Attack throttling is set to limit = 1. ## Actual Behavior Second consecutive request returns...
Running Rack Attack in production systems sometimes requires debugging misbehaving rules. One of the common ways to find misbehaving application components in Ruby is by monkey-patching in tracing information (eg:...
All examples and usages show how we can use the request to determine whether to block/throttle. However, is there any way to do so using the response? Using the request...
## Description Some errors on proxy instances could lead to requests not being passed to the next middleware. This could be behaviour that we want to avoid, we wouldn't want...