Alex Vandiver cd530d627b uwsgi: Stop generating IOError and SIGPIPE on client close. ... Clients that close their socket to nginx suddenly also cause nginx to close its connection to uwsgi. When uwsgi finishes computing the response, it thus tries to write to a closed socket, and generates either IOError or SIGPIPE failures. Since these are caused by the _client_ closing the connection suddenly, they are not actionable by the server. At particularly high volumes, this could represent some sort of server-side failure; however, this is better detected by examining status codes at the loadbalancer. nginx uses the error code 499 for this occurrence: https://httpstatuses.com/499 Stop uwsgi from generating this family of exception entirely, using configuration for uwsgi[1]; it documents these errors as "(annoying)," hinting at their general utility." [1] https://uwsgi-docs.readthedocs.io/en/latest/Options.html#ignore-sigpipe		2020-07-31 10:40:09 -07:00
..
zulip	uwsgi: Stop generating IOError and SIGPIPE on client close.	2020-07-31 10:40:09 -07:00
zulip_ops	puppet: Use correct scope for zulip_ops::munin_plugin.	2020-07-15 21:49:45 -07:00