MCP Streamable HTTP: return 202/no-body for notification-only POSTs#22597
Open
Copilot wants to merge 2 commits into
Open
MCP Streamable HTTP: return 202/no-body for notification-only POSTs#22597Copilot wants to merge 2 commits into
Copilot wants to merge 2 commits into
Conversation
Copilot
AI
changed the title
[WIP] Fix Netdata MCP v2.10.3 Codex Streamable HTTP handshake failure
MCP Streamable HTTP: return 202/no-body for notification-only POSTs
Jun 1, 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
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.



Codex Streamable HTTP MCP startup failed after
initializebecause Netdata returned200with an SSEcompleteevent fornotifications/initialized. Per MCP Streamable HTTP transport semantics, notification-only POSTs should return202 Acceptedwith no body.Handshake semantics fix (SSE adapter)
src/web/mcp/adapters/mcp-sse.c(mcp_sse_serialize_response) to detect requests that produce no JSON-RPC responses (responses_used == 0) and return:HTTP 202 AcceptedcompleteenvelopeBehavior preserved for response-bearing requests
HTTP 200 OKtext/event-streammessageevent(s) + trailingcompleteevent