That does the trick. Thanks! I suppose this means squidGuard 1.4 is not compatible with the new url_rewrite_concurrency helper method. -------- Original-Nachricht -------- > vollkommen@xxxxxxx wrote: > > Currently running squid 3.0.STABLE14-20090412, but the issue has been > around for months, possibly ever since moving to 3.0STABLE release from > 3.0PRE, or maybe > > > > squid 3.0 config: > > > > url_rewrite_program /usr/local/squid/bin/squidGuard -c > /Applications/squid/squidguard.conf > > url_rewrite_children 8 > > url_rewrite_concurrency 8 > > url_rewrite_host_header off > > > > cache.log with debug_options 61,5 > > > > 2009/04/14 19:58:13.313| redirectStart: 'http://doubleclick.net/' > > 2009/04/14 19:58:13.313| redirectHandleRead: {<NULL>} > > 2009/04/14 19:58:13.506| redirectStart: 'http://www.doubleclick.com/' > > 2009/04/14 19:58:13.507| redirectHandleRead: {<NULL>} > > > > > > squidGuard 1.4 is blocking just fine by itself: > > > > echo "http://doubleclick.net 1.2.3.4/- user GET -" | squidGuard -c > /Applications/squid/squidguard.conf -d > > That test is _not_ allowing for concurrency. Which adds a channel-ID > column as the first entry > > Try without the "url_rewrite_concurrency" line. > > Amos > -- > Please be using > Current Stable Squid 2.7.STABLE6 or 3.0.STABLE14 > Current Beta Squid 3.1.0.7 -- Neu: GMX FreeDSL Komplettanschluss mit DSL 6.000 Flatrate + Telefonanschluss für nur 17,95 Euro/mtl.!* http://dslspecial.gmx.de/freedsl-surfflat/?ac=OM.AD.PD003K11308T4569a
