esday, August 9, 2016 6:36 AM
To: Eliezer Croitoru; squid-users@lists.squid-cache.org
Subject: Re: [squid-users] Range header is a hit ratio killer
在 16/8/7 21:20, Eliezer Croitoru 写道:
> Hey Simon,
>
> I do not know the plans but it will depend on couple things which can fit to
> one
Hi,
As a workaround, I placed a nginx in the front of my bigfiles squid
box. then I tcpdump on the squid's server side, byte-range are convertd
to a fixed size, and it's cached as expected. :)
Simon
20160809
___
squid-users mailing list
http://ngtech.co.il/lmgtfy/> Eliezer Croitoru
Linux System Administrator
Mobile: +972-5-28704261
Email: elie...@ngtech.co.il
From: squid-users [mailto:squid-users-boun...@lists.squid-cache.org] On Behalf
Of Yuri Voinov
Sent: Sunday, August 7, 2016 9:23 PM
To: squid-users@lists.sq
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256
So,
the overall answer is "NO".
You can use Store-ID + collapsed forwarding functionality to achieve
something your want. May be together, may be separate. Hard luck :)
But this is your own problem. No one will solve the problem without the
id-users@lists.squid-cache.org
Subject: [squid-users] Range header is a hit ratio killer
Hi,list,
Code 206 is the most pain for our forwed proxy. Squid use
“range_offset_limit” to process byte-range request. when set it "none", it has
2 wellknown issue:
1. boost the traffic on the ser
On 6/08/2016 9:56 p.m., k simon wrote:
> Hi,list,
> Code 206 is the most pain for our forwed proxy. Squid use
> “range_offset_limit” to process byte-range request. when set it "none",
> it has 2 wellknown issue:
> 1. boost the traffic on the server side, we observed it's amplified
> 500%
Hi,list,
Code 206 is the most pain for our forwed proxy. Squid use
“range_offset_limit” to process byte-range request. when set it "none",
it has 2 wellknown issue:
1. boost the traffic on the server side, we observed it's amplified
500% compared to clients side on our box.
2. it's always
