It would have been better if the squid manipulated its receiver window
to manage the downloading rate.
This is in effect what happens, but it has to fill up first.
If you look at a packet trace of a delayed response via Squid you will see
1. Starts out at the default window size (OS controlled)
2.
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 ref
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
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
#
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
#
