Squid_ The Definitive Guide - Duane Wessels [208]
Example
digest_rebuild_chunk_percentage 3
Related
digest_generation, digest_rebuild_period, store_objects_per_bucket
Name
chroot
Synopsis
When you specify a value for this directive, Squid passes it to the chroot( ) system call. This provides an extra level of security by isolating the Squid process(es) from the rest of your filesystem. See Section 5.7 for more information.
Syntax
chroot pathname
Default
No default
Example
chroot /squid
Name
client_persistent_connections
Synopsis
This directive controls whether or not Squid uses persistent HTTP connections to cache clients. When disabled, Squid sends Connection: close headers in its responses to clients. If you suspect problems caused by client-side persistent connections, disable this directive.
Syntax
client_persistent_connections on|off
Default
client_persistent_connections on
Example
client_persistent_connections off
Related
server_persistent_connections, pipeline_prefetch
Name
server_persistent_connections
Synopsis
This directive controls whether or not Squid uses persistent HTTP connections to origin servers and neighbors. When disabled, Squid sends Connection: close headers in forwarded requests. If you suspect problems caused by server-side persistent connections, disable this directive.
Syntax
server_persistent_connections on|off
Default
server_persistent_connections on
Example
server_persistent_connections off
Related
client_persistent_connections
Name
pipeline_prefetch
Synopsis
This directive controls whether or not Squid prefetches pipelined requests. It is disabled by default, so Squid acts only on one request at a time (per connection). If you enable this directive, Squid processes up to two client requests at once.
Note that the order of responses must match the order of requests. Thus, if the prefetched (second) request completes before the first, it is delayed until the first response is sent.
Squid doesn't implement pipelining on the server-side. It always opens a new connection to an origin server (or neighbor) if there are no idle persistent connections.
Syntax
pipeline_prefetch on|off
Default
pipeline_prefetch off
Example
pipeline_prefetch on
Related
client_persistent_connections
Name
extension_methods
Synopsis
HTTP (RFC 2616) allows clients and servers to use their own extension methods. If requests with nonstandard HTTP methods go through Squid, the client receives an "Invalid Request" error message. Squid also writes a cache.log entry, such as this:
2003/09/29 13:40:24| parseHttpRequest: Unsupported method 'XGET'
If you want Squid to accept such requests, you must tell it about the nonstandard methods by listing them after the extension_methods directive.
Syntax
extension_methods HTTP-method ...
Default
No default
Example
extension_methods XGET XPOST
Name
request_entities
Synopsis
This directive determines how Squid handles GET and HEAD requests that have message bodies (entities). Such requests normally don't contain bodies. There is some confusion about whether or not RFC 2616 allows entities in GET/HEAD requests. Squid denies such requests by default. If you would rather have Squid accept them, enable the request_entities directive.
Syntax
request_entities on|off
Default
request_entities off
Example
request_entities on
Name
high_response_time_warning
Synopsis
If you provide a non-zero value for this directive, Squid periodically checks the client-side median response time. If it's above this threshold, Squid prints a warning message in cache.log. The value is given in milliseconds.
Syntax
high_response_time_warning milliseconds
Default
high_response_time_warning 0
Example
high_response_time_warning 2000
Related
high_page_fault_warning, high_memory_warning
Name
high_page_fault_warning
Synopsis
If you provide a nonzero value for this directive, Squid periodically checks the process page fault rate. Page faults generally occur when the Squid process doesn't