How's the period (expiry / timeout) information set in the cache about django-ratelimit HOT 4 CLOSED

The method of counting over time changed. Instead of relying on cache expiry (which leads to situations where good actors get blocked forever by being just a little too eager) ratelimit now calculates a fixed window that is period seconds long, and the cache key itself changes every period seconds.

from django-ratelimit.

See also the CHANGELOG, issue #48, and the upgrade notes.

from django-ratelimit.

cache key itself changes every period seconds

Oops, I overlooked this part.

However, I still have some doubt. Django has a default timeout for cache = 300 seconds. Say I have a couple of ratelimit decorators, where the slowest rate (& largest period) is 5/h (i.e. 5 requests per hour). Won't the key be lost after 300 seconds unless I explicitly change the timeout setting to be greater than say 1 hour ?

from django-ratelimit.

Won't the key be lost after 300 seconds unless I explicitly change the timeout setting to be greater than say 1 hour ?

Can you please test this and if so file a bug? No one has reported this issue.

from django-ratelimit.