Fix weird request exception issue - #330
Merged
Merged
Conversation
alexbainter
force-pushed
the
alex-329-trailing-slash-middleware-fix
branch
from
August 12, 2026 18:18
203b3d4 to
f626633
Compare
aaronjae22
approved these changes
Aug 12, 2026
alexbainter
changed the title
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
2 participants
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.
Closes #329.
Not 100% sure why, but refactoring our MCP trailing slash middleware to a pure ASGI middleware (not inheriting from BaseHTTPMiddleware) stopped the error in #329 🤷