From c577d8a4981233b4d0f65c6ce57ae33d304095b9 Mon Sep 17 00:00:00 2001 From: Tim Graham Date: Thu, 9 Mar 2017 11:55:14 -0500 Subject: [PATCH] Described DEBUG_PROPAGATE_EXCEPTIONS behavior in more detail. --- docs/ref/settings.txt | 13 +++++++++---- 1 file changed, 9 insertions(+), 4 deletions(-) diff --git a/docs/ref/settings.txt b/docs/ref/settings.txt index 02f84d90c6..4e13c1e20e 100644 --- a/docs/ref/settings.txt +++ b/docs/ref/settings.txt @@ -1097,10 +1097,15 @@ requests being returned as "Bad Request (400)". Default: ``False`` -If set to True, Django's normal exception handling of view functions -will be suppressed, and exceptions will propagate upwards. This can -be useful for some test setups, and should never be used on a live -site. +If set to ``True``, Django's exception handling of view functions +(:data:`~django.conf.urls.handler500`, or the debug view if :setting:`DEBUG` +is ``True``) and logging of 500 responses (:ref:`django-request-logger`) is +skipped and exceptions propagate upwards. + +This can be useful for some test setups. It shouldn't be used on a live site +unless you want your web server (instead of Django) to generate "Internal +Server Error" responses. In that case, make sure your server doesn't show the +stack trace or other sensitive information in the response. .. setting:: DECIMAL_SEPARATOR