bryanjknight commented on issue #25740:
URL: https://github.com/apache/superset/issues/25740#issuecomment-2009451112

   Ah, good find! Yeah, that's looks close, the one I have starts with a `.`.   
Digging into the `superset_config.py` in the main repo, I see this:
   ```
   #
   # Flask session cookie options
   #
   # See https://flask.palletsprojects.com/en/1.1.x/security/#set-cookie-options
   # for details
   #
   SESSION_COOKIE_HTTPONLY = True  # Prevent cookie from being read by frontend 
JS?
   SESSION_COOKIE_SECURE = False  # Prevent cookie from being transmitted over 
non-tls?
   SESSION_COOKIE_SAMESITE: Literal["None", "Lax", "Strict"] | None = "Lax"
   # Whether to use server side sessions from flask-session or Flask secure 
cookies
   SESSION_SERVER_SIDE = False
   # Example config using Redis as the backend for server side sessions
   # from flask_session import RedisSessionInterface
   #
   # SESSION_SERVER_SIDE = True
   # SESSION_USE_SIGNER = True
   # SESSION_TYPE = "redis"
   # SESSION_REDIS = Redis(host="localhost", port=6379, db=0)
   #
   # Other possible config options and backends:
   # # https://flask-session.readthedocs.io/en/latest/config.html
   ```
   
   Perhaps switch to server side sessions might help?


-- 
This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
URL above to go to the specific comment.

To unsubscribe, e-mail: notifications-unsubscr...@superset.apache.org

For queries about this service, please contact Infrastructure at:
us...@infra.apache.org


---------------------------------------------------------------------
To unsubscribe, e-mail: notifications-unsubscr...@superset.apache.org
For additional commands, e-mail: notifications-h...@superset.apache.org

Reply via email to