https://supertokens.com/
Join Discord
Any ideas why my supertokens when deployed doesn't return any cookies but still return 201. But runn...
# support-questions-legacy
m
Any ideas why my supertokens when deployed doesn't return any cookies but still return 201. But running the same locally I get 201 and cookies? (using postman to test) ?
wait now it doesn't work for either ❓
wait do you not send them as cookies now and as Headers?
n
Hey @Marques Can you share some info about your setup? What frontend and backend SDK do you use? What core version are you using?
r
Also, our sdks don't send back a 201 status code. Maybe something else is intercepting the requests?
m
frontend nothing as of yet as I'm in the migration from svelte to react. (old project) backend sdk: supertokens-node - 
^13.6.0
core version: 
v4.3
before I migrated to 
13
I was originally on 
9
on supertokens-node when firing 
.createNewSession
I didn't have to pass in request but now I do
Copy code
return STSession.createNewSession(req, resp , user.id, payload);
STSession is just
Copy code
export { default as STSession } from 'supertokens-node/recipe/session';
r
What’s happening when you sign in? Can we see the request / response headers?
m
I mean I get 
front-token
, 
st-access-token
, 
st-refresh-token
in my headers. My question was normally I get them as cookies in 
v9
but in 
v13
they are headers?
this is v13

https://cdn.discordapp.com/attachments/1108531006245453914/1108722572536852552/image.png▾

this is v9

https://cdn.discordapp.com/attachments/1108531006245453914/1108723045297836113/image.png▾

r
Right. So you need to set the auth-mode header to cookie when making the request.
Our frontend SDK does this automatically
But since you are querying using postman, you need to add the header manually in the sign in request
m
ah okay, did this change in versions?
r
yes. See our changelog
on the github repo
19 Views
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