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
This commit is contained in:
Adrian Holovaty 2005-07-17 02:46:04 +00:00
parent 364f3704b0
commit 4211bcb437
1 changed files with 3 additions and 1 deletions

View File

@ -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 sent out by Django doesn't match the domain in your browser. Try these two
things: 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 * 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 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 domain that doesn't have a dot in it, try going to "localhost.localdomain" or