tree 334a0ab5e0d3230c1cf779e6791af987c87ab4d9
parent f068c45dbe60411425493e58a5e8722df0f4083e
author Maxim Dounin <mdounin@mdounin.ru> 1425321872 +0300
committer Maxim Dounin <mdounin@mdounin.ru> 1425321872 +0300

Upstream: avoid duplicate finalization.

A request may be already finalized when ngx_http_upstream_finalize_request()
is called, due to filter finalization: after filter finalization upstream
can be finalized via ngx_http_upstream_cleanup(), either from
ngx_http_terminate_request(), or because a new request was initiated
to an upstream.  Then the upstream code will see an error returned from
the filter chain and will call the ngx_http_upstream_finalize_request()
function again.

To prevent corruption of various upstream data in this situation, make sure
to do nothing but merely call ngx_http_finalize_request().

Prodded by Yichun Zhang, for details see the thread at
http://nginx.org/pipermail/nginx-devel/2015-February/006539.html.