[squid-users] persistent connections not being utilized with Chrome

Brian J. Murrell brian at interlinx.bc.ca
Mon Jan 15 19:31:39 UTC 2018

On Mon, 2018-01-15 at 12:26 -0700, Alex Rousskov wrote:
> What about the transparent proxy part?

I already have that, but that is becoming more or less useless in the
everything-https world we are heading towards since you can't
transparently proxy https.  AFAIU.

> if Squid closed a CONNECT tunnel _first_, then there is a
> Squid
> bug: Under normal circumstances, Squid should only close a
> successfully
> established CONNECT tunnel if the client or origin server close their
> end first.

I'll see if I can double-check that next time I have to restart Chrome.

-------------- next part --------------
A non-text attachment was scrubbed...
Name: signature.asc
Type: application/pgp-signature
Size: 488 bytes
Desc: This is a digitally signed message part
URL: <http://lists.squid-cache.org/pipermail/squid-users/attachments/20180115/586e8af3/attachment.sig>

More information about the squid-users mailing list