-
Notifications
You must be signed in to change notification settings - Fork 97
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
feat: support for specifying additional TLS certs #308
Conversation
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
This needs a unit test in order to be merged. All the infraestructure to achieve this is there already, normal tests are even called non TLS at this point. The invalid tls test and related database should work just fine for this purpose
This commit adds support for specifying additional certificates (like required for servers with self signed certs), to the client. The certificate will be passed to `Deno.startTls` appropriately.
44513dd
to
0c0038a
Compare
0c0038a
to
d04dcb8
Compare
@lucacasonato Please rebase over latest main, it contains an important fix for TLS connection and the Deno version bump |
This commit adds support for specifying additional certificates (like required for servers with self signed certs), to the client. The certificate will be passed to `Deno.startTls` appropriately.
4c09418
to
51f7672
Compare
This reverts commit 1ae3a82.
…nto custom_tls_certs
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
LGTM Luca
So good to know this is finally supported and testable
Thanks for seeing this through @Soremwar :-) |
This commit adds support for specifying additional certificates
(like required for servers with self signed certs), to the client.
The certificate will be passed to
Deno.startTls
appropriately.Closes #284