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.
Fix misleading "Session not found" error for HTTP 404 responses when no session is present
Motivation and Context
Fixes issue #426 where the WebFlux transport was incorrectly showing "Session not found" error messages
for any HTTP 404 response, even when the endpoint didn't exist or no session was sent. This made
debugging difficult for developers who couldn't distinguish between endpoint configuration issues vs
session management problems.
The
sendMessage
method was treating all 404 responses as session errors without checking if a sessionID was actually sent with the request.
How Has This Been Tested?
All existing unit tests pass, including specific error handling tests
WebClientStreamableHttpTransportErrorHandlingTest
validates both scenarios:404 without session ID → Generic
McpTransportException
(endpoint issue)404 with session ID →
McpTransportSessionNotFoundException
(session issue)No functional changes to existing behavior when sessions are properly established
Breaking Changes
None. This is a bug fix that improves error message accuracy without changing the API or expected
behavior.
Types of changes
Checklist
Additional context