Cheers for the replies folks,
I am currently tending to agree with the use of two seperate instances of
Squid. Aside from the logs, it should actually make our system easier to
manage as I got really confused trying to suss out a squid.conf that may or
may not always have a true upstream
He's right, it will work but the loopback trigger will happen and be logged,
What I found easier was using a simple proxy for the outer proxy so that
you don't have the caching overhead, and using squid internally using
ACL's.. The bigger problem is that you can't tell squid to use a certain
On Mon, 2003-09-29 at 07:29, Joshua Brindle wrote:
He's right, it will work but the loopback trigger will happen and be logged,
What I found easier was using a simple proxy for the outer proxy so that
you don't have the caching overhead, and using squid internally using
ACL's..
Which
On Mon, 2003-09-29 at 07:29, Joshua Brindle wrote:
He's right, it will work but the loopback trigger will happen and be logged,
What I found easier was using a simple proxy for the outer proxy so that
you don't have the caching overhead, and using squid internally using
ACL's..
Which
Hi all,
I've tried posting on this in the filter (DansGuardian) message board with
not much success as it seems to require more knowledge about Squid than the
filtering.
I wish to use Squid alongside a custom identd client to allow me to
allow/disallow Internet/Cache access to client stations
On Sun, 2003-09-28 at 01:50, Chris Wilcox wrote:
Hi all,
I've tried posting on this in the filter (DansGuardian) message board with
not much success as it seems to require more knowledge about Squid than the
filtering.
You'll be hitting a routing loop, so no, you cannot do it with one
On Sun, 2003-09-28 at 07:58, Chris Wilcox wrote:
Hmm, apparently it is being done with one squid instance by at least 2
people I've messaged on a forum though they've yet to describe it fully
enough for me to understand. I was kinda wondering why I can't just send
localhost requests direct
