> Hold on a second let me get that right.
> Without TCP keep alive enabled, a client which sends some data every
> 10mins and timeout client set to 30m it more or less means that the
> connection will only drop by the client. Am I right?
Without *HTTP* keep-alive you mean. Well, that depends what mode
you are referring to exactly. The default mode is not tunnel mode
anymore, but is keep-alive since 1.5-dev21. You can still use
"option http-tunnel" to get that behavior back. But in 1.5 stable
the default mode is "option http-keep-alive", which basically
is client and server keep-alive mode.
In tunnel-mode, "timeout tunnel" is used first, then "timeout
client".
In server-close or keep-alive mode ...:
> I understand that connection should have been closed since I use
> timeout http-keep-alive 10s.
That is correct, if your HTTP sessions are idling in keep-alive mode,
but if the session is in another state, like sending a http-request,
a different timeout applies.
Because the situation is not perfectly clear, I suggested code upgrade
and "show sess" on the unix socket, that will tell us exactly the state
the session is in.
Regards,
Lukas
