Repository navigation
Deserialize header parameters regardless of casing - #490
Merged
Merged
Conversation
geemus
approved these changes
Oct 17, 2026
geemus
left a comment
geemus
left a comment
Member
There was a problem hiding this comment.
lgtm.
Case-insensitive headers cause so many problems! Thanks for the fix.
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.
Rack exposes
X-Ids: 1,2asX-IDS, while parameter deserialization looks up the schema name with exact casing. An OpenAPI 3 array header namedX-Idsis therefore left as a string and rejected with a 400 response.Match header names case-insensitively before deserialization. Add request-level regression coverage for array headers and a unit test for object headers, unknown headers, and the original input hash.