fix: issue 116 - custom_streamable_http_endpoint #117
+219
−2
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.
📌 Summary
I noticed while trying to configure a Streamable HTTP MCP server using
HyperServerOptionsthatcustom_streamable_http_endpointdoesn't seem to work. While digging through the code I noticedHyperServerOptions impl'spub fn streamable_http_endpointinstead returns self.custom_messages_endpoint🔍 Related Issues
HyperServerOptions::custom_streamable_http_endpointis not properly used #116✨ Changes Made
HyperServerOptions::streamable_http_endpoint()to consume the propercustom_streamable_http_endpointconfig value.🛠️ Testing Steps
I didn't add unit tests for this because I couldn't find any related tests. Happy to add some unit tests here, not sure if there's a preference on exactly where they should live.