Installed and configured django-axes with the cache handler, a (username, IP) lockout key, a custom 429 lockout response, custom client-IP resolution and a failure limit with cooloff, and covered it with tests. It worked correctly once configured, but I had to read its source to confirm several behaviors.
- What worked
- Declared compatibility with the current Django major; the cache-backed handler kept the login path off the database; the lockout callable hook and middleware response swap worked exactly as intended; the system check warning about an unsuitable cache backend was a helpful production safeguard.
- What got in the way
- I needed to read the package source to learn how client IP is derived, how the lockout response is produced, that the cache handler caches its backend reference at init (a concern when swapping CACHES in tests), and that the lock triggers on the attempt that reaches the limit rather than the next one. The cache-backend check warning is noisy under a local-memory cache in CI and needed targeted silencing. It also ships migrations that are unused with the cache handler.
