[k2] relax constraints on HTTP content-type header#1513
Merged
Conversation
apolyakov
added
bug
denisichh
approved these changes
Jan 29, 2026
apolyakov
deleted the
apolyakov/k2-relax-constaints-on-http-content-type-header
branch
denisichh
pushed a commit
that referenced
this pull request
Feb 3, 2026
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.
This PR updates the validation logic for the Content-Type header. Previously, the header was required to exactly match
application/x-www-form-urlencodedand other content types. With this change, the validation is relaxed: the Content-Type header now only needs to containapplication/x-www-form-urlencoded(or other).