Squid_ The Definitive Guide - Duane Wessels [206]
Name
mcast_miss_addr
Synopsis
The multicast miss stream is a largely undocumented and unsupported Squid feature. The basic idea is to send a multicast message, containing a URI, for each cache miss. The messages are encrypted with a modest algorithm to prevent casual eavesdropping.
To use this feature, you must manually define the MULTICAST_MISS_STREAM preprocessor symbol before compiling Squid. To learn more about this feature, read the source code surrounded by #if MULTICAST_MISS_STREAM in src/access_log.c.
Syntax
mcast_miss_addr multicast-address
Default
No default
Example
mcast_miss_addr 224.0.1.1
Related
mcast_miss_ttl, mcast_miss_port, mcast_miss_encode_key
Name
mcast_miss_ttl
Synopsis
This is the multicast TTL assigned to outgoing miss stream messages. See the discussion of multicast TTLs in Section 10.6.3.2.
Syntax
mcast_miss_ttl N
Default
mcast_miss_ttl 16
Example
mcast_miss_ttl 32
Related
mcast_miss_addr, mcast_miss_port, mcast_miss_encode_key
Name
mcast_miss_port
Synopsis
This is the UDP port number to which multicast miss stream messages are sent.
Syntax
mcast_miss_port port-number
Default
mcast_miss_port 3135
Example
mcast_miss_port 999
Related
mcast_miss_addr, mcast_miss_ttl, mcast_miss_encode_key
Name
mcast_miss_encode_key
Synopsis
Squid uses the Tiny Encryption Algorithm (TEA) to encrypt multicast miss messages. This directive specifies the encryption key, which should be 128 bits long.
Syntax
mcast_miss_encode_key string
Default
mcast_miss_encode_key XXXXXXXXXXXXXXXX
Example
mcast_miss_encode_key MySekRitPassWord
Related
mcast_miss_addr, mcast_miss_ttl, mcast_miss_port
Name
nonhierarchical_direct
Synopsis
A hierarchical request is one that looks like it might result in a cachable response, and therefore might be cached by one of Squid's neighbors. If your Squid doesn't have any neighbors, you don't need to worry about this directive.
By default, Squid prefers to skip the neighbor selection step for nonhierarchical requests (uncachable responses) because the request probably won't result in a cache hit. You can reverse this behavior by disabling the nonhierarchical_direct directive. See Section 10.10.
Syntax
nonhierarchical_direct on|off
Default
nonhierarchical_direct on
Example
nonhierarchical_direct off
Related
prefer_direct, never_direct, always_direct
Name
prefer_direct
Synopsis
This directive affects Squid's neighbor selection algorithm for hierarchical requests (cachable responses). It is only relevant if you have one or more neighbor caches. When Squid builds a list of next-hop locations for cache misses, it puts neighbor caches before the origin server by default. If you would rather have Squid put the origin server before neighbors, enable the prefer_direct directive. See Section 10.10.
Syntax
prefer_direct on|off
Default
prefer_direct off
Example
prefer_direct on
Related
nonhierarchical_direct, never_direct, always_direct
Name
strip_query_terms
Synopsis
When this directive is enabled, Squid doesn't log URI query terms in access.log. This feature is intended to give your users some privacy. It is enabled by default.
Syntax
strip_query_terms on|off
Default
strip_query_terms on
Example
strip_query_terms off
Related
access_log, client_netmask
Name
coredump_dir
Synopsis
Normally Squid doesn't change its current directory at startup. While this isn't usually a problem, it can be if Squid wants to leave a core-dump file. If the core file is very large, it might fill up a disk partition. Additionally, the core won't be created at all if Squid doesn't have permission to write in the current directory.
This directive changes Squid's current directory. You should set it to a location that has sufficient space, and appropriate permissions, for a large core file.
Note that the coredump_dir directive is used only when Squid starts up. If you change the value while Squid is running and then reconfigure, Squid doesn't