From 55fec16aafed30a9daa06d6ecdf8ca3ad361279e Mon Sep 17 00:00:00 2001 From: Holly Becker Date: Thu, 2 Jun 2016 17:24:48 -0700 Subject: Fixed #26628 -- Changed CSRF logger to django.security.csrf. --- docs/ref/csrf.txt | 11 +++++++++-- 1 file changed, 9 insertions(+), 2 deletions(-) (limited to 'docs/ref') diff --git a/docs/ref/csrf.txt b/docs/ref/csrf.txt index 16290cbfb5..7baf83f2e5 100644 --- a/docs/ref/csrf.txt +++ b/docs/ref/csrf.txt @@ -192,6 +192,8 @@ both is fine, and will incur minimal overhead. If you are using class-based views, you can refer to :ref:`Decorating class-based views`. +.. _csrf-rejected-requests: + Rejected requests ================= @@ -205,8 +207,13 @@ 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. -CSRF failures are logged as warnings to the :ref:`django-request-logger` -logger. +CSRF failures are logged as warnings to the :ref:`django.security.csrf +` logger. + +.. versionchanged:: 1.11 + + In older versions, CSRF failures are logged to the ``django.request`` + logger. .. _how-csrf-works: -- cgit v1.3