# OPTIONS WHICH AFFECT THE NEIGHBOR SELECTION ALGORITHM # # Optionen, welche den Algotithmus zur Auswahl der Nachbar-Chaches # beeinflussen #----------------------------------------------------------------------------- # TAG: cache_host # To specify other caches in a hierarchy, use the format: # # hostname type http_port icp_port # # For example, # # # proxy icp # # hostname type port port options # # -------------------- -------- ----- ----- ----------- # cache_host bigserver.usc.edu parent 3128 3130 [proxy-only] # cache_host littleguy1.usc.edu sibling 3128 3130 [proxy-only] # cache_host littleguy1.usc.edu sibling 3128 3130 [proxy-only] # # type: either 'parent', 'sibling', or 'multicast'. # # proxy_port: The port number where the cache listens for proxy # requests. # # icp_port: Used for querying neighbor caches about # objects. To have a non-ICP neighbor # specify '7' for the ICP port and make sure the # neighbor machine has the UDP echo port # enabled in its /etc/inetd.conf file. # # options: proxy-only # weight=n # ttl=n # no-query # default # round-robin # multicast-responder # # use 'proxy-only' to specify that objects fetched # from this cache should not be saved locally. # # use 'weight=n' to specify a weighted parent. # The weight must be an integer. The default weight # is 1, larger weights are favored more. # # use 'ttl=n' to specify a IP multicast TTL to use # when sending an ICP request to this address. # Only useful when sending to a multicast group. # Because we don't accept ICP replies from random # hosts, you must configure other group members as # peers with the 'multicast-responder' option below. # # use 'no-query' to NOT send ICP queries to this # neighbor. # # use 'default' if this is a parent cache which can # be used as a "last-resort." You should probably # only use 'default' in situations where you cannot # use ICP with your parent cache(s). # # use 'round-robin' to define a set of parents which # should be used in a round-robin fashion in the # absence of any ICP queries. # # 'multicast-responder' indicates that the named peer # is a member of a multicast group. ICP queries will # not be sent directly to the peer, but ICP replies # will be accepted from it. # # NOTE: non-ICP neighbors must be specified as 'parent'. # # Eintrag: cache_host # Zur Angabe anderer Caches in einer Hierarchie nutze das # folgende Format: # # hostname type http_port icp_port # # Zum Beispiel # # # proxy icp # # Hostname Typ Port Port Optionen # # -------------------- -------- ----- ----- ----------- # cache_host bigserver.usc.edu parent 3128 3130 [proxy-only] # cache_host littleguy1.usc.edu sibling 3128 3130 [proxy-only] # cache_host littleguy1.usc.edu sibling 3128 3130 [proxy-only] # # type: entweder 'parent', 'sibling' oder 'multicast'. # # proxy_port: Die Portnummer, auf welcher der Cache auf # Proxyanfragen "lauscht". # # icp_port: Wird fuer Anfragen an Nachbarcaches ueber Objekte # benutzt. Um einen nicht-ICP-Nachbarn anzugeben, # benutze '7' als ICP-Port und stelle sicher, dass # bei der Nachbarmaschine der UDP-echo-Port in der # /etc/inetd.conf freigeschaltet ist. # neighbor machine has the UDP echo port # enabled in its /etc/inetd.conf file. # # options: proxy-only # weight=n # ttl=n # no-query # default # round-robin # multicast-responder # # Benutze 'proxy-only' um anzugeben, das Objekte, # welche von diesem Cache kommen, nicht lokal # gespeichert werden sollen. # # Benutze 'weight=n' zur Angabe eine gewichteten # "Eltern"cache. Das Gewicht muss eine Integer-Zahl # sein. Die Vorgabe dafuer ist 1, hoehere Gewichte # werden bevorzugt. # # Benutze 'ttl=n' zur Angabe einer # IP-multicast-TTL(time-ti-live), welche benutzt # wird beim Senden von ICP-Anfragen (Requests) an # diese Adresse. Nur sinnvoll, wenn man an eine # "multicast"-Gruppe sendet. Weil keine # ICP-Anfragen (Replies) von beliebigen Hosts # akzeptiert werden, muessen die anderen Mitglieder # der "multicast"-Gruppe mit der Option # 'multicast-responder' konfiguriert werden. # # Benutze 'no-query' wenn KEINE ICP-Anfragen # (Queries) an diesen Nachbarn geschickt werden # sollen. # # Benutze 'default' wenn dies ein "Eltern"-Cache # ist, welcher als "letzte Reserve" benutzt werden # kann. Du solltest 'default' nur benutzen, wenn du # ICP nicht fuer die "Eltern"-Caches benutzen # kannst. # # Benutze 'round-robin' zum Definieren einer Menge # von "Eltern"-Caches, welche der "Reihe nach um" # (round-robin fashion) bei IPC-Anfragen benutzt # werden. # # 'multicast-responder' zeigt an, das der # entsprechende Rechner Mitglied einer # "multicast"-Gruppe ist. ICP-Anfragen werden nicht # direkt an den Rechner geschickt, aber # ICP-Antworten werden von ihm akzeptiert. # # ACHTUNG: nicht-ICP-Nachbarn muessen als 'parent' angegeben werden. # #cache_host hostname type 3128 3130 # TAG: cache_host_domain # Use to limit the domains for which a neighbor cache will be queried. # Usage: # # cache_host_domain cache-host domain [domain ...] # cache_host_domain cache-host !domain # # For example, specifying # # cache_host_domain bigserver.usc.edu .edu # # has the effect such that UDP query packets are sent to # 'bigserver' only when the requested object exists on a # server in the .edu domain. Prefixing the domainname # with '!' means that the cache will be queried for objects # NOT in that domain. # # NOTE: * Any number of domains may be given for a cache-host, # either on the same or separate lines. # * When multiple domains are given for a particular # cache-host, the first matched domain is applied. # * Cache hosts with no domain restrictions are queried # for all requests. # * There are no defaults. # * There is also a 'cache_host_acl' tag in the ACL # section. # # Eintrag: cache_host_domain # Wird benutzt, um die Domains zu beschraenken, nach welchen die # Nachbar-Caches gefragt werden. # Beispiel: # # cache_host_domain cache-host domain [domain ...] # cache_host_domain cache-host !domain # # Die folgende Angabe: # # cache_host_domain bigserver.usc.edu .edu # # hat den Effekt, das eine UDP-Anfragepacket nur dann zu # 'bigserver' gesendet wird, wenn das nachgefraget auf einem # Server innerhalb der Domain .edu liegt. Das voranstellen von # '!' vor einen Domainnamen bedeutet, dass der Cache nur fuer # Objekte gefragt wird, die NICHT in der Domain liegen. # # ACHTUNG: * Eine beliebige Anzahl von Domains kann fuer # einen Cachehost angegebn werden, entweder auf einer # Zeile, aber auch in mehreren. # * Wenn mehrere Domians fuer einen bestimmten Cachehost # angegeben sind, dann wird die erste zutreffende # Regel benutzt. # * Cachehosts ohne Domianeinschraenkung werden zu allen # Anfragen herangezogen. # * Es gibt keinen Defaultwert. # * Es gibt ausserdem den Eintrag 'cache_host_acl' in # der ACL-Sektion (dort aslo mal hinschauen). # TAG: neighbor_type_domain # # usage: neighbor_type_domain parent|sibling domain domain ... # # Modifying the neighbor type for specific domains is now # possible. You can treat some domains differently than the the # default neighbor type specified on the 'cache_host' line. # Normally it should only be necessary to list domains which # should be treated differently because the default neighbor type # applies for hostnames which do not match domains listed here. # #EXAMPLE: # cache_host parent cache.foo.org 3128 3130 # neighbor_type_domain cache.foo.org sibling .com .net # neighbor_type_domain cache.foo.org sibling .au .de # TAG: inside_firewall # This tag specifies a list of domains inside your Internet # firewall. # # Usage: inside_firewall my.domain [ my.other.domain ...] # # The use of this tag affects the server selection algorithm in # two ways. Objects which do not match any of the listed domains # will be considered "beyond the firewall." For these: # - There will be no DNS lookups for the URL-host. # - The object will always be fetched from one of # the parent or neighbor caches. # # As a special case you may specify the domain as 'none' to force # all requests to be fetched from neghbors and parents. # #inside_firewall topsecret.com # TAG: local_domain # This tag specifies a list of domains local to your organization. # # Usage: local_domain my.domain [ my.other.domain ...] # # For URLs which are in one of the local domains, the object # is always fetched directly from the source and never from a # neighbor or parent. # #local_domain bigbucks.com # TAG: local_ip # This tag specifies a list of network addresses local to your # organization. # # Usage: local_ip ip-address # # This tag is similar to local_domain, except that the IP-address # of the URL-host is checked. This requires that a DNS lookup # be done on the URL-host. For this reason, local_domain is # preferred over local_ip. By using local_domain it may be # possible to avoid the DNS lookup altogether and deliver the # object with less delay. # #local_ip 10.0.0.0 #local_ip 172.16.0.0 # TAG: firewall_ip # # Just like 'inside_firewall' but for IP addresses. NOTE: # firewall_ip and local_ip are mutually exclusive. If you # use firewall_ip then local_ip will be ignored. # #firewall_ip 10.0.0.0 #firewall_ip 172.16.0.0 # TAG: single_parent_bypass # This tag specifies that it is okay to bypass the hierarchy # "Pinging" when there is only a single parent for a given URL. # # Usage: single_parent_bypass on|off # # Before actually sending ICP "ping" packets to parents and # neighbors, we figure out which hosts would be pinged based # on the cache_host_domain rules, etc. Often it may be the # case that only a single parent cache would be pinged. # # Since there is only a single parent, there is a very good # chance that we will end up fetching the object from that # parent. For this reason, it may be beneficial to avoid # the ping and just fetch the object anyway. # # However, if we avoid the ping, we will be assuming that the # parent host is reachable and that the cache process is running. # By using the ping, we can be reasonably sure that the parent # host will be able to handle our request. If the ping fails then # it may be possible to fetch the object directly from the source. # # To favor the resiliency provided by the ping algorithm, # single_parent_bypass is 'off' by default. # #single_parent_bypass off # TAG: source_ping # If source_ping is enabled, then squid will include the source # provider site in its selection algorithm. This is accomplished # by sending ICP "HIT" packets to the UDP echo port of the source # host. Note that using source_ping may send a fair amount of UDP # traffic out on the Internet and may irritate paranoid network # administrators. # # Note that source_ping is incompatible with inside_firewall. # For hosts beyond the firewall, source_ping packets will never # be sent. # # By default, source_ping is off. # #source_ping off # TAG: neighbor_timeout (seconds) # This controls how long to wait for replies from neighbor caches. # If none of the parent or neighbor caches reply before this many # seconds (due to dropped packets or slow links), then the object # request will be satisfied from the default source. The default # timeout is two seconds. # #neighbor_timeout 2 # TAG: hierarchy_stoplist # A list of words which, if found in a URL, cause the object to # be handled directly by this cache. In other words, use this # to not query neighbor caches for certain objects. You may # list this option multiple times. # # The default is to directly fetch URLs containing 'cgi-bin' or '?'. # hierarchy_stoplist cgi-bin ? # TAG: cache_stoplist # A list of words which, if found in a URL, cause the object to # immediately removed from the cache. In other words, use this # to force certain objects to never be cached. You may list this # option multiple times. # # The default is to not cache URLs containing 'cgi-bin' or '?'. # cache_stoplist cgi-bin ? # TAG: cache_stoplist_pattern # case sensitive # TAG: cache_stoplist_pattern/i # case insensitive # # Just like 'cache_stoplist' but you can use regular expressions # instead of simple string matching. There is no default. # #cache_stoplist_pattern