details: http://hg.nginx.org/nginx/rev/292c92fb05d7
branches:
changeset: 5302:292c92fb05d7
user: Maxim Dounin <mdounin@mdounin.ru>
date: Thu Jul 25 15:00:25 2013 +0400
description:
Upstream: NGX_HTTP_CLIENT_CLOSED_REQUEST no longer reset to 0.

The NGX_HTTP_CLIENT_CLOSED_REQUEST code is allowed to happen after we
started sending a response (much like NGX_HTTP_REQUEST_TIME_OUT), so there
is no need to reset response code to 0 in this case.

diffstat:

src/http/ngx_http_upstream.c | 1 +
1 files changed, 1 insertions(+), 0 deletions(-)

diffs (11 lines):

diff --git a/src/http/ngx_http_upstream.c b/src/http/ngx_http_upstream.c
--- a/src/http/ngx_http_upstream.c
+++ b/src/http/ngx_http_upstream.c
@@ -3405,6 +3405,7 @@ ngx_http_upstream_finalize_request(ngx_h

if (u->header_sent
&& rc != NGX_HTTP_REQUEST_TIME_OUT
+ && rc != NGX_HTTP_CLIENT_CLOSED_REQUEST
&& (rc == NGX_ERROR || rc >= NGX_HTTP_SPECIAL_RESPONSE))
{
rc = 0;

_______________________________________________
nginx-devel mailing list
nginx-devel@nginx.org
http://mailman.nginx.org/mailman/listinfo/nginx-devel