  Error reports are really helpful for debugging errors, so it is generally
  useful to record as much relevant information about those errors as possible.
  For example, by default Django records the `full traceback`_ for the
  exception raised, each `traceback frame`_'s local variables, and the
  :class:`HttpRequest`'s :ref:`attributes<httprequest-attributes>`.
  
  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
  credit card number. So Django offers a set of function decorators to help you
  control which information should be filtered out of error reports in a
 
</s> remove     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.
 </s> add     error reports for certain :mod:`django.contrib.auth.views` 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. </s> remove     If one of your views receives an :class:`HttpRequest` object with
    :attr:`POST parameters<HttpRequest.POST>` susceptible to contain sensitive
    information, you may prevent the values of those parameters from being
    included in the error reports using the ``sensitive_post_parameters``
    decorator::
 </s> add     If one of your views receives an :class:`~django.http.HttpRequest` object
    with :attr:`POST parameters<django.http.HttpRequest.POST>` susceptible to
    contain sensitive information, you may prevent the values of those
    parameters from being included in the error reports using the
    ``sensitive_post_parameters`` decorator:: </s> remove         :class:`~django.db.models.fields.DateField` or
        :class:`~django.db.models.fields.DateTimeField` on the model for which
 </s> add         :class:`~django.db.models.DateField` or
        :class:`~django.db.models.DateTimeField` on the model for which </s> remove The default form widget for this field is a
:class:`~django.forms.widgets.FileInput`.
 </s> add The default form widget for this field is a :class:`~django.forms.FileInput`. </s> remove a :exc:`~django.db.DoesNotExist` exception when appropriate.
 </s> add a :exc:`~django.core.exceptions.DoesNotExist` exception when appropriate.
:class:`~django.http.HttpRequest`'s :ref:`attributes<httprequest-attributes>`.
  Error reports are really helpful for debugging errors, so it is generally
  useful to record as much relevant information about those errors as possible.
  For example, by default Django records the `full traceback`_ for the
  exception raised, each `traceback frame`_'s local variables, and the
:class:`~django.http.HttpRequest`'s :ref:`attributes<httprequest-attributes>`.
  
  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
  credit card number. So Django offers a set of function decorators to help you
  control which information should be filtered out of error reports in a
keep keep keep keep replace keep keep keep keep keep
 Fixed broken links, round 3. refs #19516 
docs/howto/error-reporting.txt