Django gives Bad Request 400 when DEBUG False

Question

I am new to django-1 6  When I run the django server with DEBUG   True  it s running perfectly  But when I change DEBUG to False in the settings file  then the server stopped and it gives the following error on the command prompt   CommandError  You must set settings ALLOWED HOSTS if DEBUG is False    After I changed ALLOWED HOSTS to   http   127 0 0 1 8000     in the browser I get the error   Bad Request  400    Is it possible to run Django without debug mode

User · Answer

in the settings py of your project  check line 28  where is the Allows Host settings py  ALLOWED HOSTS     IP    servidor      you must put the IP and the server you use  level local or web settings py ALLOWED HOSTS     127 0 0 1    localhost    www ejemplo com    or ALLOWED HOSTS

User · Answer

I had to stop the apache server first     f e  sudo systemctl stop httpd service   sudo systemctl disable httpd service    That solved my problem besides editing the  settings py  file   to ALLOWED HOSTS     se rv er ip    www example com

User · Answer

The ALLOWED HOSTS list should contain fully qualified host names  not urls  Leave out the port and the protocol  If you are using 127 0 0 1  I would add localhost to the list too   ALLOWED HOSTS     127 0 0 1    localhost     You could also use   to match any host   ALLOWED HOSTS           Quoting the documentation      Values in this list can be fully qualified names  e g   www example com    in which case they will be matched against the request   s Host header exactly  case-insensitive  not including port   A value beginning with a period can be used as a subdomain wildcard    example com  will match example com  www example com  and any other subdomain of example com  A value of     will match anything  in this case you are responsible to provide your own validation of the Host header  perhaps in a middleware  if so this middleware must be listed first in MIDDLEWARE CLASSES     Bold emphasis mine   The status 400 response you get is due to a SuspiciousOperation exception being raised when your host header doesn t match any values in that list

User · Answer

With DEBUG   False in you settings file  you also need ALLOWED HOST list set up  Try including ALLOWED HOST     127 0 0 1    localhost    www yourdomain com    Otherwise you might receive a Bad Request 400  error from django

User · Answer

For me as I have already xampp on 127 0 0 1 and django on 127 0 1 1 and i kept trying adding hosts   ALLOWED HOSTS     127 0 0 1    localhost    www yourdomain com         127 0 1 1     and i got the same error or  400  bad request    so I change the url to 127 0 1 1  the used port  project and voila    you have to check what is your virtual network address  for me as i use bitnami django stack 2 2 3-1 on Linux i can check which port django is using  if you have an error   400 bad request   then i guess django on different virtual network    good luck

User · Answer

I had the same problem and I fixed it by setting ALLOWED HOSTS         and to solve the problem with the static images you have to change the virtual paths in the environment configuration like this   Virtual Path   nbsp  nbsp  nbsp  nbsp  nbsp  nbsp  nbsp  nbsp  nbsp  nbsp  nbsp  nbsp  nbsp  nbsp  nbsp  nbsp Directory  static  nbsp  nbsp  nbsp  nbsp  nbsp  nbsp  nbsp  nbsp  nbsp  nbsp  nbsp  nbsp  nbsp  nbsp  nbsp  nbsp  nbsp  nbsp  nbsp  nbsp  nbsp  nbsp  nbsp  nbsp  nbsp  nbsp  opt python current app yourpj static   media   nbsp  nbsp  nbsp  nbsp  nbsp  nbsp  nbsp  nbsp  nbsp  nbsp  nbsp  nbsp  nbsp  nbsp  nbsp  nbsp  nbsp  nbsp  nbsp  nbsp  nbsp  nbsp   opt python current app Nuevo media   I hope it helps you   PD  sorry for my bad english

User · Answer

I had the same problem and none of the answers resolved my problem  for resolving the situation like this it s better to enable logging by adding the following config to settings py temporary  LOGGING      version   1   disable existing loggers   False   handlers      file      level    DEBUG    class    logging FileHandler    filename     tmp debug log          loggers      django      handlers     file     level    DEBUG    propagate   True            and try to tail -f  tmp debug log  and when you see your issue you can handle it much easier than blind debugging   My issue was about to   Invalid HTTP HOST header   pt web 8000   The domain name provided is not valid according to RFC 1034 1035   and resolve it by adding proxy set header Host  host  to Nginx config file and enabling port forwarding by USE X FORWARDED PORT   True in the settings py   it s because in my case I ve listened to request in Nginx on port 8080 and pass it to guni on port 8000

User · Answer

For me  I got this error by not setting USE X FORWARDED HOST to true   From the docs       This should only be enabled if a proxy which sets this header is in use    My hosting service wrote explicitly in their documentation that this setting must be used  and I get this 400 error if I forget it

User · Answer

Try to run your server with the --insecure  just like this    python manage py runserver --insecure

User · Answer

Navigate to settings and locate the base py file Set the allowed hosts to   ALLOWED HOSTS

[python] Django gives Bad Request (400) when DEBUG = False

Examples related to python

Examples related to django