[squid-users] Forcing squid to fail when the whitelist doesn't exist

Alex Rousskov rousskov at measurement-factory.com
Thu Jul 9 18:25:27 UTC 2020

On 7/9/20 11:51 AM, Matthew Macdonald-Wallace wrote:
> > Turns out we're running 3.5.x
> I have not tested this, but if my quick reading of the latest v3.5 code
> is correct, then the missing parameters() file is treated as a FATAL
> configuration error (in ConfigParser::NextToken).

FWIW, Squid v3.5.26 works as expected in my test:

> configuration_includes_quoted_values on
> acl goodGuys ssl::server_name parameters("/missing/goodGuys.acl")
> configuration_includes_quoted_values off

> 2020/07/09 14:15:17| WARNING: file :/missing/goodGuys.acl not found
> 2020/07/09 14:15:17| FATAL: Error opening config file: parameters
> FATAL: Bungled /usr/local/squid/./etc/squid-v3p5.conf line 60: acl goodGuys ssl::server_name parameters("/missing/goodGuys.acl")
> Squid Cache (Version 3.5.26-BZR): Terminated abnormally.

Please note that configuration_includes_quoted_values is required.
Without it, Squid interprets the string
`parameters("/missing/goodGuys.acl")` as a single domain name.



More information about the squid-users mailing list