I'm not familiar with these tools but I noticed this on the readme of django-cors-headers:
Note: in Django 2.1 the SESSION_COOKIE_SAMESITE setting was added, set to 'Lax' by default, which will prevent Django's session cookie being sent cross-domain. Change it to None to bypass this security restriction.
Could it be that the cookie the server is setting isn't correctly configured for cross domain requests?
I already tried that but it didn't work. Someone at StackOverflow told me I needed it to create a token in the Express app and send it with the user data to the Django app. I will try that. I'll let you know.
For further actions, you may consider blocking this person and/or reporting abuse
We're a place where coders share, stay up-to-date and grow their careers.
I'm not familiar with these tools but I noticed this on the readme of django-cors-headers:
Could it be that the cookie the server is setting isn't correctly configured for cross domain requests?
See also docs.djangoproject.com/en/2.2/ref/...
Let me know if we are on the right path :)
I already tried that but it didn't work. Someone at StackOverflow told me I needed it to create a token in the Express app and send it with the user data to the Django app. I will try that. I'll let you know.