You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Rack Attack works great with Rails. I'm finding, though, that I'm responding to most attack requests twice: first, my rails stack redirects it to https, then Rack Attack denies it.
So, with config.force_ssl = true in Rails, would there be a way for Rack Attack to filter first, before any redirects to https? Maybe setting it up lower in the stack? I'd like to clean up my logs, and also not spend time on these (known) attack requests.
This discussion was converted from issue #519 on March 21, 2021 20:40.
Heading
Bold
Italic
Quote
Code
Link
Numbered list
Unordered list
Task list
Attach files
Mention
Reference
Menu
reacted with thumbs up emoji reacted with thumbs down emoji reacted with laugh emoji reacted with hooray emoji reacted with confused emoji reacted with heart emoji reacted with rocket emoji reacted with eyes emoji
-
Rack Attack works great with Rails. I'm finding, though, that I'm responding to most attack requests twice: first, my rails stack redirects it to https, then Rack Attack denies it.
So, with
config.force_ssl = true
in Rails, would there be a way for Rack Attack to filter first, before any redirects to https? Maybe setting it up lower in the stack? I'd like to clean up my logs, and also not spend time on these (known) attack requests.Beta Was this translation helpful? Give feedback.
All reactions