Network Configurations

Bind To IP: used to specify the socket addresses where Behalf will listen for HTTP client requests. Multiple socket addresses can be specified. If IP address are specified, then Behalf binds the socket to that specific address.
In the event that Behalf has been installed on the same box as your router, internet surfers can be able to connect to Behalf. Security issues will arise, so please bind Behalf to your local network address/subnet.
Http Port: Port on which Behalf will listen to and accept requests.
Icp: Specifies the port number from which Behalf sends and receives ICP queries to and from neighbor caches. To disable "0" is used. ICP is a protocol used for communication among Behalf caches. ICP is primarily used within a cache hierarchy to locate specific objects in sibling caches. If a Behalf cache does not have a requested document, it sends an ICP query to its siblings, and the siblings respond with ICP replies indicating a "HIT" or a "MISS". The cache then uses the replies to choose from which cache to resolve its own MISS.
Ftp User: This tag can be used if you want the anonymous login password to be more informative. You can set this to something reasonable for your domain, like Behalf@behalf@baraka.ca. The reason why this is domainless by default is that the request can be made on the behalf of a user in any domain, depending on how the cache is used.
Ftp Passive: If your firewall does not allow Behalf to use passive connections, then turn off this option.

Cache Configuration

Default Cache_mem: specifies the ideal amount of memory to be used for :

• In-Transit objects

• Hot Objects

• Negative-Cached objects l

This parameter specifies the ideal upper limit on the total size of 4 KB blocks allocated. In-Transit objects take the highest priority. In-transit objects have priority over the others. When additional space is needed for incoming data, negative-cached and hot objects will be released. In other words, the negative-cached and hot objects will fill up any unused space not needed for in-transit objects. If circumstances require, this limit will be exceeded. Specifically, if your incoming request rate requires more than 'cache_mem' of memory to hold in-transit objects, Behalf will exceed this limit to satisfy the new requests. When the load decreases, blocks will be freed until the high-water mark is reached. Thereafter, blocks will be used to store hot objects.

Caution : This parameter does not specify the maximum process size. It places a limit on one aspect of Behalf's memory usage. Behalf uses memory for other things as well. Process will probably become twice or three times bigger than the value put here.
Minimum Object Size: Objects smaller than this size will NOT be saved on disk. The value is specified in kilobytes, and the default is 0 KB, which means there is no minimum.
Maximum Object Size: Objects larger than this size will NOT be saved on disk. The value is specified in kilobytes, and the default is 4MB. If you wish to get a high BYTES hit ratio, you should probably increase this (one 32 MB object hit counts for 3200 10KB hits). If you wish to increase speed more than you want to save bandwidth you should leave this low.
Maximum Object Size in Mem: Objects greater than this size will not be attempted to be kept in the memory cache. This should be set high enough to keep objects accessed frequently in memory to improve performance whilst low enough to keep larger objects from hoarding cache_mem.
Cache Manager: Using this tag we can specify the email-address of the local cache manager who will receive mail if the cache dies. The default is "webmaster". In case Behalf dies the mail will be sent to the given mail id.
Cache Size: the amount of disk space (MB) to use.
Dir Level1: is the number of first-level subdirectories, which will be created.
Dir Level2: is the number of second-level subdirectories, which will be created under each first-level directory.

Time Outs

Connection Timeout: The time duration until which Behalf waits for the reply from the origin server. If it exceeds this Behalf will respond with the error message "Connection timed out" to the client.
Request Timeout: specifies Behalf the time in seconds to wait for an HTTP request after connection establishment. For persistent connections, Behalf will wait this long after the previous request completes.
Client Lifetime: 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.
Dns Timeout: used to set the DNS Query time-out. If no response is received to a DNS query within this time then all DNS servers for the queried domain is assumed to be unavailable.

ICMP

Netdb Low: The low and high water marks for the ICMP measurement database. These are counts, not percents. The defaults are 900 and1000. When the high water mark is reached, database entries will be deleted until the low mark is reached.
Netdb high: read Netdb Low
Netdb Ping Period: The minimum period for measuring a site. There will be at least this much delay between successive pings to the same network
Query Icmp: If you want to ask your peers to include ICMP data in their ICP replies, enable this option. If you enable this option then the ICP replies from that peer will include the ICMP data (if available). Then, when choosing a parent cache, Behalf will choose the parent with the minimal RTT to the origin server.