Closed danopia closed 3 years ago
Hopefully they will decide to add the options parameter to the websocket like nodejs did, regardless of what the standards group says about it.
I just released v0.3.0 including this. Right now a recent Deno canary build is required. I believe Deno v1.14.0 will be the first proper release with it. In any case --unstable
is required.
I'm tracking Deno support for TLS auth in WebSocketStream
here: https://github.com/denoland/deno/issues/11846
This library still doesn't have merged WebSocket code so no harm yet.
mTLS support for
fetch()
just merged into deno's development branch from https://github.com/denoland/deno/pull/11721Once that merge commit https://github.com/denoland/deno/commit/dccf4cbe36d66140f9e35a6ee755c3c440d745f9 is in a tagged release we can introduce client certificate support as seen in #5.
Unfortunately, there's still not a way of passing these configurations to a WebSocket client, which continues to keep exec/attach/portforward just a tad out of reach.