Well, I too miss a feature which tells us (maybe in cache.log or somewhere else) which acl caused the "access denied". Today often it is very hard to find out why a page is blocked. You should give some donations to Henrik to help us with such a feature;-) Mit freundlichem Gruß/Yours sincerely Werner Rost GMT-FIR - Netzwerk ZF Boge Elastmetall GmbH Friesdorfer Str. 175, 53175 Bonn, Deutschland/Germany Telefon/Phone +49 228 3825 - 420 Telefax/Fax +49 228 3825 - 398 werner.rost@xxxxxx >-----Ursprüngliche Nachricht----- >Von: Mike Branda [mailto:mbranda@xxxxxxxxxxxxx] >Gesendet: Dienstag, 24. Mai 2005 22:45 >An: squid-users@xxxxxxxxxxxxxxx >Betreff: Re: [squid-users] google images issue > > >On Tue, 2005-05-24 at 13:27 -0300, galle wrote: >> ----- Original Message ----- >> From: Mike Branda <mbranda@xxxxxxxxxxxxx> >> To: <squid-users@xxxxxxxxxxxxxxx> >> Sent: Tuesday, May 24, 2005 12:55 PM >> Subject: [squid-users] google images issue >> >> >> > I have a user who went to look up a winnebago (no...really..) as a >> > reference for artwork. He kept getting page cannot be retrieved >> > access denied. The strange thing is that it won't even look up >> > winnebago as a web search although I can type "hard drive" >in images >> > and web and they both work. I went looking through the acl >> > blacklists I have set up and removed any reference to >> > images.google.com and google.com yet it still says access >denied on >> > a search for winnebago. Any idea as to to track down what is >> > causing the denied hit?? I've tailed the access.log file and it >> > only prints one line: >> > >> > 1116946703.711 154 192.168.17.210 TCP_DENIED/403 1434 GET >> > http://images.google.com/images? - NONE/- text/html >> > >> > Is there a way to kick up the verbosity or another way to find the >> > offense?? >> you can change de verbosity level with: >> debug_options >> try >> debug_options 28,9 > >O.K. that worked to find the acl hit but the log file quickly >jumped to 1.4 GB. I've been searching the docs and googling >for a better description of the debug levels (0-9) for squid >and haven't found one. Anyone know where it's hiding?? > >> the number of the debug sections can be found in >debug-sections.txt in >> the /doc of the squid-instalation >> > >Thanks! This is great for the different sections. Now all I >need is a bread crumb trail to the level info. ;^) > > >Mike > >