On 7/16/19 1:51 PM, Arunabha Saha wrote:
> i did get it working with the latest 5.0.0 (unreleased) code
> in github.The configuration has to be "ssl-bump client-first .."
> for this to work. Does that sound right?
No, it does not, both because the deprecated "client-first" action
should not
On 7/10/19 7:44 PM, Arunabha Saha wrote:
>> The client will attempt to open a TLS/TCP connection to the origin
>> server. Your router (or some such) will redirect client TLS/TCP bytes to
>> your Squid's https_port. If configured correctly, Squid will accept that
>> TCP connection and wrap/forward
On 7/9/19 9:10 AM, Tardif, Christian wrote:
> I have a node on which there’s an application which isn’t proxy aware so
> basically, the only remaining option would be to use a transparent
> proxy. But my corporate proxy isn’t a transparent proxy. So I have to
> build this in two layers. My
Hi,
I'm trying to figure out how to make the following setup work:
I have a node on which there's an application which isn't proxy aware so
basically, the only remaining option would be to use a transparent proxy. But
my corporate proxy isn't a transparent proxy. So I have to build this in two
