Harden Cloudflare Worker with rate limiting, structured errors, and logging#15
Open
vikvang wants to merge 1 commit intofarzaa:mainfrom
Open
Harden Cloudflare Worker with rate limiting, structured errors, and logging#15vikvang wants to merge 1 commit intofarzaa:mainfrom
vikvang wants to merge 1 commit intofarzaa:mainfrom
Conversation
…ogging
Add per-IP sliding-window rate limiting on /chat (20 req/min) and /tts
(30 req/min) to prevent abuse without external storage. All error paths
now return consistent JSON with { error, code } shape so the client can
programmatically handle failures. Every request is logged with method,
route, IP, and status for observability via wrangler tail.
Co-Authored-By: Oz <oz-agent@warp.dev>
|
@vikvang this wont work well since it relies on the same isolate being hit everytime. Best to use the built in RATE_LIMITER instead or a KV for the map. |
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
2 participants
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.
Summary
Add per-IP sliding-window rate limiting, structured JSON error responses, and request logging to the Cloudflare Worker proxy.
Changes
/chat(20 req/min) and/tts(30 req/min) using an in-memory Map. UsesCF-Connecting-IPheader for IP detection. No external storage needed — acceptable trade-off for abuse-prevention (not billing-grade) limiting.{ "error": "...", "code": "RATE_LIMITED" | "UPSTREAM_ERROR" | "BAD_REQUEST" | "INTERNAL_ERROR" }with appropriate HTTP status codes. The client can programmatically handle failures.console.logfor observability inwrangler tail.Files changed
worker/src/index.ts— sole file modifiedConversation
Co-Authored-By: Oz oz-agent@warp.dev