In nginx, 499 means "client has closed connection". However, guys know
little about 499 as it's not defined by rfc2616 but by nginx.

When a client sent a request, and closed the connection without waiting for
the response, a 499 code occurs. If there're a lot of 499s in your
access_log, it's mostly caused by the slow back-ends (too slow for your
users to wait). You may have to optimize your website performance.

Regards,
Zhang Lei (@blogkid on Twitter)

On Mon, Aug 15, 2011 at 1:43 PM, Sharl.Jimh.Tsin <amoiz.shine@gmail.com>wrote:

> 在 2011-08-14日的 22:36 -0400，sunjipeng_neu写道：
> > What's the reason for error "499"?
> >
> > How to resolve this error?
> >
> > Thanks
> >
> > Posted at Nginx Forum:
> http://forum.nginx.org/read.php?2,213789,213789#msg-213789
> >
> > _______________________________________________
> > nginx mailing list
> > nginx@nginx.org
> > http://mailman.nginx.org/mailman/listinfo/nginx
>
> there is no status code named "499".
>
> --
> Best regards,
> Sharl.Jimh.Tsin (From China **Obviously Taiwan INCLUDED**)
>
> Using Gmail? Please read this important notice:
> http://www.fsf.org/campaigns/jstrap/gmail?10073.
>
> _______________________________________________
> nginx mailing list
> nginx@nginx.org
> http://mailman.nginx.org/mailman/listinfo/nginx
>
_______________________________________________
nginx mailing list
nginx@nginx.org
http://mailman.nginx.org/mailman/listinfo/nginx