mirror of
https://github.com/django/django.git
synced 2025-11-07 07:15:35 +00:00
Fixed #14614 - filtering of sensitive information in 500 error reports.
This adds a flexible mechanism for filtering what request/traceback information is shown in 500 error emails and logs. It also applies screening to some views known to be sensitive e.g. views that handle passwords. Thanks to oaylanc for the report and many thanks to Julien Phalip for the patch and the rest of the work on this. git-svn-id: http://code.djangoproject.com/svn/django/trunk@16339 bcc190cf-cafb-0310-a4f2-bffc1f526a37
This commit is contained in:
@@ -116,6 +116,26 @@ help with AJAX heavy sites, protection for PUT and DELETE, and settings
|
||||
the security and usefulness of the CSRF protection. See the :doc:`CSRF docs
|
||||
</ref/contrib/csrf>` for more information.
|
||||
|
||||
Error report filtering
|
||||
~~~~~~~~~~~~~~~~~~~~~~
|
||||
|
||||
Two new function decorators, :func:`sensitive_variables` and
|
||||
:func:`sensitive_post_parameters`, were added to allow designating the
|
||||
traceback frames' local variables and request's POST parameters susceptible
|
||||
to contain sensitive information and that should be filtered out of error
|
||||
reports.
|
||||
|
||||
All POST parameters are now systematically filtered out of error reports for
|
||||
certain :mod:`contrib.views.auth` views (``login``, ``password_reset_confirm``,
|
||||
``password_change``, and ``add_view`` and ``user_change_password`` in the
|
||||
``auth`` admin) to prevent the leaking of sensitive information such as user
|
||||
passwords.
|
||||
|
||||
You may override or customize the default filtering by writing a
|
||||
:ref:`custom filter<custom-error-reports>`. Learn more on
|
||||
:ref:`Filtering error reports<filtering-error-reports>`.
|
||||
|
||||
|
||||
.. _backwards-incompatible-changes-1.4:
|
||||
|
||||
Backwards incompatible changes in 1.4
|
||||
|
||||
Reference in New Issue
Block a user