Hi Susan, James,
Just reproduced same behavior on latest master.
1) TS_SSL_SNI_HOOK gets called:
#0 CB_servername (contp=0x2877b90, event=18, edata=0x2b9bfc0195a0) at
../ts-tls.cc:27
#1 0x00519503 in INKContInternal::handle_event
(this=0x2877b90, event=18, edata=0x2b9bfc0195a0) at InkA
> On Jan 5, 2015, at 8:40 AM, Lev Stipakov wrote:
>
> Hello,
>
>
> In my plugin I play with SNI callback which was introduced in TS-3006.
> I have patched OpenSSL, made iptables route packets to ATS and was
> able to start a blind tunnel from TS_SSL_SNI_HOOK callback. So far so
> good.
>
> Ho
Hi Lev,
I didn't see that kind of behavior when working with the ssl_cert_loader
(one of the experimental plugins). It also spawns a thread in the case
where it needs to load a certificate from a file. Are you perhaps
calling TSVConnReenable() in the case that you want to delay? That
would
Hello,
In my plugin I play with SNI callback which was introduced in TS-3006.
I have patched OpenSSL, made iptables route packets to ATS and was
able to start a blind tunnel from TS_SSL_SNI_HOOK callback. So far so
good.
However I'd like to make decision on blind tunnel / proxying / closing
conn
