-
Notifications
You must be signed in to change notification settings - Fork 3.1k
fix: enforce request body size limit during buffering in AiProxyPlugin #6897
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Open
wy471x
wants to merge
4
commits into
apache:master
Choose a base branch
from
wy471x:fix_AiProxyPlugin-validates-body-size
base: master
Could not load branches
Branch not found: {{ refName }}
Loading
Could not load tags
Nothing to show
Loading
Are you sure you want to change the base?
Some commits from the old base branch may be removed from the timeline,
and old review comments may become outdated.
+29
−12
Open
Changes from all commits
Commits
Show all changes
4 commits
Select commit
Hold shift + click to select a range
cf83bb7
fix: enforce request body size limit during buffering in AiProxyPlugin
wy471x b6b9986
test: add unit test for DataBufferLimitException → 413 in AiProxyPlugin
wy471x 75d19ca
Merge branch 'master' into fix_AiProxyPlugin-validates-body-size
Aias00 43981cf
Merge branch 'master' into fix_AiProxyPlugin-validates-body-size
wy471x File filter
Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
There are no files selected for viewing
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
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
Oops, something went wrong.
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.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Context
Nice catch, this is a real fix. Buffering the whole body with the single argument DataBufferUtils.join before checking readableByteCount meant the memory was already spent by the time the limit was enforced, and passing the maxSize into join so it aborts mid stream and onErrorResume maps it to 413 is the right shape.
▎ Example: The test mocks DataBufferUtils.join statically and matches the size argument with anyInt(), so it only proves the DataBufferLimitException to 413 mapping and never pins the limit the plugin is responsible for. A regression that weakened the limit, say passing Integer.MAX_VALUE or a mis scaled constant, would still pass green.
Suggestion
An ArgumentCaptor or an eq(MAX_REQUEST_BODY_SIZE_BYTES) matcher so the test asserts join is called with exactly the 5MB constant would close that gap. If it is easy, one unmocked test that feeds a real body over the limit through doExecute and asserts 413 with no downstream call would make the guarantee end to end.
NOTE
Not blocking, the production change looks correct as is.