Software: Apache/2.2.3 (CentOS). PHP/5.1.6 

uname -a: Linux mx-ll-110-164-51-230.static.3bb.co.th 2.6.18-194.el5PAE #1 SMP Fri Apr 2 15:37:44
EDT 2010 i686 

uid=48(apache) gid=48(apache) groups=48(apache) 

Safe-mode: OFF (not secure)

/usr/libexec/webmin/squid/help/   drwxr-xr-x
Free 50.89 GB of 127.8 GB (39.82%)
                            Encoder    Tools    Proc.    FTP brute    Sec.    SQL    PHP-code    Update    Feedback    Self remove    Logout    

Viewing file:     edit_icp.it.html (1.73 KB)      -rw-r--r--

Directly fetch URLs containing: Defaults to ".cgi" and "?". Allows you to force Squid to always fetch certain content types directly from the origin server. Ordinarily this needs no modification, as most things are handled automatically by Squid without help.

ICP query timeout: Defaults to an 'optimal' value. If you want to override the value determined by Squid, set this to a non-zero value. The default in old versions of Squid was 2000.

Multicast ICP timeout: Defaults to 2000msec or 2 seconds. For Multicast peers, Squid regularly sends out ICP "probes" to count how many other peers are listening on the given multicast address. This value specifies how long Squid should wait to count all the replies.

Dead peer timeout: Defaults to 10 seconds. This controls how long Squid waits to declare a peer cache as "dead." If there are no ICP replies received in this amount of time, Squid will declare the peer dead and not expect to receive any further ICP replies. However, it continues to send ICP queries, and will mark the peer as alive upon receipt of the first subsequent ICP reply.

This timeout also affects when Squid expects to receive ICP replies from peers. If more than 'dead_peer' seconds have passed since the last ICP reply was received, Squid will not expect to receive an ICP reply on the next query. Thus, if your time between requests is greater than this timeout, you will see a lot of requests sent DIRECT to origin servers instead of to your parents.