From 9d918dabaa8eb2fa9a285e84ba1e5707a6dea27c Mon Sep 17 00:00:00 2001 From: Eric Covener Date: Thu, 4 Nov 2010 16:24:51 +0000 Subject: [PATCH] PR#50174: don't offer 120ms as a "typical" TCP keepalive frequency. Initial keepalive timers can be as high as 2 hours (windows/linux/solars defaults via google). Drive home the idea that users need to figure out their OS and Firewall timers and make the former smaller than th elatter. git-svn-id: https://svn.apache.org/repos/asf/httpd/httpd/trunk@1031062 13f79535-47bb-0310-9956-ffa450edef68 --- docs/manual/mod/mod_proxy.html.en | 11 +++++++---- docs/manual/mod/mod_proxy.xml | 11 +++++++---- 2 files changed, 14 insertions(+), 8 deletions(-) diff --git a/docs/manual/mod/mod_proxy.html.en b/docs/manual/mod/mod_proxy.html.en index 22df183d12a..81c34adc110 100644 --- a/docs/manual/mod/mod_proxy.html.en +++ b/docs/manual/mod/mod_proxy.html.en @@ -1013,12 +1013,15 @@ through keepalive Off - This parameter should be used when you have a firewall between your +

This parameter should be used when you have a firewall between your Apache httpd and the backend server, who tend to drop inactive connections. This flag will tell the Operating System to send KEEP_ALIVE - messages on inactive connections (interval depends on global OS settings, - generally 120ms), and thus prevent the firewall to drop the connection. - To enable keepalive set this property value to On. + messages on inactive connections and thus prevent the firewall to drop the connection. + To enable keepalive set this property value to On.

+

The frequency of initial and subsequent TCP keepalive probes + depends on global OS settings, and may be as high as 2 hours. To be useful, + the frequency configured in the OS must be smaller than the threshold used + by the firewall.

lbset 0 diff --git a/docs/manual/mod/mod_proxy.xml b/docs/manual/mod/mod_proxy.xml index c610c5be2b1..fc5dfeb7ba1 100644 --- a/docs/manual/mod/mod_proxy.xml +++ b/docs/manual/mod/mod_proxy.xml @@ -884,12 +884,15 @@ expressions keepalive Off - This parameter should be used when you have a firewall between your +

This parameter should be used when you have a firewall between your Apache httpd and the backend server, who tend to drop inactive connections. This flag will tell the Operating System to send KEEP_ALIVE - messages on inactive connections (interval depends on global OS settings, - generally 120ms), and thus prevent the firewall to drop the connection. - To enable keepalive set this property value to On. + messages on inactive connections and thus prevent the firewall to drop the connection. + To enable keepalive set this property value to On.

+

The frequency of initial and subsequent TCP keepalive probes + depends on global OS settings, and may be as high as 2 hours. To be useful, + the frequency configured in the OS must be smaller than the threshold used + by the firewall.

lbset 0 -- 2.47.2