Re: problem with always_direct

Hi Jason,

This doesn't sound too bad to me; as I know from my Squid boxes, when you
access servers which are directly routed, you still generate entries in the
access.log. That's perfectly normal. Just look at the routing used;
Internet access will show up as "SINGLE_PARENT" or "FIRST_UP_PARENT" or
something similar. Accesses to URLs in www.cs.yorku.ca should be listed as
"DIRECT". This is all the confirmation you need.

Rgds

Richard Stagg

jas@cs.yorku.ca on 18/02/99 15:27:17

To: squid-users@ircache.net
cc: (bcc: Richard Stagg/TMU/CSC)
Subject: problem with always_direct

I set up Squid 2.1.PATCH2 yesterday for the first time, and spent a good
portion of the day reading through the various documentation and FAQs.
Squid is up and running well, and doing what it's supposed to do. I'm
running my test squid server directly on our NFS server, and our web
server is running on a server that accesses the web data VIA NFS. I'm
just running in proxy mode though -- none of the accelerated/mirroring
stuff. For a test, what I wanted to be able to do was to tell Squid not
to cache stuff sent to our local web server. From my reading, I *know*
always_direct is the way to do this, and I did it like this:
acl local-servers dstdomain www.cs.yorku.ca
always_direct allow local-servers
I had squid re-read the config file (squid -k reconfigure), but every
time I go to access anything at "http://www.cs.yorku.ca", I still see
all the references in access.log. I was under the impression that I
shouldn't see anything at all.
Any ideas?
Jason Keltz
jas@cs.yorku.ca
Received on Thu Feb 18 1999 - 09:38:33 MST