add IP-based rate limiting to Cloudflare Worker #37
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Description:
This PR introduces IP-based rate limiting to the Cloudflare Worker handling
/v1/translate
and/v1/explain
routes. The main goal is to protect the Gemini API from abuse and prevent excessive requests that could exhaust our quota.Changes Made:
checkRateLimit
function using Cloudflare KV to track request counts per IP.429 Too Many Requests
error if exceeded.fetch
handler to integrate the rate limiting check before processing requests./v1/translate
and/v1/explain
routes.Benefits:
Screenshots: