Skip to content

issue with 11.0 and safari #1222

Answered by frankie567
wesleysanjose asked this question in Q&A
Discussion options

You must be logged in to vote

The problem comes from the cookie_secure=True flag.

This flag means the browser should forward the cookie to the server only if we're on an HTTPS connection, which is usually not the case when developing on localhost.

However, Chrome and Firefox are a bit nicer with this rule: when the server is served on localhost, they will ignore the cookie Secure flag, for developers convenience. Safari is very strict and won't do this, that's why it doesn't work with this browser.

My advice is to set cookie_secure through an environment variable, so you can easily switch it to False in development and to True in production (which is crucial in terms of security).

Replies: 1 comment

Comment options

You must be logged in to vote
0 replies
Answer selected by wesleysanjose
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Category
Q&A
Labels
None yet
2 participants
Converted from issue

This discussion was converted from issue #1221 on May 29, 2023 07:04.