-
Poul-Henning Kamp authored
Previously we always used SO_LINGER to make sure that all queued data got transmitted, no matter under which circumstances we closed the client connection. Change this so that SO_LINGER is only activated for orderly connection closure (ie: "Connection: close" from client or error handling), in all other cases (usually the client connecting on us, abandon any data queued for transmission. This _may_ reduce the tendency of worker threads to get hung up on network failures a little bit. git-svn-id: http://www.varnish-cache.org/svn/trunk/varnish-cache@4046 d4fa192b-c00b-0410-8231-f00ffab90ce4
7243e9c5
Name |
Last commit
|
Last update |
---|---|---|
.. | ||
tests | ||
Makefile.am | ||
flint.lnt | ||
flint.sh | ||
t001.vtc | ||
varnishtest.1 | ||
vtc.c | ||
vtc.h | ||
vtc_client.c | ||
vtc_http.c | ||
vtc_log.c | ||
vtc_sema.c | ||
vtc_server.c | ||
vtc_varnish.c |