Mercurial > hg > nginx-quic
view auto/lib/sha1/makefile.bcc @ 5994:5abf5af257a7
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.
author | Maxim Dounin <mdounin@mdounin.ru> |
---|---|
date | Mon, 02 Mar 2015 21:44:32 +0300 |
parents | d620f497c50f |
children |
line wrap: on
line source
# Copyright (C) Igor Sysoev # Copyright (C) Nginx, Inc. CFLAGS = -q -O2 -tWM $(CPU_OPT) -DL_ENDIAN !if "$(SHA1_ASM)" == "YES" sha1.lib: cd $(SHA1) bcc32 -c $(CFLAGS) -DSHA1_ASM sha1dgst.c tlib sha1.lib +sha1dgst.obj +"asm\s-win32.obj" !else sha1.lib: cd $(SHA1) bcc32 -c $(CFLAGS) sha1dgst.c tlib sha1.lib +sha1dgst.obj !endif