Action on cookie create/update about scs HOT 1 CLOSED

I'm not an expert in SPAs, but I think that a common way of handling this is to implement some kind of /profile endpoint in your API. The JS frontend can then make a request to /profile, which (CORS and WithCredentials issues aside) will pass the HttpOnly session cookie along with it. The /profile endpoint can then check for the presence of a session cookie in the request and return the user information and you know they are 'logged in' (if no valid session cookie is present, then it can return a error code instead). This user information can then be cached by the SPA and used for the duration of the browser session for things like displaying the user name etc. The session cookie should continue to be sent to all subsequent requests to the API and checked before doing anything that requires authentication.

from scs.