Options
|
Functions
|
proxy-only
|
to specify that objects fetched from this cache should not be saved locally.
|
weight=n
|
to specify a weighted parent. The weight must be an integer. The default weight is 1, larger weights are favored more.
|
basetime=n
|
to specify a base amount to be subtracted from round trip times of parents. It is subtracted before division by weight in calculating which parent to fetch from. If the rtt is less than the base time then the rtt is set to a minimal value.
|
ttl=n
|
to specify a IP multicast TTL to use when sending an ICP queries 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.
|
no-query
|
NOT to send ICP queries to this neighbor.
|
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).
|
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 willnot be sent directly to the peer, but ICP replies will be accepted from it.
|
closest-only
|
indicates that, for ICP_OP_MISS replies, we'll only forward CLOSEST_PARENT_MISSes and never FIRST_PARENT_MISSes.
|
no-digest
|
NOT to request cache digests from this neighbor.
|
no-netdb-exchange
|
disables requesting ICMP RTT database (NetDB) from the neighbor.
|
no-delay
|
to prevent access to this neighbor from influencing the delay pools.
|
login=user:password
|
if this is a personal/workgroup proxy and your parent requires proxy authentication. The string can include URL escapes (i.e. %20 for spaces). This also means that % must be written as %%.
|
login=PASS
|
if users must authenticate against the upstream proxy. This will pass the users credentials as they are to the peer proxy. This only works for the Basic HTTP authentication scheme. To combine this with proxy_auth both proxies must share the same user database as HTTP only allows for one proxy login. Also be warned that this will expose your users proxy password to the peer. USE WITH CAUTION
|
login=*:password
|
to pass the username to the upstream cache, but with a fixed password. This is meant to be used when the peer is in another administrative domain, but it is still needed to identify each user. The star can optionally be followed by some extra information which is added to the username. This can be used to identify this proxy to the peer, similar to the login=username:password option above.
|
connect-timeout=nn
|
to specify a peer specific connect timeout (also see the peer_connect_timeout directive)
|
digest-url=url
|
to tell Squid to fetch the cache digest (if digests are enabled) for this host from the specified URL rather than the Squid default location.
|
allow-miss
|
to disable Squid's use of only-if-cached when forwarding requests to siblings. This is primarily useful when icp_hit_stale is used by the sibling. To extensive use of this option may result in forwardingloops, and you should avoid having two-way peerings with this option. (for Example(s) to deny peer usage on requests from peer by denying cache_peer_access if the source is a peer)
|
max-conn
|
to limit the amount of connections Squid may open to this peer.
|
htcp
|
to send HTCP, instead of ICP, queries to the neighbor. You probably also want to set the "icp port" to 4827 instead of 3130.
|
htcp-oldsquid
|
to send HTCP to old Squid versions
|
carp-load-factor
|
to define a parent cache as one participating in a CARP array.
|
originserver
|
causes this parent peer to be contacted as a origin server. Meant to be used in accelerator setups.
|
userhash
|
to load-balance amongst a set of parents based on the client proxy_auth or ident username.
|
sourcehash
|
to load-balanse amongs a set of parents based on the client source ip.
|
name=xxx
|
if you have multiple peers on the same host but different ports. This name can then be used to differentiate the peers in cache_peer_access and similar directives.
|
monitorurl=url
|
to have periodically request a given URL from the peer, and only consider the peer as alive if this monitoring is successful
|
monitorsize=sizespec
|
to limit the size range of 'monitorurl' replies considered valid.
|
monitorinterval=seconds
|
to change frequency of how often the peer is monitored with 'monitorurl'
|
monitortimeout=seconds
|
to change the timeout of 'monitorurl'. Defaults to 'monitorinterval'.
|
group=name
|
Group Name of the peer-cache
|
forceddomain=name
|
to forcibly set the Host header of requests forwarded to this peer. Useful in accelerator setups where the server (peer) expects a certain domain name and using redirectors to feed this domainname is not feasible.
|
ssl
|
to indicate that connections to this peer should bs SSL/TLS encrypted.
|
sslcert= /path/to/ssl/certificate
|
to specify a client SSL certificate to use when connecting to this peer.
|
sslkey= /path/to/ssl/key
|
to specify the private SSL key corresponding to sslcert above. If 'sslkey' is not specified then 'sslcert' is assumed to reference a combined file containing both the certificate and the key.
|
sslversion=1|2|3|4
|
to specify the SSL version to use when connecting to this peer 1 = automatic (default) 2 = SSL v2 only 3 = SSL v3 only 4 = TLS v1 only
|
sslcipher=...
|
to specify the list of valid SSL chipers to use when connecting to this peer
|
ssloptions=...
|
to specify various SSL engine options NO_SSLv2 Disallow the use of SSLv2 NO_SSLv3 Disallow the use of SSLv3 NO_TLSv1 Disallow the use of TLSv1
|
front-end-https
|
to enable the "Front-End-Https: On" header needed when using Squid as a SSL frontend infront of Microsoft OWA. See MS KB document Q307347 for details on this header. If set to auto then the header will only be added if the request is forwarded as a https://URL.
|
connection-auth[=on|off|auto]
|
to tell Squid that this peer does not support Microsoft connection oriented authentication, and any such challenges received from there should be ignored.
|