We've noticed that when making calls that return a 413 http status code we sometimes see an error with the response from uwsgi. It seems random and we cannot figure out what causes this exactly. The only pattern we've noticed is some machines usually get an error, and others usually do not. We're using uwsgi 1.9.6 on CentOS 5 built without libcap devel. Has anyone seen this or can anyone explain what's going on?
Thanks, Charles Below is an example bad call using curl: * About to connect() to greencde.dev port 8001 (#0) * Trying 127.0.0.1... * Connected to greencde.dev (127.0.0.1) port 8001 (#0) > POST /creative/upload_file HTTP/1.1 > User-Agent: curl/7.29.0 > Host: greencde.dev:8001 > Accept: */* > Cookie: access_token=d29bcab1a2c72a29d0b1ab9fe9e1416cce7af08dd5d500d7958180460564d7534d41752194f8d10d50d20119af5c101fa99b8469b3271cb4d9c8e31ab65d4a6a05193f9b4 > Content-Length: 14625352 > Expect: 100-continue > Content-Type: multipart/form-data; boundary=----------------------------9247cf3763f8 > < HTTP/1.1 413 REQUEST ENTITY TOO LARGE < Content-Type: text/html < Content-Length: 174 * HTTP error before end of send, stop sending < Request Entity Too Large Requests cannot be larger than 10752 kb * Closing connection 0 -- Charles Law Software Developer Watch how we make online advertising simple: http://bit.ly/Ent_vid www.openx.com <http://www.openx.org/> | follow us on: Twitter<http://twitter.com/openx> Facebook <http://www.facebook.com/OpenX> LinkedIn<http://www.linkedin.com/company/openx/products>
_______________________________________________ uWSGI mailing list [email protected] http://lists.unbit.it/cgi-bin/mailman/listinfo/uwsgi
