Squid configuration directive client_delay_access
History:
- Changes in 3.2 client_delay_access
-
New setting for client bandwidth limits to determines the client-side delay pool for the request.
Configuration Details:
Option Name: | client_delay_access |
---|---|
Replaces: | |
Requires: | --enable-delay-pools |
Default Value: | none |
Suggested Config: |
|
This option determines the client-side delay pool for the request: client_delay_access pool_ID allow|deny acl_name All client_delay_access options are checked in their pool ID order, starting with pool 1. The first checked pool with allowed request is selected for the request. If no ACL matches or there are no client_delay_access options, the request bandwidth is not limited. The ACL-selected pool is then used to find the client_delay_parameters for the request. Client-side pools are not used to aggregate clients. Clients are always aggregated based on their source IP addresses (one bucket per source IP). Please see delay_access for more examples. Example: client_delay_access 1 allow low_rate_network client_delay_access 2 allow vips_network |
|
Search
Introduction
- About Squid
- Why Squid?
- Squid Developers
- How to Help Out or Donate
- Getting Squid
- Squid Source Packages
- Squid Deployment Case-Studies
- Squid Software Foundation
Documentation
- Configuration:
- FAQ and Wiki
- Guide Books:
- Non-English
- More...
Support
- Security Advisories
- Bugzilla Database
- Mailing lists
- Contacting us
- Commercial services
- Project Sponsors
- Squid-based products
Miscellaneous
- Developer Resources
- Related Writings
- Related Software:
- Squid Artwork