Repository navigation
Return 400 for invalid UTF-8 query parameters - #486
Merged
Merged
Conversation
ydah
force-pushed
the
fix/invalid-utf8-query-parameter
branch
from
September 24, 2026 07:20
7388950 to
45f632b
Compare
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
2 participants
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.
OpenAPI 3 query validation can raise
ArgumentErrorwhen a query value contains invalid UTF-8 bytes and a string pattern is checked. The exception escaped validation, causing a server error for malformed query values.Convert the exception to
Committee::InvalidRequestso the middleware returns a client error, and add regression coverage for a percent-encoded invalid UTF-8 value.Fixes: #268