Il 09/04/2013 19:33, Mr Dash Four ha scritto:
[snip]
if the maximum_object_size_in_memory is reduced,
then I suppose squid's memory footprint will have to go down too, which
makes the cache_mem option a bit useless.
I think will just store more objects in RAM.
--
Marcello Romani
How do you handle dest port 443 ?
It is not enough simply to route all traffic (dest port 80 and dest port
443) to squid:3128. This will not work for https:
May be, you post your complete squid.conf. And the rules for iptables etc.
to achieve transparency.
In squid.conf you will need such stuff
AFAIK FF uses the first auth scheme presented. IE (and Chrome ?) use the
safest method.
So, assuming, you want Negotiate first to appear in the headers, I would
consider this a typical case for a site specific Brutal Hack of the squid
sources.
Regarding FF, it is possible to mess around with
Il 09/04/2013 19:33, Mr Dash Four ha scritto:
[snip]
if the maximum_object_size_in_memory is reduced,
then I suppose squid's memory footprint will have to go down too, which
makes the cache_mem option a bit useless.
I think will just store more objects in RAM.
Agreed.
But it should also
On Tue, 9 Apr 2013, Mr Dash Four wrote:
The system is atom-based machine with 2GB memory. Even though squid starts OK
at first, it gradually baloons and the current memory usage (according to ps)
is:
Older versions of squid 3 do have some known memory leaks which might be
your problem here,
* M A Young m.a.yo...@durham.ac.uk:
On Tue, 9 Apr 2013, Mr Dash Four wrote:
The system is atom-based machine with 2GB memory. Even though squid
starts OK at first, it gradually baloons and the current memory
usage (according to ps) is:
Older versions of squid 3 do have some known memory
On Tue, Apr 9, 2013 at 11:35 PM, Youssef Ghorbal d...@pasteur.fr wrote:
Hello,
Is there any recent figures about max throughput to be expected from
a squid 3.x install (on recent hardware) in the scenario of a single stream
downloading a large file ( 1GB) (read not cacheable)
Because your question is specific to google, may be, this could help you as
well:
https://groups.google.com/forum/#!topic/comp.protocols.dns.bind/hNRTWz1T1MY
Having done a lot of content mod myself, I can confirm, that this finally
works for browser sessions.
--
View this message in context:
Amen to that. It got A LOT better.
Interesting. Any facts available about mem leaks in 2.7 final, at least ?
I am still using it, not recognizing a leak. Which might be caused to
non-default configs only, though.
--
View this message in context:
Hi,
I run 3.2.7 squid successfully for some weeks now.
Yesterday I tried to upgrade to squid 3.3.3 and after a few minutes
squid exits and I get the following messages in my cache.log:
--snip--
2013/04/09 08:44:40| Starting Squid Cache version 3.3.3 for
x86_64-suse-linux-gnu...
2013/04/09
- Original Message -
From: Dieter Bloms sq...@bloms.de
To: squid-users@squid-cache.org
Cc:
Sent: Wednesday, 10 April 2013 3:03 PM
Subject: [squid-users] assertion failed: Checklist.cc:287: !needsAsync
!matchFinished after upgrade from squid 3.2.7 to 3.3.3
Hi,
I run 3.2.7
Which version of squid are you using ?
squid -v
Also interesting to see the ./configure options.
Do you really need 1/2 parent proxies ? Or do you simply want to split up
the traffic to the two interfaces ?
In case you need parent(s), then I would use 2.
(Although it should also be possible
On Apr 10, 2013, at 10:37 AM, Kinkie gkin...@gmail.com wrote:
On Tue, Apr 9, 2013 at 11:35 PM, Youssef Ghorbal d...@pasteur.fr wrote:
Hello,
Is there any recent figures about max throughput to be expected from
a squid 3.x install (on recent hardware) in the scenario of a single
Hello Amm,
On Wed, Apr 10, Amm wrote:
- Original Message -
From: Dieter Bloms sq...@bloms.de
To: squid-users@squid-cache.org
Cc:
Sent: Wednesday, 10 April 2013 3:03 PM
Subject: [squid-users] assertion failed: Checklist.cc:287: !needsAsync
!matchFinished after upgrade from
I am going to assume that is a problem with it being a transparent proxy?
Yep. That is another issue to take care of.
Look here:
http://wiki.squid-cache.org/Features/BumpSslServerFirst
I suggets, first do NOT take SSL into consideration. Adds another layer of
complexity.
First, get your setup
On 4/9/2013 10:46 PM, Duncan, Brian M. wrote:
Thanks for the reply and further clarification,
I still believe the issue I am reporting is specific to DNS and how Squid's
internal DNS resolver works.
I forgot to mention if I bypass using the hostname in my test, and enter one of
the resolved
Then to add some more conditions in squid.conf, like
never_direct allow all
always_direct deny all
--
View this message in context:
http://squid-web-proxy-cache.1019090.n4.nabble.com/peer-cache-question-tp4659419p4659460.html
Sent from the Squid - Users mailing list archive at Nabble.com.
Hi,
I'm trying to get the following to work:
- all requests must go to the redirect_program. after the request went
through the redirect program:
- all requests must be forwarder to proxy A
- UNLESS they are to 172.19.0.0/16 or listed in
/usr/local/etc/squid3-directurls.txt
- if they
Marcello Romani wrote:
Il 09/04/2013 19:33, Mr Dash Four ha scritto:
[snip]
if the maximum_object_size_in_memory is reduced,
then I suppose squid's memory footprint will have to go down too, which
makes the cache_mem option a bit useless.
I think will just store more objects in RAM.
I am
M A Young wrote:
On Tue, 9 Apr 2013, Mr Dash Four wrote:
The system is atom-based machine with 2GB memory. Even though squid
starts OK at first, it gradually baloons and the current memory usage
(according to ps) is:
Older versions of squid 3 do have some known memory leaks which might
You probably want to check http://wiki.squid-cache.org/KnowledgeBase/Benchmarks
Unfortunately the benchmarks reported are often expressed as RPS and
not bandwidth.
On Wed, Apr 10, 2013 at 1:21 PM, Youssef Ghorbal d...@pasteur.fr wrote:
On Apr 10, 2013, at 10:37 AM, Kinkie gkin...@gmail.com
Il 10/04/2013 10:20, Ralf Hildebrandt ha scritto:
* M A Young m.a.yo...@durham.ac.uk:
On Tue, 9 Apr 2013, Mr Dash Four wrote:
The system is atom-based machine with 2GB memory. Even though squid
starts OK at first, it gradually baloons and the current memory
usage (according to ps) is:
Older
I was aware of that page.
As you said, it's often RPS so it's not relevant for me.
Youssef
On Apr 10, 2013, at 2:02 PM, Kinkie gkin...@gmail.com wrote:
You probably want to check
http://wiki.squid-cache.org/KnowledgeBase/Benchmarks
Unfortunately the benchmarks reported
Il 10/04/2013 13:59, Mr Dash Four ha scritto:
Marcello Romani wrote:
Il 09/04/2013 19:33, Mr Dash Four ha scritto:
[snip]
if the maximum_object_size_in_memory is reduced,
then I suppose squid's memory footprint will have to go down too, which
makes the cache_mem option a bit useless.
I
What currently seems to happen is that cache_mem is completely ignored
and squid is trying to shove up as many objects into my ram as possible,
Not exactly.
You might be a victim of max_object_size, as I mentionead already above.
squid will store a 500MB video temporarily in mem, unles you put
FYI. They upstream keyserver has been fixed. [rt.ubuntu.com #21348]
→ curl -v keyserver.ubuntu.com
* About to connect() to keyserver.ubuntu.com port 80 (#0)
* Trying 91.189.89.49...
* connected
* Connected to keyserver.ubuntu.com (91.189.89.49) port 80 (#0)
GET / HTTP/1.1
User-Agent:
Il 10/04/2013 14:29, Marcello Romani ha scritto:
Il 10/04/2013 13:59, Mr Dash Four ha scritto:
Marcello Romani wrote:
Il 09/04/2013 19:33, Mr Dash Four ha scritto:
[snip]
if the maximum_object_size_in_memory is reduced,
then I suppose squid's memory footprint will have to go down too,
I opened a bug report on this today. Thanks
-Original Message-
From: Eliezer Croitoru [mailto:elie...@ngtech.co.il]
Sent: Wednesday, April 10, 2013 6:53 AM
To: squid-users@squid-cache.org
Subject: Re: [squid-users] Issue related to using Squid 3.1 or 3.29 and
accessing a site that
As an addition to my previous comment, please read this comment in
squid.conf (3.1.6 FWIW):
# TAG: store_avg_object_size (kbytes)
# Average object size, used to estimate number of objects your
# cache can hold.
May I chime in? ^ That's an interesting directive that I have
Hi,
I spent more time on this today by looking at the code. I see from
the code that squid does not accept certificates which require
passphrase to read the private key.
In the function readSslPrivateKey(...), I see this
EVP_PKEY *pkey = PEM_read_bio_PrivateKey(bio.get(), NULL,
Marcello Romani wrote:
Il 10/04/2013 13:59, Mr Dash Four ha scritto:
Marcello Romani wrote:
Il 09/04/2013 19:33, Mr Dash Four ha scritto:
[snip]
if the maximum_object_size_in_memory is reduced,
then I suppose squid's memory footprint will have to go down too,
which
makes the cache_mem
As an addition to my previous comment, please read this comment in
squid.conf (3.1.6 FWIW):
# TAG: store_avg_object_size (kbytes)
# Average object size, used to estimate number of objects your
# cache can hold.
I don't see how this helps fixing the problem I described in my initial
On Apr 10, 2013, at 10:05 AM, Prasanna Venkateswaran prasca...@gmail.com
wrote:
Hi,
I spent more time on this today by looking at the code. I see from
the code that squid does not accept certificates which require
passphrase to read the private key.
In the function
Hello list,
im playing around with Bump-Server-First method at the moment and I have
a quite simple question about this.
For me it seems to work in non transparent mode at the moment, so i can
see also the https traffic going over the Proxy. But my browser gives me
out a warning that the
On 04/10/2013 09:22 AM, Mr Dash Four wrote:
the total memory used of all objects placed in ram should
not be 6 times the cache_mem value
There is no such rule or law of physics. cache_mem is not squid_mem (a
not-yet-supported option that would limit total Squid memory usage).
The total memory
On Apr 10, 2013, at 1:07 PM, .. sauro...@gmx.de wrote:
Hello list,
im playing around with Bump-Server-First method at the moment and I have
a quite simple question about this.
For me it seems to work in non transparent mode at the moment, so i can
see also the https traffic going over the
Alex Rousskov wrote:
On 04/10/2013 09:22 AM, Mr Dash Four wrote:
the total memory used of all objects placed in ram should
not be 6 times the cache_mem value
There is no such rule or law of physics. cache_mem is not squid_mem (a
not-yet-supported option that would limit total Squid
Good afternoon,
I wonder if you can help me with an issue that has me stuck for several days, I
always use it to generate HTML reports SqStat real-time:
http://samm.kiev.ua/sqstat/
It all started from that install a CentOS 6.3 server that comes with 64 Bits
SQUID 1.3.10 (with previous works
Gentlemen, this exchange is not even close to being constructive, let us
start over shall we.
Please, give us your entire squid.conf and version, as well as your OS
and Kernel version.
-
Signed,
Fix Nichols
http://www.squidblacklist.org
resending because i got a mailer-daemon failure for HTML formatting...
all,
i am running squid 3.2.5 on fedora 16 64 bit on two separate boxes,
load balanced with HA Proxy. i am trying to access cachemgr on either
one of the squid instances, and both exhibit the behaviour where the
40 matches
Mail list logo
