WebSocket ReceiveAsync hangs forever on server

[osexpert]

NetCore\AspNetCore 3.1.8
Kestrel, running in debug
Simple example, middleware doing
var ws = await context.WebSockets.AcceptWebSocketAsync();
await ws.ReceiveAsync(buff, CancellationToken.None);

Client connect:
var ws = new ClientWebSocket();
await ws.ConnectAsync(new Uri("ws://host/ws/test"), CancellationToken.None);
await ws.ReceiveAsync(buff, CancellationToken.None);

Pull out network cable. After a while, client throws WebSocketException (as expected).
But server is "blocking" on ReceiveAsync forever. Seems there is something wrong with the pingpong logic? Pingpong is keeping the client alive but server does not care when client stops responding to pingpong and will Recieve forever in vain. I don't see how WebSocket can be usable in real life with this behaviour?

[ghost]

Tagging subscribers to this area: @dotnet/ncl
See info in area-owners.md if you want to be subscribed.

[osexpert]

After being assigned area-websockets I see 3 other cases complaining about the same and being closed.
In any case, this is higly inconsistent that the client actually closes while the server does not. I can accept this behavior if you change the client to also hang forever:-D

[BrennanConroy]

Triage notes: The WebSocket on the server side will send Pings every 2 minutes by default. The problem is that the RFC doesn't say that you should kill the connection if a Pong isn't received in response to a Ping so the WebSocket is just going to stay open. If you wait for the TCP timeout (which could be 15+ minutes on Windows) then you will see that the WebSocket is closed at that point.

We are tracking this sort of issue in #24614