After a while looking for solutions on this problem still havent resolve this
issue. I added an extra dsl line to our network and things are going the same
way. Also, tried other mailing list and posted on WISPA and got this response:
"Could be your squid cache. "
Someone replied to that with:
I have I am running squid 2.6 stable 21 on Centos 5.5 the box is
authenticated using winbind to the active directory domain
Wbinfo -t tells me that the RPC call was successful and everything is
working well, my ntlm SSO is working with chrome,ff,ie6,ie7 and ie8 on
windows xp,windows vista
My only
Hello,
I have upgraded to squid-3.1 recently, and found a change of behaviour.
I have been using dansguardian in front of squid.
It appears to be because squid now buffers uploaded POST data slightly
differently.
In versions < 3.1, it would take some data, send it through to the website,
and then
Hi Amos,
The problem addressed here, I've found in my log file too.
You have indicated, a solution. Can you say more about this.
Thanks
Uwe
>Re: [squid-users] Re: squid receives (null) instead of http
>
>Sun, 17 Jan 2010 17:29:23 -0800Amos Jeffries
>
>On Mon, 18 Jan 2010 00:22:09 +0200, Arthur
On 25/11/10 19:52, Compu Serve wrote:
Hello list,
I'm running squid for reverse proxy.
I have been setting up "negative_ttl 0 seconds" for no caching all 404
like pages.
But now I want to no cache for a special domain with 404 response, but
not others.
for example,
www.abc.com 404 will get n
I have my cache mounted on a drive at /var/spool/squid.
The other day I tied to mount a new folder also on the same drive, which is
apparently not the best thing to do.
Since then, I am not sure if my squid cache is updating or not. It seems to
be stuck at 35Gb use and 16% capacity.
Is there any
On Thu, Nov 25, 2010 at 12:27:50AM +, Amos Jeffries wrote:
> On Wed, 24 Nov 2010 13:26:03 +, Declan White
> wrote:
> > I've got some 'uncaught exception' coredumping squids which are leaving no
> > clues about their deaths.
> > They are *meant* to be sending an SOS via:
> >
> > main.cc:11
Hi List,
I have nailed a few niggles relating to extremely high CPU usage for my
authenticators, and I can now clearly look at the requests coming in on the
access.log. I use a combination of Kerb & NTLM helpers for my 700 users -
majority Kerberos.(70/30). I started tailing the log yesterday a
