-
Notifications
You must be signed in to change notification settings - Fork 30.1k
New issue
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
Doc: Agent ctor options are not fully documented, such as lookup
#24098
Comments
Agreed, if the options are passed to net.connect (EDIT: sorry, |
@sam-github I will take a look at doc style guide and see what I can do. |
@Trott I can take a spin at this if thats okay. I think we just need to look at the |
For new Agent() signature in http doc, list the supported options in socket.connect(). Refs: nodejs#24098 PR-URL: nodejs#24846 Reviewed-By: Vse Mozhet Byt <vsemozhetbyt@gmail.com> Reviewed-By: Luigi Pinca <luigipinca@gmail.com> Reviewed-By: Trivikram Kamat <trivikr.dev@gmail.com>
For new Agent() signature in http doc, list the supported options in socket.connect(). Refs: nodejs#24098 PR-URL: nodejs#24846 Reviewed-By: Vse Mozhet Byt <vsemozhetbyt@gmail.com> Reviewed-By: Luigi Pinca <luigipinca@gmail.com> Reviewed-By: Trivikram Kamat <trivikr.dev@gmail.com>
This appears to have been fixed but never closed. |
ref:
lookup
option fortls.connect()
#12839issue:
socket.connect
.new Agent([options])
.agent.createConnection(options[, callback])
does mention this but few users realize this allows them to make custom dns lookup via passing a custom Agent instance.The text was updated successfully, but these errors were encountered: