Ratelimits for 1/h appear to allow 2, but no more about django-ratelimit HOT 4 CLOSED

What version of django-ratelimit are you using? Can you include the line that's dumping out the contents of the cache, as well as the cache backend?

from django-ratelimit.

Also... because it does a > check, which ISTR is for a reason, though I'm not 100% sure what that reason was.

from django-ratelimit.

Also... because it does a > check, which ISTR is for a reason, though I'm not 100% sure what that reason was.

Ah, it's coming back to me a little—because this is an atypical way to use ratelimit.

When you use the decorator or the mixin, it pre-increments, so if you say rate='5/m' then 5 requests per minute are allowed. When you post-increment, you're allowing the action to happen (twice) before counting it. So when you check the ratelimit in dispatch(), you have not yet surpassed the ratelimit.

Ratelimit may not actually be the right tool here. Remember that it relies on the cache, which is not always reliable, and has staggered windows. If you only want each IP to have one submission per clock hour, just checking to see whether or not there is a saved submission since datetime.now().replace(minute=0) might be more what you're looking to achieve.

from django-ratelimit.

Great thanks for the clarification - I thought I might be missing something - really helpful.

from django-ratelimit.