Pass keepAlive from custom agent #68
Open
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Currently, keepAlive flag is ignored in this issue. This causes to keepAlive to be false at agent level, which prevents connection re-use for all endpoints (see nodejs Agent). While some servers may not support keep-alive well, globally disabling the flag seems too broad of impact. It would be great if clients can decide on whether to use keepAlive (through request's keepAlive) instead.
This PR changes the logic of passing keepAlive flag. If client uses a custom http or https agent, then pass its keepAlive flag in creation of PacProxyAgent.