nginix 0.5.34 returns 499's for proxied content

[Dave Cheney]

However, from the applications point of view, we handled the request  
successfully, and invested processing resources doing so, so it should  
be accounted for.

Cheers

Dave

On 05/01/2008, at 1:15 PM, Wayne Robinson wrote:

> Are you sure you want it to return 200? My understanding is that the  
> user never received the content because they closed the connection.
>
> On Jan 5, 2008 11:14 AM, Dave Cheney < dave at cheney.net> wrote:
> Thank you very much. I guess my only question is, can I rewrite this
> error code to 200 (as the 499 upsets awstats)
>
> Cheers
>
> Dave
>
> On 03/01/2008, at 1:31 AM, Roxis wrote:
>
> > special code 499 means client closed connection
> > before nginx response
>
>
>

-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://nginx.org/pipermail/nginx/attachments/20080105/5047e61b/attachment.html>