feat: support custom headers in direct connection HTTP stream #3
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.
Motivation and Context
This change adds support for sending custom headers when establishing a direct HTTP stream connection.
It's necessary for use cases where authentication tokens or other metadata must be sent with the initial request.
How Has This Been Tested?
Tested locally in a real application using both static and dynamic header values.
Verified that headers are correctly set and received on the server side.
Breaking Changes
No breaking changes. Existing connections without custom headers continue to work as before.
Types of changes
Checklist
Additional context
This change introduces a new configuration option `headers` within the direct connection stream setup.