SSL/TLS support
Opened this issue · 5 comments
Hi thanks for sharing this library. Is there any plan to support SSL/TLS so we can do wss in a near future ?
Any update on having support for SSL?
We discussed this in a parallel issue, but basically it isn't on my list of
things to do. Reasons:
- Since the library builds on the socket API (not the stream API), it is
going to need a huge amount of work - The socket-based code will already require a huge amount of work to port
to "core", if that is a plan - We currently terminate SSL at the NLB (haproxy), which works really well
and requires no code changes - Putting 1 and 3 together doesn't make this appealing - lots of work for
little reason; I'm open to pull requests, but: this will not be trivial to
do
On Wed, 16 Mar 2016 07:33 integral-llc, notifications@github.com wrote:
Any update on having support for SSL?
—
You are receiving this because you are subscribed to this thread.
Reply to this email directly or view it on GitHub
#2 (comment)
Any update on this?.. Seems a bit unsecured without SSL no?
As stated above, SSL/TLS is done at the load balancer here (as we do at Stack Overflow). No status change.
Since we’re attempting to move off NetGain and onto the Microsoft WebSocket implementation (so we improve things for all, not just this lib), there will likely be little effort spent here going forward. That new server implantation goes into testing this week or next. We’re just seeing how it scales before deciding anything.