<html><head></head><body style="word-wrap: break-word; -webkit-nbsp-mode: space; -webkit-line-break: after-white-space; ">Thanks Xav and Valentin for the quick response. Sorry - I have to copy your responses because I was subscribed on digest rather than real-time email. But I am now on the normal mailing list.<div><br></div><div><b>Error Log</b></div><div>The error log shows nothing. Literally. The access_log shows the access url and the 400 error. But the error log does not. I know that is hard to believe its similar to what is said here:</div><div><br></div><div><a href="http://www.ruby-forum.com/topic/2573586">http://www.ruby-forum.com/topic/2573586</a></div><div><br></div><div>In that the also had the same problem that Bad Request nothing shows in the error log. I thought it might be a similar issue but I don't have any spaces in python urllib2 header so I don't think that is the issue.</div><div><br></div><div>I have also created application logging in Django and have "GOT HERE" log statement in the first line of the view that handles the POST request.. That line never gets called so it appears Nginx is kicking out the request before it ever passes to the django app.</div><div><br></div><div>This is what makes so irritatingly difficult to debug. It is also I feel it some type of permission error or setting that does not allow POST requests. I've also read here (<a href="https://calomel.org/nginx.html">https://calomel.org/nginx.html</a>) that Nginx by default only allows GET requests but I couldn't find anywhere where the is verified nor how to enable that.</div><div><br></div><div>I'm stumped.</div><div><br></div><div><b>WSGI</b></div><div>Xav - I am happy try <a href="http://gunicorn.org">gunicorn.org</a> as a wsgi server instead of fcgi. Particularly if there isn't a reasonable solution to this problem. Again - I'm now to this. Can you give a quick background on why you don't recommend fcgi and do recommend gunicorn? (current. problem excluded ;-)</div><div><br></div><div>Henry</div><div><br></div><div><br></div><div><div><div><div>On Jan 17, 2012, at 4:35 PM, Henry Ward wrote:</div><br class="Apple-interchange-newline"><blockquote type="cite"><div>Hello Nginx Group.<br><br>I am new to Ngnix and installing my first Nginx/Django server. I've been struggling with a Bad Request 400 Error for two days now and I have nowhere else to go. Here is the problem:<br><br>I have Nginx configured with django. My default config file is below. I am have a basic django-piston REST service setup that works correctly with django's runserver. The following two commands work perfectly with django's runserver http server:<br><br>url = '<a href="http://localhost/receipts'">http://localhost/receipts'</a><br># GET receipts data<br>req = urllib2.Request(url)<span class="Apple-tab-span" style="white-space:pre"> </span><span class="Apple-tab-span" style="white-space:pre"> </span><br>f = urllib2.urlopen(req)<br><br># POST Receipts data with json data<br>data = <json data...><br>req = urllib2.Request(url, data=data, headers={'Content-Type': 'application/json'}) <span class="Apple-tab-span" style="white-space:pre"> </span><br>f = urllib2.urlopen(req)<br><br>When I run the same requests against my nginx installation the GET function works just fine. However, the POST request returns a HTTP Error 400: BAD REQUEST error. <br><br>It is exactly the same code and I know this is working with the django runserver. It must be some configuration in Nginx that is regecting the POST request. I get that error for any Content-Type. <br><br>I have looked everywhere and I cannot find anything about allowing this post request. I hope someone here can help nudge me in the right direction. My Nginx config file settings is below. I have modified many variables like buffer sizes and body sizes and it is not that. The data I'm posting is less than 8k. <br><br>Any ideas?<br><br>----------------------------<br><br>server {<br> include mime.types;<br> default_type application/json;<br><br> client_body_buffer_size 1200K;<br> client_header_buffer_size 1200K;<br> client_max_body_size 2m;<br> large_client_header_buffers 2 1200K;<br><br> listen 80; ## listen for ipv4; this line is default and implied<br> #listen [::]:80 default ipv6only=on; ## listen for ipv6<br><br><br> # Make site accessible from <a href="http://localhost/">http://localhost/</a><br> server_name localhost;<br><br> # Log information<br> access_log /home/henry/logs/access.log;<br> error_log /home/henry/logs/error.log;<br><br> root /home/henry/webservice/public;<br><br> location /site_media<br> {<br> root /path/to/yoursite.com/public;<br> }<br><br> location / {<br> # host and port to fastcgi server<br> fastcgi_pass 127.0.0.1:8081;<br> fastcgi_param PATH_INFO $fastcgi_script_name;<br> fastcgi_param REQUEST_METHOD $request_method;<br> fastcgi_param QUERY_STRING $query_string;<br> fastcgi_param SERVER_NAME $server_name;<br> fastcgi_param SERVER_PORT $server_port;<br> fastcgi_param SERVER_PROTOCOL $server_protocol;<br> fastcgi_param CONTENT_TYPE $content_type;<br> fastcgi_param CONTENT_LENGTH $content_length;<br> fastcgi_pass_header Authorization;<br> fastcgi_intercept_errors off;<br> }<br><br> location /doc {<br> root /usr/share;<br> autoindex on;<br> allow 127.0.0.1;<br> deny all;<br> }<br><br> location /images {<br> root /usr/share;<br> autoindex off;<br> }<br><br>}<br><br><br></div></blockquote></div><br></div></div></body></html>