diff options
| author | Holly Becker <becker.holly@gmail.com> | 2016-06-02 17:24:48 -0700 |
|---|---|---|
| committer | Tim Graham <timograham@gmail.com> | 2016-06-04 10:17:06 -0400 |
| commit | 55fec16aafed30a9daa06d6ecdf8ca3ad361279e (patch) | |
| tree | 6b3ec068888cec04e9fc5368e6c15e851dfbd0df /docs/ref | |
| parent | c3495bb984a6f639e828e568fd333e36b46f270f (diff) | |
Fixed #26628 -- Changed CSRF logger to django.security.csrf.
Diffstat (limited to 'docs/ref')
| -rw-r--r-- | docs/ref/csrf.txt | 11 |
1 files changed, 9 insertions, 2 deletions
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<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 +<django-security-logger>` logger. + +.. versionchanged:: 1.11 + + In older versions, CSRF failures are logged to the ``django.request`` + logger. .. _how-csrf-works: |