On 2024-09-05 01:52, YAMAGUCHI NOZOMI (JIT ICC) wrote:
If there were duplicate domains in the list of domains used, restarting
the squid would cause the process to stop.
Below is the error statement.
ERROR: 'a.example.com' is a subdomain of 'example.com
FATAL: /etc/squid/squid.conf
Hi Nichole,
FWIW, this and several related problems were fixed in master/v7
commit 0898d0f4: https://github.com/squid-cache/squid/commit/0898d0f4
I don't think the same thing happened with my previous squid3.5.
AFAICT, the relevant code is the same in v3.5 and v5.5, but I did not
check carefully because both versions are not supported by the Squid
Project. Squid v6.10 does suffer from the same problem as well.
・Is it possible to configure the process not to stop even if there are
duplicates in the domain list?
Short answer: No. The problematic behavior is hard-coded.
Needless to say, one can (and should) configure Squid using ACLs without
duplicates.
・Are there any other user actions besides duplicate domains that would
trigger a process stop?
Yes, lots of configuration errors still result in Squid death. We are
actively working on eliminating such cases during reconfiguration; if
our changes are officially accepted, Squid v7 should be significantly
better in this regard. Please see Matus's earlier response on this
thread for ways to avoid such deaths.
HTH,
Alex.
_______________________________________________
squid-users mailing list
squid-users@xxxxxxxxxxxxxxxxxxxxx
https://lists.squid-cache.org/listinfo/squid-users
