HTTP2 Window Full

Would it be possible for wireshark to perform analysis on http2 connection and stream window size and generate "HTTP2 Window Full" warnings the way it does for TCP Window Full?

I'm interacting with an HTTP server that gets impatient after a few TCP ZeroWindowProbes, and closes the connection. I suspect it's doing the same with HTTP2 streams that aren't being read on the client side, but it sends GOAWAY without an error code. Being able to keep track of the connection and stream window sizes in wireshark would make it easier to identify this problem.

I think I understand the series of events.

The TCP client's window is zero.
The TCP server sends TCP window probes because it is waiting for the client to update the window size.
The server sends HTTP GOAWAY to terminate the HTTP session. Afterwards, it either sends a TCP FIN or RESET

I would start Wireshark and then have the client try to duplicate the issue. When the client experiences the issue, immediately stop Wireshark and save the data to a file. If the file is large, you may have to filter for HTTP GOAWAY and then export that stream to another file. If more data is needed, the original file is available.

BigFatCat

answered 2021-08-14 09:36:00 +0000

edit flag offensive 0 remove flag delete link

Comments

I'd like to have Wireshark highlight the case when the client's TCP window is not zero, but one or more of the HTTP2 stream windows are zero, i.e. the client is accepting data one one stream, but not another.

xn (2021-08-16 13:52:43 +0000) edit

add a comment see more comments

Your Answer

Please start posting anonymously - your entry will be published after you log in or create a new account. This space is reserved only for answers. If you would like to engage in a discussion, please instead post a comment under the question or an answer that you would like to discuss.

HTTP2 Window Full edit

Comments

1 Answer

Comments