Adding better deeplink support for streamable-http #3986
Merged
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.
Problem
Deeplinks for streamable HTTP extensions had two issues:
transport=streamable_http, ignoredtype=streamable_http(some organizations like Kiwi Flight search have the goose URIThis caused extensions like Kiwi.com to be registered as SSE instead of streamable_http, and prevented extensions requiring auth headers from working via deeplinks.
Solution
Enhanced the deeplink parser to:
transportandtypeparametersheader=key%3Dvalueparameters for streamable HTTP extensionsWhy
typeParameter Support?The deeplink parser only recognized
transport=streamable_httpbut the actual config schema usestype: 'streamable_http'. This inconsistency led extension developers (like Kiwi.com) to naturally usetype=streamable_httpin their deeplinks, expecting it to match the config field name.The fix maintains backward compatibility with
transportwhile adding support for the more intuitivetypeparameter that aligns with the config schema.Examples Now Working
Fixes #3438