Skip to content

References to an "KeepAlive" flag in the http.Agent constructor, when it is actually "keepAlive" #10567

Closed

Description

@papiro
  • Version:
  • Platform:
  • Subsystem:

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 :)

Activity

  1. added
    docIssues and PRs related to Node.js documentation.
    on Jan 1, 2017
  2. added
    httpIssues and PRs related to the http subsystem.
    on Jan 1, 2017
  3. evanlucas commented on Jan 2, 2017

    @evanlucas
    Contributor

    @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!

  4. added
    good first issueIssues that are suitable for first-time contributors.
    on Jan 2, 2017
  5. gibfahn commented on Jan 2, 2017

    @gibfahn
    Member

    Adding the good first contribution label, if anyone would like to PR this change (including @papiro !) then awesome.

  6. papiro commented on Jan 2, 2017

    @papiro
    Author

    I'll give it a shot :) Thanks!

  7. papiro commented on Jan 2, 2017

    @papiro
    Author

    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.

  8. added a commit that references this issue on Jan 4, 2017
  9. martinakraus commented on Jan 9, 2017

    @martinakraus

    Is this stilla point?

  10. papiro commented on Jan 9, 2017

    @papiro
    Author
  11. sam-github commented on Jan 9, 2017

    @sam-github
    Contributor

    Have you seen #10715, in process of addressing this?

  12. papiro commented on Jan 9, 2017

    @papiro
    Author
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Metadata

Metadata

Assignees

No one assigned

    Labels

    docIssues and PRs related to Node.js documentation.good first issueIssues that are suitable for first-time contributors.httpIssues and PRs related to the http subsystem.

    Type

    No type

    Projects

    No projects

      Milestone

      No milestone

      Relationships

      None yet

      Development

      No branches or pull requests

      Issue actions