[squid-users] Forcing squid to fail when the whitelist doesn't exist
matt at mockingbirdconsulting.co.uk
Thu Jul 9 18:27:24 UTC 2020
On Thu, 9 Jul 2020, 19:25 Alex Rousskov, <rousskov at measurement-factory.com>
> 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.
Connecting you with your environment
e: info at mockingbirdconsulting.co.uk
<mailto:matt at mockingbirdconsulting.co.uk>
t: +44 (0) 1600 717142
Registered in England and
Wales, Company Number 10488438
-------------- next part --------------
An HTML attachment was scrubbed...
More information about the squid-users