SSL considerations - self-signed certificate

[giuseppe.corti]

I am slightly puzzled by this scenario. It seems that your chrome does not care about the invalid certificate and still allows the connection to start.
I confirm you that the SSL ceritificate stuff are handled by the browser outside the Lighstreamer client library.

Have you the opportunity to raise to DEBUG level the logger

<logger name="LightstreamerLogger.connections.ssl" level="DEBUG"/>

in this way we can investigate the dynamics of the SSL handshake and maybe figure out where all that time is lost.