Configuration Manual
| Squid
2.4 Stable1 Configuration Manual |
|
|
| Previous |
Tag Name |
connect_timeout |
|
Usage |
connect_timeout seconds |
|
Description |
||
The time duration until which squid waits for the reply from the origin server. If it exceeds this squid will respond with the error message “Connection timed out” to the client |
||
Default |
connect_timeout 120 seconds |
|
Example connect_timeout 180 seconds |
||
Caution Increasing the time here will lead to annoying of browser user |
||
Tag Name |
peer_connect_timeout |
|
Usage |
peer_connect_timeout time-units |
|
Description |
||
This parameter specifies how long to wait for a pending TCP connection to a peer cache. The default is 30 seconds. You may also set different timeout values for individual neighbors with the 'connect-timeout' option on a 'cache_peer' line |
||
Default |
peer_connect_timeout 30 seconds |
|
Example peer_connect_timeout 45 seconds |
||
Caution Setting of peer_connect_timeout to more than 30 seconds will be a performance issue. |
||
Tag Name |
siteselect_timeout |
|
Usage |
siteselect_timeout time-units |
|
Description |
||
For URN to multiple URL's URL selection |
||
Default |
siteselect_timeout 4 seconds |
|
Example |
siteselect_timeout 6 seconds |
|
Caution |
- |
|
Tag Name |
read_timeout |
|
Usage |
read_timeout time-units |
|
Description |
||
The read_timeout is applied on server-side connections. After each successful read(), the timeout will be extended by this amount. If no data is read again after this amount of time, the request is aborted and logged with ERR_READ_TIMEOUT. The default is 15 minutes |
||
Default |
read_timeout 15 minutes |
|
Example |
read_timeout 10 minutes |
|
Caution |
- |
|
Tag Name |
request_timeout |
|
Usage |
request_timeout seconds |
|
Description |
||
This tag specifies Squid the time in seconds to wait for an HTTP request after connection establishment. For persistent connections, Squid will wait this long after the previous request completes |
||
Default |
request_timeout 30 seconds |
|
Example |
request_timeout 20 seconds |
|
Caution |
- |
|
Tag Name |
client_lifetime |
|
Usage |
client_lifetime time-units |
|
Description |
||
The maximum amount of time that a client (browser) is allowed to remain connected to the cache process. This protects the Cache from having a lot of sockets (and hence file descriptors) tied up in a CLOSE_WAIT state from remote clients that go away without properly shutting down (either because of a network failure or because of a poor client implementation). The default is one day, 1440 minutes |
||
Default |
client_lifetime 1 day |
|
Example |
client_lifetime 1000 minutes |
|
Caution The default value is intended to be much larger than any client would ever need to be connected to your cache. You should probably change client_lifetime only as a last resort. If you seem to have many client connections tying up filedescriptors, we recommend first tuning the read_timeout, request_timeout, pconn_timeout and quick_abort values. If the more filedescriptors are in use then the memory in use will also increase, which is also a performance issue |
||
Tag Name |
half_closed_clients |
|
Usage |
half_closed_clients on|off |
|
Description |
||
Some clients may shutdown the sending side of their TCP connections, while leaving their receiving sides open. Sometimes, Squid cannot tell the difference between a half-closed and a fully-closed TCP connection. By default, half-closed client connections are kept open until a read(2) or write(2) on the socket returns an error. Change this option to 'off' and Squid will immediately close client connections when read (2) returns "no more data to read |
||
Default |
half_closed_clients on |
|
Example |
half_closed_clients off |
|
Caution |
- |
|
Tag Name |
pconn_timeout |
|
Usage |
pconn_timeout seconds |
|
Description |
||
This tag specifies the timeout for idle persistent connections to servers and other proxies |
||
Default |
pconn_timeout 120 seconds |
|
Example |
pconn_timeout 60 seconds |
|
Caution |
- |
|
Tag Name |
ident_timeout |
|
Usage |
ident_timeout seconds |
|
Description |
||
Maximum time to wait for IDENT requests. If this is too high, and you enabled 'ident_lookup', then you might be susceptible to denial-of-service by having many ident requests going at once. Only src type ACL checks are fully supported. An src_domain ACL might work at times, but it will not always provide the correct result. This option may be disabled by using --disable-ident with the configure script |
||
Default |
ident_timeout 10 seconds |
|
Example |
ident_timeout 5 seconds |
|
Caution |
- |
|
Tag Name |
shutdown_lifetime |
|
Usage |
shutdown_lifetime time-units |
|
Description |
||
When SIGTERM or SIGHUP is received, the cache is put into "shutdown pending" mode until all active sockets are closed. This value is the lifetime to set for all open descriptors during shutdown mode. Any active clients after this many seconds will receive a 'timeout' message |
||
Default |
shutdown_lifetime 30 seconds |
|
Example |
shutdown_lifetime 45 seconds |
|
Caution If this timeis set to be too low then some file descriptors may remain open which will be an performance issue in memory usage |
||