feat(http): enforce a request body size limit#150
Open
SVilgelm wants to merge 1 commit into
Open
Conversation
Add a configurable max_request_body_size (default 4 MiB) and reject larger streamable-HTTP request bodies with 413 instead of buffering them. Assisted-By: Claude Opus 4.7 <noreply@anthropic.com> Signed-off-by: Sergey Vilgelm <sergey@vilgelm.com>
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
1 participant
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
The streamable HTTP endpoint buffered the entire request body into a
Stringwith no limit, so a single large POST could exhaust server memory. The router now enforces a configurable body-size limit and rejects oversized requests with413 Payload Too Large.🔍 Related Issues
✨ Changes Made
HyperServerOptions::max_request_body_size(defaults to 4 MiB).DefaultBodyLimitto the router inapp_routes.413for oversized bodies.