-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
On 9/10/2014 4:19 a.m., Mirza Dedic wrote:
> Thanks Amos, It seems I spoke too fast, the proxy prompt is back,
> so disabling SG didn't do the trick.
Replying with a config file audit separately so it does not get lost
in the technical details of run
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
On 9/10/2014 4:19 a.m., Mirza Dedic wrote:
> Thanks Amos, It seems I spoke too fast, the proxy prompt is back,
> so disabling SG didn't do the trick. Two two hits I see in
> access.log are: 1412778349.755141 172.16.12.110 TCP_MISS/200
> 462 POST ht
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
On 8/10/2014 9:32 a.m., silblackw wrote:
> Hello,
>
> I am setting up my squid to require user authentication with a
> digest. I have noticed that if authentication fails, it prompts the
> user again, and if the user clicks "cancel" then squid just re
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
On 7/10/2014 11:33 p.m., masterx81 wrote:
> Hi to all! I'm having an issue on squid 3.3.13 using
> basic_ldap_auth. I'm using the following helpers: auth_param
> negotiate program /usr/local/bin/negotiate_wrapper --ntlm
> /usr/bin/ntlm_auth --helper-p
Markus Moeller wrote:
>
>I only found the following explanation:
>
> This error will happen if you didn't write the key into the keytab file, or
> the permission setting of keytab file reject the read access, or the key
> file is not the one you should access (for example, you want
> /opt/som
Hi Victor,
I only found the following explanation:
This error will happen if you didn't write the key into the keytab file, or
the permission setting of keytab file reject the read access, or the key
file is not the one you should access (for example, you want
/opt/somedir/conf/krb5.conf, but
Hi Victor,
I only found the following explanation:
This error will happen if you didn't write the key into the keytab file, or
the permission setting of keytab file reject the read access, or the key
file is not the one you should access (for example, you want
/opt/somedir/conf/krb5.conf,
Hi Eliezer,
The DNS we are using is the ISP default for external, our internal domain DNS
for internal. Nslookup works for all tests.
I would like to update to the latest stable, but I am concerned of breaking the
current setup. It took a little work to get it working correctly particularity
o
I still get a TCP_DENIED/403 while accessing a bumped https-site after
putting a "-" or even "^root$" in /etc/squid/DENY_USERS_LOCAL. The
cache.log with "debug_options 29,3 28,9" activated looks like this:
014/10/08 20:03:00.539 kid2| Acl.cc(157) matches: checking DENY_USERS_LOCAL
2014/10/08 20:03
Hello,
I have squid configured to forward requests to two parents, like following:
cache_peer host1 XXX YYY proxy-only weighted-round-robin weight=1
cache_peer host2 ZZZ BBB proxy-only weighted-round-robin weight=1
But when one of parents is not available squid can't determine that it's
down and s
On 08.10.14 15:05, Amos Jeffries wrote:
New patch added to bug 4088. Please see if it resolves the
external_acl_type leak.
Seems to fix the problem - thank you!
--
- Steve Hill
Technical Director
Opendium Limited http://www.opendium.com
Direct contacts:
Instant messager: xmpp:s
Squid Cache v3.3.3 included in cygwin was ./configured with:
$ ./squid -vSquid Cache: Version 3.3.3
'--srcdir=/usr/src/ports/squid/squid-3.3.3-2.i686/src/squid-3.3.3'
'--prefix=/usr' '--exec-prefix=/usr' '--bindir=/usr/bin' '--sbindir=/usr/sbin'
'--libexecdir=/usr/libexec' '--datadir=/usr/share'
Thanks Amos,
It seems I spoke too fast, the proxy prompt is back, so disabling SG didn't do
the trick.
Two two hits I see in access.log are:
1412778349.755141 172.16.12.110 TCP_MISS/200 462 POST
http://sqm.microsoft.com/sqm/wm/sqmserver.dll - DIRECT/65.55.7.141
-1412778349.911515 172.16.
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
On 9/10/2014 3:21 a.m., Amos Jeffries wrote:
> On 9/10/2014 2:09 a.m., Tom Tom wrote:
>> I think, this behaviour was introduced with squid 3.4.4.1
>> (http://www.squid-cache.org/Versions/v3/3.4/changesets/squid-3.4-13113.patch).
>
>> I don't exactly
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
On 9/10/2014 2:09 a.m., Tom Tom wrote:
> I think, this behaviour was introduced with squid 3.4.4.1
> (http://www.squid-cache.org/Versions/v3/3.4/changesets/squid-3.4-13113.patch).
>
> I don't exactly understand this behaviour. Any hints for this?
Ah
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
On 8/10/2014 4:40 a.m., Steve Hill wrote:
> On 30.09.14 16:13, Amos Jeffries wrote:
>
>>> I'm trying to figure out if there's a way of convincing
>>> valgrind to dump info about all the currently allocated memory
>>> while the program is still running
I think, this behaviour was introduced with squid 3.4.4.1
(http://www.squid-cache.org/Versions/v3/3.4/changesets/squid-3.4-13113.patch).
I don't exactly understand this behaviour.
Any hints for this?
Thanks a lot.
Kind regards,
Tom
On Mon, Oct 6, 2014 at 11:59 AM, Tom Tom wrote:
> Hi
>
> After
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Eliezer Croitoru wrote:
> >
> > I could find the said script neither in the source nor in the
> > binary package. However I think I can guess what could be inside.
> > Could you look below if that makes sense?
>
> Or you can just look at the source c
18 matches
Mail list logo
