https://supertokens.com/ logo
Join Discord
Powered by
Hi, I have a problem with signOut where the sFront...
# support-questions-legacy
o
Hi, I have a problem with signOut where the sFrontToken cookie sometimes remains undeleted and persists until the next session refresh.
r
hey @on4m4 can i see the sign out API call request and response headers when this happens?
o
it deletes refresh and acces token if you need more info then that i can ss it for you
r
would be good to see a screenshot of the headers.
o
and this does not happen always
only when i leave website for one refresh cycle
so if i signout if i just signed up
it works okay
r
request headers?
also, there is no response header for front-token from this API call. Thats odd. Is something removing it on your end?
o
there is nothing can it be because i use cookieDomain for multiple subdomains and use multiple api endpoints
r
ont really
this seems fine
the missing thing is the front-token response header
o
so config for session cannot cause this?
i have nextjs app and nodejs which acts as api and serves react app
r
yup.. usually it's some reverse proxy issue
this is the proper response
you see, there should be a front-token: remove in the response header
u might wanna check why thats not there for you.
o
what can be the reason for that?
r
not sure
o
nginx ?
r
yea.. maybe
it's not from our sdks. So..
o
i just wanted to confirm that session config isn't the reason.
okay thanks 🙂
5 Views
PreviousNext
Powered by