Re: [squid-users] doubt regarding delay_access

2005-02-20 Thread Henrik Nordstrom
On Mon, 14 Feb 2005, Dinil Divakaran wrote:
delay_access 2 allow allowed_hosts
delay_access 1 allow localhost
delay_access 1 allow all
delay_access is sorted per pool, always starting with pool 1, then pool 2 
etc... so the above configuration is equivalent to

  delay_access 1 allow localhost
  delay_access 1 allow all
  delay_access 2 allow allowed_hosts
so with the above configuration all requests will go into pool 1.
Regards
Henrik



Re: [squid-users] doubt regarding delay_access

2005-02-20 Thread Dinil Divakaran


delay_access 2 allow allowed_hosts
delay_access 1 allow localhost
delay_access 1 allow all
delay_access is sorted per pool, always starting with pool 1, then pool 2 
etc... so the above configuration is equivalent to

 delay_access 1 allow localhost
 delay_access 1 allow all
 delay_access 2 allow allowed_hosts
so with the above configuration all requests will go into pool 1.
Thanks Henrik.
This solved the confusion. Perhaps this explanation should be added 
to the squid.conf file to make it clearer.

One more doubt - how does squid manage the downloading rate from
any web server to the squid; is it just by introducing a delay in
the application level while receiving data ?


Re: [squid-users] doubt regarding delay_access

2005-02-20 Thread Henrik Nordstrom
On Sun, 20 Feb 2005, Dinil Divakaran wrote:
One more doubt - how does squid manage the downloading rate from
any web server to the squid; is it just by introducing a delay in
the application level while receiving data ?
When the delay pool is empty Squid simply stops reading data from the 
server until the pool has been refilled by the refill rate.

Regards
Henrik


Re: [squid-users] doubt regarding delay_access

2005-02-20 Thread Henrik Nordstrom
On Sun, 20 Feb 2005, Dinil Divakaran wrote:
This solved the confusion. Perhaps this explanation should be added to the 
squid.conf file to make it clearer.
Please file a bug report on it, preferably with a suggestion on wording 
(optimally as a patch to cf.data.pre)

Regards
Henrik


[squid-users] doubt regarding delay_access

2005-02-19 Thread Dinil Divakaran
Hello,
In the squid.conf file, it is said that,
#  TAG: delay_access
#   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.
Now, given below is the squid.conf file that I use:
---
acl all src 0.0.0.0/0.0.0.0
acl allowed_hosts src 10.6.21.3/255.255.255.255
acl localhost src 127.0.0.1/255.255.255.255
delay_pools 2
delay_class 1 1
delay_class 2 1
delay_parameters 1 -1/-1 -1/-1
delay_parameters 2 8000/8000 8000/8000
delay_access 2 allow allowed_hosts
delay_access 1 allow localhost
delay_access 1 allow all
---
But, when I tested with this configuration, it was found that the machine with
IP 10.6.21.3 was able to download at a very high rate, indicating that it is
in class 1 delay pool (which contradicts the description for delay_access given
above.)
When I changed the delay_access lines as shown below, the machine 10.6.21.3 was
indeed restricted to rate around 8000 bytes per second.
--
delay_access 2 allow allowed_hosts
delay_access 2 deny all # new line added to the old config. above.
delay_access 1 allow localhost
delay_access 1 allow all
--
Is this confusion due to my misinterpretation or something to do with the 
explanation in the squid.conf file ?

Please advise.
Thanks and Regards,
Dinil


[squid-users] doubt regarding delay_access

2005-02-14 Thread Dinil Divakaran
Hello
In the squid.conf file, it is said that,
#  TAG: delay_access
#   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.
Now, given below is the squid.conf file that I use:
---
acl all src 0.0.0.0/0.0.0.0
acl allowed_hosts src 10.6.21.3/255.255.255.255
acl localhost src 127.0.0.1/255.255.255.255
delay_pools 2
delay_class 1 1
delay_class 2 1
delay_parameters 1 -1/-1 -1/-1
delay_parameters 2 8000/8000 8000/8000
delay_access 2 allow allowed_hosts
delay_access 1 allow localhost
delay_access 1 allow all
---
But, when I tested with this configuration, it was found that the machine with
IP 10.6.21.3 was able to download at a very high rate, indicating that it is
in class 1 delay pool (which contradicts the description for delay_access given
above.)
When I changed the delay_access lines as shown below, the machine 10.6.21.3 was
indeed restricted to rate around 8000 bytes per second.
--
delay_access 2 allow allowed_hosts
delay_access 2 deny all # new line added to the old config. above.
delay_access 1 allow localhost
delay_access 1 allow all
--
Is this confusion due to my misinterpretation or something to do with the 
explanation in the squid.conf file ?

Please advise.
Thanks and Regards,
Dinil