Skip to content
Open
Show file tree
Hide file tree
Changes from all commits
Commits
File filter

Filter by extension

Filter by extension

Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
11 changes: 11 additions & 0 deletions docs/mcpgodebug.md
Original file line number Diff line number Diff line change
Expand Up @@ -28,6 +28,17 @@ Options listed below were added and will be removed in the 1.11.0 version of the
that large integers and other exact JSON values do not silently lose
precision.

- `nosessionreinit` added. If set to `1`, the streamable HTTP client treats a
`404 Not Found` response to a request carrying an `Mcp-Session-Id` as
terminal, failing the connection with an error wrapping `ErrSessionMissing`,
restoring the previous behavior. The default behavior was changed to follow
the 2025-11-25 specification, which requires the client to start a new
session: the client re-sends its `initialize` request without a session ID,
adopts the new session ID and sends the failed request again. The 404 stays
terminal when the session holds server-side state that a new session would
lose (a `resources/subscribe` subscription or a `logging/setLevel` level) or
when the server negotiates a different protocol version. See issue #1299.

### 1.8.0

Options listed below were added and will be removed in the 1.9.0 version of the SDK.
Expand Down
11 changes: 11 additions & 0 deletions internal/docs/mcpgodebug.src.md
Original file line number Diff line number Diff line change
Expand Up @@ -27,6 +27,17 @@ Options listed below were added and will be removed in the 1.11.0 version of the
that large integers and other exact JSON values do not silently lose
precision.

- `nosessionreinit` added. If set to `1`, the streamable HTTP client treats a
`404 Not Found` response to a request carrying an `Mcp-Session-Id` as
terminal, failing the connection with an error wrapping `ErrSessionMissing`,
restoring the previous behavior. The default behavior was changed to follow
the 2025-11-25 specification, which requires the client to start a new
session: the client re-sends its `initialize` request without a session ID,
adopts the new session ID and sends the failed request again. The 404 stays
terminal when the session holds server-side state that a new session would
lose (a `resources/subscribe` subscription or a `logging/setLevel` level) or
when the server negotiates a different protocol version. See issue #1299.

### 1.8.0

Options listed below were added and will be removed in the 1.9.0 version of the SDK.
Expand Down
Loading