Squid version 3.1.13 on CentOS with no working IPv6.
Thanks for the help, I solved the problem by disabling the internal dns client.
Ok, so even if I have about 150 000 clients making arround 20 4xx
requests / day on 1500 Squid servers which relay its on 4 Squid
servers and then on 1 Apache, is it not a big deal for the last one?
(it's almost equal to 34 requests / sec)
Regards,
Romain
2011/7/3 Amos Jeffries
On 04/07/11 19:15, Filip wrote:
Squid version 3.1.13 on CentOS with no working IPv6.
Thanks for the help, I solved the problem by disabling the internal dns client.
3.1.14 is ow available to resolve this properly.
Amos
--
Please be using
Current Stable Squid 2.7.STABLE9 or 3.1.14
Beta
On 04/07/11 20:40, Romain wrote:
Ok, so even if I have about 150 000 clients making arround 20 4xx
requests / day on 1500 Squid servers which relay its on 4 Squid
servers and then on 1 Apache, is it not a big deal for the last one?
(it's almost equal to 34 requests / sec)
34 req/sec? no that
The Squid HTTP Proxy team is very pleased to announce the
availability of the Squid-3.1.14 release!
This release is a bug fix on 3.1.13 release. Fixing a major regression
in DNS handling.
The patch for this bug can be found at
On 28.06.11 11:46, Fabiano Carlos Heringer wrote:
Hey, Please some advice how to figure out my squid box not caching
(not getting any HIT or cache growing) only RELEASE on store.log
I think you should start with clean config, apply only ACL's and delay
pools, see if it helps, and THEN play
Yes, we are trying to convince our customer to go on last stable
version released for the 4 upstream Squid, and schedule 2.6 migration
for 1500 others but we need a good reason (or proof) and it's seems
that 3.1 doesn't change anything in our case (I mean, visible
change)... or maybe, I didn't see
Hi;
I want to pass https traffic through squid without processing it, only
pass the traffic. I'm not interested with filtering or seeing the
content. I won't use proxy, the iptables rule below will redirect
https traffic to squid.
iptables -t nat -I PREROUTING -p tcp --dport 443 -j DNAT
On 04/07/11 23:03, Deniz Eren wrote:
Hi;
I want to pass https traffic through squid without processing it, only
pass the traffic. I'm not interested with filtering or seeing the
content. I won't use proxy, the iptables rule below will redirect
https traffic to squid.
iptables -t nat -I
On 28/06/11 23:00, Go Wow wrote:
I forgot to mention the other day, I searched for latest versions rpm
and couldn't find it. Do you know of any location which provides rpms
for centos 5.4.
I'm afraid not. I have been unable to track down any packaging
maintainer for CentOS. They have 2.6
On 18/06/11 06:08, Shoebottom, Bryan wrote:
Amos,
Any luck with coding the bit mask? Is there anything else you need from me?
No pressure, this e-mail is mainly to keep this thread on track as you
mentioned previously.
Sorry, I got into it then found an exceptionally complicated
No problem, I know you guys are busy and appreciate the time and effort the
team(s) put into this project.
It sounds like this isn't a simple switch outside of the configuration file.
Should I be making a feature request or will this thread suffice? If the
latter, how often should I bump
Amos Jeffries wrote:
This new release can be downloaded from our HTTP or FTP servers
http://www.squid-cache.org/Versions/v3/3.1/
According to that page, 3.1.13 is the latest - does something need
updating or is it just me?!
Mark
pgp36ZdOenUV7.pgp
Description: PGP signature
Hi Amos,
I am trying to make the intermediate certs into the dynamic ssl connection.
Based on the code, the cert entry of http_port configure is actually a cert
chain file. So the configure does have enough info for the intermediate cert
chain to work. What is missing is when the SSL_CTX is
On Mon, 4 Jul 2011 19:59:34 +0100, Mark Foxwell wrote:
Amos Jeffries wrote:
This new release can be downloaded from our HTTP or FTP servers
http://www.squid-cache.org/Versions/v3/3.1/
According to that page, 3.1.13 is the latest - does something need
updating or is it just me?!
Mark
On Mon, 4 Jul 2011 19:25:41 +, Ming Fu wrote:
Hi Amos,
I am trying to make the intermediate certs into the dynamic ssl
connection.
Based on the code, the cert entry of http_port configure is
actually a cert chain file. So the configure does have enough info
for
the intermediate cert
On Mon, 4 Jul 2011 12:49:25 -0400, Shoebottom, Bryan wrote:
No problem, I know you guys are busy and appreciate the time and
effort the team(s) put into this project.
It sounds like this isn't a simple switch outside of the
configuration file. Should I be making a feature request or will
this
Hello,
i'm trying to get squid to work with a max os x based LDAP.
I have a couple of questions if you can help me with:
1. Does a centos based yum installation contain ldap and kerberos support?
2. Is the following squid.conf config enough to get things up and
running (complete article
On 07/05/2011 05:04 PM, Roland Roland wrote:
Hello,
i'm trying to get squid to work with a max os x based LDAP.
I have a couple of questions if you can help me with:
1. Does a centos based yum installation contain ldap and kerberos
support?
2. Is the following squid.conf config enough to
19 matches
Mail list logo
