Re: proposal: change installed default squid.conf to fit best practice.

From: Jeff Tharp <>
Date: Tue, 2 Jan 2007 14:54:25 -0800

As a user whose done his share of wading through the well-commented
default squid.conf, I would definitely appreciate it if there was a
minimal squid.conf (maybe sans comments, for sake of brevity) with the
fully commented squid.conf available as well for reference purposes.

Speaking of the conf file, I have often wondered if it would be possible
to allow for additional conf files to be included, ala Apache's Include
directive (
This would be handy for those of us who use Squid as a reverse proxy
server--configuration related to specific site, such as ACLs and so
forth could be broken out in per-site files for easier maintenance and
thus reduce chances that a core configuration bit would be changed by

I looked at the source code to see if I could hack this in myself, but
how Apache reads in it's config files is very different from Squid, so I
wasn't able to do a quick and dirty hack. Still if this could be done,
I'd be most appreciative.

Jeff Tharp
System Administrator
ESRI - Redlands, CA

>From: Robert Collins <>
>Date: Tue, 02 Jan 2007 07:48:38 +1100
>On Sat, 2006-12-30 at 16:49 +0800, Adrian Chadd wrote:
>> On Sat, Dec 30, 2006, Robert Collins wrote:
>> > As we all recommend that users have a minimal config - just the
>> > set settings, why dont we install that by default ?
>> What I'd actually like to see is a default squid.conf file with
>> options - "Here's your LAN addresses", "here's some default refresh
>> "here's an example UFS/AUFS/DISKD and COSS configuration", "Here's
the sections
>> to enable for Basic authentication with ncsa_auth", that kind of
>> squid.conf.default is pretty daunting..

>I think that would be fine too - but *not* the full list. And not the
>complete set of options either for a specific area, just the ones that
>are common.
Received on Tue Jan 02 2007 - 16:23:58 MST

This archive was generated by hypermail pre-2.1.9 : Thu Feb 01 2007 - 12:00:02 MST