Commit 3f4b27d
doc: maxReservedRemoteStreams value constraints
PR-URL: #26309
Reviewed-By: James M Snell <jasnell@gmail.com>
Reviewed-By: Rich Trott <rtrott@gmail.com>
Reviewed-By: Matteo Collina <matteo.collina@gmail.com>
Reviewed-By: Colin Ihrig <cjihrig@gmail.com>
Reviewed-By: Luigi Pinca <luigipinca@gmail.com>1 parent bc5771e commit 3f4b27d
1 file changed
Lines changed: 3 additions & 1 deletion
| Original file line number | Diff line number | Diff line change | |
|---|---|---|---|
@@ -2141,7 +2141,9 @@ changes: | |||
| 2141 | 2141 | * `maxReservedRemoteStreams` {number} Sets the maximum number of reserved push | |
| 2142 | 2142 | streams the client will accept at any given time. Once the current number of | |
| 2143 | 2143 | currently reserved push streams exceeds reaches this limit, new push streams | |
| 2144 | - sent by the server will be automatically rejected. | ||
| 2144 | + sent by the server will be automatically rejected. The minimum allowed value | ||
| 2145 | + is 0. The maximum allowed value is 2<sup>32</sup>-1. A negative value sets | ||
| 2146 | + this option to the maximum allowed value. **Default:** `200`. | ||
| 2145 | 2147 | * `maxSendHeaderBlockLength` {number} Sets the maximum allowed size for a | |
| 2146 | 2148 | serialized, compressed block of headers. Attempts to send headers that | |
| 2147 | 2149 | exceed this limit will result in a `'frameError'` event being emitted | |
0 commit comments