Nginx 499错误代码 [英] Nginx 499 error codes

问题描述

我收到了很多499个nginx错误代码。我看到这是客户端问题。这不是Nginx或我的uWSGI堆栈的问题。我注意到当获得499时uWSGI日志中的相关性。

I am 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

我正在寻找更深入的解释，并希望我的nginx配置没有错对于uwsgi。我正在考虑它的面值...它不是我的问题......客户问题。

I am looking for a more indepth explanation and hoping it is nothing wrong with my nginx config for uwsgi. I am taking it on face value...its not a me problem..its a client issue.

谢谢

推荐答案

Nginx中的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屋！