Django app runs with DEBUG=True but gives "Bad Request (400)" error with DEBUG=False (Using Apache and WSGI). Why?

[Chris Seberino]

If I set DEBUG=True this Django app runs fine.  If I remove DEBUG=True I get

a "Bad Request (400)" and apache error logs show lots of this..

[Fri Aug 15 03:04:27.400567 2014] [core:warn] [pid 2011:tid 140575764432768] AH00045: child process 2015 still did not exit, sending a SIGTERM

[Fri Aug 15 03:04:29.402824 2014] [core:warn] [pid 2011:tid 140575764432768] AH00045: child process 2015 still did not exit, sending a SIGTERM

[Fri Aug 15 03:04:31.405041 2014] [core:warn] [pid 2011:tid 140575764432768] AH00045: child process 2015 still did not exit, sending a SIGTERM

[Fri Aug 15 03:04:33.407308 2014] [core:error] [pid 2011:tid 140575764432768] AH00046: child process 2015 still did not exit, sending a SIGKILL

Why would it work with DEBUG turned on?

cs

[Collin Anderson]

a quick thing to check: is your ALLOWED_HOSTS set correctly?

[Chris Seberino]

Ug!! That was it!! THanks!!!

cs