HTTP client fails connect when the server acknowledges notifications/initialized with an empty 200
維護者通常 1 天內回覆
評估
- 難度
- 1/5
- 預估耗時
- 1 小時以內
- 新手友好度
- 20/100
- Issue 類型
- 缺陷
- 描述清晰度
- 描述清楚
- 活躍度
- 停滯
- 技術堆疊
- ruby
研究方向
Read MCP::Client::HTTP#send_request and resolve_response_body, which the issue identifies as the failing path. Check the existing tests for the notifications/initialized response and the linked pull requests #599 and #600 to see the work already underway. Done means a notification acknowledged with a bodyless 2xx no longer raises, while a request with the same response still raises unsupported_media_type.
由索引模型根據 Issue 內容生成。
描述
Observed behavior
With mcp 1.7.0 (and 0.15.0), MCP::Client#connect with the legacy initialize handshake over Streamable HTTP fails against servers that acknowledge notifications/initialized with 200 OK, an empty body and no Content-Type, instead of 202 Accepted:
MCP::Client::RequestHandlerError: Unsupported Content-Type: nil. Expected application/json or text/event-stream.
error_type: :unsupported_media_type
The initialize request succeeds. The error comes from the following notifications/initialized POST: send_request passes the response to resolve_response_body, which returns early only for 202 and raises for any other response without a JSON or SSE content type.
For example, Freshservice's hosted MCP server (Freshworks, https://<account>.freshservice.com/mcp) responds this way:
POST /mcp {"jsonrpc":"2.0","method":"notifications/initialized"}
HTTP/1.1 200 OK
Content-Length: 0
I ran each SDK's client against the same Freshservice server, with the same OAuth token, on 2026-10-13:
| Client | notifications/initialized response |
Result |
|---|---|---|
TypeScript SDK 1.32.1 (StreamableHTTPClientTransport) |
200, no Content-Type |
Connects, listTools returns 40 tools |
Python SDK 2.3.0 (streamable_http_client) |
200, no Content-Type |
Connects, list_tools returns 40 tools |
Ruby SDK main (7735046) |
200, no Content-Type |
Unsupported Content-Type: nil |
Expected behavior
The spec says the server MUST return 202 Accepted with no body when it accepts a notification (Transports, Sending Messages to the Server), so the server is out of spec here. Still, a notification awaits no response, and both reference SDKs accept any 2xx for it:
- TypeScript SDK 1.32.1: after the
202check, the content type is checked only when the POST carried a request. For a notification, any other 2xx reaches the// No requests in message but got 200 OK - still need to release connectionbranch, which cancels the body and returns. - Python SDK 2.3.0: after the
202check, the content-type handling is gated onisinstance(message, JSONRPCRequest), with the comment "The server MUST NOT send a response to notifications." A notification answered with 2xx falls through without reading the body.
In both, a request answered the same way is still an error: TypeScript throws StreamableHTTPError and Python returns a JSON-RPC error, each with "Unexpected content type".
I'd expect connect to succeed when a notification is acknowledged with a 2xx and no body. Requests should keep raising unsupported_media_type for the same response.
Reproduction
require "mcp"
require "webmock"
include WebMock::API
WebMock.enable!
url = "https://example.com/mcp"
stub_request(:post, url)
.with { |req| JSON.parse(req.body)["method"] == "initialize" }
.to_return(
status: 200,
headers: { "Content-Type" => "application/json" },
body: { jsonrpc: "2.0", id: "1", result: { protocolVersion: "2025-11-25", capabilities: {}, serverInfo: { name: "s", version: "1" } } }.to_json,
)
stub_request(:post, url)
.with { |req| JSON.parse(req.body)["method"] == "notifications/initialized" }
.to_return(status: 200, body: "")
MCP::Client.new(transport: MCP::Client::HTTP.new(url: url)).connect(mode: :legacy)
# => MCP::Client::RequestHandlerError: Unsupported Content-Type: nil. ...
Fix: #599. It returns nil instead of raising in that branch when the message is a notification and the status is 2xx, matching the behaviour above.
- 主要語言
- Ruby
- 星號
- 924
- 分支
- 136
- 平均合併
- 1 天 6 小時
- 30 天內合併 PR
- 35
環境準備
- 沒有 Dockerfile 或 Docker Compose 檔案
- 沒有 Pull Request 範本
- 閱讀貢獻指南
從這裡開始
- 先讀完整個 Issue，再讀專案的貢獻指南。
- 在 Issue 下留言說明你要接手 —— 這能避免兩個人做同樣的事。
- Fork 儲存庫，在一個分支上完成修改。
- 送出 Pull Request，並在描述裡引用這個 Issue 編號。
modelcontextprotocol/ruby-sdk 的其他 Issue
-
Support modelcontextprotocol/experimental-ext-triggers-events可能已有人在做 @koic 於 3 天前認領。 未關閉enhancement
modelcontextprotocol/ruby-sdk#594 · 已指派 1 人 ·
維護者通常 1 天內回覆
-
SEP-2640: Skills Extension可能已有人在做 @koic 於 22 天前認領。 未關閉enhancement
modelcontextprotocol/ruby-sdk#568 · 1 則留言 · 2 個 reaction · 已指派 1 人 ·
維護者通常 1 天內回覆
-
SEP-2663: Tasks Extension可能重新可做 @koic 於 108 天前認領，目前沒有進行中的 PR。 未關閉enhancement
modelcontextprotocol/ruby-sdk#391 · 1 個 reaction · 已指派 1 人 ·
維護者通常 1 天內回覆
查看 modelcontextprotocol/ruby-sdk 的全部 Issue
相似的 Issue
-
bug
難度 2/5 1-3 小時 新手友好度 82/100
維護者通常 1 天內回覆
-
難度 2/5 1-3 小時 新手友好度 75/100
GantMan/jail-monkey#380 ·
-
難度 2/5 1-3 小時 新手友好度 62/100
voxpupuli/puppet-wireguard#151 ·
-
bug
難度 2/5 1-3 小時 新手友好度 72/100
維護者通常 1 天內回覆
-
Search accepts any value for `requests_per_page` and `per_page`可能已有人在做 關聯的 PR 仍在進行中或已合併。 未關閉bug f:search
難度 2/5 1-3 小時 新手友好度 78/100
維護者通常 1 天內回覆