From 86277254dda48d76f3617ceb8ee934dfddeb332f Mon Sep 17 00:00:00 2001
From: Maxim Dounin <mdounin@mdounin.ru>
Date: Thu, 25 Jul 2013 15:00:25 +0400
Subject: [PATCH] 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.
---
 src/http/ngx_http_upstream.c | 1 +
 1 file changed, 1 insertion(+)

diff --git a/src/http/ngx_http_upstream.c b/src/http/ngx_http_upstream.c
index c4e0c645c..8590f4e2e 100644
--- a/src/http/ngx_http_upstream.c
+++ b/src/http/ngx_http_upstream.c
@@ -3405,6 +3405,7 @@ ngx_http_upstream_finalize_request(ngx_http_request_t *r,
 
     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;