I have issue with set-token in mobile browser. Using mobile version of Safari 16.1 (but can be rep...
k
I have issue with set-token in mobile browser. Using mobile version of Safari 16.1 (but can be reproduced in chrome mobile version also) Desktop version of set-cookie: Mobile version of set-cookie: as you can see, set-cookie is not full in mobile version. is it a bug?
r
hey @kuzyaross
k
hello again @rp_st
r
it's the same backend serving both, the mobile and web app? If so, im not sure why this could happen just for the mobile app
k
no, it's just one core
r
huh?
whats happening on the mobile view exactly?
Please explain your entire setup in detail
k
Setup: Django 4.1 ,Supertokens from docker (supertokens-postgresql:4.1), Safari 16.1 Problem: set-cookie is wrong is IOS devices only. after closing browser, there is no cookie available, so user should re-login every time.
r
whats the apiDomain and websiteDomain?
k
api_domain = api.267.uz website_domain = https://id.267.uz
r
i see. Can i see all the request and response headers of the sign in API call?
ok one more question
are you using nginx or some api proxy?
k
nginx
will you need response headers?
r
it's possible that nginx may be doing something to cut out long response headers.
k
oh, i see
but is it possible that nginx will do so only for IOS browsers?
r
yea.. thats the weird thing.
That shouldn't be the case.. but you never know
cause this is a very strange issue
k
I will dig in this direction in this direction and will let u know
thank you a lot !
2 Views