We read every piece of feedback, and take your input very seriously.
To see all available qualifiers, see our documentation.
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
v16.10.0
all
http
server.maxRequestPerSocket as defined in https://nodejs.org/api/http.html#http_server_maxrequestspersocket uses null for "no limit". However in most other places of http we use 0 to identify no limit.
server.maxRequestPerSocket
null
0
server.maxRequestPerSocket should use 0 as well as null (to not break anybody), or just consider it a bugfix and remove null support.
No response
The text was updated successfully, but these errors were encountered:
cc @ronag
Sorry, something went wrong.
This was added in #40082
wdyt @fatal10110, would you be able to send a fix?
Sure
Since #40192 landed, I guess we can close it?
yes, thx
Successfully merging a pull request may close this issue.
Version
v16.10.0
Platform
all
Subsystem
http
What steps will reproduce the bug?
server.maxRequestPerSocket
as defined in https://nodejs.org/api/http.html#http_server_maxrequestspersocket usesnull
for "no limit". However in most other places of http we use0
to identify no limit.server.maxRequestPerSocket
should use0
as well asnull
(to not break anybody), or just consider it a bugfix and removenull
support.How often does it reproduce? Is there a required condition?
No response
What is the expected behavior?
No response
What do you see instead?
No response
Additional information
No response
The text was updated successfully, but these errors were encountered: