[MEDIUM] introduce separation between contimeout, and tarpit + queue
Now the connect timeout, tarpit timeout and queue timeout are
distinct. In order to retain compatibility with older versions,
if either queue or tarpit is left unset both in the proxy and
in the default proxy, then it is inherited from the connect
timeout as before.
diff --git a/src/proto_http.c b/src/proto_http.c
index 370fded..55c67c1 100644
--- a/src/proto_http.c
+++ b/src/proto_http.c
@@ -2038,17 +2038,17 @@
tv_eternity(&req->rex);
}
- /* When a connection is tarpitted, we use the queue timeout for the
- * tarpit delay, which currently happens to be the server's connect
- * timeout. If unset, then set it to zero because we really want it
- * to expire at one moment.
+ /* When a connection is tarpitted, we use the tarpit timeout,
+ * which may be the same as the connect timeout if unspecified.
+ * If unset, then set it to zero because we really want it to
+ * eventually expire.
*/
if (txn->flags & TX_CLTARPIT) {
t->req->l = 0;
/* flush the request so that we can drop the connection early
* if the client closes first.
*/
- if (!tv_add_ifset(&req->cex, &now, &t->be->contimeout))
+ if (!tv_add_ifset(&req->cex, &now, &t->be->timeout.tarpit))
req->cex = now;
}