As part of the Squid configuration cleanup project hierarchy_stoplist
has appeared as a directive which is almost but not quite obsolete.
Points against it:
1) it only affects configurations with cache_peer.
2) The default settings published with earlier Squid versions are
obsolete since around 3.1 version.
If you are only using "hierarchy_stoplist cgi-bin \?" you can remove
it completely from any Squid-3 config file.
3) The following
hierarchy_stoplist A B C
is almost exactly equivalent to:
acl Foo url_regex A B C
always_direct allow Foo
With the exception that never_direct is applied before
hierarchy_stoplist but not before always_direct.
Before it gets formally deprecated, I need to know whether anyone is
actually utilizing this obscure never_direct override behaviour. And if
so, are you able to update your configuration to use always_direct and
ACL logics to accomodate the override conditions? or do we need to wait
on further upgrades to the DNS DIRECT selection logics?
In absence of any objections this will be scheduled for deprecation
within the squid-3.4 release cycle.
Amos Jeffries
Squid Project
