Bug 3502: client timeout uses server-side read_timeout, not request_timeout

Also adjusts request_timeout description in squid.conf to clarify that
request_timeout applies to receiving complete HTTP request headers and not
just the first header byte or body. We reset the connection timeout to
clientLifetimeTimeout after parsing request headers.

https_port was correctly using Config.Timeout.request already.

diff --git a/src/cf.data.pre b/src/cf.data.pre
index 25cd11f041d2b9c2f2618e484a0d4fbe899142e8..ae9d7f53ee7bfd84d8edc8aa161230053b2b2d31 100644 (file)
--- a/src/cf.data.pre
+++ b/src/cf.data.pre
@@ -4113,7 +4113,7 @@ TYPE: time_t
 LOC: Config.Timeout.request
 DEFAULT: 5 minutes
 DOC_START
-       How long to wait for an HTTP request after initial
+       How long to wait for complete HTTP request headers after initial
        connection establishment.
 DOC_END
 

diff --git a/src/client_side.cc b/src/client_side.cc
index d156b88f9c073ac826bc041d1fc0dd6cc097d4b7..596e6ea2ea6aa9da77d89e05a48d59ada3371921 100644 (file)
--- a/src/client_side.cc
+++ b/src/client_side.cc
@@ -3161,7 +3161,7 @@ httpAccept(int sock, int newfd, ConnectionDetail *details,
     typedef CommCbMemFunT<ConnStateData, CommTimeoutCbParams> TimeoutDialer;
     AsyncCall::Pointer timeoutCall =  JobCallback(33, 5,
                                       TimeoutDialer, connState, ConnStateData::requestTimeout);
-    commSetTimeout(newfd, Config.Timeout.read, timeoutCall);
+    commSetTimeout(newfd, Config.Timeout.request, timeoutCall);
 
 #if USE_IDENT
     if (Ident::TheConfig.identLookup) {