Forum Discussion
HenryO_166334
Aug 09, 2014Nimbostratus
Keepalive v TCP Idle timeout
Hi
In relation to F5 Load balancing, could someone explain to me the difference between the Keepalive and TCP Idle timeout?
Client > F5 > Server in Server pool
Does one relate to clien...
Kevin_Davies_40
Aug 10, 2014Nacreous
Keeping connections alive is the default for HTTP v1.1 which is currently the worldwide standard. Is is a header provided by the web browser whenever HTTP version 1.1 requests are used. See HTTP Persistent Connections
Connection: Keepalive
The TCP Idle timeout is the longest the F5 will keep a TCP client connection open when talking with the either side depending on the TCP profile you apply. See Solution ID 7606 for more information on the BIGIP TCP behaviour and its settings.
- Peter_ZAug 10, 2014CirrusKevin, I don`t think tcp keepalive, configured in the tcp profile is the same as HTTP keepalive you are mentioning. TCP profile settings will affect any L7 protocol..
- Kevin_Davies_40Aug 10, 2014NacreousThat is correct they are quite separate. The OP wanted to know the difference.
Recent Discussions
Related Content
DevCentral Quicklinks
* Getting Started on DevCentral
* Community Guidelines
* Community Terms of Use / EULA
* Community Ranking Explained
* Community Resources
* Contact the DevCentral Team
* Update MFA on account.f5.com
Discover DevCentral Connects