From 8ed8fda3ced328bd67f40710552ae841be3cf53b Mon Sep 17 00:00:00 2001
From: serassio <>
Date: Thu, 10 Mar 2005 03:14:37 +0000
Subject: [PATCH] Bug #1245: Clarify delay_access function

Forward port of 2.5 patch.
---
 src/cf.data.pre | 13 ++++++++-----
 1 file changed, 8 insertions(+), 5 deletions(-)

diff --git a/src/cf.data.pre b/src/cf.data.pre
index 2e9d79111e..bff4a2fe18 100644
--- a/src/cf.data.pre
+++ b/src/cf.data.pre
@@ -1,6 +1,6 @@
 
 #
-# $Id: cf.data.pre,v 1.379 2005/03/06 21:08:13 serassio Exp $
+# $Id: cf.data.pre,v 1.380 2005/03/09 20:14:37 serassio Exp $
 #
 #
 # SQUID Web Proxy Cache          http://www.squid-cache.org/
@@ -3990,10 +3990,13 @@ IFDEF: DELAY_POOLS
 LOC: Config.Delay
 DOC_START
 	This is used to determine which delay pool a request falls into.
-	The first matched delay pool is always used, i.e., if a request falls
-	into delay pool number one, no more delay are checked, otherwise the
-	rest are checked in order of their delay pool number until they have
-	all been checked.  For example, if you want some_big_clients in delay
+
+	delay_access is sorted per pool and the matching starts with pool 1,
+	then pool 2, ..., and finally pool N. The first delay pool where the
+	request is allowed is selected for the request. If it does not allow
+	the request to any pool then the request is not delayed (default).
+
+	For example, if you want some_big_clients in delay
 	pool 1 and lotsa_little_clients in delay pool 2:
 
 Example:
-- 
2.47.2