From 21cee79ee42c4b6827de031ad9e6d486ad9a3657 Mon Sep 17 00:00:00 2001 From: Karen Tracey Date: Sun, 17 May 2009 16:57:50 +0000 Subject: [PATCH] =?UTF-8?q?Fixed=20#11054=20--=20Corrected=20typo=20in=20a?= =?UTF-8?q?uth-remote-user.txt.=20=20Thanks=20Jan=20H=C3=BClsbergen.?= MIME-Version: 1.0 Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: 8bit git-svn-id: http://code.djangoproject.com/svn/django/trunk@10803 bcc190cf-cafb-0310-a4f2-bffc1f526a37 --- docs/howto/auth-remote-user.txt | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/docs/howto/auth-remote-user.txt b/docs/howto/auth-remote-user.txt index aa39b1fba4..05532da0b0 100644 --- a/docs/howto/auth-remote-user.txt +++ b/docs/howto/auth-remote-user.txt @@ -22,7 +22,7 @@ When the Web server takes care of authentication it typically sets the Django, ``REMOTE_USER`` is made available in the :attr:`request.META ` attribute. Django can be configured to make use of the ``REMOTE_USER`` value using the ``RemoteUserMiddleware`` and -``RemoteUserBackend`` classes found in :mod:`django.contirb.auth`. +``RemoteUserBackend`` classes found in :mod:`django.contrib.auth`. Configuration =============