Fix remaining redirects to 0.0.0.0 in callback and middleware #118
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
The previous fix missed the success redirect in the callback route (different closing paren pattern) and the middleware login redirect. Both now use APP_BASE_URL with fallback to request origin. Co-Authored-By: Claude Opus 4.6 <noreply@anthropic.com>
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
callback/route.ts:167) was missed by Use APP_BASE_URL for all OAuth redirects #116 due to a different closing-paren pattern — still usedrequest.urlproxy.ts) also usedrequest.urlfor login redirectsAPP_BASE_URLwith fallback torequest.nextUrl.originrequest.urlusages in the codebaseTest plan
forecasting-staging.tailc06f30.ts.net/loginon the correct host🤖 Generated with Claude Code