feat: add WORKOS_SKIP_MIDDLEWARE_CHECK env var to bypass middleware header check #353
Conversation
This file contains hidden or 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
…eader check This adds a fallback mechanism for scenarios where the x-workos-middleware header doesn't propagate correctly to API routes (e.g., when using custom middleware wrappers in Next.js 16 with proxy.ts). When WORKOS_SKIP_MIDDLEWARE_CHECK=true is set, the getSessionFromHeader() function will fall back to reading the session directly from cookies instead of throwing an error about missing middleware coverage. Fixes workos#351
Member
|
As mentioned in #351 bypassing middleware can cause issues. Closing this in favor of the recommended solution in that issue. Thanks! |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
2 participants
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.
This adds a fallback mechanism for scenarios where the x-workos-middleware header doesn't propagate correctly to API routes (e.g., when using custom middleware wrappers in Next.js 16 with proxy.ts).
When WORKOS_SKIP_MIDDLEWARE_CHECK=true is set, the getSessionFromHeader() function will fall back to reading the session directly from cookies instead of throwing an error about missing middleware coverage.
Fixes #351