From a3037ea91a0fa3f67d4128d4bbfaa74ac1d196b7 Mon Sep 17 00:00:00 2001 From: Zev Benjamin Date: Mon, 28 Jan 2013 12:33:33 -0500 Subject: [PATCH] Revert "Set a wildcard subdomain for the session and csrf cookie domains on staging" This was to support get_updates sharding, which we never fully implemented. We can recommit this change later if we choose to bring the feature back. This reverts commit fda2d99d9e9a07951d11fcd9fc61cf229988f471. (imported from commit aec8203c8d8a94dd6f30089aeee22814d1595fc5) --- humbug/settings.py | 5 ----- 1 file changed, 5 deletions(-) diff --git a/humbug/settings.py b/humbug/settings.py index 02848a03ad..c922852652 100644 --- a/humbug/settings.py +++ b/humbug/settings.py @@ -117,11 +117,6 @@ if DEPLOYED: SESSION_COOKIE_SECURE = True CSRF_COOKIE_SECURE = True -# For get_updates host sharding -if STAGING_DEPLOYED: - SESSION_COOKIE_DOMAIN = '.' + platform.node() - CSRF_COOKIE_DOMAIN = '.' + platform.node() - # Prevent Javascript from reading the CSRF token from cookies. Our code gets # the token from the DOM, which means malicious code could too. But hiding the # cookie will slow down some attackers.