Rate Limiting resetting not working as intended

[daveallie]

Each time the key gets updated, the expiry is reset (see here).

What is happening

1. Setup endpoint that allows 100 requests per 1 day
2. Make 90 requests in 1 hour (at time 00:00)
3. 22 hours later make 9 more requests (at time 22:00)
4. 3 hours after that make 2 requests (at time 01:00 the next day)

The last request will be rate limited.

What should be happening

In the example above, 24 hours after the first request (midnight on the second day) the rate limiting should have been reset. At step 4, there should be 100 remaining requests available, however there is only 1.

[nedcampion]

This gem seems to no longer be maintained, but if anyone is interested we have a fork we are maintaining that has a few changes on top of the last released version of grape-attack in which we've just added a new 'sliding window' algorithm (using sorted sets) that solves this issue for us (along with loosening some dependencies to allow for grape-attack to be used in more recent versions of Grape and Bunlder).

[gottfrois]

Hey folks, i'm happy to transfer the ownership of the project if you want 👍