-
Notifications
You must be signed in to change notification settings - Fork 142
SSL/TLS support #2
Comments
Any update on having support for SSL? |
We discussed this in a parallel issue, but basically it isn't on my list of
On Wed, 16 Mar 2016 07:33 integral-llc, [email protected] wrote:
|
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. |
Perhaps, but it is usually possible to use TLS terminators (or NLBs) as
intermediaries. Yes, it would be nice if it supported TLS too, but simply:
it hasn't been something I've needed (due to our network config).
I'm currently playing with "kestrel" options for future directions, which
would obviate the TLS requirement since kestrel has that built in. We have
it all coded up ready to test with Stack Overflow in prod - I just need to
flip a switch when I'm back at work (taking a week off).
…On Mon, 8 Oct 2018, 12:35 yhydra, ***@***.***> wrote:
Any update on this?.. Seems a bit useless without SSL no?
—
You are receiving this because you commented.
Reply to this email directly, view it on GitHub
<#2 (comment)>,
or mute the thread
<https://github.com/notifications/unsubscribe-auth/AABDsIXrJBSMKWq-BRL-ButHlnw-MA1Oks5uiziHgaJpZM4HRd6w>
.
|
Hi thanks for sharing this library. Is there any plan to support SSL/TLS so we can do wss in a near future ?
The text was updated successfully, but these errors were encountered: