-
Notifications
You must be signed in to change notification settings - Fork 104
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
Support for per URL connection options #29
Comments
That definitely sounds like it could be done - make it so |
Thanks @jwalton -- sorry for the delay. I think I can look at doing this when I get a moment... |
🎉 This issue has been resolved in version 2.1.0 🎉 The release is available on: Your semantic-release bot 📦🚀 |
Some of the connectionOptions we use are per URL (for example "servername" which boils down to TLSSocket.servername and used as part of the TLS Server Name Indication). Could
connect
be altered to accept an array of {url:... , options:...} or something along those lines.The text was updated successfully, but these errors were encountered: