github-starred/better-auth
2
0
Fork 0
mirror of https://github.com/better-auth/better-auth.git synced 2026-05-23 07:18:56 -05:00
Code Issues 2.5k Packages Projects Releases 112 Wiki Activity

Redirect to an URL option in signOut() #128

New Issue
Closed
opened 2026-03-13 07:34:29 -05:00 by GiteaMirror · 2 comments
GiteaMirror commented 2026-03-13 07:34:29 -05:00
Owner
Copy Link

Originally created by @mmikhan on GitHub (Oct 23, 2024).

Right now, signOut() function doesn't handle the redirect after signing out. It only accept {fetchOptions: {redirect: RequestRedirect}}. RequestRedirect can be either follow, error, or manual but no URL. Manually adding a redirect doesn't validate whether the sign out action was successful. So, it would be great to have a redirect to option there.

Originally created by @mmikhan on GitHub (Oct 23, 2024). Right now, `signOut()` function doesn't handle the redirect after signing out. It only accept `{fetchOptions: {redirect: RequestRedirect}}`. `RequestRedirect` can be either `follow`, `error`, or `manual` but no URL. Manually adding a redirect doesn't validate whether the sign out action was successful. So, it would be great to have a redirect to option there.
GiteaMirror commented 2026-03-13 07:34:30 -05:00
Author
Owner
Copy Link

@mmikhan commented on GitHub (Oct 23, 2024):

As a workaround, fetchOptions has an onSuccess() function that can be used to redirect on a successful sign out.

8899ed1877/demo/nextjs/app/dashboard/user-card.tsx (L390-L396)

@mmikhan commented on GitHub (Oct 23, 2024): As a workaround, `fetchOptions` has an `onSuccess()` function that can be used to redirect on a successful sign out. https://github.com/better-auth/better-auth/blob/8899ed18771fa221376182c014804a52e6c019d4/demo/nextjs/app/dashboard/user-card.tsx#L390-L396
GiteaMirror commented 2026-03-13 07:34:30 -05:00
Author
Owner
Copy Link

@RubenSmn commented on GitHub (May 28, 2025):

I also added router.refresh() after the push. After I signed out I was still able to visit pages with the browser history back button. The refresh prevents this.

    await authClient.signOut({
      fetchOptions: {
        onSuccess: () => {
          router.push(Routes.getSignIn());
          router.refresh();
        },
      },
    });
@RubenSmn commented on GitHub (May 28, 2025): I also added `router.refresh()` after the push. After I signed out I was still able to visit pages with the browser history back button. The refresh prevents this. ```ts await authClient.signOut({ fetchOptions: { onSuccess: () => { router.push(Routes.getSignIn()); router.refresh(); }, }, }); ```
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
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#128
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?