Rack Attack Versions Save

Rack middleware for blocking & throttling

v6.7.0

9 months ago

What's Changed

New Contributors

Full Changelog: https://github.com/rack/rack-attack/compare/v6.6.1...v6.7.0

v6.6.1

2 years ago

Details in CHANGELOG entry.

v6.6.0

2 years ago

Details in CHANGELOG entry.

v6.5.0

3 years ago

Details in CHANGELOG entry.

v6.4.0

3 years ago

Details in CHANGELOG entry.

v6.2.2

4 years ago

Fixed

  • Fixed occasional Redis::FutureNotReady error (#445) (@fatkodima)

v6.2.1

4 years ago

Fixed

  • Remove unintended side-effects on Rails app initialization order. It was potentially affecting the order of config/initializers/* in respect to gems initializers (#457)

v6.2.0

4 years ago

Added

  • Failsafe on Redis error replies in RedisCacheStoreProxy (#421) (@cristiangreco)
  • Rack::Attack middleware is now auto added for Rails 5.1+ apps to simplify gem setup (#431) (@fatkodima)
  • You can disable Rack::Attack with Rack::Attack.enabled = false (#431) (@fatkodima)

v6.1.0

4 years ago

Added

  • Provide throttle discriminator in the env throttle_data

v6.0.0

5 years ago

Added

  • #blocklist and #safelist name argument (the first one) is now optional.
  • Added support to subscribe only to specific event types via ActiveSupport::Notifications, e.g. subscribe to the throttle.rack_attack or the blocklist.rack_attack event.

Changed

  • Changed ActiveSupport::Notifications event naming to comply with the recommneded format.

Deprecated

  • Subscriptions via ActiveSupport::Notifications to the "rack.attack" event will continue to work (receive event notifications), but it is going to be removed in a future version. Replace the event name with /rack_attack/ to continue to be subscribed to all events, or "throttle.rack_attack" e.g. for specific type of events only.

Removed

  • Removed support for ruby 2.2.
  • Removed support for obsolete memcache-client as a cache store.
  • Removed deprecated methods #blacklist and #whitelist (use #blocklist and #safelist instead).