Instead of dstdomain, you could use a regular expression. You could use a
pattern like:
^(www\.)?(google\.com?(\...)?)
Which would catch:
google.co
google.com
google.co.XX where XX is any two characters
google.com.XX "" ""
(with and without www.)
That would probably catch most of them withou
Did you set the limit before you compiled it? The upper limit is set at compile
time. I ran into this problem myself.
-Dan
-Original Message-
From: Superted666 [mailto:ruckafe...@gmail.com]
Sent: Mon 7/5/2010 3:33 PM
To: squid-users@squid-cache.org
Cc:
Subject:[squi
From: Franz Angeli [mailto:franz.ang...@gmail.com]
> I configured one debian box with squid 3.1 (compiling it with ssl
> support) enabling sslBump feature with a self signed certificate,
> obviously browser and
> applications warn about the certificate but all seems to work.
>
> Is there a way to
>-Original Message-
>From: Amos Jeffries [mailto:squ...@treenet.co.nz]
>Sent: Wednesday, April 07, 2010 10:56 PM
>
>Mellem, Dan wrote:
>> Hi,
>>
>> Thanks for your response. Please see below.
>>
>>> From: Amos Jeffries [mailto:squ...@tre
>-Original Message-
>From: Jean-Luc Wasmer [mailto:sq...@2010.jl.wasmer.ca]
>Sent: Thursday, April 08, 2010 1:02 PM
>
>Hi,
>
>What is the format of the regex file when defining an ACL
>based on regexes?
Just a list of matches. E.g.:
^http://www\.google\.com #Allow access to Google
# Ne
Hi,
Thanks for your response. Please see below.
>From: Amos Jeffries [mailto:squ...@treenet.co.nz]
>Sent: Wednesday, April 07, 2010 7:33 PM
>On Wed, 07 Apr 2010 19:12:53 -0700, "Mellem, Dan"
>> access.log or to another log. Only successful requests are logged
>>
Hi,
We're running Squid version 2.6. In our configuration, some URLs require
proxy authentication so we use the squid_ldap_auth helper with basic
auth. Everything works fine.
We would like to log any password failures, including the source IP
address, to track down password guessers. The failure
