Server shutdown prevents large response from being sent to client during draining

Is there an existing issue for this?

• I have searched the existing issues

Describe the bug

Starting application host shutdown causes a large pending response to not be gracefully sent during shutdown.

1. Start HTTP/2 request. Request pauses for 5 seconds on server.
2. Start server application host shutdown during pause.
3. HTTP/2 request resumes, writes 2mb to response, and finishes.
4. Client only receives part of the response, e.g. 180kb. Hangs while waiting for the rest.
5. Server application eventually hits shutdown timeout and forcefully closes connection.
6. Client gets IOException.

Expected Behavior

I expect the client to get the entire response.

If the client app doesn’t start application host shutdown then the client correctly gets the entire response.

Steps To Reproduce

Ignore gRPC in the repo and project titles. gRPC user originally reported this but I reduce the repo to basic HTTP.

https://github.com/JamesNK/GrpcShutdownTest

1. Run server.
2. Run client.

(optional: comment out await StartShutdownCall(logger, client); in client to see the request succeed when no shutdown is triggered)

Exceptions (if any)

No response

.NET Version

6.0.300-preview.22154.4

Anything else?

No response

[JamesNK]

Confirmed this is a Kestrel bug.

[JamesNK]

The test app works from the browser, i.e. the browser successfully downloads the 2mb response after GOAWAY.

I think this is a HttpClient issue. Moving.

May have spoken too soon. The browser has the same problem but it downloads up to 6mb of the response. A response bigger than 6mb has the same issue.

I’ll keep investigating.