Adam ,
Thanks a lot for your response .
I used sniffer tool to catch the packet in both Poly graph Server
(10.56.233.99) and Squid server side (198.18.24.3).
I could see 198.18.24.3 send out SYNs, they SYNs were also could be
captured in PolyServer(10.56.233.99) side , but no ack were genenated
Christos Tsantilas wrote:
johan firdianto wrote:
dear guys,
I reading in release notes of squid-3.0stable8,
there's note in New Tags section, in ICAP subsection
Note: reqmod_precache and respmod_postcache is not yet implemented
Only reqmod_precache and respmod_precache vectoring points are
Hi Amos,
Christos Tsantilas wrote:
johan firdianto wrote:
dear guys,
I reading in release notes of squid-3.0stable8,
there's note in New Tags section, in ICAP subsection
Note: reqmod_precache and respmod_postcache is not yet implemented
Only reqmod_precache and respmod_precache vectoring
Christos Tsantilas wrote:
Hi Amos,
Christos Tsantilas wrote:
johan firdianto wrote:
dear guys,
I reading in release notes of squid-3.0stable8,
there's note in New Tags section, in ICAP subsection
Note: reqmod_precache and respmod_postcache is not yet implemented
Only reqmod_precache and
I think you can safely ignore this error message.
Yes but maybe I might have some problems to convince my customer to ignore
it! :)
You should upgrade to newer squid3.0 version, a number of bugs has been
fixed
Ok I've done, I've upgradedo to squid 3.0 STABLE8, the latest stable on
the
I don't know if this is still relevant:
I modified the machine-account of my test system, so that the AD creates
the large tickets (around 7600 chars) again.
When I enlarge the buffers to 32K (via attached patch) it works.
Tested with squid-2.7-STABLE3.
Greets
Malte
On Sun, 29 Jun 2008 10:51:30
daniele.piaggesi wrote:
I think you can safely ignore this error message.
Yes but maybe I might have some problems to convince my customer to ignore
it! :)
You should upgrade to newer squid3.0 version, a number of bugs has been
fixed
Ok I've done, I've upgradedo to squid 3.0 STABLE8,
I think you can safely ignore this error message.
Yes but maybe I might have some problems to convince my customer to ignore
it! :)
This message can appeared when the squid 3.0 shutdown while the ICAP
subsystem shutdown the ICAP services and in this case this message can
ignored.
If you
Hi,
We are moving from proxies using Basic auth to a Squid setup with NTLM and
winbind/Samba authenticating against Active Directory controllers.
We have run into the performance problem with NTLM auth requests to the
Windows domain controllers. I think the NTLM IP caching options should help
us
Hi!
I'm compiling squid_3.0.stable8 (the last stable version on the page
squid-cache.org) and everything go fine, but when i try to start the
squid i got this error:
*Can't use proxy auth because no authentication schemes are fully
configured*.
My options are:
./configure
I believe the error is from your squid.conf file. Did you configure any auth in
the squid.con file?
Jason
..·º
-Original Message-
From: Edward Ortega [mailto:[EMAIL PROTECTED]
Sent: Friday, July 25, 2008 3:23 PM
To: squid-users@squid-cache.org
Subject: [squid-users]
Hi!
Yes, I did. I try to use *digest_ldap_auth*, in fact is the same
squid.conf that i use on squid 2.6 but in the old squid i use
*squid_ldap_auth* instead of *digest_ldap_auth*, that all.
Thanks!
Jason Staudenmayer escribió:
I believe the error is from your squid.conf file. Did you
Hi!
Sorry but i all ready solve the problem, as you said i had a problem
with the configuration when i call digest.
Thanks agains.
Jason Staudenmayer escribió:
I believe the error is from your squid.conf file. Did you configure any auth
in the squid.con file?
Jason
..·º
Hi people,
Since first 3.0 version i've noticed this:
2008/07/25 21:56:24| WARNING: '0.0.0.0/0.0.0.0' is a subnetwork of
'192.168.1.0/255.255.255.0'
2008/07/25 21:56:24| WARNING: because of this '192.168.1.0/255.255.255.0' is
ignored to keep splay tree searching predictable
2008/07/25 21:56:24|
Thank you very much for confirming.
Markus
Malte Schröder [EMAIL PROTECTED] wrote in message
news:[EMAIL PROTECTED]
I don't know if this is still relevant:
I modified the machine-account of my test system, so that the AD creates
the large tickets (around 7600 chars) again.
When I enlarge the
Jorge Bastos escreveu:
Hi people,
Since first 3.0 version i've noticed this:
2008/07/25 21:56:24| WARNING: '0.0.0.0/0.0.0.0' is a subnetwork of
'192.168.1.0/255.255.255.0'
2008/07/25 21:56:24| WARNING: because of this '192.168.1.0/255.255.255.0' is
ignored to keep splay tree searching
Christos Tsantilas wrote:
I think you can safely ignore this error message.
Yes but maybe I might have some problems to convince my customer to ignore
it! :)
This message can appeared when the squid 3.0 shutdown while the ICAP
subsystem shutdown the ICAP services and in this case this
Leonardo Rodrigues Magalhães wrote:
Jorge Bastos escreveu:
Hi people,
Since first 3.0 version i've noticed this:
2008/07/25 21:56:24| WARNING: '0.0.0.0/0.0.0.0' is a subnetwork of
'192.168.1.0/255.255.255.0'
2008/07/25 21:56:24| WARNING: because of this
'192.168.1.0/255.255.255.0' is
18 matches
Mail list logo
