From 46dacb5bb157ff78e21c19f1f1b109edf378ddcb Mon Sep 17 00:00:00 2001 From: Tim Graham Date: Sun, 9 Jun 2013 15:05:15 -0400 Subject: [1.5.x] Fixed #19875 - Added warnings regarding DEBUG=False and empty ALLOWED_HOSTS Backport of 4e94c84e50 from master --- docs/ref/settings.txt | 4 ++++ 1 file changed, 4 insertions(+) (limited to 'docs/ref') diff --git a/docs/ref/settings.txt b/docs/ref/settings.txt index 6f7fc475bc..783af7c5ff 100644 --- a/docs/ref/settings.txt +++ b/docs/ref/settings.txt @@ -823,6 +823,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 DEBUG_PROPAGATE_EXCEPTIONS -- cgit v1.3