github-starred/better-auth
2
0
Fork 0
mirror of https://github.com/better-auth/better-auth.git synced 2026-05-22 14:21:55 -05:00
Code Issues 2.5k Packages Projects Releases 112 Wiki Activity

[PR #7662] docs: fix wording on Session Cookie Checks in NextJS Integration #7475

New Issue
Open
opened 2026-03-13 13:37:59 -05:00 by GiteaMirror · 0 comments
GiteaMirror commented 2026-03-13 13:37:59 -05:00
Owner
Copy Link

📋 Pull Request Information

Original PR: https://github.com/better-auth/better-auth/pull/7662
Author: @TheUntraceable
Created: 1/28/2026
Status: 🔄 Open

Base: canary ← Head: patch-5

📝 Commits (1)

  • ef62d55 Improve clarity on session cookie handling in Next.js

📊 Changes

1 file changed (+1 additions, -1 deletions)

View changed files

📝 docs/content/docs/integrations/next.mdx (+1 -1)

📄 Description

Clarified recommendation on session cookie checks in Next.js proxy/middleware.

Summary by cubic

Clarified the Next.js integration docs to recommend only checking for the presence of a session cookie in proxy/middleware, so redirects don’t block on API or database calls.

Written for commit ef62d551ef5ce21816693bbeed039b005b74e05a. Summary will update on new commits.

🔄 This issue represents a GitHub Pull Request. It cannot be merged through Gitea due to API limitations.

## 📋 Pull Request Information **Original PR:** https://github.com/better-auth/better-auth/pull/7662 **Author:** [@TheUntraceable](https://github.com/TheUntraceable) **Created:** 1/28/2026 **Status:** 🔄 Open **Base:** `canary` ← **Head:** `patch-5` --- ### 📝 Commits (1) - [`ef62d55`](https://github.com/better-auth/better-auth/commit/ef62d551ef5ce21816693bbeed039b005b74e05a) Improve clarity on session cookie handling in Next.js ### 📊 Changes **1 file changed** (+1 additions, -1 deletions) <details> <summary>View changed files</summary> 📝 `docs/content/docs/integrations/next.mdx` (+1 -1) </details> ### 📄 Description Clarified recommendation on session cookie checks in Next.js proxy/middleware. <!-- This is an auto-generated description by cubic. --> --- ## Summary by cubic Clarified the Next.js integration docs to recommend only checking for the presence of a session cookie in proxy/middleware, so redirects don’t block on API or database calls. <sup>Written for commit ef62d551ef5ce21816693bbeed039b005b74e05a. Summary will update on new commits.</sup> <!-- End of auto-generated description by cubic. --> --- <sub>🔄 This issue represents a GitHub Pull Request. It cannot be merged through Gitea due to API limitations.</sub>
GiteaMirror added the pull-request label 2026-03-13 13:37:59 -05:00
Sign in to join this conversation.
No Branch/Tag Specified
Branches Tags
Labels
Clear labels
adapter
astro
awaiting external contributor
blocked
breaking
breaking change
bug
c-devops
core
credentials
database
dependencies
devops
devtools
docs
documentation
duplicate
elysia
enhancement
enterprise
expo
express
fastify
good first issue
help wanted
hono
identity
infra
integration
invalid
javascript
locked
maintenance
need-more-information
needs: info
needs: repro
nextjs
nuxt
oauth
organization
P0
payments
perf
platform
plugin
pull-request
Mirrored from GitHub Pull Request
 question
ready
regression
remix
security
social-provider
solid
stale
svelte
tanstack-start
tracking
version-bump
vue
wontfix
No Label pull-request
Milestone
No items
No Milestone
Projects
Clear projects
No project
Assignees
Clear assignees
GiteaMirror ninjasurge
No Assignees
1 Participants
Notifications
Due Date
No due date set.
Dependencies

No dependencies set.

Reference: github-starred/better-auth#7475
Delete Branch "%!s()"

Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?