Re: [squid-users] squidGuard configuration (was: squid dies)

Hi,

the following text is from Adam Aube and is copied from another posting,
but i think it fits to your request as well:

<cut>
Please don't post a question by replying to someone else's message.
Doing so ruins threading, makes the archives harder to read, and list
members who are ignoring that thread will not notice your question.
Instead, post a new message (with its own subject) to the list.
</cut>

To your question:

Name is squidGuard - like Guardian.
I am not sure what you mean with error-message. If you mean the page
which is displayed instead of the blocked URL: This is configured in
squidGuard.conf

This is from default - squidGuard.conf which comes with the debian
package. Just change that file to suit your needs.

default {
pass local none
redirect http://admin.foo.bar.no/cgi-bin/squidGuard.cgi?...(paramaters)
         }

Is there a squidGuard.cgi in the distribution/source? Didn't know that.
We use a selfmade cgi which tells the user what happened and gives them
a email-form to post an unlock request - blacklists may contain false
positives.
If you use authentication, you can greet them with their name to wake
them up. Some users do not seem to read a lot when browsing, sometimes
they try to use such a page as a search engine due to the input box in
the middle :-)

Regards, Hendrik

Frank Chibesakunda wrote:

> ist,
> I want to customize the error message, i have just installed squidGaurd
> and it has its default error message of
> http://localhost/cgi-bin/squidGaurd cgi ?
>
> rgds
>
> frank
>
> Mike Rambo wrote:
>
>> Since upgrading to squid 2.5 a month or so ago we have been having to
>> restart squid about once a week when it dies suddenly. Here are the last
>> dozen lines or so from cache.log. Is the final line the cause of death
>> in this case? What does it mean. What other info do you need?
>>
>>
>> 2004/05/26 11:51:52| fqdncacheParse: No PTR record
>> 2004/05/26 11:51:52| fqdncacheParse: No PTR record
>> 2004/05/26 11:52:00| Request header is too large (11680 bytes)
>> 2004/05/26 11:52:00| Config 'request_header_max_size'= 10240 bytes.
>> 2004/05/26 11:52:01| Request header is too large (11680 bytes)
>> 2004/05/26 11:52:01| Config 'request_header_max_size'= 10240 bytes.
>> 2004/05/26 11:52:01| Request header is too large (11680 bytes)
>> 2004/05/26 11:52:01| Config 'request_header_max_size'= 10240 bytes.
>> 2004/05/26 11:53:04| NETDB state saved; 0 entries, 12 msec
>> 2004/05/26 12:07:49| commConnectDnsHandle: Bad dns_error_message
>> 2004/05/26 12:31:48| WARNING: Closing client 10.6.24.111 connection due
>> to lifetime timeout
>> 2004/05/26 12:31:48|
>> http://d.centralmedia.ws/d.aspx?ver=4.5.26&host=5-A237-5
>> 2004/05/26 12:34:03| urlParse: Illegal character in hostname '<'
>> 2004/05/26 12:43:15| assertion failed: errorpage.c:292: "mem->inmem_hi
>> == 0"
>>
>>
>> # squid -v
>> Squid Cache: Version 2.5.STABLE5
>> configure options: --prefix=/usr --exec-prefix=/usr
>> --sysconfdir=/etc/squid --libexecdir=/usr/libexec/squid
>> --sharedstatedir=/var/squid/com --localstatedir=/var/squid
>> --libdir=/usr/lib/squid --enable-gnuregex
>> --enable-storeio=ufs,aufs,diskd --with-pthreads
>> --enable-removal-policies=lru,heap --enable-icmp --enable-delay-pools
>> --enable-useragent-log --enable-referer-log --enable-xmalloc-statistics
>> --enable-kill-parent-hack --enable-snmp
>> --enable-cachemgr-hostname=squid.lpsd.local --enable-htcp --enable-ssl
>> --enable-cache-digests --enable-linux-netfilter --enable-auth=basic,ntlm
>> --enable-basic-auth-helpers=getpwnam,LDAP,MSNT,NCSA,PAM,SMB,winbind
>> --enable-ntlm-auth-helpers=fakeauth,no_check,SMB,winbind
>> --enable-ntlm-fail-open --enable-x-accelerator-vary --enable-carp
>>
>>
>>
>>
>
>
Received on Wed May 26 2004 - 13:57:36 MDT