<html>
<head>
<meta content="text/html; charset=utf-8" http-equiv="Content-Type">
</head>
<body bgcolor="#FFFFFF" text="#000000">
<br>
-----BEGIN PGP SIGNED MESSAGE----- <br>
Hash: SHA256 <br>
<br>
So.<br>
<br>
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.<br>
<br>
any other compression - false. No. No way. Get out. and so on.<br>
<br>
identity - this is uncompressed type.<br>
<br>
That's all, folks.<br>
<br>
Finally. As Joe does, we can remain only gzip and identity in
Accept-Encoding and truncate all remaining.<br>
<br>
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.<br>
<br>
As I said, this does Squid it must be.<br>
<br>
06.06.2016 23:47, Heiler Bemerguy пишет:<br>
<span style="white-space: pre;">><br>
><br>
> These are the variations for the "accept-encoding" tag I
found when sniffing my client's connections. And they're of all
kind. Newer and older browsers, mobile phones, windows updates,
whatever..<br>
><br>
> It got a total of 11.437 requests from clients to squid.<br>
><br>
><br>
> *accept-encoding: gzip, deflate**<br>
> **Accept-Encoding: gzip, deflate**<br>
> **Accept-Encoding: gzip,deflate**<br>
> **Accept-Encoding: gzip, deflate, lzma, sdch**<br>
> **Accept-Encoding: gzip, deflate, sdch**<br>
> **Accept-Encoding: gzip,deflate,sdch**<br>
> **Accept-Encoding: gzip, xeflate, sdch**<br>
> **Accept-Encoding: identity**<br>
> **Accept-Encoding: identity;q=1, *;q=0*<br>
><br>
><br>
> Notice that some have spaces, some not, but I haven't seen
any "%20" representing a space. Is the "%20" put there by squid
itself?<br>
><br>
><br>
> -- <br>
> Best Regards,<br>
><br>
> Heiler Bemerguy<br>
> Network Manager - CINBESA<br>
> 55 91 98151-4894/3184-1751<br>
><br>
><br>
> Em 06/06/2016 12:08, Yuri Voinov escreveu:<br>
> Ok, why not to replace %20 to original space symbol?<br>
><br>
><br>
> 06.06.2016 20:27, joe пишет:<br>
> >>> not good just to strip %20 lol as i post it
remove also string was belong to<br>
> >>> the date<br>
> >>> we need to remove all of those string start with
,%20 as ,%20sdch so<br>
> >>> its not eassy detection<br>
> >>><br>
> >>> it kill
if-modified-since="Mon,%2006%20Jun%202016%2014%3A31%3A32%20GMT",<br>
> >>><br>
> >>> if you notice this string in vary has %20 so
just wide search and<br>
> clear it<br>
> >>> remove those :(<br>
> >>><br>
> >>><br>
> >>><br>
> >>> --<br>
> >>> View this message in context:<br>
>
<a class="moz-txt-link-freetext" href="http://squid-web-proxy-cache.1019090.n4.nabble.com/Vary-object-loop-returns-tp4677716p4677856.html">http://squid-web-proxy-cache.1019090.n4.nabble.com/Vary-object-loop-returns-tp4677716p4677856.html</a><br>
> >>> Sent from the Squid - Users mailing list archive
at Nabble.com.<br>
> >>> _______________________________________________<br>
> >>> squid-users mailing list<br>
> >>> <a class="moz-txt-link-abbreviated" href="mailto:squid-users@lists.squid-cache.org">squid-users@lists.squid-cache.org</a><br>
> >>>
<a class="moz-txt-link-freetext" href="http://lists.squid-cache.org/listinfo/squid-users">http://lists.squid-cache.org/listinfo/squid-users</a><br>
>><br>
>><br>
>><br>
>> _______________________________________________<br>
>> squid-users mailing list<br>
>> <a class="moz-txt-link-abbreviated" href="mailto:squid-users@lists.squid-cache.org">squid-users@lists.squid-cache.org</a><br>
>> <a class="moz-txt-link-freetext" href="http://lists.squid-cache.org/listinfo/squid-users">http://lists.squid-cache.org/listinfo/squid-users</a><br>
><br>
><br>
><br>
> _______________________________________________<br>
> squid-users mailing list<br>
> <a class="moz-txt-link-abbreviated" href="mailto:squid-users@lists.squid-cache.org">squid-users@lists.squid-cache.org</a><br>
> <a class="moz-txt-link-freetext" href="http://lists.squid-cache.org/listinfo/squid-users">http://lists.squid-cache.org/listinfo/squid-users</a></span><br>
<br>
-----BEGIN PGP SIGNATURE-----
<br>
Version: GnuPG v2
<br>
<br>
iQEcBAEBCAAGBQJXVbkTAAoJENNXIZxhPexGLN0H/A0lUTMgvb3xkJTYWu3kbgJS
<br>
wob2/TriqzMS01o7EUviaqUrZXmaexZJ3Qh8k9I0MQ/enAVUKDNtsAq0S+616XlK
<br>
szc3HEZjOzWV7S5y4hBGasMopOnml2PMfPIQyHC1KeoEuHoprNCFNPjhOtU0/YwM
<br>
Vhe3sPljNfEGjys/CCt38EqaDL3jGTKZLxjwwtn+iRlQMR8Mmo/c3RQJ6gAKFlKn
<br>
BRVTRtj1F3R5tNauuVl4d4xVKd+gQuAmLLCQAwhJ8FzhSPv0qkfBfsZpeZe9BmHy
<br>
jBmUO4ZnNtkBgaNmEdZgqxifitfH/eBaHfV0Q6n+ofyGEYW6S6jG2n2ZFocwP0s=
<br>
=l49S
<br>
-----END PGP SIGNATURE-----
<br>
<br>
</body>
</html>