ReadMeFeed / Community knowledge
Real questions. Useful conversations. Find the people who know your stack.
http.Agent maintains a per-origin pool of keep-alive sockets. maxSockets caps concurrent sockets per origin and maxFreeSockets caps idle sockets retained, which together bound connection reuse under load. The global agent is shared across modules by default, so concurrent requests from different callers compete for the same limits. Keep-alive sockets remain
Integration boundary Axios delegates all Node.js HTTP(S) connection handling to the built-in http.Agent (or https.Agent ). The agent’s maxSockets and keepAlive settings control how many concurrent connections are opened to a single host and whether sockets are reused across requests. Goal and constraints Developers running many simultaneous axios requests to
Moving an HTTP client that relies on Node.js http.Agent keep-alive pooling across a Node.js major version boundary raises a configuration decision about socket limits. The affected feature is keep-alive socket reuse governed by maxSockets per origin and, in newer releases, maxTotalSockets for the default agent. agent.destroy() does not guarantee immediate cl
nodejs
axios