Repository navigation
fix(dashboard): enforce image proxy limits while streaming - #1118
Conversation
|
@maskjelly is attempting to deploy a commit to the Databuddy OSS Team on Vercel. A member of the Team first needs to authorize it. |
|
The latest updates on your projects. Learn more about Vercel for GitHub. 1 Skipped Deployment
|
|
Important Review skippedAuto reviews are disabled on this repository. Please check the settings in the CodeRabbit UI or the ⚙️ Run configuration
You can disable this status message by setting the Use the checkbox below for a quick retry:
Thanks for using CodeRabbit! It's free for OSS, and your support helps us grow. If you like it, consider giving us a shout-out. Comment |
|
ed6c3e6 to
47503ef
Compare
d1a2af8
into
databuddy-analytics:staging
Description
The image proxy previously buffered an entire upstream response before applying its 2 MiB limit. This checks size while reading and cancels oversized or rejected responses early.
Slice
bug(author cannot apply upstream labels)stagingChanges
Validation
bun run lint: passed.bun run check-types: 37/37 tasks passed.bun test app/api/image-proxy/route.test.ts: 11 passed, including oversized streams, exact-limit success, rejected-body cancellation, read failure, SSRF rejection, and a stalled body interrupted by the deadline.Merge notes
This is an independent change based on current
staging. The 2 MiB bound applies to application accumulation; the fetch implementation supplies each incoming chunk. Maintainer review and CI are still required.Before merge
action_requiredwith zero jobs).AI disclosure: implemented and tested with Codex. Source and local test results were reviewed during implementation; maintainer human review is required.