Embedio: SSL and .Net Core/Standard

Created on 5 Sep 2017  Â·  2Comments  Â·  Source: unosquare/embedio

Hey,
I just ported all my apps to .Net Core and noticed that it's not possible to establish SSL connections using embedio. For me, a webserver without HTTPS is useless, encryption is absoluetly necessary and I really love embedio. I have a few questions here: Why is there no ssl? In .Net Standard 2.0, the HttpListener was added so you can remove your own implementation (and I imagine that the offical listener will support SSL). Why are there so many targets? Isn't the goal of .Net Standard to reduce the targets to only one platform that will work with every framework?

enhancement

Most helpful comment

Yes, we need to give it a try to net standard 2.0 new APIs properly.
Meanwhile any pull request is welcomed.

On Sep 5, 2017 9:38 AM, "Alkalinee" notifications@github.com wrote:

Hey,
I just ported all my apps to .Net Core and noticed that it's not possible
to establish SSL connections using embedio. For me, a webserver without
HTTPS is useless, encryption is absoluetly necessary and I really love
embedio. I have a few questions here: Why is there no ssl? In .Net Standard
2.0, the HttpListener was added
https://apisof.net/catalog/System.Net.HttpListener so you can remove
your own implementation (and I imagine that the offical listener will
support SSL). Why are there so many targets? Isn't the goal of .Net
Standard to reduce the targets to only one platform that will work with
every framework?

—
You are receiving this because you are subscribed to this thread.
Reply to this email directly, view it on GitHub
https://github.com/unosquare/embedio/issues/92, or mute the thread
https://github.com/notifications/unsubscribe-auth/ABsYsFVE2LvOOFyFuZEWigoWV2EAykdqks5sfVzugaJpZM4PNDF9
.

All 2 comments

Yes, we need to give it a try to net standard 2.0 new APIs properly.
Meanwhile any pull request is welcomed.

On Sep 5, 2017 9:38 AM, "Alkalinee" notifications@github.com wrote:

Hey,
I just ported all my apps to .Net Core and noticed that it's not possible
to establish SSL connections using embedio. For me, a webserver without
HTTPS is useless, encryption is absoluetly necessary and I really love
embedio. I have a few questions here: Why is there no ssl? In .Net Standard
2.0, the HttpListener was added
https://apisof.net/catalog/System.Net.HttpListener so you can remove
your own implementation (and I imagine that the offical listener will
support SSL). Why are there so many targets? Isn't the goal of .Net
Standard to reduce the targets to only one platform that will work with
every framework?

—
You are receiving this because you are subscribed to this thread.
Reply to this email directly, view it on GitHub
https://github.com/unosquare/embedio/issues/92, or mute the thread
https://github.com/notifications/unsubscribe-auth/ABsYsFVE2LvOOFyFuZEWigoWV2EAykdqks5sfVzugaJpZM4PNDF9
.

Closed because the pull request was merged. Thank you.

Was this page helpful?
0 / 5 - 0 ratings