Re: [squid-users] Call for adaptation after sni peeked

2019-10-28 Thread Jatin Bhasin
Hi Alex, If I use below squid configuration: ssl_bump peek step1 ssl_bump splice all I would see fake connect request in step 2 as well. I did not check squid version 4 but squid version 3 will send second fake connect in ecap adapter only if we splice step 2 which will be true in above

Re: [squid-users] Call for adaptation after sni peeked

2019-10-23 Thread Alex Rousskov
On 10/23/19 3:37 PM, Jatin Bhasin wrote: > This question is related to ssl decryption and ecap adaptation call.  > When the ssl connection starts then before it even extracts sni squid sends  > fakeConnect which comes to ecap as well. Yes, this happens during SslBump step1 as described at

[squid-users] Call for adaptation after sni peeked

2019-10-23 Thread Jatin Bhasin
Hi All, This question is related to ssl decryption and ecap adaptation call. When the ssl connection starts then before it even extracts sni squid sends fakeConnect which comes to ecap as well. I am using peek in step 1 and after fakeConnect squid extracts the sni, but at this point squid does

[squid-users] Call for adaptation after sni peeked

2019-10-22 Thread Jatin Bhasin
Hi All, This question is related to ssl decryption and ecap adaptation call. When the ssl connection starts then before it even extracts sni squid sends fakeConnect which comes to ecap as well. I am using peek in step 1 and after fakeConnect squid extracts the sni, but at this point squid does