Re: "timeout client" weird behaviour in 1.3.22

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.

Here's a minimalist configuration that reproduces the bug:

defaults

	timeout connect 10s
	timeout client 3s
	timeout server 15m
        option forceclose

listen  testssh 192.168.0.1:23
	mode tcp
        server localhost 127.0.0.1:22

listen  testssh 192.168.0.1:81
        server localhost 127.0.0.1:80

If you connect on port 23, you get disconnected after 3 seconds, even if you keep on typing.

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?

-- 
Cyril Bouthors