New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Implement https connection support for the managed HttpListener #14691

Open
Priya91 opened this Issue Dec 22, 2016 · 6 comments

Comments

Projects
None yet
7 participants
@Priya91
Member

Priya91 commented Dec 22, 2016

This requires a mechanism to get the ssl certificate info to use on the port of httplistener connection.

Possible solutions:

  • Expose an API that gets the cert filename on Unix and throws PNSE on Windows.
  • Create a tool to maintain/create/delete httplistener certs, mimicking windows httpcfg.

Current behavior:

  • Connections drop on https.

@karelz karelz changed the title from Implement https connection support on httplistener on Unix to Implement https connection support on HttpListener on Unix Dec 23, 2016

@karelz karelz added the os-linux label Dec 23, 2016

@Priya91 Priya91 removed the netstandard2.0 label Jan 3, 2017

@Priya91 Priya91 added this to the Future milestone Jan 3, 2017

@CIPop CIPop changed the title from Implement https connection support on HttpListener on Unix to Implement https connection support for the managed HttpListener Jul 6, 2017

@CIPop CIPop added the os-windows-uwp label Jul 6, 2017

@CIPop CIPop modified the milestones: 2.1.0, Future Jul 6, 2017

@CIPop

This comment has been minimized.

Member

CIPop commented Jul 6, 2017

/cc @davidsh @DavidGoll
@Priya91 on Mono, HttpListener is searching for certs in a hardcoded path: https://github.com/mono/mono/blob/3f779475e3fc982e312212d5dbbd86515eddfc0c/mcs/class/System/System.Net/HttpListener.Mono.cs#L64
(also see this Stack Overflow discussion).

I couldn't find any documentation on how this could be achieved on Xamarin.

@Priya91

This comment has been minimized.

Member

Priya91 commented Jul 7, 2017

@CIPop Yes, that's the second bullet in the description. We could re-use the dotnet crypto cert-store for this purpose, similar to mono, instead the hardcoded path here will be some custom dotnet path.

@DavidGoll

This comment has been minimized.

Member

DavidGoll commented Jul 11, 2017

@davidsh Document this as a compat issue for UWP6.0. This will require significant design for a cross-plat implementation.

@davidsh

This comment has been minimized.

Member

davidsh commented Jul 12, 2017

Added documentation to https://github.com/dotnet/corefx/wiki/ApiCompat

@davidsh davidsh removed the documentation label Jul 12, 2017

@davidsh davidsh removed their assignment Jul 12, 2017

@dabretin

This comment has been minimized.

dabretin commented Oct 16, 2017

Any news on this ?

@m5x

This comment has been minimized.

m5x commented May 31, 2018

It would be great if it was possible to supply the certificate as a stream. It would remove additional steps that are required on each OS to install the certficate and at the same time it would allow developers to control themselves how and where is the certificate stored.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment