l
-Original Message-
From: Amos Jeffries [mailto:squ...@treenet.co.nz]
Sent: Monday, January 21, 2019 10:10
To: Eliezer Croitoru
Cc: squid-users@lists.squid-cache.org
Subject: Re: [squid-users] https debug
On 21/01/19 11:15 am, Eliezer Croitoru wrote:
> You probably meant 4.5...
>
On 21/01/19 11:15 am, Eliezer Croitoru wrote:
> You probably meant 4.5...
> http://www1.ngtech.co.il/repo/centos/7/x86_64/squid-4.5-1.el7.x86_64.rpm
>
Time travel ...
> -Original Message-
> From: Amos Jeffries
> Sent: Wednesday, January 2, 2019 12:01
... back when 4.4 was all you had.
-cache.org] On Behalf
Of Amos Jeffries
Sent: Wednesday, January 2, 2019 12:01
To: squid-users@lists.squid-cache.org
Subject: Re: [squid-users] https debug
On 2/01/19 10:30 pm, Sampei wrote:
> About way to use https protocol I think I use connect tunnel, here
When a CONNECT tunnel is being used
On 2/01/19 10:30 pm, Sampei wrote:
> About way to use https protocol I think I use connect tunnel, here
When a CONNECT tunnel is being used and not SSL-Bump'ed then all TLS
related issues are problems with one of the endpoint software. Not
related to the proxy at all. Squid is just blindly relayin
On 31/12/18 10:48 pm, Sampei wrote:
> I'm using application which uses https protocol by Squid 3.5.20 and It
> often occurs application timeout and other problems to use this software.
Please explain with more details about what this setup actually is.
There are many very different ways to "uses
I'm using application which uses https protocol by Squid 3.5.20 and
It often occurs application timeout and other problems to use this
software.
I tried to use application without Squid, bypassing it, and
It works fine.
How can I find out where Squid could create problems to
this application?
