On Wed, May 07, 2014 at 07:30:43AM +0200, Willy Tarreau wrote: > > The strange news: Contrary to your statement, the client connection is > > closed after the 1 second timeout. It even logs this. The only thing > > that doesn't happen properly is the absence of any response. Just > > immediate connection close. > > > > > > Before patch: > > haproxy[26318]: 127.0.0.1:51995 [06/May/2014:18:55:33.002] f1 b1/s1 > > 0/0/0/-1/2001 504 194 - - sH-- 0/0/0/0/0 0/0 "GET / HTTP/1.1" > > > > After patch: > > haproxy[27216]: 127.0.0.1:52027 [06/May/2014:18:56:34.165] f1 b1/s1 > > 0/0/0/-1/1002 -1 0 - - cD-- 0/0/0/0/0 0/0 "GET / HTTP/1.1" > > Interesting, for me it waited till the end. Or maybe you have > "option abortonclose" ?
OK I found, it's because your server receives the abort and closes immediately that the client timeout is enforced. In my test, the server was waiting a predefined amount of time, thus the server timeout was enforced. Willy
