On 5/14/19 8:07 AM, Alex Rousskov wrote:
> On 5/14/19 12:25 AM, johnr wrote:
>> how do the pconn_lifetime and client_idle_pconn_timeout interact?
> There should be virtually no interaction: The former limit is checked
> just when a connection becomes idle and Squid decides whether to pool
> the co
On 5/14/19 12:25 AM, johnr wrote:
> If in the context of this directive became idle means "done processing the
> previous request" then how is the pconn_lifetime directive different than
> the client_idle_pconn_timeout and server_idle_pconn_timeout (other than
> affecting both at the same time)?
On 14/05/19 6:25 pm, johnr wrote:
> Alex - thank you for the reply.
>
> If in the context of this directive became idle means "done processing the
> previous request" then how is the pconn_lifetime directive different than
> the client_idle_pconn_timeout and server_idle_pconn_timeout (other than
>
Alex - thank you for the reply.
If in the context of this directive became idle means "done processing the
previous request" then how is the pconn_lifetime directive different than
the client_idle_pconn_timeout and server_idle_pconn_timeout (other than
affecting both at the same time)? If my quest
On 5/10/19 12:18 PM, johnr wrote:
> The configuration directive pconn_lifetime
> (http://www.squid-cache.org/Doc/config/pconn_lifetime/), seems to give the
> squid admin control over whether squid closes idle connections or moves them
> into the 'idle connection pool'...
Correct. I would say "now
Hi,
The configuration directive pconn_lifetime
(http://www.squid-cache.org/Doc/config/pconn_lifetime/), seems to give the
squid admin control over whether squid closes idle connections or moves them
into the 'idle connection pool'... I am curious if in squid3, the connection
was automatically term
