From 3f4b27d68102e0c809f417c1d87d23d21bd3ea84 Mon Sep 17 00:00:00 2001 From: Sebastiaan Deckers Date: Tue, 26 Feb 2019 10:03:48 +0800 Subject: [PATCH] doc: maxReservedRemoteStreams value constraints PR-URL: https://github.com/nodejs/node/pull/26309 Reviewed-By: James M Snell Reviewed-By: Rich Trott Reviewed-By: Matteo Collina Reviewed-By: Colin Ihrig Reviewed-By: Luigi Pinca --- doc/api/http2.md | 4 +++- 1 file changed, 3 insertions(+), 1 deletion(-) diff --git a/doc/api/http2.md b/doc/api/http2.md index da2201d55c99a5..c7a12b75b663f9 100644 --- a/doc/api/http2.md +++ b/doc/api/http2.md @@ -2141,7 +2141,9 @@ changes: * `maxReservedRemoteStreams` {number} Sets the maximum number of reserved push streams the client will accept at any given time. Once the current number of currently reserved push streams exceeds reaches this limit, new push streams - sent by the server will be automatically rejected. + sent by the server will be automatically rejected. The minimum allowed value + is 0. The maximum allowed value is 232-1. A negative value sets + this option to the maximum allowed value. **Default:** `200`. * `maxSendHeaderBlockLength` {number} Sets the maximum allowed size for a serialized, compressed block of headers. Attempts to send headers that exceed this limit will result in a `'frameError'` event being emitted