-
Notifications
You must be signed in to change notification settings - Fork 424
fix: Remove obsolete warning about cookie-size #2012
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
Conversation
@@ -235,9 +235,6 @@ If you'd like to customize the `user` object to include additional custom claims | |||
## Additional changes | |||
|
|||
- By default, v4 is edge-compatible and as such there is no longer a `@auth0/nextjs-auth0/edge` export. | |||
- Cookie chunking has been removed | |||
- If the cookie size exceeds the browser limit of 4096 bytes, a warning will be logged | |||
- To store large session data, please use a [custom data store](https://github.com/auth0/nextjs-auth0/tree/main?tab=readme-ov-file#database-sessions) with a SessionStore implementation |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Also removing this from the migration guide, as this is no longer accurate in the latest version of v4.
cb1066e
to
989d726
Compare
Codecov ReportAll modified and coverable lines are covered by tests ✅
Additional details and impacted files@@ Coverage Diff @@
## main #2012 +/- ##
==========================================
- Coverage 74.77% 74.68% -0.09%
==========================================
Files 21 21
Lines 1859 1853 -6
Branches 287 286 -1
==========================================
- Hits 1390 1384 -6
Misses 462 462
Partials 7 7 ☔ View full report in Codecov by Sentry. 🚀 New features to boost your workflow:
|
989d726
to
baeb49b
Compare
Currently, if you try to google the warning, nothing comes up, so for the sake of google-ability, the warning is,
|
With the fact that we brought back cookie-chunking, we no longer want to output a warning message when the cookie exceeds the limit in size. Instead, we chunk the cookie in that case.
Additionally, since we added id token back in the session, there is a high chance of users hitting the limit, ending up with chunked cookies, and the fact that they will see an irrelevant warning message.