supertokens/docs

verifySession without using SDK can take long processing time

Opened this issue · 3 comments

akalitenya commented

I suggest to make it clear in docs that not updating access token on frontend from response of request to ANY user protected route (not only verify-code or refresh) can lead to long processing time for verifySession for all next requests until token updated.

https://supertokens.com/docs/session/quick-setup/handling-session-tokens#making-network-requests-to-protected-apis-1

rishabhpoddar commented

@akalitenya this is only true for header based auth (with authorization bearer token) being used right?

akalitenya commented

I used header based auth (bearer token) and did not try the cookie approach.

rishabhpoddar commented

Makes sense. We will update the docs. Thanks.

  • 👍1