Re: [squid-users] REQUEST: Turn "reply_body_max_size" into ACL - Please!!

The problem with doing this in a "simple" way is that the ACL must be tested
on every network read()/write() (choose one) for the object - because not
all objects have a size. (ie dynamic objects, transfer encoded objects both
don't).

As an ACL, the generic http_reply acl handling code will handle the test -
but calling that code for every network transfer will incur a large
overhead. So this means we need two sorts of acls for replies - ones that
are checked once, and ones checked continually. OR we need to ignore
transfer encoded and dynamic objects with the ACL - which means it's
coverage will be less than coplete.

Also: What about partial object transfers - how should they be handled?

Rob

----- Original Message -----
From: "Mads Rasmussen" <mads@cit.com.br>
To: <squid-users@squid-cache.org>
Sent: Tuesday, July 24, 2001 10:58 PM
Subject: [squid-users] REQUEST: Turn "reply_body_max_size" into ACL -
Please!!

Is it possible in the new version of squid to change this global setting of
max download to an ACL.

I (and I am sure many others) need the ability to generate exceptions. E.g.
some users must be able to download with no limits, some users may have
another limit and some users may not download at all.

Maybe this is already done in the 2.5 version

Anyone knows ste status?

Regards,

Mads
Received on Tue Jul 24 2001 - 07:06:20 MDT