# Nginx will return 499 when php is too busy

**URL:** <https://www.ruby-forum.com/t/nginx-will-return-499-when-php-is-too-busy/206178>\
**Category:** NGINX\
**Created:** [April 25, 2011, 5:03am UTC](https://www.ruby-forum.com/t/nginx-will-return-499-when-php-is-too-busy/206178 "2011-04-25T05:03:36Z")\
**Posts on this page:** 2\
**Page:** 1

<div class="post-metadata">

**Author:** ![luislavena](https://www.ruby-forum.com/letter_avatar_proxy/v4/letter/l/0ea827/32.png) [@luislavena](https://www.ruby-forum.com/u/luislavena)\
**Post date:** [April 25, 2011, 5:03am UTC](https://www.ruby-forum.com/t/nginx-will-return-499-when-php-is-too-busy/206178/1 "2011-04-25T05:03:36Z")

</div>

123.150.182.101 - - [24/Apr/2011:00:15:03 +0800] “GET  
/plus/qzhlove.php?do=1&t=0.7795113758845088 HTTP/1.1” 499 0  
“[NameBright - Domain Expired](http://www.qzhlove.com/wenzhang/201119695.html)” “-” -

218.29.216.133 - - [24/Apr/2011:00:15:06 +0800] “GET /js/tuijian.php  
HTTP/1.1” 499 0 “-” “Mozilla/4.0 (compatible; MSIE 8.0; Windows NT 5.1;  
Trident/4.0; .NET CLR 2.0.50727; .NET CLR 3.0.04506.648; .NET CLR  
3.5.21022; TheWorld)” -

it seems that it’s not because client closed the connection but php-cgi,  
can I rewrite this error code to 200 or can I request once more.

---

<div class="post-metadata">

**Author:** ![kalso\_k](https://www.ruby-forum.com/letter_avatar_proxy/v4/letter/k/e68b1a/32.png) [@kalso\_k](https://www.ruby-forum.com/u/kalso_k)\
**Post date:** [April 25, 2011, 9:11pm UTC](https://www.ruby-forum.com/t/nginx-will-return-499-when-php-is-too-busy/206178/2 "2011-04-25T21:11:54Z")

</div>

Hello!

On Mon, Apr 25, 2011 at 05:03:36AM +0200, kalso k. wrote:

> it seems that it’s not because client closed the connection but php-cgi,  
> can I rewrite this error code to 200 or can I request once more.

499 means “client closed the connection before it got something”.  
In your case it’s probably may be re-spelled as “client bored  
waiting for php to answer and went away”.

There is nothing that can be done on server side here, except  
adding more backends and/or optimizing them to handle requests  
faster.

Maxim D.
