Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

django-banish stops working after cache TIMEOUT reached #22

Open
groovecoder opened this issue Feb 11, 2015 · 0 comments
Open

django-banish stops working after cache TIMEOUT reached #22

groovecoder opened this issue Feb 11, 2015 · 0 comments

Comments

@groovecoder
Copy link
Collaborator

Steps to reproduce:

  1. Set the default cache timeout to 60s using CACHES argument.
  2. Throw a bunch of abusive traffic at django. (e.g., ab -c 2 -n 1000 http://127.0.0.1:8000/)

Expected results:
After the traffic trips the ABUSE_THRESHOLD, django-banish should respond with 403 for the client

Actual results:
After the traffic trips the ABUSE_THRESHOLD, django-banish responds with 403 for the client until the CACHES TIMEOUT value is reached. Then django-banish forgets that the IP is banished. It allows the requests thru until the same client trips the ABUSE_THRESHOLD again. And repeats this pattern.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

1 participant