-
-
Notifications
You must be signed in to change notification settings - Fork 3.7k
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
fix(next-auth): cannot parse action at /session #10218
fix(next-auth): cannot parse action at /session #10218
Conversation
fix: support apps hosted on subpaths
The latest updates on your projects. Learn more about Vercel for Git ↗︎
1 Ignored Deployment
|
@bwallberg is attempting to deploy a commit to the authjs Team on Vercel. A member of the Team first needs to authorize it. |
Codecov ReportAttention: Patch coverage is
Additional details and impacted files@@ Coverage Diff @@
## main #10218 +/- ##
==========================================
- Coverage 39.36% 39.35% -0.01%
==========================================
Files 171 171
Lines 27288 27292 +4
Branches 1159 1165 +6
==========================================
Hits 10742 10742
- Misses 16546 16550 +4 ☔ View full report in Codecov by Sentry. |
* fix(next-auth): cannot parse action at /session fix: support apps hosted on subpaths * refactor: use createActionURL from core directly --------- Co-authored-by: Nico Domino <[email protected]> Co-authored-by: Thang Vu <[email protected]>
* fix(next-auth): cannot parse action at /session fix: support apps hosted on subpaths * refactor: use createActionURL from core directly --------- Co-authored-by: Nico Domino <[email protected]> Co-authored-by: Thang Vu <[email protected]>
☕️ Reasoning
All frameworks should use the core util
createActionsURL()
, however sincenext-auth
doesn't provide the request itself we have to rely on thex-forwarded-proto
header that next-auth sets so instead of callingcreateActionsURL
directly we wrap it to avoid some unnecessary code duplication.Depends on #10094
🧢 Checklist
🎫 Affected issues
Fixes the original issue described in #10081
Depends on #10094
📌 Resources