I have this cgi file running on CentOS 5 with Apache 2.2.3 and although it executes most fields are empty, a typical block by squidGuard yields this:
Supplementary info : Client address = 192.168.0.5+clientname Client name = User ident = Client group = URL = Target class =
The redirect lines is: http://localhost/cgi-bin/squidGuard-simple.cgi?clientaddr=%a+clientname=%n+c...
I assume the "+" throws this off somehow, something to do with cgi and apache?
Any ideas? Thanks! jlc
I assume that based on your last message to the list of "is there another way to handle redirects other than installing an Apache server" and now this, there is no other way?
I only ask because I am now setting up squid in my spare time and this is the next task to handle?
Regards, James.
2008/12/10 Joseph L. Casale JCasale@activenetwerx.com:
I have this cgi file running on CentOS 5 with Apache 2.2.3 and although it executes most fields are empty, a typical block by squidGuard yields this:
Supplementary info : Client address = 192.168.0.5+clientname Client name = User ident = Client group = URL = Target class =
The redirect lines is: http://localhost/cgi-bin/squidGuard-simple.cgi?clientaddr=%a+clientname=%n+c...
I assume the "+" throws this off somehow, something to do with cgi and apache?
Any ideas? Thanks! jlc _______________________________________________ CentOS mailing list CentOS@centos.org http://lists.centos.org/mailman/listinfo/centos
I assume that based on your last message to the list of "is there another way to handle redirects other than installing an Apache server" and now this, there is no other way?
I only ask because I am now setting up squid in my spare time and this is the next task to handle?
Yea, it doesn't look like you can. Squidguard is pretty simple compared to squidproxy itself...
I am pretty sure squidproxy can do what squidguard can but I don't think it would be as easy to maintain as I presume all the blacklists would have to be in the one conf file. Too bad...
Let me know you how you make out!
jlc