We read every piece of feedback, and take your input very seriously.
To see all available qualifiers, see our documentation.
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
When using Laravel's RateLimiter, the attempts are stored globally instead of separately per tenant.
Execute in the first tenant:
RateLimiter::attempt( 'key', 100, function () { return true; }, 60*60 );
In the second tenant, you can see that the remaining attempts is 99 instead of 100:
RateLimiter::remaining( 'key', 100 );
Like the Cache calls, I think that RateLimiter calls should be separated by the tenant.
11.9
3.8
The text was updated successfully, but these errors were encountered:
What bootstrappers do you have enabled?
Sorry, something went wrong.
The default ones from 3.8, nothing changed
Does enabling the RedisTenancyBootstrapper fix this?
stancl
No branches or pull requests
Bug description
When using Laravel's RateLimiter, the attempts are stored globally instead of separately per tenant.
Steps to reproduce
Execute in the first tenant:
In the second tenant, you can see that the remaining attempts is 99 instead of 100:
Expected behavior
Like the Cache calls, I think that RateLimiter calls should be separated by the tenant.
Laravel version
11.9
stancl/tenancy version
3.8
The text was updated successfully, but these errors were encountered: