feat: add middleware support to mcp_http_handler #112
Merged
Conversation
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
1 participant
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.
📌 Summary
Add Middleware Support to
mcp_http_handlerfor Enhanced Request/Response Processing and future Oauth support.This pull request adds middleware support to
the mcp_http_handlermodule, enabling modular and extensible processing of HTTP requests and responses. The implementation includes a Middleware trait, a MiddlewareChain struct for chaining multiple middleware instances, and utility functions to support consistent body handling.This feature enables developers to insert custom logic- such as logging, authentication, or rate limiting—into the HTTP request/response pipeline in a thread-safe, asynchronous-compatible way, independent of the underlying HTTP framework.
🛠️ Testing Steps