You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
{{ message }}
Repository navigation
References to an "KeepAlive" flag in the http.Agent constructor, when it is actually "keepAlive" #10567
In the version 7.3.0 documentation, in the page on http, in the first few paragraphs of the http.Agent section it makes references to a KeepAlive flag in the http.Agent constructor which you can specify as true if you'd like to keep unused sockets pooled. Admittedly this caused me a decent amount of confusion because of the case mismatch :)
@papiro would you be interested in making a contribution to the documentation that fixes this? It would be greatly appreciated. The actual file that is used to generate that documentation can be found at https://github.com/nodejs/node/blob/master/doc/api/http.md. Feel free to ping me if you have any questions on making this change. Thanks for bringing it to our attention!
To be honest, I'm trying to grok what the documentation is actually trying to say and I just don't get it. This line specifically:
This means that Node.js's pool has the benefit of keep-alive when under load but still does not require developers to manually close the HTTP clients using KeepAlive.
Is it referring to HTTP clients with an agent that has the keepAlive flag set to true (Nodejs-specific)? I've googled "KeepAlive" and can't find any useful references to it (everything seems to be talking about the Connection header with a value of keep-alive.
Also, this line:
If you opt into using HTTP KeepAlive...
Is it referring again to the option to the http.Agent constructor? It's confusing because it refers to it as "HTTP" KeepAlive, which makes me think it's not Node-specific.
Any clarity on these would be greatly appreciated.
Activity
evanlucas commentedon Jan 2, 2017
@papiro would you be interested in making a contribution to the documentation that fixes this? It would be greatly appreciated. The actual file that is used to generate that documentation can be found at https://github.com/nodejs/node/blob/master/doc/api/http.md. Feel free to ping me if you have any questions on making this change. Thanks for bringing it to our attention!
gibfahn commentedon Jan 2, 2017
Adding the
good first contributionlabel, if anyone would like to PR this change (including @papiro !) then awesome.papiro commentedon Jan 2, 2017
I'll give it a shot :) Thanks!
papiro commentedon Jan 2, 2017
To be honest, I'm trying to grok what the documentation is actually trying to say and I just don't get it. This line specifically:
Is it referring to HTTP clients with an agent that has the
keepAliveflag set to true (Nodejs-specific)? I've googled "KeepAlive" and can't find any useful references to it (everything seems to be talking about theConnectionheader with a value ofkeep-alive.Also, this line:
Is it referring again to the option to the
http.Agentconstructor? It's confusing because it refers to it as "HTTP" KeepAlive, which makes me think it's not Node-specific.Any clarity on these would be greatly appreciated.
Changes to http.md
martinakraus commentedon Jan 9, 2017
Is this stilla point?
papiro commentedon Jan 9, 2017
sam-github commentedon Jan 9, 2017
Have you seen #10715, in process of addressing this?
papiro commentedon Jan 9, 2017
doc: update http.md for consistency and clarity
doc: update http.md for consistency and clarity
doc: update http.md for consistency and clarity
doc: update http.md for consistency and clarity
doc: update http.md for consistency and clarity
doc: update http.md for consistency and clarity