Hello.
We have an issue with squid when it tries to re-forward / retry failed
request even when forward_max_tries is set to 1. The situation when it
happens is when there's no response, parent just closes the connection.
Relevant parts of configuration so you understand the architecture:
cache_p
On 23/11/17 03:33, Vieri wrote:
From: Amos Jeffries
If we assume that each request opens a new connection and they are not
closed until TCP times out on the socket we do get numbers much more
like that 11K+ you are seeing.
That implies that ICAP transactions
From: Amos Jeffries
>
> If we assume that each request opens a new connection and they are not
> closed until TCP times out on the socket we do get numbers much more
> like that 11K+ you are seeing.
>
> That implies that ICAP transactions are probably not finis
On 22/11/17 23:48, Vieri wrote:
From: Amos Jeffries
If you place that after the default "deny CONNECT !SSL_ports", and
before your UA checks, AND if you are using ssl_bump on the allowed
tunnels then you can relatively safely use "allow CONNECT".
Just be caref
after investigating bug was exist but hidden all update ar correct
https://bugs.squid-cache.org/show_bug.cgi?id=3279
bug 3279 not yet fixed in v5
hint if they adapt the v3 patch will solve the problem :)
-
**
* Crash to the future
From: Amos Jeffries
>
> If you place that after the default "deny CONNECT !SSL_ports", and
> before your UA checks, AND if you are using ssl_bump on the allowed
> tunnels then you can relatively safely use "allow CONNECT".
>
> Just be careful that the CONNECT al
I was updating from squid-5.0.0-20171103-re3bf07f
to squid-5.0.0-20171117-rd816577 (and I was also testing
squid-5.0.0-20171117-r4d27d0a)
today and immediately found lots of "BUG 3279: HTTP reply without
Date:" messages in my log (cache_dir had been cleared upon start,
meaning I'
