You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
{{ message }}
This repository has been archived by the owner on Aug 5, 2021. It is now read-only.
Unfortunately no, the issue is that by default it gets set to the root of the domain (i.e. '.python.org') so CSRF and SESSION cookies between www. and staging. seem to be conflicting with each other.
So actually for completeness sake we probably want www to be setting those two as 'www.python.org' as well.
On Thu, Jul 24, 2014, at 08:44, Frank Wiles wrote:
Unfortunately no, the issue is that by default it gets set to the root of
the domain (i.e. '.python.org') so CSRF and SESSION cookies between www.
and staging. seem to be conflicting with each other.
So actually for completeness sake we probably want www to be setting
those two as 'www.python.org' as well.
Reply to this email directly or view it on GitHub: #132 (comment)
Need to adjust Django's cookie domains on staging to be:
CSRF_COOKIE_DOMAIN = 'staging.python.org'
SESSION_COOKIE_DOMAIN = 'staging.python.org'
Otherwise we can't login to staging to poke at changes before releasing. Thanks!
The text was updated successfully, but these errors were encountered: