Skip to content

Http listener on non iIs #785

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

Closed
gregoryyoung opened this issue Jul 31, 2015 · 8 comments
Closed

Http listener on non iIs #785

gregoryyoung opened this issue Jul 31, 2015 · 8 comments

Comments

@gregoryyoung
Copy link

this can be seen in mono today.

The http listener interface doesn't make much sense without iis. Currently the way you bind to a port is to pass a http prefix eg http://*:4444 this is used for two purposes. The first is to setup accept parameters it will bad host not matching requests this is also used to determine the port to bind to though!

Where this causes problems is in places like aws where I need to accept an elastic ip say 24.112.72.53 but bind locally on 10.114.56.74. As of now the httplistener code in mono does the only "reasonable" thing here and binds all.

There are quite a few other little things like this around this api. What are the plans if any for supporting http listener cross platform and is this a time this interface could be fixed? I would like to fix monos but prefer to keep api compatibility as opposed to mono specific ways of doing things.

Greg

@benaadams
Copy link
Member

The http listener interface doesn't make much sense without iis.

You mean without http.sys port and path sharing on windows? Don't need iis for httplistener.

@gregoryyoung
Copy link
Author

sure. without a separated ability to manage things it makes no sense. id be interested in seeing what unusual behaviors come out in windows out of this as well btw.

@Eilon
Copy link
Member

Eilon commented Jul 31, 2015

@Tratcher any thoughts on this?

@Tratcher
Copy link
Member

Yes, there were issues trying to adapt Windows concepts for HttpListener over to Mono. HttpListener is being replaced by WebListener on Windows or Kestrel on cross-plat. Here's how we expect the bindings to work on Kestrel (soon) aspnet/KestrelHttpServer#98 (comment)

IIS, HttpListener, and WebListener all build on the native Windows Http.Sys library and it controls the prefix logic.

@gregoryyoung
Copy link
Author

So leave everyone behind and have a new Api?

On Friday, July 31, 2015, Chris R [email protected] wrote:

Yes, there were issues trying to adapt Windows concepts for HttpListener
over to Mono. HttpListener is being replaced by WebListener on Windows or
Kestrel on cross-plat. Here's how we expect the bindings to work on Kestrel
(soon) aspnet/KestrelHttpServer#98 (comment)
aspnet/KestrelHttpServer#98 (comment)

IIS, HttpListener, and WebListener all build on the native Windows
Http.Sys library and it controls the prefix logic.


Reply to this email directly or view it on GitHub
#785 (comment).

Studying for the Turing test

@aspnet-hello
Copy link

This issue is being closed because it has not been updated in 3 months.

We apologize if this causes any inconvenience. We ask that if you are still encountering this issue, please log a new issue with updated information and we will investigate.

@davidalpert
Copy link

davidalpert commented Dec 31, 2017 via email

@davidalpert
Copy link

davidalpert commented Dec 31, 2017 via email

ryanbrandenburg pushed a commit that referenced this issue Nov 16, 2018
- Addresses "SqlClient fails with netcoreapp2.0 on Win7/Server2008" (https://github.com/dotnet/corefx/issues/18406)
- Revert if and when $(CoreFxVersion) is upgraded to 4.4.0-*
@ghost ghost locked as resolved and limited conversation to collaborators Dec 4, 2019
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
None yet
Projects
None yet
Development

No branches or pull requests

6 participants