NGINX 499错误代码的可能原因 [英] Possible reason for NGINX 499 error codes

问题描述

我收到了很多499个NGINX错误代码.我看到这是一个客户端问题. NGINX或我的uWSGI堆栈都没有问题.我注意到当获得499时，uWSGI日志中的相关性.

I'm getting a lot of 499 NGINX error codes. I see that this is a client side issue. It is not a problem with NGINX or my uWSGI stack. I note the correlation in uWSGI logs when a get a 499.

address space usage: 383692800 bytes/365MB} {rss usage: 167038976
bytes/159MB} [pid: 16614|app: 0|req: 74184/222373] 74.125.191.16 ()
{36 vars in 481 bytes} [Fri Oct 19 10:07:07 2012] POST /bidder/ =>
generated 0 bytes in 8 msecs (HTTP/1.1 200) 1 headers in 59 bytes (1
switches on core 1760)
SIGPIPE: writing to a closed pipe/socket/fd (probably the client
disconnected) on request /bidder/ (ip 74.125.xxx.xxx) !!!
Fri Oct 19 10:07:07 2012 - write(): Broken pipe [proto/uwsgi.c line
143] during POST /bidder/ (74.125.xxx.xxx)
IOError: write error

我正在寻找更深入的解释，希望uwsgi的NGINX配置没有问题.我把它看成是面值.似乎是一个客户问题.

I'm looking for a more in depth explanation and hoping it is nothing wrong with my NGINX config for uwsgi. I'm taking it on face value. It seems like a client issue.

推荐答案

HTTP 499表示客户端在服务器响应请求之前已关闭连接.根据我的经验，通常是由客户端超时引起的.据我所知，这是Nginx特定的错误代码.

HTTP 499 in Nginx means that the client closed the connection before the server answered the request. In my experience is usually caused by client side timeout. As I know it's an Nginx specific error code.

这篇关于NGINX 499错误代码的可能原因的文章就介绍到这了，希望我们推荐的答案对大家有所帮助，也希望大家多多支持IT屋！