W3C home > Mailing lists > Public > ietf-http-wg@w3.org > January to March 2023

Re: HTTP2 question about setting the initial connection window size

From: Meiling Chen <chenmeiling@chinamobile.com>
Date: Tue, 10 Jan 2023 17:16:55 +0800
To: "Kevin Grigorenko" <kevin.grigorenko@us.ibm.com>, ietf-http-wg <ietf-http-wg@w3.org>
Message-ID: <202301101716552668995@chinamobile.com>
The window size can only be changed by WINDOW_UPDATE frames, I am so sure because I have a draft for how to set the minimum window size.
Now the draft is expired, may it help you, https://www.ietf.org/archive/id/draft-chen-httpbis-window-size-03.html 

From: Kevin Grigorenko
Date: 2023-01-09 23:14
To: ietf-http-wg@w3.org
Subject: HTTP2 question about setting the initial connection window size
Hi, I'm looking into enhancing the Wireshark HTTP2 dissector to track the connection and session window sizes to investigate flow control bottlenecks. I have a question about RFC9113 ยง6.9.2:
"When an HTTP/2 connection is first established, new streams are created with an initial flow-control window size of 65,535 octets. The connection flow-control window is also 65,535 octets. Both endpoints can adjust the initial window size for new streams by including a value for SETTINGS_INITIAL_WINDOW_SIZE in the SETTINGS frame. The connection flow-control window can only be changed using WINDOW_UPDATE frames."
Does the last sentence mean that the connection flow-control window size can only be changed using a WINDOW_UPDATE frame _after_ the SETTINGS_INITIAL_WINDOW_SIZE?
In other words, does SETTINGS_INITIAL_WINDOW_SIZE also apply to the initial connection flow-control window size?
Kevin Grigorenko
IBM Automation Portfolio SWAT - App Platform, Software Engineer
Received on Tuesday, 10 January 2023 09:18:22 UTC

This archive was generated by hypermail 2.4.0 : Thursday, 2 February 2023 18:44:08 UTC