-
-
Notifications
You must be signed in to change notification settings - Fork 3.1k
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: add getSetCookie to session cookies if supported #8631
fix: add getSetCookie to session cookies if supported #8631
Conversation
The latest updates on your projects. Learn more about Vercel for Git ↗︎ 2 Ignored Deployments
|
@edenstrom is attempting to deploy a commit to the authjs Team on Vercel. A member of the Team first needs to authorize it. |
Closed due to not currently working.. Fixing. |
hey @edenstrom are you still working on a fix for this? |
Yes, reopened PR with fix. :) Works here. https://next-auth-error-vercel.vercel.app/ |
You're a lifesaver 🔥 |
Could we get this merged? |
f2c23db
into
nextauthjs:feat/nextjs-auth
☕️ Reasoning
I saw that .getSetCookie were finally supported in the edge runtime when deployed to Vercel. This uses
getSetCookie
if supported, otherwise falls back to.get('set-cookie)
Deployed a version with this patch here:
Reproduction deployment: next-auth-error-vercel.vercel.app
Reproduction repo: edenstrom/next-auth-error-vercel
🧢 Checklist
🎫 Affected issues
This solves the long standing issue were chunked cookies didn't work when using the edge runtime deployed to Vercel.
#7443 (comment)
Related issues:
fetch
vercel/edge-runtime#536📌 Resources