23 ms·
Isn't HttpListener still windows only ? I Remember the times we used it and it relied on http.sys on windows... Or did they port it during NET/NET Core. As Kes
by Gluber 2y ago
Isn't HttpListener still windows only ? I Remember the times we used it and it relied on http.sys on windows...
Or did they port it during NET/NET Core. As Kestrel has been the recommendation from NET Core 1.0 onwards.
- neonsunset 2y agoIt appears to use Socket (which is POSIX socket's send/recv and epoll/kqueue based) and SslStream. Can't say much about HttpListener itself, but the first two are used by Kestrel (and everything else). There is Http.sys integration for Windows though. https://github.com/dotnet/runtime/blob/ac663e44b907618c631edd614231b73677843952/src/libraries/System.Net.HttpListener/src/System/Net/Managed/HttpConnection.cs https://github.com/dotnet/runtime/blob/ac663e44b907618c631ed...
- tubs 2y agoHttplistener has two implementations. Managed (cross platform) and http.sys (windows only). It’s “ok”. You can’t do things like re use contexts but it’s perfectly fine for throwing small backends together when you don’t want to force users to install asp runtime. I did a minimal web api around it to make life easier going between it and kestrel. If kestrel was nugettable without the asp runtime it would be a dream but it requires a lot of that aspcore infra so it is what it is.