Repository navigation
fix: admit image-heavy requests up to 256 MiB - #86
Merged
Merged
Conversation
pavelhov
changed the title
pavelhov
marked this pull request as ready for review
October 22, 2026 20:10
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
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.
Image-heavy HTTP requests between 128 and 256 MiB now reach normal processing instead of receiving an early 413 from Bun. The listener uses the existing shared 256 MiB parser cap; bounded reads, decompression safeguards, authentication, and the 2 MiB management limit remain unchanged. Prepares version 0.1.22.
Real-listener regression tests cover 128 MiB + 1, exactly 256 MiB, and 256 MiB + 1 without allocating large bodies. Removing the listener setting reproduces two failures; restoring it passes all three tests.
Validation: typecheck, privacy scan, all 632 proxy test files (one build/install collision recovered through the runner’s same-mode batch retry), GUI lint/i18n/888 tests/build, docs frozen install/build, macOS core/UI tests, and CLI help smoke passed. Independent review found no actionable issues.
Security and distribution review: no authentication, credential, logging, updater, or publishing-tool changes. The release uses the existing external single-link 0600 signing key, verified matching public key, and pinned Sparkle 2.9.6 tools. The universal archive retains the existing unnotarized-preview designation; fresh arm64 installed updater tests passed for stopped, native-routing, proxy-routing, and active-request recovery states. Intel slices are verified, but Intel updater execution is unavailable without Rosetta. Signed draft-asset verification remains a pre-publication gate.