[squid-users] Vary object loop returns
yvoinov at gmail.com
Tue Jun 7 08:48:32 UTC 2016
-----BEGIN PGP SIGNED MESSAGE-----
07.06.2016 4:57, Amos Jeffries пишет:
> On 7/06/2016 5:55 a.m., Yuri Voinov wrote:
>> Squid DOES NOT and DON'T BE support gzip. The only way to do it - use
>> ecap + desupported ecap gzip adapter. Let's accept this. We can support
>> gzip. With restrictions. Ok.
>> any other compression - false. No. No way. Get out. and so on.
>> identity - this is uncompressed type.
>> That's all, folks.
>> Finally. As Joe does, we can remain only gzip and identity in
>> Accept-Encoding and truncate all remaining.
> Locking the entire Internet to using your personal choice of gzip
> compression or none.
> gzip is the slowest and more resource hungry type of compression there
> is. deflate is actually faster for clients and just as widely supported.
Unfortunately, Amos, no one has written any other compression algorithms
support module. We have to eat what they give.
>> Without any problem. Moreover, this type of can be push to all brunches
>> of squid without any problem, because of this dramatically increases
>> byte HIT.
> Responding with a single object to all requests makes your HIT ratio
> 100% guaranteed. The clients wont like you though if all they ever see
> is the same cat picture.
> It sounds ridiculous when put that way, but that is what these patches
> are doing for a unknown number of those "gained" HITs. See my previous
> post about how none of these patches are changing the request the server
But no one asked the question - why Squid in production installations
has such a low hit ratio that raises the question of expediency of
application caching proxy. We do believe that this is a caching proxy?
> You are once again sweeping asside the critical requirement of content
> integrity to achieve high HIT ratio. Which is not something that I can
> accept into Squid as a default action.
I continue to believe that 20% is unacceptably low cache hit ratio,
given the very aggressive settings and the active use of Store ID. Which
brings us back to the idea of the feasibility of using the SQUID as a whole.
> squid-users mailing list
> squid-users at lists.squid-cache.org
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v2
-----END PGP SIGNATURE-----
-------------- next part --------------
A non-text attachment was scrubbed...
Size: 2437 bytes
Desc: not available
More information about the squid-users