http: make maximum header size configurable per-stream or per-server#30570
http: make maximum header size configurable per-stream or per-server#30570addaleax wants to merge 4 commits intonodejs:masterfrom
Conversation
mcollina
left a comment
There was a problem hiding this comment.
LGTM
(this is also backportable to Node 12 with a bit of work).
@mcollina Are you having something in mind that’s only enabled when not using |
|
Exactly. |
sam-github
left a comment
There was a problem hiding this comment.
Looks good, modulo a doc nit. Might be interesting to test tiny values, like 12 (itended to be 12 K, but not actually). Maybe there should be a minimum of 500 or something? <-- just a suggestion/question, not even a nit.
|
@cjihrig @sam-github Nits should be addressed now
I’d figure somebody would notice pretty quickly if they set overly small values, but if a user is sure that that is what they want, I don’t think we need to stop them. |
I'd be curious if setting a max size of |
Make `maxHeaderSize` a.k.a. `--max-header-size` configurable now that the legacy parser is gone (which only supported a single global value). Refs: nodejs#30567
cc20b41 to
65d8813
Compare
|
Landed in 6bf5a1d |
Make `maxHeaderSize` a.k.a. `--max-header-size` configurable now that the legacy parser is gone (which only supported a single global value). Refs: #30567 PR-URL: #30570 Reviewed-By: Matteo Collina <matteo.collina@gmail.com> Reviewed-By: David Carlier <devnexen@gmail.com> Reviewed-By: Colin Ihrig <cjihrig@gmail.com> Reviewed-By: Sam Roberts <vieuxtech@gmail.com> Reviewed-By: James M Snell <jasnell@gmail.com> Reviewed-By: Denys Otrishko <shishugi@gmail.com>
Make `maxHeaderSize` a.k.a. `--max-header-size` configurable now that the legacy parser is gone (which only supported a single global value). Refs: #30567 PR-URL: #30570 Reviewed-By: Matteo Collina <matteo.collina@gmail.com> Reviewed-By: David Carlier <devnexen@gmail.com> Reviewed-By: Colin Ihrig <cjihrig@gmail.com> Reviewed-By: Sam Roberts <vieuxtech@gmail.com> Reviewed-By: James M Snell <jasnell@gmail.com> Reviewed-By: Denys Otrishko <shishugi@gmail.com>
Notable changes:
* http:
* Make maximum header size configurable per-stream or per-server
(Anna Henningsen) #30570
* http2:
* Make maximum tolerated rejected streams configurable (Denys
Otrishko) #30534
* Allow to configure maximum tolerated invalid frames (Denys
Otrishko) #30534
* wasi:
* Introduce initial WASI support (cjihrig)
#30258
PR-URL: #30774
Notable changes:
* fs:
* Reworked experimental recursive `rmdir()` (cjihrig)
#30644
* The `maxBusyTries` option is renamed to `maxRetries`, and its
default is set to 0. The `emfileWait` option has been removed,
and `EMFILE` errors use the same retry logic as other errors.
The `retryDelay` option is now supported. `ENFILE` errors are
now retried.
* http:
* Make maximum header size configurable per-stream or per-server
(Anna Henningsen) #30570
* http2:
* Make maximum tolerated rejected streams configurable (Denys
Otrishko) #30534
* Allow to configure maximum tolerated invalid frames (Denys
Otrishko) #30534
* wasi:
* Introduce initial WASI support (cjihrig)
#30258
PR-URL: #30774
Notable changes:
* fs:
* Reworked experimental recursive `rmdir()` (cjihrig)
#30644
* The `maxBusyTries` option is renamed to `maxRetries`, and its
default is set to 0. The `emfileWait` option has been removed,
and `EMFILE` errors use the same retry logic as other errors.
The `retryDelay` option is now supported. `ENFILE` errors are
now retried.
* http:
* Make maximum header size configurable per-stream or per-server
(Anna Henningsen) #30570
* http2:
* Make maximum tolerated rejected streams configurable (Denys
Otrishko) #30534
* Allow to configure maximum tolerated invalid frames (Denys
Otrishko) #30534
* wasi:
* Introduce initial WASI support (cjihrig)
#30258
PR-URL: #30774
Make
maxHeaderSizea.k.a.--max-header-sizeconfigurable now thatthe legacy parser is gone (which only supported a single global value).
Refs: #30567
Checklist
make -j4 test(UNIX), orvcbuild test(Windows) passes