Skip to content
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

golang filter: should return status 500 instead of 413 when response body exceeding buffer limit #34240

Merged
merged 1 commit into from
May 21, 2024

Conversation

doujiang24
Copy link
Member

fix #34115

it's hard to add tests for such case, leave it for now.

Commit Message:
Additional Description:
Risk Level:
Testing:
Docs Changes:
Release Notes:
Platform Specific Features:
[Optional Runtime guard:]
[Optional Fixes #Issue]
[Optional Fixes commit #PR or SHA]
[Optional Deprecated:]
[Optional API Considerations:]

…body exceeding buffer limit

Signed-off-by: doujiang24 <doujiang24@gmail.com>
@doujiang24
Copy link
Member Author

@spacewander Could you please take a look?

@spacewander
Copy link
Contributor

@spacewander Could you please take a look?

Approved, thanks!

@zuercher zuercher merged commit 1b7d9ac into envoyproxy:main May 21, 2024
51 checks passed
@doujiang24 doujiang24 deleted the golang-fix-buffer branch May 22, 2024 02:58
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

golang filter returns with unexpected response code when the payload exceeds its buffer limit size
3 participants