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

minimum value for SETTINGS_MAX_CONCURRENT_STREAMS

From: Daniel Sommermann <dcsommer@fb.com>
Date: Thu, 2 Jan 2014 16:11:40 -0800
Message-ID: <52C6003C.6040602@fb.com>
To: <ietf-http-wg@w3.org>
The HTTP/2.0 spec allows clients to advertise 
SETTINGS_MAX_CONCURRENT_STREAMS of 0 to indicate they do not support 
server push. However, it is not specified whether a server may advertise 
a value of zero for this setting. It seems odd for a server to advertise 
such a value, and it is not clear to me what a client implementation 
should do in such a case (close the connection and try again, wait for 
another SETTINGS frame, etc).

Should servers be limited to sending values greater than zero for 
SETTINGS_MAX_CONCURRENT_STREAMS? This question also applies to SPDY.
Received on Friday, 3 January 2014 00:12:09 UTC

This archive was generated by hypermail 2.4.0 : Friday, 17 January 2020 17:14:23 UTC