On 2/04/20 5:42 pm, saiyan_gc wrote:
> Hi, thank you for reply me. Really appreciated!
>
> I modified the squid conf file to:
>
> http_port 2128 ssl-bump cert=/etc/squid/ssl_cert/example.com.cert \
> key=/etc/squid/ssl_cert/example.com.private \
> generate-host-certificates=on \
> dyn
On 4/3/20 16:34, Alex Rousskov wrote:
On 4/3/20 4:26 PM, zrm wrote:
In the first case we get TCP_MISS every time because it isn't caching
the data, in the second case it's only the first time and after that we
get TCP_REFRESH_UNMODIFIED. But how and why is this happening?
Those questions can o
On 4/3/20 4:26 PM, zrm wrote:
> In the first case we get TCP_MISS every time because it isn't caching
> the data, in the second case it's only the first time and after that we
> get TCP_REFRESH_UNMODIFIED. But how and why is this happening?
Those questions can often be answered by looking at HTTP
On Friday 03 April 2020 at 22:26:13, zrm wrote:
> Greetings! Today I bring you a Squid cache mystery.
> In the first case we get TCP_MISS every time because it isn't caching
> the data, in the second case it's only the first time and after that we
> get TCP_REFRESH_UNMODIFIED. But how and why is
Greetings! Today I bring you a Squid cache mystery.
I configured a simple transparent proxy to cache package downloads for
Debian, using Squid on Debian 10. When apt clients download packages
from deb.debian.org, Squid says TCP_MISS, downloads the package, and
then doesn't cache it. The myster
