Repository navigation
fix: reject non-JSON Content-Type with 415 and validate protocol version header on initialize - #968
Closed
suryateja-g13 wants to merge 2 commits into
Closed
suryateja-g13 wants to merge 2 commits into
suryateja-g13 wants to merge 2 commits into
Conversation
Copy link
Copy Markdown
Sorry, something went wrong.
…ion on initialize HttpServletStreamableServerTransportProvider and HttpServletStatelessServerTransport accepted POST requests regardless of Content-Type, processing text/plain and form-encoded bodies as if they were application/json. Add an early Content-Type guard in doPost() on both transports that returns HTTP 415 Unsupported Media Type when Content-Type is absent or does not start with application/json. Also validate on initialize requests that the MCP-Protocol-Version HTTP header, when present, is consistent with the protocolVersion field in the JSON-RPC body. A mismatch returns HTTP 400 with a JSON-RPC INVALID_REQUEST error. Fixes modelcontextprotocol#961 Fixes modelcontextprotocol#963 Signed-off-by: Gorre Surya <suryateja.g13@gmail.com>
suryateja-g13
force-pushed
the
fix/961-content-type-validation
branch
from
34d1eb6 to
580cdf3
Compare
May 19, 2026 02:33
…idation Covers the validation added in the previous commit: - HttpTransportValidationTests: verifies POST with non-JSON or missing Content-Type returns 415 for both streamable and stateless transports, and that application/json with charset parameter is accepted. - StreamableTransportProtocolVersionTests: verifies that a matching MCP-Protocol-Version header passes, an absent header passes, and a mismatched header returns 400. Signed-off-by: Gorre Surya <suryateja.g13@gmail.com>
Copy link
Copy Markdown
Contributor
|
Superseded by #1164 for the content-type |
Sorry, something went wrong.
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.
Fixes #961 and #963.
Changes
#961 — Content-Type validation (HTTP 415)
HttpServletStreamableServerTransportProvider.doPost() accepted POST requests regardless of their Content-Type header, processing text/plain, application/x-www-form-urlencoded, and requests with no Content-Type identically to application/json requests.
Added an early guard in doPost() that returns HTTP 415 Unsupported Media Type when Content-Type is absent or does not start with application/json.
#963 — Protocol version header/body consistency on initialize
When the MCP-Protocol-Version request header on an initialize request disagrees with params.protocolVersion in the JSON-RPC body, the server now returns HTTP 400 with a JSON-RPC INVALID_PARAMS error rather than silently accepting the mismatched input.
Test plan