Gunicorn and 400 bad request

[Benjamin....@leica-geosystems.com]

Hello everybody,

I am struggling a bit to get the latest socorro running using vagrant. I have

• ported the Vagrant config in socorro mainline to use a precise32 box and migrated the puppet module in order to get the required toolchains (gcc/python) working on my virtual box. I couldnt get socorro to build in CentOS box as the gcc and python were outdated
• compiled socorro using the documentation online ( i had to fix some things along the was but it seems to have worked)

Now, I am using apache2 as proxy on the virtual box to forward requests to gunicorn serving the WSGI Django web crashstatistic app. I have fiddled around now for some hours but i cannot get a valid HTTP response back from the gunicorn server.

Im stuck at getting BAD REQUESTs back:

vagrant@precise32:~/socorro/webapp-django/wsgi$ curl -I http://0.0.0.0:5000
HTTP/1.1 400 BAD REQUEST
Server: gunicorn/18.0
Date: Thu, 10 Sep 2015 14:56:10 GMT
Connection: close
Transfer-Encoding: chunked
X-Frame-Options: DENY
Content-Type: text/html


Now I have read with new versions of django/gunicorn ALLOWED_HOSTS might have to be set but I couldnt get it to work.
Ive tried putting settings.py or production.py files in either the webapp-django and webapp-django/wsgi/ folder but to no avail. Im pretty new to django so right now I am a bit lost.

Hoping for your help, its very much appreciated.

best,


Benjamin Fabricius
Software Engineer

Leica Geosystems AG, part of Hexagon
Machine Control Division
Heinrich-Wild-Strasse
9435 Heerbrugg, Switzerland
Skype: b.fabricius
Phone: +41 71 727 3407
E-Mail: benjamin....@leica-geosystems.com
Website: http://www.leica-geosystems.com

Social Networks: