Disable SESSION_COOKIE_DOMAIN in local environment

[niccolomineo]

In Safari, in the context of a local environment, there seems to occur a collision between the anti CSRF mechanism and the SESSION_COOKIE_DOMAIN value, for Talos as a tool is intended to be used with a multiple project mentality. Hardcoding the SESSION_COOKIE_DOMAIN as localhost for all projects currently renders ineffective any attempt to log in to any Django admin, but the first Django admin one has ever logged in to, with said browser.

The first solution that comes to mind is to disable SESSION_COOKIE_DOMAIN locally.

[trottomv]

In Safari, in the context of a local environment, there seems to occur a collision between the anti CSRF mechanism and the SESSION_COOKIE_DOMAIN value, for Talos as a tool is intended to be used with a multiple project mentality. Hardcoding the SESSION_COOKIE_DOMAIN as localhost for all projects currently renders ineffective any attempt to log in to any Django admin, but the first Django admin one has ever logged in to, with said browser.

The first solution that comes to mind is to disable SESSION_COOKIE_DOMAIN locally.

I don’t think removing the parametric handling of this setting is ideal. I’ve found it useful in some projects to keep SESSION_COOKIE_DOMAIN configured even locally, as it allows me to test session behaviors across multiple instances. Disabling it entirely could limit that flexibility.

[niccolomineo]

Ok, I will just set it to None in my local environment then.