Connection is kept alive when "Connection: close" is set in response headers

[tschuegge]

As stated in the official Microsoft documentation, the HttpSendHttpResponse function produces undefined results when combining the flags HTTP_SEND_RESPONSE_FLAG_DISCONNECT and HTTP_SEND_RESPONSE_FLAG_MORE_DATA in a single call (see https://msdn.microsoft.com/en-us/library/windows/desktop/aa364499(v=vs.85).aspx). This makes absolutely sense. However, in HttpSysServer (2.0.0 and earlier) when you set "Connection: close" in the response headers, the HttpSendHttpResponse function gets called (within Response.SendHeaders) with both of these flags set and afterwards when the body is going to be sent, there are no flags set. Instead the HTTP_SEND_RESPONSE_FLAG_DISCONNECT flag should have been set, so HTTP.SYS closes the connection. To reproduce the behavior mentioned, you can debug the test Microsoft.AspNetCore.Server.HttpSys.ResponseHeaderTests.ResponseHeaders_ServerSendsConnectionClose_Closed.

[Tratcher]

Interesting. Note the client should also react to the "Connection: close" header and terminate the connection after the request and response are complete. Both client and server would have to get this wrong for it to become a problem.

[tschuegge]

We have a piece of hardware, that unfortunately lets the connection open.

[aspnet-hello]

Thanks for your feedback. We appreciate your letting us know about the problem you've encountered or suggestion but we are not planning to take further action on this issue because our focus has been on issues with significantly higher customer interest and issues impacting a broad number of customers.