From fbc06eef1af1d7ecf91fae5a94a1994f356ffd22 Mon Sep 17 00:00:00 2001 From: Tim Graham Date: Tue, 25 Dec 2012 09:56:22 -0500 Subject: [1.5.X] Fixed broken links, round 3. refs #19516 Backport of b3a8c9dab8 from master --- docs/howto/error-reporting.txt | 20 ++++++++++---------- 1 file changed, 10 insertions(+), 10 deletions(-) (limited to 'docs/howto') diff --git a/docs/howto/error-reporting.txt b/docs/howto/error-reporting.txt index 78e797b607..5fbe5eda59 100644 --- a/docs/howto/error-reporting.txt +++ b/docs/howto/error-reporting.txt @@ -123,7 +123,7 @@ 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`. +:class:`~django.http.HttpRequest`'s :ref:`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 @@ -165,11 +165,11 @@ production environment (that is, where :setting:`DEBUG` is set to ``False``): .. function:: sensitive_post_parameters(*parameters) - If one of your views receives an :class:`HttpRequest` object with - :attr:`POST parameters` 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:: + If one of your views receives an :class:`~django.http.HttpRequest` object + with :attr:`POST parameters` 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:: from django.views.decorators.debug import sensitive_post_parameters @@ -198,10 +198,10 @@ production environment (that is, where :setting:`DEBUG` is set to ``False``): .. versionchanged:: 1.4 Since version 1.4, all POST parameters are 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. + 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. .. _custom-error-reports: -- cgit v1.3