-
Notifications
You must be signed in to change notification settings - Fork 3.8k
New issue
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
🚀 Feature: Custom abuse control/rate limits #5737
Comments
DH-555
changed the title
🚀 Feature: Custom abuse control limits
🚀 Feature: Custom abuse control/rate limits
Jun 21, 2023
Hi @DHsoftw , as I can see there is another issue regarding the same feature request already open which is #2953 , can we please close this issue since it is a duplicate and we can carry the conversation there itself? |
This was referenced Jul 25, 2023
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
🔖 Feature description
Make all rate limits (requests per second limits) or potential abuse limits, like pagination or maximum number of fetched documents customizable
🎤 Pitch
By allowing users to customise their rate limits, that could make it more difficult to abuse an app. For example, if an app doesn't needs to make more than 10 requests, you could fine-tune to a smaller limit to prevent abuse and save resources in your server from bad requests.
Same with pagination and maximum amount of fetched documents. By allowing customizing it, you can prevent someone making a query with 1000 documents in an app that doesn't needs fetching more than 30 documents at once.
With pagination it could be great having custom limits too, since they're slower when the amount of pages increases.
👀 Have you spent some time to check if this issue has been raised before?
🏢 Have you read the Code of Conduct?
The text was updated successfully, but these errors were encountered: