comparison src/http/ngx_http_upstream.c @ 5302:292c92fb05d7

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.
author Maxim Dounin <mdounin@mdounin.ru>
date Thu, 25 Jul 2013 15:00:25 +0400
parents a50e26148d21
children 0fb714d80909
comparison
equal deleted inserted replaced
5301:a50e26148d21 5302:292c92fb05d7
3403 3403
3404 #endif 3404 #endif
3405 3405
3406 if (u->header_sent 3406 if (u->header_sent
3407 && rc != NGX_HTTP_REQUEST_TIME_OUT 3407 && rc != NGX_HTTP_REQUEST_TIME_OUT
3408 && rc != NGX_HTTP_CLIENT_CLOSED_REQUEST
3408 && (rc == NGX_ERROR || rc >= NGX_HTTP_SPECIAL_RESPONSE)) 3409 && (rc == NGX_ERROR || rc >= NGX_HTTP_SPECIAL_RESPONSE))
3409 { 3410 {
3410 rc = 0; 3411 rc = 0;
3411 } 3412 }
3412 3413