Django/django
11
0
Fork 0
Code Pull Requests Projects Releases Activity

[1.9.x] Fixed #26436 -- Added a link to the settings filtering in the error reporting howto.

Browse Source 
Thanks mlissner for the suggestion.

Backport of 8928823b135b9ce2c7b18f4da0d2602b113a247e from master
This commit is contained in:
Tim Graham 2016-03-31 13:41:06 -04:00
parent bca42c709f
commit cac320bfaa
1 changed files with 6 additions and 4 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

10
docs/howto/error-reporting.txt
View File

@ -143,10 +143,12 @@ exception raised, each `traceback frame`_’s local variables, and the
However, sometimes certain types of information may be too sensitive and thus However, sometimes certain types of information may be too sensitive and thus
may not be appropriate to be kept track of, for example a user's password or may not be appropriate to be kept track of, for example a user's password or
credit card number. So Django offers a set of function decorators to help you credit card number. So in addition to filtering out settings that appear to be
control which information should be filtered out of error reports in a sensitive as described in the :setting:`DEBUG` documentation, Django offers a
production environment (that is, where :setting:`DEBUG` is set to ``False``): set of function decorators to help you control which information should be
:func:`sensitive_variables` and :func:`sensitive_post_parameters`. filtered out of error reports in a production environment (that is, where
:setting:`DEBUG` is set to ``False``): :func:`sensitive_variables` and
:func:`sensitive_post_parameters`.
.. _`full traceback`: https://en.wikipedia.org/wiki/Stack_trace .. _`full traceback`: https://en.wikipedia.org/wiki/Stack_trace
.. _`traceback frame`: https://en.wikipedia.org/wiki/Stack_frame .. _`traceback frame`: https://en.wikipedia.org/wiki/Stack_frame