That's fine, because a pre-requisite would be that all new children flush their cache before the first time they become a child of the SquidGuard parent.
This will ensure that all requests from then on will have to go to the parent and thus SquidGuard will process them. All users connecting to the child will have the same access rights, so no-one will be bypassing the parent to possibly introduce inappropriate material into the child cache. cheers for pointing it out though. -----Original Message----- From: Chris Fletcher [mailto:[EMAIL PROTECTED]] Sent: Wednesday, 5 June 2002 4:15 PM To: Jay Turner Cc: [EMAIL PROTECTED] Subject: Re: Cascading Proxy and SquidGuard The issue with this is if certain users have different access (using proxy authentication upstream is a big issue like this) as if someone is able to access something they do and it gets proxied. Then later on someone in a different group tries to access that same thing knowing full well the person with access accessed it earlier. It hits the first proxy and the content is delivered without even talking to the upstream box. On Wed, 5 Jun 2002, Jay Turner wrote: > > Hi All, > > I was wondering if anyone has tried cascading a proxy to become a child of a > SquidGuard proxy? > > What I would be interested in doing is having a SquidGuard proxy configured > as a Parent and then a number of non SquidGuard proxies acting as children > of this parent cache. > The idea being that these children send all their requests to the SquidGuard > parent which then runs the request through SquidGuard and either allows or > disallows it. > > Has anyone successfully achieved this? I am currently experimenting with it, > but am not having a lot of luck at this stage. > > Thanks > > Regards > Jay > >
