simpleStreamableHttp: fix example code #660
Merged
+12
−14
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.
Update simpleStreamableHttp.ts example so its in-memory OAuth server isn't always strict (only make it strict if
--oauth-strict
isn't passed).Follow up to #638 cc/ @pcarleton
Motivation and Context
While testing an old inspector's refresh flow w/ the new simpleStreamableHttp.ts, realized the in-memory oauth is too strict. This loosens it unless
--oauth-strict
is set.How Has This Been Tested?
Using a pre-resources inspector (before modelcontextprotocol/inspector#526) + new typescript-sdk (after #638):
Breaking Changes
None (just better example in main branch)
Types of changes