> > To answer both questions, above and below: you need to redirect the > request to an http server somewhere that will run squidGuard.cgi to > satisfy the redirect request. That server should be listening on an > interface that other machines on your LAN can reach, because they'll > be sending requests to it when their requests are blocked.
OK - So ho do I do that? When I run squid on its own (on machine 192.168.123.101) and a user on (say) machine 192.168.123.103 accesses a blocked site, squid pops up a message which is (physically) held in a file on m/c 192.168/123.101/usr/share/errors/ERR_Somemessage - so squid *can* access the local drive on 192.168.123.101. SquidGuard - running on the same machine together with the same instance of squid - can't access the same file - nor can it run the cgi file in /var/www/cgi-bin. I guess my question boils down to - why can't squidGuard use the same redirect file as squid? I know that my dumb questions must be frustrating for you guys - but not half as frustrating as it is for me being so close to a solution yet so far. Thanks again for all your help Mark
pgpFPwRzV3V0j.pgp
Description: PGP signature
