From 307f3a95c7c0466f8b821395b611d3253ae4c79c Mon Sep 17 00:00:00 2001 From: Adrian Holovaty Date: Tue, 19 Jul 2005 19:13:33 +0000 Subject: [PATCH] Fixed the annoying login error that happens in some cases when REGISTRATION_COOKIE_DOMAIN isn't set. Now, generally you don't have to sete REGISTRATION_COOKIE_DOMAIN unless you want to use multi-domain cookies (such as '.foo.com') git-svn-id: http://code.djangoproject.com/svn/django/trunk@216 bcc190cf-cafb-0310-a4f2-bffc1f526a37 --- django/models/auth.py | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/django/models/auth.py b/django/models/auth.py index 121704d9e71..ecc03de6145 100644 --- a/django/models/auth.py +++ b/django/models/auth.py @@ -232,7 +232,7 @@ class Session(meta.Model): user.save() session = create_session(user_id) key, value = session.get_cookie() - cookie_domain = REGISTRATION_COOKIE_DOMAIN or request.META['SERVER_NAME'] + cookie_domain = REGISTRATION_COOKIE_DOMAIN or None response.set_cookie(key, value, domain=cookie_domain) class Message(meta.Model):