OTR Comm wrote: > > Hello, > > This may seem like a dumb question, but... > > I have squid running with authentication and with squidGuard as a > redirect program. All this is working okay. I have set some debugging > hooks in the squidGuard code to watch operation and how squid and > squidGuard interface. > > My question is this, if squid is a caching proxy, how come it sends all > GETs to the redirector? That is, even a sight that is not blocked by
The redirector usage is defined by >you< by specifying a redirector in squid.conf , in this case squidGuard. If squidGuard is the authority for your blocking purposes, then by definition all url's must pass squidGuard first for checking. > the squidGuard blacklist is passed to squidGuard for checking. For > example, every time I go to my own web site (http://www.wildapache.net), > I see all the GETs go through squidGuard. > > When does squid check it's cache for the information on any given > request? Is it after the call to squidGuard? > Most probably , because squidGuard can transfer or transfers an URL into another one. Hence checking for the cache is only meaningfull for the returned-by-squidguard request. > I guess I do not understand how squid works. It seems to me that squid > would check it's cache first before it called the redirector, but it > doesn't seem to work this way. Could someone please explain to me the > functional model for squid and the justification for the model, or > direct me to a site that can explain this? A functional flow diagram > would be helpful if one exists on the web. > > Thanks, > Murrah Boswell -- 'Love is truth without any future. (M.E. 1997)
