add custom headers on initial _startOrAuth call #318
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.
Ensure that custom headers provided in
this._requestInit?.headers
are included in the initial call to the/sse
endpoint.Motivation and Context
Fixes #317, where custom headers (e.g.
Host
,X-*
) were not sent in the initial/sse
request, but were correctly sent in/messages
. This is needed for MCP servers behind proxies that rely on these headers.This PR aligns the behavior of the
/sse
request withsend()
by ensuring that all custom headers (when provided) are forwarded appropriately.How Has This Been Tested?
/sse
request.Breaking Changes
No
Types of changes
Checklist
Additional context
N/a