Re: "timeout client" weird behaviour in 1.3.22

Hi Cyril and Willy,

Le mardi 13 avril 2010 19:10:14, Cyril Bouthors a écrit :
> On 13 Apr 2010, cyril#bouthors.org wrote:
>
> > I upgraded from 1.3.15 (lenny) to 1.3.22 (lenny-backports) and "timeout
> > client X" now seems to close connections at X even if client
> > continuously sends something.
>
> After a short chat on #haproxy with Hervé Commowick, I came to the
> conclusion that this bug is only reproducible when "option forceclose"
> is activated and "mode tcp" is used.
>
> "option forceclose" should not affect "mode tcp" behavior but it does.
> (...)
> > I can reproduce the bug with 1.3.18, 1.3.22 and 1.3.24.
>
> The same configuration works as expected with 1.3.15, I mean you only
> get disconnected after 3 seconds of *inactivity*.
>
> Any idea what happened between 1.3.15 and 1.3.18?
 

This changes were introduced in 1.3.16 with this commit : http://haproxy.1wt.eu/git?p=haproxy-1.3.git;a=commit;h=55a8d0e1bb1507c7c80e812dff6e516e29f3c507 where a test on "PR_O_FORCE_CLO" was moved in session.c

Maybe "option forceclose" should be automatically disabled in tcp mode, as it is done for "option httplog" and others since 1.3.23 (or maybe someone might also want it in tcp mode).

-- 
Cyril Bonté