Re: [squid-users] crash squid-3.1.18

2011-12-08 Thread Amos Jeffries
On 8/12/2011 8:44 p.m., Knop, Uwe wrote: Hi, i create a bugreport for this error http://bugs.squid-cache.org/show_bug.cgi?id=3442: assertion failed: external_acl.cc:841: ch-auth_user_request bye UK This is fixed already. Just winding its way down through QA. Thanks for the info that 3.1

[squid-users] URL parsing crashing squid 3.2.0.13... snapshot

2011-12-08 Thread alex sharaz
Hi, 2011/12/08 10:05:13 kid5| Starting Squid Cache version 3.2.0.13-20111206-r11454 for x86_64-unknown-linux-gnu... 2011/12/08 10:05:13 kid5| Process ID 6007 2011/12/08 10:05:13 kid5| Process Roles: worker 2011/12/08 10:05:13 kid5| With 49152 file descriptors available 2011/12/08 10:05:13

[squid-users] icap problem with 3.1.18

2011-12-08 Thread Daniel Beschorner
After upgrading to 3.1.18 (+adaption compile patch) the following url never stops loading in the browser http://x.ligatus.com/cgi-bin/ivw/CP/11260-365/83-1056/129647-107545-_129709-105679-_128565-101085-// If I bypass the ICAP server for this url (which is indeed a redirect to

Re: [squid-users] crash squid-3.1.18

2011-12-08 Thread Jan Sievers
Hi Amos, On 2011-12-08 10:04, Amos Jeffries wrote: On 8/12/2011 8:44 p.m., Knop, Uwe wrote: i create a bugreport for this error http://bugs.squid-cache.org/show_bug.cgi?id=3442 assertion failed: external_acl.cc:841: ch-auth_user_request This is fixed already. Just winding its way down

[squid-users] config help on squid-3.1.8 on Tomato router

2011-12-08 Thread Jason Ianacone
I am running squid 3.1.8 (non-transparent) on a Tomato based router. I connect to my router via SSH (PuTTY). In the GUI I have a tunnel setup to forward port 444 to 3128. I have a couple of small problems that bother me. 1. I run a WHS on my LAN. When I am connected to the SSH and I type in

Re: [squid-users] Kerberos auth and users in another AD domain

2011-12-08 Thread Emmanuel Lacour
(sorry for the thread break, I loosed original messages and cannot find the Message-ID) Amos, thanks for your hints. I did some tests to connect to a kerberos enabled squid from a windows client not within the AD domain: squid auth setup is: negotiate squid_kerb_auth ntlm basic (ldap) As

Re: [squid-users] config help on squid-3.1.8 on Tomato router

2011-12-08 Thread Amos Jeffries
On 9/12/2011 8:37 a.m., Jason Ianacone wrote: I am running squid 3.1.8 (non-transparent) on a Tomato based router. I connect to my router via SSH (PuTTY). In the GUI I have a tunnel setup to forward port 444 to 3128. I have a couple of small problems that bother me. 1. I run a WHS on my LAN.

[squid-users] MAC addresses as the only ACL restriction

2011-12-08 Thread Inter Node
Hello everyone, I have a question (and it may be a stupid one), but here goes. I use squid on my server for privacy reasons when I surf the web. I currently use IP addresses as my access restriction; only my home IP has access to my squid server. I was thinking of transitioning to MAC addresses

Re: [squid-users] MAC addresses as the only ACL restriction

2011-12-08 Thread Pieter De Wit
Hi, MAC address filtering will only work on the same LAN segment. The mac address for your IP will be the gateway of the squid server if you are connecting remotely. Cheers, Pieter On Thu, 8 Dec 2011, Inter Node wrote: Hello everyone, I have a question (and it may be a stupid one), but

Re: [squid-users] config help on squid-3.1.8 on Tomato router

2011-12-08 Thread Jason Ianacone
I totally agree. Just hoping someone could say what exactly. Problem #2 had to do with the hosts name redirecting the device name to the ipv4 and ipv6 addresses. I have a unique name to the ipv4 and the problem went away. Sent from my iPhone On Dec 8, 2011, at 3:41 PM, Amos Jeffries

[squid-users] Prevent squid from adding headers

2011-12-08 Thread Jan van Riebeeck
Hi list, I'm using squid proxy in a debugging context. So I've configured it to not cache anything. However, squid still adds headers to all my requests and responses. I'd like to see the response *exactly* as it came from the web server, and I'd like the web server to receive my request