Fixed window strategy using mongodb storage not working about limits HOT 6 OPEN

I don’t think I understand the issue clearly, could you provide a reproduction step?

from limits.

I don’t think I understand the issue clearly, could you provide a reproduction step?

1. Use mongodb for storage.
2. Adopt the fixed-window strategy.
3. Set the rate limit to 2/1 minute.
4. Hit the endpoint at 00:00:55 and again at 00:00:59.
5. Hit the endpoint once more at 00:01:01. You'll receive a 429 error (indicating too many requests).

If I'm understanding correctly, the fixed-window strategy should reset the limit based on the specified period, in this case, every minute (at zero seconds). However, it currently seems to reset the limit based on the second of the first request (moving-window strategy).

from limits.

Yes this is the expected behavior of the fixed window strategy is implemented (regardless of the storage type) - i.e. the window is constructed based on the second of the first hit.

from limits.

Yes this is the expected behavior of the fixed window strategy is implemented (regardless of the storage type) - i.e. the window is constructed based on the second of the first hit.

So If I want to make it reset every month let's say, how to achieve that?

from limits.

So If I want to make it reset every month let's say, how to achieve that?

You could call the reset method on the storage if it supports it using a scheduled job

from limits.