feat(mcp): webflux support custom http header #169
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.
For #161
Motivation and Context
If I can change the HTTP request header, I can do some extra processing on the server side like data permission checking. I briefly checked this article https://modelcontextprotocol.io/specification/2025-03-26/basic/authorization It doesn't seem to have been developed yet, so I don't know exactly how it will be used.
For common API Server to MCP Server conversion scenarios, the API Server already has its own authentication methods, and functional access control, data access control, for the current only missing the HTTP Header transfer.
How Has This Been Tested?
Breaking Changes
Types of changes
Checklist
Additional context