When an SSE response ended before its JSON-RPC response arrived, HttpTransport discarded the stream. It did not retain the SSE id or retry fields, so the pending request waited for its timeout instead of resuming from the last event.
The fix
Track the latest SSE event ID and the server-provided retry interval.
Resume interrupted streams with a GET carrying Accept: text/event-stream, Mcp-Session-Id, and Last-Event-ID.
By default, use 1/2/4/8/10 second fallback backoff and stop after five consecutive failed attempts. A server retry: value takes precedence.
Stop reconnecting after a final response, timeout or cancellation, explicit close, or when the stream has no resumable event ID.
Add the sse-retry conformance path and remove it from the expected-failure baseline.
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
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.
The bug
When an SSE response ended before its JSON-RPC response arrived, HttpTransport discarded the stream. It did not retain the SSE id or retry fields, so the pending request waited for its timeout instead of resuming from the last event.
The fix
Tests
Fixes #327.