-
Not sure if this matters for newer versions of Chrome but for older Chrome versions this warning shows: A cookie associated with a cross-site resource at was set without the Provisional headers are shown Can someone verify if anything needs to be done with either this app, nginx/apache, middleware, or django settings to get these warnings to go away? |
Beta Was this translation helpful? Give feedback.
Replies: 3 comments
-
You need to enable https on your application. The development server does not support https so you'll have to do that when you set up your production server. you can find documentation about the alternate values for samesite here: |
Beta Was this translation helpful? Give feedback.
-
Good to know. Thanks! |
Beta Was this translation helpful? Give feedback.
-
@JoelEdem Hi, I enabled https on my app, and set all those settings in the settings.py, in production it is still prompting the same warning for samesite. Any alternative fix for that ? |
Beta Was this translation helpful? Give feedback.
You need to enable https on your application. The development server does not support https so you'll have to do that when you set up your production server.
then set
SESSION_COOKIE_SAMESITE = None
LANGUAGE_COOKIE_SAMESITE = None
CSRF_COOKIE_SAMESITE = None
SESSION_COOKIE_SECURE = True
LANGUAGE_COOKIE_SECURE = True
CSRF_COOKIE_SECURE = True
you can find documentation about the alternate values for samesite here:
https://docs.djangoproject.com/en/3.0/ref/settings/#session-cookie-secure