AspNetCoreModule doesn't work with WebListener/Http.Sys

[Tratcher]

From @Tratcher on October 5, 2015 16:39

Right now all the tests run with Kestrel. When I briefly tried WebListener some of the test cases failed. The logs showed WebListener starting fine, but it never served any requests and HttpPlatformHandler kept re-starting the back-end process until it gave up.

I've seen it work when published to full IIS, so it might be a test setup issue.

Copied from original issue: aspnet/IISIntegration#8

[Tratcher]

From @Schlurcher on October 24, 2015 23:7

Can confirm this is happening with 1.2 on full IIS 8 on Server 2012. Backend keeps restarting until IIS gives up and serves a 502 Bad Gateway.

[Tratcher]

From @muratg on January 21, 2016 22:24

Moving this to Backlog as we will be in RC2 ask mode very soon. If you feel strongly about this issue, please ping me.

[Tratcher]

Ok, now we understand why it doesn't work, and it won't any time soon.

HttpPlatformHandler starts the back-end process (dnx.exe). Then it opens a socket and tries to connect to the specified port. When that succeeds it cross checks the process that opened the port with it's list of child processes. If it finds a mismatch then it assumes it has a port conflict and it ends all of it's child processes and starts over. In the case of WebListener the port is actually opened by Http.Sys in the System process, so it never matches and always gets ended by platform handler.

HttpPlatformHandler will eventually need to support Http.Sys based back-end servers, but it's a non-trivial change for them so this isn't happening any time soon.

[muratg]

This is unlikely to be done. Closing.