Alex,
first of all, thank you for your clarification.
>Squid does not know that the response headers and body have not changed.
>Squid could, in theory, trust the URL+Vary+ETag+etc. combination as a
>precise response identity, but it is a bit risky to do that by default
>because ET
On 6/28/20 2:41 PM, Tabacchiera, Stefano wrote:
>>Squid does not know that the response headers and body have not changed.
>>Squid could, in theory, trust the URL+Vary+ETag+etc. combination as a
>>precise response identity, but it is a bit risky to do that by default
>>because ETag
On 6/28/20 10:56 AM, Patrick Chemla wrote:
> I got last week a bad "issue" where a squid Version 4.0.23
Please upgrade to the latest Squid v4 (or v5). While the problem you are
writing about is unlikely to disappear, there are other problems in your
Squid version. My answer is based on Squid v5,
Hi,
Thank you all for the great work on Squid.
I got last week a bad "issue" where a squid Version 4.0.23 set to
send requests to 4 VMs didn't detect a dead peer.
On each VM are running Apache as the frontal, and php-fpm as php
script
Hey, I am unsure on how to answer your questions.Squid-Cache is a proxy server “source code”.It comes bundled with sources for a set of utilities (helpers) that extends Squid ACLs capabilities by a very simple STDIN\STDOUT api. I know that SquidGuard is the most “famous” external ACL helper for all
