On 03/28/2014 08:05 AM, Amos Jeffries wrote:
It should not be the idle timeout if its a CONNECT request unless they
are ssl-bumping it.
It may be read or request total timeout. Some of the old 3.2 earlier
releases did not update those as traffic went through.
Amos
it's the latest 3.4.4.
I am yet to be sure about the reason to the issue so I have no conclusions.
As of now I changed the client_idle_pconn_timeout to 60 mintutes since
this is a show of 20 minutes.
I will look at the tcp stuff layer later on.
(MultiWAN lab is up and running using ubuntu)
Eliezer
