rack-attack/spec
Gonzalo Rodriguez e3056e737f
fix: avoid unintended effects on load_config_initializers and other gems load order
Because of the sort algorithm rails uses to satisfy `after` and `before`
constraints, gems can have unintended effects on others. See
0a120a818d

Prefer making rack-attack middleware idempotent instead of relying on
the load order and the contents of the middleware stack too much.

closes #452
closes #456
2019-10-29 15:45:26 -03:00
..
acceptance fix: avoid unintended effects on load_config_initializers and other gems load order 2019-10-29 15:45:26 -03:00
integration style: prefer ruby 1.9+ hash syntax 2019-02-27 23:29:32 -03:00
support Refactor the "doesn't leak keys" spec 2018-08-30 21:52:13 -03:00
allow2ban_spec.rb test: fix minitest/spec deprecation warnings 2019-10-01 17:19:44 -03:00
fail2ban_spec.rb test: fix minitest/spec deprecation warnings 2019-10-01 17:19:44 -03:00
rack_attack_dalli_proxy_spec.rb Remove support for unmaintained ruby 2.2 2018-06-28 17:08:15 -03:00
rack_attack_instrumentation_spec.rb test: fix minitest/spec deprecation warnings 2019-10-01 17:19:44 -03:00
rack_attack_path_normalizer_spec.rb test: fix minitest/spec deprecation warnings 2019-10-01 17:19:44 -03:00
rack_attack_request_spec.rb Remove support for unmaintained ruby 2.2 2018-06-28 17:08:15 -03:00
rack_attack_spec.rb Do not auto-plug for rails < 5 2019-10-08 13:08:07 +03:00
rack_attack_throttle_spec.rb test: fix minitest/spec deprecation warnings 2019-10-01 17:19:44 -03:00
rack_attack_track_spec.rb test: fix minitest/spec deprecation warnings 2019-10-01 17:19:44 -03:00
spec_helper.rb fix: avoid unintended effects on load_config_initializers and other gems load order 2019-10-29 15:45:26 -03:00