Re: [squid-users] reply_body_max_size + delay_pools

On Tue, Jul 8, 2008 at 3:36 PM, Chris Robertson <crobertson_at_gci.net> wrote:
[cut]
> Just use delay pools, and set the initial bucket size to the max object size
> you don't want to limit. This will have the added benefit of preventing
> someone from circumventing your reply_body_max_size slowdown by grabbing
> lots of little bits of a large file.
>
> delay pools 1
> delay_class 1 2
> delay_access 1 allow all
> delay_parameters 1 -1/-1 1048576/32000 # The first MByte of non-cached
> traffic is delay free, and the bucket refills at 256kbps.

Cool, thanks.

My rules are per user, like this (one of them):

acl test src x.y.z.k
http_access allow test
delay_class 1414 1
delay_parameters 1414 16000/16000
delay_access 1414 allow test
delay_access 1414 deny all

I only add/change an other delay_parameters:

delay_parameters 1414 16000/16000
delay_parameters 1414 1048576/8000

Normal traffic (not cached) is 128kbps limit, objects > 10MB 64kbps.

Its working, I tested!

My question is: this structure is right? (per dst.)
Received on Thu Jul 10 2008 - 19:05:56 MDT