https://supertokens.com/
Join Discord
Hi, When calling Session.signout on the frontend (angular, supertokens-web-js), it is sending a GET ...
# support-questions-legacy
u
Hi, When calling Session.signout on the frontend (angular, supertokens-web-js), it is sending a GET Request to /api/auth/signout instead of a POST Request, I'm using the Session recipe on the backend (NestJS, supertokens-node), therefore I always get back error 404: "Cookie 'sAcessToken', 'sRefreshToken' and 'sIdRefreshToken' has been rejected"), what am I doing wrong here?
r
get @99_chris - can you show me the network tab screenshot when you call this function?
u
I‘m currently at work, coming Home in about 9-10 Hours, then I can send it to you. Thanks
r
This seems to be fine
u
Response is {"status":"OK"}, but in the console i get the following error:
and when i click on signout on the right, it shows the following: {"statusCode":404,"message":"Cannot GET /api/auth/signout","error":"Not Found"}
so it seems to send a get request instead of post
r
The screenshot above have a POST request
u
yes, signout is working correctly, i was just wondering, because i get this error message in the console
r
After you click sign out, do u see the sAccessToken cookie in the browser’s application tab?
u
no just the sIRTFrontend with value remove
r
right. So it's all working fine. You can ignore the browser warning
u
one other question, how can i make sure that I am logged out immedialely in other tabs, if I call logout on one tab
r
well, you want to probably create some sort of polling thing on each tab then which query doesSessionExist funciton
otherwise, even if you don't do that, whenever an API call is made or the user navigates in those other tabs, it will detect the logout anyway
u
okay thanks for your help
PreviousNext
Powered by

SuperTokens.com

SuperTokens is an open source authentication solution offering features like: Different types of login: Email / password, Passwordless (OTP or Magic link based).

Powered by