That's why it returned a 4xx error instead of a 5xx error. 4xx errors (like 404 - File not found, 403 - Unauthorized) tend to be because the client has done something wrong, 5xx errors are when the server did something wrong.
<br><br><div class="gmail_quote">On Jan 5, 2008 12:47 PM, Dave Cheney <<a href="mailto:dave@cheney.net">dave@cheney.net</a>> wrote:<br><blockquote class="gmail_quote" style="border-left: 1px solid rgb(204, 204, 204); margin: 0pt 0pt 0pt 0.8ex; padding-left: 1ex;">
<div style="">However, from the applications point of view, we handled the request successfully, and invested processing resources doing so, so it should be accounted for.<div><br></div><div>Cheers</div><font color="#888888">
<div><br></div><div>Dave</div></font><div><div></div><div class="Wj3C7c"><div><br><div><div>On 05/01/2008, at 1:15 PM, Wayne Robinson wrote:</div><br><blockquote type="cite">Are you sure you want it to return 200? My understanding is that the user never received the content because they closed the connection.
<br><br><div class="gmail_quote">On Jan 5, 2008 11:14 AM, Dave Cheney <<a href="mailto:dave@cheney.net" target="_blank"> dave@cheney.net</a>> wrote:<br><blockquote class="gmail_quote" style="border-left: 1px solid rgb(204, 204, 204); margin: 0pt 0pt 0pt 0.8ex; padding-left: 1ex;">
Thank you very much. I guess my only question is, can I rewrite this <br>error code to 200 (as the 499 upsets awstats)<br><br>Cheers<br><font color="#888888"><br>Dave<br></font><div><div></div><div><br>On 03/01/2008, at 1:31 AM, Roxis wrote:
<br><br>> special code 499 means client closed connection <br>> before nginx response<br><br><br></div></div></blockquote></div><br></blockquote></div><br></div></div></div></div></blockquote></div><br>