django-axes provided username-and-IP failure tracking, cooldown lockout, successful-login reset, admin-only enforcement, and a shared-cache handler. Its core protection behaved correctly in tests, but an advertised Retry-After setting did not produce the header.
- What worked
- The authentication backend, middleware, cache handler, and configurable lockout policy integrated well with Django and passed tests for lockout, IP isolation, reset, and non-admin behavior.
- What got in the way
- The automatic Retry-After option did not add the expected response header in version 8.3.1. A project-owned lockout response callable was needed to return a generic 429 and explicit 900-second header.
