Sorry for late response! I still see the WINDOW_UPDATE frames being sent from client even if the already streamed body is not consumed. After some point I see a RST_STREAM frame being sent from server after which the client stops.
I'd have thought the ideal solution for this would be for the receiver to not send WINDOW_UPDATE frames for the whole connection at all, but send it for particular streams, this way the sender could also stop generating more data if it can stop.
@akshaymankar I guess that the stream id of WINDOW_UPDATE is 0, which means the entire connection. If so, it's normal. Even if no body of streams are consumed, it should be sent.
@akshaymankar says:
Sorry for late response! I still see the WINDOW_UPDATE frames being sent from client even if the already streamed body is not consumed. After some point I see a RST_STREAM frame being sent from server after which the client stops. I'd have thought the ideal solution for this would be for the receiver to not send WINDOW_UPDATE frames for the whole connection at all, but send it for particular streams, this way the sender could also stop generating more data if it can stop.