fix(docs): add middleware prerequisite #10667
Closed
Conversation
This file contains 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 latest updates on your projects. Learn more about Vercel for Git ↗︎
|
|
@JasperAlexander unfortunately this is not the case, you can use the database session with middleware, as long as you use a database who is edge runtime compatible. Check out my reply to the other thread you posted in: #8161 (comment) |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
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.
☕️ Reasoning
Currently, the Next.js middleware only supports the jwt session strategy. When using an adapter, the default session strategy is database. It is not well documented that you need to set the session strategy to jwt when using an adapter in order to use the middleware. I added this to the docs.
🧢 Checklist
🎫 Affected issues
Fixes: #10276
📌 Resources