feat(nextjs)!: Remove middleware bypass for tunnel route requests - #24589
Merged
Merged
Conversation
In webpack builds, the middleware wrapper returned early for requests to the tunnel route so the user's middleware never ran for them. Turbopack builds never had this behavior, and keeping the SDK's request matching in sync with the tunnel rewrite is fragile. Tunnel requests now go through the user's middleware like any other request. Users whose middleware blocks unauthenticated requests need to exclude the tunnel route in their matcher. Refs JS-3719 Co-Authored-By: Claude Fable 5.1 <noreply@anthropic.com>
Member
Author
|
bugbot run |
There was a problem hiding this comment.
Cursor Bugbot has reviewed your changes and found 1 potential issue.
❌ Bugbot Autofix is OFF. To automatically fix reported issues with cloud agents, enable autofix in the Cursor dashboard.
Reviewed by Cursor Bugbot for commit 5df0122. Configure here.
Contributor
size-limit report 📦
|
Co-Authored-By: Claude Fable 5.1 <noreply@anthropic.com>
chargome
marked this pull request as ready for review
September 22, 2026 12:15
chargome
requested review from
nicohrubec and
s1gr1d
and removed request for
a team
September 22, 2026 12:15
logaretm
approved these changes
Sep 22, 2026
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
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.

Follow-up to #24499.
In webpack builds, the middleware wrapper skipped the user's middleware for tunnel route requests so that middleware redirecting unauthenticated requests would not swallow Sentry events. Keeping that check in sync with the tunnel rewrite is fragile, and Turbopack builds never had it.
This removes the bypass so tunnel requests go through the user's middleware like any other request on both bundlers. Middleware that blocks unauthenticated requests globally has to exclude the tunnel route in its matcher, which requires a fixed string route instead of
tunnelRoute: true.Refs JS-3719