Right now, if one is using the HTTP plugin and a read timeout occurs when
reading the body from the client, something is logged like
"[uwsgi-body-read] Timeout reading 2358 bytes. Content-Length: 2358
consumed: 0 left: 2358" and then the socket is closed. This typically
causes a load balancer / reverse proxy to emit a 502. It would be nice if
the HTTP plugin could instead emit a 408 when such a body read timeout
occurs. Does anybody know if that's possible?

-- 
James Brown
Engineer
_______________________________________________
uWSGI mailing list
uWSGI@lists.unbit.it
http://lists.unbit.it/cgi-bin/mailman/listinfo/uwsgi

Reply via email to