[squid-users] Squid4 has extremely low hit ratio due to lacks of ignore-no-cache

[Yuri Voinov]

-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA256
 


27.10.15 1:37, Amos Jeffries пишет:
> On 27/10/2015 6:22 a.m., Yuri Voinov wrote:
>>
>> Ah, ok:
>>
>> We see in redbot.org this info in server response:
>>
>>  Cache-Control: no-cache
>>
>
> It also says "this content was negotiated but does not have an
> appropriate Vary header". Which is marked as a protocol error.
>
> And has a status code of 400 (unspecified error by the client).
>
> And has passed through three non-Squid proxies without being cached
> there either.
>
>
>>
>>
>> So, what? 3.5.10 permit ignore this. 4.0.x - deny.
>>
>
> Rather bold statement. Where is the cache.log line(s) saying that was
> the decision Squid made?
>
>
>> Squid decides?
>>
>
> No, the content owner does.
>
>
>> Maybe I'll decide what and how to cache in the my setup?
>
> You are just the caretaker of the information. It belongs to its
> creators. What you can do with their property depends on what they allow
> to be done with it.
Sure. But in real world we have much, very much unscrupulous webmasters,
such as distributors of advertising or unscrupulous CEOs who abuse their
rights.

This is why we fight againts them with our caches.
>
>
> HTTP is the legal rights granting methodology they chose to distribute
> with. The creators have granted you/anyone the license to cache
> (redistribute) that object. They did so via the badly named
> Cache-Control:no-cache header. Which comes with the license condition
> that the content be revalidated before redistribution.
>
> In other words, the content owner(s) retain the right to veto any
> recipient receiving their content or to provide alternative content at
> any time.
I understand, Amos.
>
>
> [[ Given that it seems to flip between an error page and an image
> depicting the internal design of a nuclear device - depending on where
> in the world one views it from. It would seem that the behaviour is
> probably intentional. ]]
>
>
> Within your new right to cache and redistribute you then get to choose
> how long for - on that particular item.
>
>
> BTW: Revalidate does not lead to MISS. It leads to a REFRESH_MODIFIED or
> REFRESH_UNMODIFIED.
Absolutely sure. But this not occurs.

This problem occurs at the same time on different squid's. 4.0.1 leads
TCP_MISS, but 3.5.10 on _the_same_ content gets TCP_HIT or TCP_MEM_HIT.
>
>
>
> Amos
> _______________________________________________
> squid-users mailing list
> squid-users at lists.squid-cache.org
> http://lists.squid-cache.org/listinfo/squid-users

-----BEGIN PGP SIGNATURE-----
Version: GnuPG v2
 
iQEcBAEBCAAGBQJWLpH6AAoJENNXIZxhPexGtMwIAIy4TJi14vSO9d0EKmzsLyHz
PMN850bJ+6+kinDy5bPg9Y+SByGgrUU81wpTEqDHPj0AwxW0lUoyurQQLPmY2CMB
1n93eWZrDsJRz2MJNXPNubKxA9qmxsTze2yZbjzPLjysVp8C2VWbRJWl5UePH7NZ
1xyY1qCWsrlGRjnQrQVptn1yeK2fFjy08fUzfO7uDG1+oRuhVCuJ1nTr6ESe60U3
BAacyaP4R8YngFMnz8+bKSV06MIZswjYe9+zYORxX2E/acXmL5b0hN3gQH211RNN
8cfEYO7nxA2MnjlvbKqHmJj9flly98yj7BNdRHvYYa6VDQ6lDYzwMuzbwDLB4DE=
=w0DL
-----END PGP SIGNATURE-----