diff options
| author | Tim Graham <timograham@gmail.com> | 2013-06-09 15:05:15 -0400 |
|---|---|---|
| committer | Tim Graham <timograham@gmail.com> | 2013-06-09 15:05:15 -0400 |
| commit | 4e94c84e50b960405d5708d8d9528c44c7dabe83 (patch) | |
| tree | 51139dcd674f66ddff3a9c8ef52e21b5ebd12f06 /docs/ref | |
| parent | 175a102ddceae2ebd1a4e03916a23adafc35bda5 (diff) | |
Fixed #19875 - Added warnings regarding DEBUG=False and empty ALLOWED_HOSTS
Diffstat (limited to 'docs/ref')
| -rw-r--r-- | docs/ref/settings.txt | 4 |
1 files changed, 4 insertions, 0 deletions
diff --git a/docs/ref/settings.txt b/docs/ref/settings.txt index ef52d3170c..897af275a0 100644 --- a/docs/ref/settings.txt +++ b/docs/ref/settings.txt @@ -852,6 +852,10 @@ It is also important to remember that when running with :setting:`DEBUG` turned on, Django will remember every SQL query it executes. This is useful when you're debugging, but it'll rapidly consume memory on a production server. +Finally, if :setting:`DEBUG` is ``False``, you also need to properly set +the :setting:`ALLOWED_HOSTS` setting. Failing to do so will result in all +requests being returned as "Bad Request (400)". + .. _django/views/debug.py: https://github.com/django/django/blob/master/django/views/debug.py .. setting:: DEBUG_PROPAGATE_EXCEPTIONS |