From 96520e87bdd37a6a32c49cfa2df124421f6ec3ed Mon Sep 17 00:00:00 2001 From: Luke Plant Date: Wed, 20 Apr 2011 11:39:10 +0000 Subject: [PATCH] Corrected factual error regarding logging in the CSRF docs git-svn-id: http://code.djangoproject.com/svn/django/trunk@16047 bcc190cf-cafb-0310-a4f2-bffc1f526a37 --- docs/ref/contrib/csrf.txt | 8 ++++---- 1 file changed, 4 insertions(+), 4 deletions(-) diff --git a/docs/ref/contrib/csrf.txt b/docs/ref/contrib/csrf.txt index 459a71ffe1..013125aaef 100644 --- a/docs/ref/contrib/csrf.txt +++ b/docs/ref/contrib/csrf.txt @@ -170,10 +170,10 @@ usually only be seen when there is a genuine Cross Site Request Forgery, or when, due to a programming error, the CSRF token has not been included with a POST form. -No logging is done, and the error message is not very friendly, so you may want -to provide your own page for handling this condition. To do this, simply set -the :setting:`CSRF_FAILURE_VIEW` setting to a dotted path to your own view -function, which should have the following signature:: +The error page, however, is not very friendly, so you may want to provide your +own view for handling this condition. To do this, simply set the +:setting:`CSRF_FAILURE_VIEW` setting to a dotted path to your own view function, +which should have the following signature:: def csrf_failure(request, reason="")