Hello!
You can still use the connection pool to avoid short connection
overhead and SSL handshake overhead for requests to repeated targets.
The balancer_ssl_session_fetch_by_lua* and
balancer_ssl_session_store_by_lua* might be open sourced soon (we got
them in our commercial openresty+ builds atm).
Regards,
Yichun
On Tue, Apr 24, 2018 at 2:00 AM, Kone <dongb...@gmail.com> wrote:
> I use balancer_by_lua to set current peer in my own algorithm.
>
> And the upstream severs maybe changed at any time;
> I want to cache ssl session according to ip:port of upstream server, that
> ssl session can be reused and no full ssl handshake.
>
> How should I do?.