From 4211bcb43767b66e65599f7f3e38cdb52cd44243 Mon Sep 17 00:00:00 2001 From: Adrian Holovaty Date: Sun, 17 Jul 2005 02:46:04 +0000 Subject: [PATCH] Added an example to one of the FAQ answers from [132] git-svn-id: http://code.djangoproject.com/svn/django/trunk@133 bcc190cf-cafb-0310-a4f2-bffc1f526a37 --- docs/faq.txt | 4 +++- 1 file changed, 3 insertions(+), 1 deletion(-) diff --git a/docs/faq.txt b/docs/faq.txt index 24a06d84cc..29cc3696c8 100644 --- a/docs/faq.txt +++ b/docs/faq.txt @@ -219,7 +219,9 @@ The login cookie isn't being set correctly, because the domain of the cookie sent out by Django doesn't match the domain in your browser. Try these two things: -* Set the ``REGISTRATION_COOKIE_DOMAIN`` setting to match your domain. +* Set the ``REGISTRATION_COOKIE_DOMAIN`` setting to match your domain. For + example, if you're going to "http://www.mysite.com/admin/" in your browser, + set ``REGISTRATION_COOKIE_DOMAIN = 'www.mysite.com'``. * Some browsers (Firefox?) don't like to accept cookies from domains that don't have dots in them. If you're running the admin site on "localhost" or another domain that doesn't have a dot in it, try going to "localhost.localdomain" or