-
Notifications
You must be signed in to change notification settings - Fork 26.6k
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
Cookies, logout/auth issue after 14.2 #66934
Comments
We could not detect a valid reproduction link. Make sure to follow the bug report template carefully. Why was this issue closed?To be able to investigate, we need access to a reproduction to identify what triggered the issue. We need a link to a public GitHub repository (template for App Router, template for Pages Router), but you can also use these templates: CodeSandbox: App Router or CodeSandbox: Pages Router. The bug template that you filled out has a section called "Link to the code that reproduces this issue", which is where you should provide the link to the reproduction.
What should I do?Depending on the reason the issue was closed, you can do the following:
In general, assume that we should not go through a lengthy onboarding process at your company code only to be able to verify an issue. My repository is private and cannot make it publicIn most cases, a private repo will not be a sufficient minimal reproduction, as this codebase might contain a lot of unrelated parts that would make our investigation take longer. Please do not make it public. Instead, create a new repository using the templates above, adding the relevant code to reproduce the issue. Common things to look out for:
I did not open this issue, but it is relevant to me, what can I do to help?Anyone experiencing the same issue is welcome to provide a minimal reproduction following the above steps by opening a new issue. I think my reproduction is good enough, why aren't you looking into it quickly?We look into every Next.js issue and constantly monitor open issues for new comments. However, sometimes we might miss one or two due to the popularity/high traffic of the repository. We apologize, and kindly ask you to refrain from tagging core maintainers, as that will usually not result in increased priority. Upvoting issues to show your interest will help us prioritize and address them as quickly as possible. That said, every issue is important to us, and if an issue gets closed by accident, we encourage you to open a new one linking to the old issue and we will look into it. Useful Resources |
Link to the code that reproduces this issue
none
To Reproduce
COOKIE_NAME here is the sessionId, that is sent with each request.
Cookie revalidate is set to 0. We use this function to all API related requests.
Backend is written in PHP.
Current vs. Expected behavior
Current behaviour:
The logout feature works only SOMETIMES. Aprox 4 in 5 requests to de-authenticate session are ignored.
It did work without problems before 14.2. I have tested both version and the requests are same, the cookies are sent correctly.
The server DOES respond same in both versions.
This looks like an API problem, but it is not. After 2 day investigation, we realised our older version is working fine, the POSTMAN is working fine and we found out that migrating to 14.2 is what breaks our logout feature.
We noticed this is an issue in build and also dev.
Expected:
Cookies be working without issues.
Provide environment information
Next.js v14.2.3. Custom server.js Running with "bun" Reproduced on multiple machines (OSX/Linux)
Which area(s) are affected? (Select all that apply)
Not sure
Which stage(s) are affected? (Select all that apply)
next dev (local), next build (local)
Additional context
No response
The text was updated successfully, but these errors were encountered: