---------------------
PatchSet 10482 
Date: 2008/04/01 12:22:02
Author: adri
Branch: s2_delaywork
Tag: (none) 
Log:

Fiddle the description to match the code.

Members: 
	src/cf.data.pre:1.240.2.3->1.240.2.4 

Index: squid/src/cf.data.pre
===================================================================
RCS file: /cvsroot/squid-sf//squid/src/cf.data.pre,v
retrieving revision 1.240.2.3
retrieving revision 1.240.2.4
diff -u -r1.240.2.3 -r1.240.2.4
--- squid/src/cf.data.pre	30 Mar 2008 13:49:01 -0000	1.240.2.3
+++ squid/src/cf.data.pre	1 Apr 2008 12:22:02 -0000	1.240.2.4
@@ -1,6 +1,6 @@
 
 #
-# $Id: cf.data.pre,v 1.240.2.3 2008/03/30 13:49:01 adri Exp $
+# $Id: cf.data.pre,v 1.240.2.4 2008/04/01 12:22:02 adri Exp $
 #
 # SQUID Web Proxy Cache          http://www.squid-cache.org/
 # ----------------------------------------------------------
@@ -927,16 +927,10 @@
         high speed. When the delay headers are received, the reply_body_max_size
         lines are processed, and the first line with a result of "allow" is used
         as the maximum body size for this reply to be unassigned in delay_pool.
-        This size is checked twice. First when we get the reply headers,
-        we check the content-length value.  If the content length value exists
-        and is larger than the allowed size, the request is denied and the
-        user receives an error message that says "the request or reply
-        is too large." If there is no content-length, and the reply
-        size exceeds this limit, the client's connection is just inserted into
-        the delay_pool.
+	The client connection is inserted into the delay pool once the amount
+	of data sent to the client exceeds the value specified.
 
-        If you set this parameter to zero (the default), there will be
-        no limit imposed.
+	There will be no limit imposed by a rule if the "bytes" value is set to 0.
 DOC_END