Hi Kevin,
Yes, you are right, indeed we also suggest to disable sslv3, please refer to this blog post.
I confirm you that this library 6.1.4 build 1640.17, is fully compatible with Lighstreamer 5.1.x and contains the fix.
Printable View
Hi Kevin,
Yes, you are right, indeed we also suggest to disable sslv3, please refer to this blog post.
I confirm you that this library 6.1.4 build 1640.17, is fully compatible with Lighstreamer 5.1.x and contains the fix.
....andt he client will negotiate a connection regardless of the fact that SSLv3 is disabled?
Hi Kevin,
Yes, the client should be able to switch to one of the TLS protocols.
I think the answer to my last question is "no" they won't. Clients that insist on SSLv3 will not be able to establish a connection at all.
So, in summary, are we saying that the connection "flooding" was a client-side issue caused by the server being offline for a long period of time, and that this is fixed with the latest client ?
Hi Kevin,
The client and the server establish a connection if they can agree on a common protocol.
...but not browsers that don't support TLS (like IE 6 for example). They will just fail?
That aside, are we agreed on my last statement/question:
"So, in summary, are we saying that the connection "flooding" was a client-side issue caused by the server being offline for a long period of time, and that this is fixed with the latest client ?"
By the way, if I try to use the latest version of Lightstreamer.js with server 5.1.2 then I get constant alerts saying "License not valid for this client version".
is there something else I need to change? This server is running with a trial licence.
Obviously it all works well with server 6.0
Hi Kevin,
There are two different patched libraries:
- for Lightstreamer 5.1.2 which is this (6.1.4 build 1640.17);
- for Lightstreamer 6.0 which is this (6.2.6 build 1670).
If you use the first with the server 5.1.2 you should not get the error mentioned.
Yes, I can confirm that we expect that the new library should avoid the "flooding" of connections.
Excellent - and yes of course I was told earlier about the correct patch version to use with 5.1.2 and then just conveniently forgot about it. I think I am going senile :(